Revenue Per Available Parking Space, Explained

Revenue per available space (RevPAS) is a facility’s parking revenue for a stated period divided by its available capacity over that same period. It is analogous to the hotel industry’s revenue per available room. RevPAS normalizes revenue for facility size and helps you investigate changes in pricing and use; it does not by itself prove why revenue changed. It needs revenue records; occupancy counts alone can’t produce it.

What RevPAS Measures

A parking space works like a hotel room or an airline seat: if it sits empty during a period, the revenue it could have earned in that period is gone. RevPAS measures how well each space earns, whatever the facility’s size.

Facility A earns $100,000 a month from 1,000 spaces: $100 per space. Facility B earns $50,000 from 250 spaces: $200 per space. A brings in twice the total revenue, but B earns twice as much from each space. If you’re deciding where to invest in better equipment or where to test a new rate, that difference matters more than the totals.

Two things must always accompany a RevPAS figure:

• The period. Per day and per month give very different numbers, and neither is comparable to the other.
• The capacity over that period. Use spaces that were actually available, not the painted total. If a level closes for half the month, count its spaces for the half when they were open. A single month-end count would misstate the denominator.

Without both, two RevPAS figures can’t be compared.

How to Calculate RevPAS

Before the step-by-step math, here is the whole idea in one picture. RevPAS breaks into two parts: how much of your capacity gets used, and how much each hour of use earns.

Occupancy rateoccupied space-hours ÷ available space-hours

×

Revenue per occupied space-hourrevenue ÷ occupied space-hours

=

RevPAS per space-hourrevenue ÷ available space-hours

× hours open in the period → RevPAS per day or per month

The basic calculation

Take a 300-space lot open 10 hours a day, every day (300 operating hours in a 30-day month). That schedule matters later: many municipal and commercial garages run 24 hours, so check your own facility’s hours before reusing these numbers. In the month, the lot takes in $45,000 from all sources: hourly parkers, monthly permits, and validations.

• Monthly RevPAS = $45,000 ÷ 300 = $150 per space per month
• Daily RevPAS = $150 ÷ 30 = $5.00 per space per day

That’s all a facility with unchanged capacity and operating hours needs for monthly reporting. When capacity changes, calculate available space-hours instead: sum the spaces open in each hour of the period.

Multiplying revenue per available space-hour by the scheduled open hours gives the same per-space figure as dividing by effective available spaces. For example, if 100 of 300 spaces close for half of a 300-hour month, available space-hours are (300 × 150) + (200 × 150) = 75,000, or 250 effective spaces. Revenue of $45,000 would be $0.60 per available space-hour, or $180 per effective space for the month. Report the closure and denominator alongside the figure.

Splitting RevPAS into revenue per occupied hour and utilization

When RevPAS changes, the next question is what moved: use of available capacity, revenue earned per occupied hour, or both. The trick is to measure both in the same unit: the space-hour, meaning one space for one hour. The second component reflects rates, permit mix, discounts, and payment capture together; it is not a pure price measure.

Return to the constant-capacity example: 300 spaces, open 10 hours a day throughout the month. In general form, the split is:

Plugging in the numbers:

1. Available space-hours = spaces × hours open. 300 × 10 hours × 30 days = 90,000.
2. Occupied space-hours = the total hours cars were parked, from counts or entry and exit records. Say 45,000.
3. Occupancy rate = occupied ÷ available space-hours = 45,000 ÷ 90,000 = 50%.
4. Revenue per occupied space-hour = revenue ÷ occupied space-hours = $45,000 ÷ 45,000 = $1.00. This is realized revenue per hour of use, after the effects of permits, discounts, validations, and the rate mix.

Multiply the two and you get revenue per available space-hour: 50% × $1.00 = $0.50. Multiply by the hours open to get back to the period figures:

• Per day: $0.50 × 10 hours = $5.00
• Per month: $0.50 × 300 hours = $150

These match the basic calculation, which is the check that the split is right. Now a change in RevPAS can be traced: if next month’s RevPAS rises, you can see whether occupancy rose, revenue per occupied hour rose, or both.

The mistake to avoid

A tempting shortcut is occupancy × average ticket. It does not account for how long each car stays or how many times each space turns over.

For a separate example, take a 300-space lot open 10 hours a day, with all revenue coming from parking tickets. It sells 600 tickets at an average of $2.50, earning $1,500 a day. If each car stays an average of 2.5 hours, occupied space-hours are 600 × 2.5 = 1,500 out of 3,000 available space-hours: 50% occupancy. Occupancy × average ticket gives 50% × $2.50 = $1.25, but actual daily RevPAS is $1,500 ÷ 300 = $5.00 per space. The shortcut mixes a proportion of available space-hours (occupancy) with a price per visit (ticket). It leaves out the two parking sessions per available space per day.

Hotels can use occupancy × average daily rate because a room is usually sold once per night. A parking space can be sold several times a day, which is why the calculation has to go through space-hours.

What Data You Need

• For RevPAS itself: revenue by period from every channel (hourly, monthly permits, validations, events), assigned to the right facility and period; plus available spaces and operating hours over that period, including partial closures.
• For the revenue-and-utilization split: occupied space-hours, from sufficiently frequent counts or from entry and exit records. Sparse snapshots cannot establish total occupied hours.
• A caveat for ticketless systems: with license plate recognition (LPR) or mobile pay-by-plate, occupancy and payment come from different records, and they can drift apart. If you measure occupied hours from paid sessions, vehicles that park without paying or registering are invisible, so occupancy looks lower and revenue per occupied hour looks higher than it is. If you measure from camera reads, those vehicles are counted but missed or misread plates add noise to dwell times. Either way, the gap between vehicles seen and vehicles paid is the payment-capture issue covered under What Moves RevPAS.

Occupancy data alone won’t get you there. In my analytics project on Istanbul’s municipal parking network, the city’s feed reports capacity and empty spaces for each facility, which supports occupancy. It has no revenue at all. So the project doesn’t calculate RevPAS or make any revenue claims, even though it would be easy to make up a plausible-looking number. The rule applies to any operator: don’t publish a metric your data can’t support.

Price vs. Occupancy: The Trade-Off

One reason to track RevPAS is to see the combined revenue effect when price and use both change. A higher rate can come with lower occupancy, but the response varies by facility and period. RevPAS shows the net revenue per available capacity; compare other conditions before attributing the change to price.

For this simplified example, assume each occupied space serves one paying car for the full operating day, with no turnover, permits, discounts, or unpaid parking. A 200-space lot charges $8 a day at 95% occupancy: 190 cars generate $1,520 a day, or $7.60 per available space. It raises the rate to $14. If occupancy falls to 70% under the same assumptions, 140 cars generate $1,960 a day, and daily RevPAS becomes $9.80 per space: 29% higher, even with about a quarter fewer cars. With shorter stays or turnover, use the space-hour calculation instead.

The 70% in that example is an assumption, and that’s the point to take from it. You won’t know how drivers respond until after the change. Some move to a nearby lot, some shift their arrival times, some pay. So:

• Compare RevPAS for several weeks before and after, against the facility’s own normal range and similar days or seasons. A change inside the range the facility usually varies over the past six to twelve months may be noise.
• Split the change into utilization and revenue per occupied hour, as above; then investigate what moved each component.
• If you run nearby facilities, watch whether demand simply moved next door.

What Moves RevPAS

• Pricing by time of day. Charging more during the hours a facility runs near capacity and less when it’s quiet. Set those hours from the facility’s own occupancy history rather than a fixed trigger.
• Event pricing. A flat rate during events, when demand is predictable and high.
• Reserved spaces. A named reserved space sits empty whenever its holder is away. Moving to unassigned permits lets others use it.
• Permit mix. How many spaces go to monthly permits and whether permit arrivals overlap with peak transient demand. Any decision to sell more permits than allocated spaces needs its own history and stress test.
• Payment capture. If 80% of parked vehicles pay and that rises to 95%, revenue from those vehicles rises 18.75% (95 ÷ 80 = 1.1875), assuming the number of parkers and the average payment per paying vehicle stay unchanged. That average depends on rates, length of stay, and discounts; the percentage is not guaranteed if any of those change or drivers leave because enforcement tightened. Measuring the change needs vehicle counts matched to payments.

A Property-Value Sensitivity Illustration

For owners, sustained revenue changes may affect net operating income (NOI), which is one input to property valuation. The following calculation shows sensitivity to assumptions; it does not estimate a realizable sale price.

A 400-space garage raises monthly RevPAS by $25, from $125 to $150. That’s $10,000 a month, or $120,000 a year. Assume 85% of the added revenue reaches NOI after added costs: $102,000. At an assumed 7% capitalization rate, $102,000 ÷ 0.07 is about $1,457,000 of added value.

That’s arithmetic, not an appraisal or evidence that a buyer would pay $1.457 million more. Actual value depends on the lease or management structure, costs, market, appraisal method, and whether the higher RevPAS is expected to last.

A Monthly RevPAS Check

1. Calculate RevPAS for each facility for the month. State the period and the space count.
2. Compare it with that facility’s last six to twelve months. Judge the change against how much it normally varies.
3. If it’s off track, split it. Did occupancy move, or revenue per occupied hour?
4. Assign one action, with an owner and a date.

How to build a monthly KPI scorecard shows a spreadsheet layout for tracking RevPAS alongside targets and variance.

Frequently Asked Questions

What is a good RevPAS?

There’s no general figure. RevPAS depends on location, facility type, pricing, and demand. Compare each facility with its own history and with your other facilities.

What’s the difference between RevPAS and average ticket?

Average ticket is revenue per parking session. RevPAS is revenue per available space. A higher average ticket can come with lower RevPAS if fewer cars park.

Should RevPAS include monthly permit revenue?

Yes. Include all parking revenue for the facility. Tracking the hourly and permit shares separately helps explain changes.

Can I calculate RevPAS from occupancy data?

No. RevPAS needs revenue. Occupancy data tells you how much of the capacity was used, not what it earned.