
For two years I was proud of one number: my studio in Tashkent ran 91% occupancy. Always booked, almost never a gap. Then I had coffee with a host who runs an identical unit two floors up in the same building — same square metres, same view of the same courtyard — and she ran 71% occupancy and earned about $380 more per month than I did. She charged $34 more a night. My 91% wasn't a trophy. It was a receipt for everything I'd left on the table.
The number that would have told me this years earlier is RevPAR. Occupancy alone lies. ADR alone lies. RevPAR is the one figure that catches both of them at it.
What RevPAR actually measures
RevPAR — revenue per available rental night — comes from the hotel industry, where it has been the headline metric for decades. Hotels worked out long ago that "we were 95% full" and "we made money" are not the same sentence.
The formula is two lines:
RevPAR = accommodation revenue ÷ available nights
RevPAR = occupancy rate × ADR
Both give the same answer. The second line is the one worth tattooing on the inside of your eyelids, because it shows what RevPAR is: the product of how often you sell and how much you sell for. Push either lever and RevPAR moves. Pull one while the other sags and RevPAR stands still — which is exactly the trap that high occupancy hides.
A definition for each term, because hosts use them loosely:
- Accommodation revenue is the nightly rate times nights booked. It excludes the cleaning fee and excludes occupancy tax. Those are passthrough money — fold them in and RevPAR balloons on short stays for no real reason.
- Available nights is the nights the listing was actually open for sale. If you blocked six nights for your own visit, available nights is 24 in a 30-day month, not 30.
- ADR — average daily rate — is accommodation revenue divided by nights booked. Note the denominator: booked, not available. ADR and RevPAR share a numerator and differ only in the denominator, and that one difference is the whole point.
Three listings that look nothing alike
Here is the table that ended my pride in 91%. Three real-shaped listings, one 30-night month, accommodation revenue only.
| Listing | ADR | Occupancy | Nights booked | Accommodation revenue | RevPAR |
|---|---|---|---|---|---|
| A — "always booked" | $96 | 88% | 26.4 | $2,534 | $84.48 |
| B — "feast or famine" | $158 | 61% | 18.3 | $2,891 | $96.38 |
| C — "the quiet one" | $124 | 74% | 22.2 | $2,753 | $91.76 |
Listing A is the one every host wants to be. It is booked almost solid. The owner of A tells people at dinner that their place "basically never sits empty." And listing A is the worst-performing of the three by RevPAR — it earns $84.48 per available night against B's $96.38.
Over the month that gap is $357. Over a year, holding the pattern, it is roughly $4,300 that listing A's owner is not earning, while feeling like the winner the whole time. Listing A's owner is me, two years ago.
Listing B looks alarming on the Airbnb dashboard — 61% occupancy reads as a problem, and the owner of B probably loses sleep over the empty nights. But B converts each available night into the most money of the three. B's owner has the opposite problem to A's: B might be slightly overpriced, leaving occupancy on the table, but B is closer to the money-maximising point than A is.
Listing C is the actual lesson. C is not the most booked and not the most expensive. C sits at 74% occupancy and $124 ADR and quietly out-earns the "always booked" listing by $7 per available night. C is what A becomes after a price correction.
How to calculate RevPAR for your own listing
You need two numbers for a chosen period — start with a single calendar month.
1. Accommodation revenue. On Airbnb, open the host menu, go to Earnings, then Transaction history, and filter to the month. Sum the gross accommodation lines — Airbnb itemises them separately from the cleaning fee and the guest service fee. On Booking.com the equivalent lives under Finance → Reservation statements. Exclude cleaning fees and any tourist or occupancy tax. If you want one figure that nets out the platform commission, subtract Airbnb's host service fee (typically 3% on the standard split) — just be consistent and never compare a gross RevPAR against a net one.
2. Available nights. Count the calendar days in the month and subtract every night the listing was not for sale: owner stays, maintenance closures, the three nights you blocked because your cleaner was on holiday. Do not subtract nights that were simply unsold — an unsold night is still an available night, and pretending otherwise turns RevPAR into a number that always looks great and means nothing.
Then divide:
RevPAR = accommodation revenue ÷ available nights
A worked example. Your studio earned $2,040 in accommodation revenue in a 30-day June. You blocked 6 nights for your own trip, so available nights is 24. RevPAR is $2,040 ÷ 24 = $85.00. If you had carelessly divided by 30 you would have logged $68.00 — and concluded your pricing was failing when it was not. The denominator is where most RevPAR calculations quietly go wrong.
The lever RevPAR points at
RevPAR is diagnostic, not just descriptive. The shape of your two inputs tells you what to do next.
High occupancy, ordinary RevPAR. Occupancy above 90% and a RevPAR no better than comparable listings means one thing: you are underpriced. You are selling out because you are cheap. The fix is to raise the nightly rate and accept that occupancy will fall — that is the trade working for you, not against you.
Here is the test that makes the decision unscary. Before raising your rate, compute the break-even occupancy:
break-even occupancy = current RevPAR ÷ proposed nightly rate
Take listing A. Current RevPAR is $84.48. Suppose A's owner considers moving the rate from $96 to $115. Break-even occupancy is $84.48 ÷ $115 = 73.5%. That means A can lose every booking that drags occupancy down to 73.5% and still earn exactly what it earns today. A is currently at 88%. Occupancy would have to crater by 14.5 percentage points before the price hike costs anything — and any night above 73.5% occupancy is pure gain. That is an enormous margin of safety, and it is invisible if you only watch the occupancy number.
Low occupancy, low RevPAR. Occupancy under 55% paired with a weak RevPAR is the genuine problem case. Either the price is too high for the demand, or the demand itself is broken — thin photos, few reviews, a slow calendar, a location working against you. Dropping the price is the obvious move, but check the demand drivers first; a price cut on a listing with bad photos just loses money faster. If your low occupancy traces back to calendar friction rather than price, that is a fixable mechanical problem — see avoiding double bookings and the calendar-hygiene basics.
Low occupancy, high RevPAR. This is listing B. You are extracting a lot per night but selling few of them. There may be room to nudge the price down and pick up volume — but only if the volume gained outearns the rate given up. Run the break-even test in reverse: a price cut is worth it only if occupancy rises enough to keep RevPAR flat or growing.
For the mechanics of moving price across a week and a season rather than as a single flat number, dynamic pricing for short-term rentals goes deeper. RevPAR is the scoreboard; dynamic pricing is how you play.
The RevPAR mistakes that cost real money
Counting calendar nights instead of available nights. Already covered, and it is the single most common error. Calendar nights flatter a host who blocks a lot of personal time and punish a host who keeps the listing open. Always divide by available nights.
Comparing across seasons. January RevPAR against July RevPAR tells you nothing except that summer exists. Compare a month to the same month last year, or use a trailing-12-month RevPAR if you want one stable number. A RevPAR that drops in November is not a failure; it is November.
Mixing gross and net. Decide once whether your RevPAR is gross of platform commission or net of it. Write the choice down. A gross RevPAR of $96 and a net RevPAR of $93 are both fine — comparing one host's gross against another's net is not.
Folding in the cleaning fee. A two-night stay with a $60 cleaning fee adds $30/night of phantom RevPAR; a ten-night stay with the same fee adds $6/night. Including cleaning fees makes short stays look artificially strong and quietly biases every decision toward churn. Keep cleaning fees out. If you want to understand cleaning-fee strategy on its own terms, that is a separate question covered in the cleaning fee vs all-in pricing breakdown.
Treating occupancy as the goal. Occupancy is an input to RevPAR, not a target. A host optimising purely for occupancy will price down until the calendar is full and the bank account is thin. The goal is RevPAR. Occupancy is just one of the two dials you turn to move it.
One opinionated take
Airbnb's host dashboard shows you occupancy because occupancy is the metric that feels good. A full calendar looks like success the way a busy restaurant looks like a good restaurant — and sometimes the busy restaurant is just cheap. RevPAR is the metric that pays your mortgage, and the platforms bury it because it occasionally tells you to do the uncomfortable thing: raise prices, accept empty nights, stop chasing the green calendar.
If your listing runs above 90% occupancy, stop reading and go raise your rate. You are not a great host with a popular listing. You are a host who is cheap, and the only person who has not noticed is you. Track RevPAR for three months, let occupancy fall to the high 70s, and the number that matters will go up. If you want one place that tracks RevPAR, occupancy, and ADR across every listing without exporting three spreadsheets, that is what RentTools is for.
Frequently asked questions
What is a good RevPAR for a short-term rental?
There is no universal number — RevPAR is only meaningful against a benchmark. The right comparison is your own listing month-over-year, and listings genuinely like yours in the same city and the same season. A $90 RevPAR is excellent in one market and poor in another. Track the trend of your own RevPAR before you worry about anyone else's absolute figure.
Is RevPAR the same as ADR?
No, and confusing them is the core mistake this post exists to fix. ADR is revenue divided by nights booked — it measures price only. RevPAR is revenue divided by nights available — it measures price and how often you sold combined. A listing can have a high ADR and a low RevPAR because it barely sells. RevPAR is the truer measure of the business.
Should RevPAR include the cleaning fee?
No. The cleaning fee is roughly passthrough money that covers a real cost, and because it is a flat charge it distorts per-night figures on short stays. Use accommodation revenue — nightly rate times nights booked — and leave cleaning fees and occupancy taxes out of both the numerator and your thinking.
How is RevPAR different from RevPAN?
They are effectively the same metric with different names. Hotels say RevPAR — revenue per available room. Short-term-rental hosts sometimes say RevPAN — revenue per available night — because a single listing is one "room" and the meaningful unit is the night. The formula and the use are identical. Pick whichever word your market uses and move on.
Does RevPAR work for a single listing or only a portfolio?
It works perfectly for a single listing — that is where this post calculated it. RevPAR is just revenue divided by available nights, and a one-listing host has both numbers. For a portfolio you can compute a blended RevPAR across all listings, which is useful for spotting which property is dragging the average down.
How often should I recalculate RevPAR?
Monthly is the right cadence for review, compared against the same month a year earlier. Recalculating weekly produces noisy numbers that tempt you into overcorrecting on price. If you also keep a trailing-12-month RevPAR, you get one figure that smooths out seasonality and shows the real direction of the business.
Why is my occupancy high but my RevPAR low?
Because you are underpriced. High occupancy with low RevPAR is the textbook signal that your nightly rate is below what the market would pay. Run the break-even occupancy test — current RevPAR divided by the rate you are considering — and if the break-even sits comfortably below your current occupancy, raise the price.
Does RevPAR account for length-of-stay discounts?
Yes, automatically, because it works from actual revenue received. If a weekly discount lowered your effective nightly rate, that shows up in accommodation revenue and therefore in RevPAR. To decide whether a length-of-stay discount is pulling its weight, compare RevPAR in months with and without it — see length-of-stay discount math.
Keep reading
Airbnb Superhost: the four thresholds and what the badge is worth
The four quarterly metrics that win the Superhost badge, the search-rank lift it actually gives you, and when chasing it stops being worth the response-rate cognitive load.
Airbnb host-only fee vs split-fee: the breakeven math
When 15% host-only beats 3% + ~14% split, the conversion uplift hosts actually see, and the worked spreadsheet across budget, mid-tier, and luxury listings.
Airbnb extra guest fee: the per-person pricing math
What an extra guest actually costs you per night, the three pricing models hosts use, and the spreadsheet that shows when a per-guest fee funds your linen budget vs when it spooks the booking.
Airbnb instant book vs request to book: the conversion math
What Airbnb's instant book actually costs you in bookings, the four guest signals where request-to-book pays for itself, and the spreadsheet to decide.
Airbnb co-host commission math: what 20% really costs you
A worked breakdown of co-host pay models for short-term rental hosts. Percent-of-gross vs percent-of-net vs per-task, real dollar math at 5, 10, and 20 stays per month, and the threshold where the co-host pays for themselves.
Guest registration laws for short-term rentals: a country-by-country guide
What guest data EU short-term rental hosts must collect and report to authorities — Spain, Italy, France, Portugal, Germany — with deadlines and retention rules.
Comments
Sign in to comment.
- No comments yet.