
In this article9 sections
A boutique inn in Charleston and a two-bedroom condo in Scottsdale can post the identical RevPAR this month, $168, and be running completely different businesses. One number, two very different stories. For an independent hotel, that $168 is close to the whole picture: room revenue, divided by every room the property had to sell. For the Scottsdale condo, $168 might be hiding a cleaning fee line that is worth more than the room rate itself, a week the owner blocked off for a family visit, and a comp set built from four listings that are nothing like it. Short-term rental operators have spent the last few years borrowing a hotel metric wholesale, and in 2026 the gap between what RevPAR measures and what an Airbnb host actually needs to know is wide enough to cost real money. This article breaks down what Airbnb RevPAR actually calculates, where the hotel version of the formula quietly stops working for a single-unit or multi-unit rental portfolio, and what the current short-term rental data says a host should be comparing themselves against instead.
What Airbnb RevPAR Actually Means
Airbnb RevPAR is the average daily rate a listing earned on its booked nights, multiplied by the share of available nights it actually sold. AirDNA, the short-term rental data firm most hosts pull comp data from, defines it exactly the way hotels do: RevPAR equals ADR times occupancy rate, and the same number also comes out of dividing total room revenue by every available night in the period, booked or not. It is a rate metric and a volume metric collapsed into one figure, which is why it caught on in hotel finance in the first place and why short-term rental platforms borrowed it wholesale once portfolios got big enough to need a single number to compare.
Take a one-bedroom cabin listed at an average of $220 a night. Over a 30-night month it sells 20 of those nights, for an occupancy rate of 66.7 percent. Multiply $220 by 0.667 and the RevPAR comes out to $146.67. You get the same answer the other way: 20 nights times $220 is $4,400 in room revenue, and $4,400 divided by 30 available nights is $146.67. Neither the ADR alone nor the occupancy rate alone tells you that number. A listing running $300 ADR at 45 percent occupancy and a listing running $180 ADR at 75 percent occupancy both land close to $135 in RevPAR, even though an owner glancing at just the ADR or just the occupancy chart would read those two listings as opposites.
That is the real value of the metric: one figure that cannot be gamed by rate or occupancy alone, which is exactly why hotel finance teams built their reporting around it decades ago. It is also exactly what gets misapplied once you move from a 100-room hotel to a handful of rental units. A hotel's room count on any given night is fixed by the building. A short-term rental portfolio's available-night count moves with every owner block, every maintenance closure, and every unit a host adds or pulls from the platform mid-month, which means the denominator in the RevPAR formula is a lot less stable than it looks on a spreadsheet.
AirDNA's glossary spells out the two feeder metrics the same way most short-term rental data platforms do. ADR is total revenue from booked nights divided by booked nights, which means it only ever reflects nights that actually sold, never the nights sitting empty on the calendar. Occupancy rate is total booked days divided by active listing nights, which is where the variable-denominator problem starts, since active listing nights depends entirely on how consistently a host marks a property available versus blocked. Multiply the two together and RevPAR inherits whatever instability sits inside that occupancy figure.
Change one input and the distortion shows up immediately. If the same cabin's owner blocks four nights in the month for a personal stay, available nights drop from 30 to 26 while booked nights stay at 20, which pushes occupancy from 66.7 percent to 76.9 percent and RevPAR from $146.67 up to $169.23, with guest demand completely unchanged. A host who blocks calendar time without fully deactivating the listing can inflate their own RevPAR without selling a single additional night, simply by shrinking the denominator the occupancy rate is built on.
Bottom line: Airbnb RevPAR is ADR multiplied by occupancy, exactly as AirDNA and the hotel industry define it, and a $220 ADR at 66.7 percent occupancy produces a RevPAR of $146.67.
Is RevPAR a Good Airbnb Metric?
RevPAR is a good starting metric for an Airbnb listing because it stops a host from being fooled by either rate or occupancy in isolation, but it was never built to capture everything that drives a short-term rental's profitability. Hospitality Net's explainer on the metric, written for the hotel side of the industry, states the case plainly: RevPAR "captures both rate and volume" and exposes the trade-off a property makes when it discounts to fill rooms. That trade-off is just as real for a rental host chasing a 90 percent occupancy badge as it is for a hotel general manager chasing a conference group, and ignoring it in either business tends to show up as the same mistake with a different name.
The same explainer is equally direct about where RevPAR stops being useful. It calls relying on RevPAR alone a pitfall, because the metric says nothing about costs and ignores every other revenue line a property might carry. In a hotel, that missing piece is food and beverage, spa, and event space. In a short-term rental, the missing piece is cleaning fees, pet fees, early check-in charges, and damage waiver income, several of which can be a larger dollar amount per booking than the swing in nightly rate a host spends weeks optimizing.
Cost blindness compounds that gap. A hotel's RevPAR says nothing about housekeeping labor, utilities, or franchise fees sitting underneath that room revenue, and a short-term rental's RevPAR says nothing about the cleaning fee's own cost, the platform's service fee, or the property management commission taken off the top. Two listings posting the same $146 RevPAR can carry very different net margins if one pays a 20 percent management commission plus outsourced cleaning while the other pays nothing because the owner cleans and manages the property personally. RevPAR is a revenue signal, not a profit signal, and conflating the two is how a host ends up chasing a rate strategy that grows gross numbers while shrinking what actually lands in the bank account.
The discounting trap shows up constantly on properties chasing a fuller-looking calendar. Hosts frequently believe a near-constant stretch of booked nights signals strength to future guests, and will cut ADR by 15 to 20 percent to chase that look. Run the cut through the math and it rarely pays for itself: dropping ADR from $220 to $185 to push occupancy from 66.7 percent to 78 percent moves RevPAR from $146.67 to roughly $144.30, a net loss despite the far busier-looking calendar. The break-even math between ADR and occupancy only favors a discount when the occupancy gain is large enough to outrun the rate cut, and most discounting decisions never run that check before the new price goes live.
There is a second problem that is specific to short-term rentals and does not exist in a hotel at all: the denominator itself is negotiable. A hotel cannot quietly remove ten rooms from its RevPAR calculation because the general manager wants a nicer-looking number. A short-term rental host can block a property for a family visit, a renovation, or an extended personal stay, and every platform and data provider treats that blocked time differently when it comes to counting "available nights." Two identical listings can report different RevPAR in the same month purely because one owner blocked five nights and the other didn't, with nothing about guest demand changing at all.
In the portfolios we price at Revenuenaire, this is the single most common reason a RevPAR number looks wrong at first glance: it isn't wrong, it is just answering a narrower question than the host thinks it is. RevPAR tells you what a listing earned against the nights it was actually offered for sale. It does not tell you what it earned against the nights it could have been offered, and it does not tell you what it earned in total once ancillary fees are counted.
Bottom line: RevPAR is a reliable rate-and-volume signal but it excludes costs, excludes ancillary revenue, and depends on an available-night count that a short-term rental owner can change at will, none of which is true inside a hotel's fixed room inventory.
RevPAR vs RevPAN for Rentals
RevPAR and RevPAN measure two different pools of money, and mixing them up is the single fastest way to misread a short-term rental's performance. RevPAR, as defined above, counts only the nightly room rate. RevPAN, revenue per available night, counts every dollar a booking generates, nightly rate plus cleaning fees plus pet fees plus any other add-on, and divides that total by the same available-night denominator. Property management glossaries built specifically for the rental industry treat the gap between the two as material enough to warrant its own metric, because non-room income on a vacation rental is nowhere near the rounding error it is at most hotels.
Go back to the one-bedroom cabin from the earlier example: $220 ADR, 20 booked nights out of 30, RevPAR of $146.67. Assume an average length of stay of four nights, which puts five separate bookings in that month. Each booking carries a $150 cleaning fee, so that is $750 in cleaning revenue the RevPAR calculation never sees. Two of those five bookings also add a $35 pet fee, for another $70. Total ancillary income for the month comes to $820. Add that to the $4,400 in room revenue and total revenue for the property is $5,220. Divide by the same 30 available nights and RevPAN comes out to $174, against a RevPAR of $146.67. That is an 18.6 percent gap between the two numbers, on the exact same property, in the exact same month, with nothing about guest demand changing between one calculation and the other.
Scale that gap across a portfolio and the distortion compounds. A host running ten units who tracks RevPAR alone and ignores RevPAN is routinely underestimating true revenue performance by a sixth to a quarter, which skews every downstream decision: which property gets capital for an upgrade, which one gets flagged as underperforming, which one justifies a management fee increase. Industry estimates on how much of total short-term rental revenue comes from fees rather than nightly rate run in the 15 to 30 percent range, and that share has only grown as platforms have pushed hosts toward itemized pricing rather than all-in nightly rates.
Put that percentage in portfolio-scale dollars and the gap stops looking academic. A ten-unit portfolio generating $1.2 million in combined gross room revenue a year, with ancillary income tracking the low end of that 15 to 30 percent range, is sitting on something between $180,000 and $360,000 in additional revenue that a RevPAR-only dashboard never shows anyone. That money is real, it is already collected, and it is completely invisible to an owner, a lender, or a prospective buyer who only ever looks at the RevPAR line.
There is a case for tracking both numbers side by side rather than picking one. RevPAR is the cleaner number for comparing against a hotel comp set or a market-wide benchmark, because it isolates the same room-revenue logic hotels use. RevPAN is the more honest number for understanding what a property is actually generating and for underwriting a new acquisition, because it reflects every dollar that lands in the owner's account. A host who reports RevPAR to an investor and RevPAN to themselves is not being dishonest, they are just using the right tool for each question, as long as they know which one they are looking at.
Bottom line: On a typical short-term rental, RevPAN runs 15 to 25 percent above RevPAR because of cleaning and ancillary fees, and a host who tracks only RevPAR is working from an incomplete revenue picture every month.
Where Hotel RevPAR Breaks for STR
Hotel RevPAR breaks down for short-term rentals in four specific places: a variable available-night count, no shared cost base across units, minimum-stay distortion, and a comp set that is far noisier than a hotel competitive set. Each of these is a structural difference between a 150-room building with one owner and a scattered portfolio of individually owned units, and each one changes what a RevPAR number is actually telling you.
The first break is the available-night count itself. A hotel's inventory is whatever the building has, night after night, with closures rare and almost always disclosed to a benchmarking service like STR or CoStar so the comp set adjusts. A short-term rental host can pull a listing for a weekend, block two weeks for a relative, or go completely dark during a renovation, and none of that is uniformly reported anywhere. AirDNA's own glossary defines occupancy rate as total booked days divided by active listing nights, which means the moment a host starts blocking calendar days without marking the unit fully inactive, the "available" denominator used across different tools can disagree, and RevPAR calculated on two different available-night counts for the same property will not match.
The second break is cost structure. A hotel's RevPAR sits inside a single P&L: housekeeping, utilities, and front desk staff are shared across every room, so a RevPAR comparison between two similar hotels is roughly a comparison of similar cost bases too. A short-term rental portfolio mixes self-managed units, fully outsourced units, co-hosted units, and units on wildly different cleaning and platform fee structures. Two properties can post an identical RevPAR and land at completely different net margins once management fees, which typically run in a meaningful percentage of gross revenue, are backed out.
The third break is minimum length of stay. A hotel sells by the night with almost no restriction. A short-term rental host frequently sets a two, three, or seven-night minimum, especially around holidays or in markets with local short-term rental ordinances that cap turnover. A three-night minimum on a property with soft midweek demand can leave nights unsold that a one-night minimum would have filled at a lower rate, which drags occupancy and RevPAR down even though the host made a deliberate, often profitable, choice to protect against high turnover costs. RevPAR has no way to distinguish "we couldn't sell these nights" from "we chose not to sell these nights individually."
The fourth break, and the one with the biggest practical impact, is the comp set. A hotel's competitive set is usually five to ten similarly branded, similarly sized properties within the same submarket, tracked consistently by a third party that both the hotel and its competitors can see. A short-term rental comp set has to be built from individually owned, individually managed units that vary wildly in size, amenities, and even whether they are still active on the platform this month. Get the comp set wrong and the RevPAR comparison tells you nothing useful, no matter how clean the arithmetic underneath it is.
None of this means RevPAR is the wrong tool everywhere in short-term rentals. A branded aparthotel or a condo-hotel running forty units under one management company, one brand, and one booking engine looks far more like a hotel than a scattered single-owner portfolio does, and RevPAR behaves close to the way it does in a traditional property once inventory is centrally controlled and costs are pooled across units. The same logic hotels use to read their own RevPAR index against a managed competitive set translates cleanly to that kind of operation. The break happens specifically at the scattered, individually owned end of the market, which is where most Airbnb hosts actually sit, and it is worth naming because not every short-term rental business has the same problem.
A second edge case worth naming is a co-hosted or revenue-share property, where two parties split income under a management agreement. RevPAR calculated on gross booking revenue can look healthy while the owner's actual net share, after a co-host fee that commonly runs 15 to 25 percent of booking revenue, tells a very different story. Anyone reviewing RevPAR on a co-hosted unit should confirm whether the figure is gross or net of that split before comparing it to a fully self-managed property down the street.
Bottom line: Hotel RevPAR assumes stable inventory, a shared cost base, unrestricted night-by-night selling, and a clean comp set, and a short-term rental violates all four assumptions to some degree, which is why the same formula needs real adjustment before it means anything for a rental host.
Building a Short-Term Comp Set
A workable short-term rental comp set starts with AirDNA's market grade inputs and narrows from there to three to five properties that actually resemble the subject listing, not just the first handful of results a search radius returns. AirDNA's market scoring methodology, which grades every market it tracks on a 40 to 100 scale, requires at least 15 active listings in a market before it will generate a reliable score at all, and markets with more listings carry more weight in the comparisons AirDNA runs. Below that threshold, treat any RevPAR benchmark for the area as directional at best.
AirDNA builds its market grade from five separate inputs: investability, which compares home prices to typical short-term rental income in US markets; rental demand, a blend of occupancy and listing growth; revenue growth, which is literally the year-over-year change in RevPAR for properties booked in both periods; seasonality, measured as the swing between a market's lowest and highest revenue month; and regulation, scored on how much enforcement activity shows up in host and property behavior. A market can post a strong headline RevPAR and still carry a weak grade if seasonality is brutal or regulatory risk is high, which is exactly the kind of nuance a single average RevPAR figure hides.
Guesty's guidance on estimating rental revenue accurately makes the comp set problem concrete rather than abstract: pick a search radius too wide and the comp set blends in a completely different micro-market, and the firm recommends anchoring a comparison to three to five genuinely comparable listings rather than a market-wide average. A beachfront condo and a condo six blocks inland in the same zip code are not the same comp set, even though most default search radii would lump them together. Bedroom count, walk score to the attraction driving demand, and whether the unit allows pets or large groups all matter more to the comp set than raw proximity.
A practical build looks like this. Start with AirDNA or a similar data provider and pull every active listing within the subject property's immediate neighborhood, not the whole zip code. Filter to the same bedroom count, plus or minus one. Cross off anything with a materially different review count or review score, since a brand-new listing and a five-year veteran with 400 reviews are not competing for the same guest decision. What survives that filter, usually four to six properties, becomes the comp set a host should track RevPAR against, updated at least quarterly since listings churn on and off platforms constantly.
Here is what that comp set looks like once it is actually built, using the Blue Pine Cabin from earlier in this article as the subject property against four genuinely comparable one-bedroom listings within half a mile:
| Listing | ADR | Occupancy | RevPAR |
|---|---|---|---|
| Blue Pine Cabin (subject) | $220 | 66.7% | $146.67 |
| Comp A | $235 | 61.0% | $143.35 |
| Comp B | $210 | 70.0% | $147.00 |
| Comp C | $245 | 58.0% | $142.10 |
| Comp D | $225 | 64.0% | $144.00 |
Average comp set RevPAR comes out to $144.11, which puts the subject property essentially in line with its real competition despite its ADR sitting in the middle of the pack rather than at the top or bottom. That is the kind of read a wide search radius or a mismatched bedroom count would never produce, and it is the entire reason a comp set has to be built by hand rather than pulled as a wide market-wide average.
A short checklist keeps the build consistent every time it gets refreshed:
- Pull every active listing within the immediate neighborhood, not the full zip code or city.
- Filter to the same bedroom count, plus or minus one.
- Drop listings with a materially different review count or review score.
- Confirm each comp allows or restricts the same amenities, including pets and large groups.
- Refresh the comp set at least quarterly, since listings churn on and off platforms constantly.
Bottom line: A short-term rental comp set needs at least 15 listings in the broader market to be statistically meaningful by AirDNA's own threshold, and the usable working comp set for any one property should be narrowed to three to five genuinely similar listings, not a wide-radius average.
Common RevPAR Mistakes to Avoid
The most common RevPAR mistake short-term rental hosts make is treating a platform calculator's single number as a forecast rather than a snapshot, and every other mistake on this list compounds from that same root error. Guesty's own research on revenue estimation tools is blunt about it: a calculator gives a snapshot, and a host's actual booking history is a better predictor of future performance than any generic tool output, because the calculator smooths seasonality into one annual average and hides the exact swing a host needs to plan around.
A second mistake is confusing gross RevPAR with net RevPAR. Every projection built on gross nightly rate, before platform fees and management costs, overstates what actually lands in an owner's account. Typical fee and management deductions run in the 25 to 35 percent range of gross revenue, which means a property posting a gross RevPAR of $150 might be clearing closer to $105 after costs. A host who underwrites a purchase or a renovation on gross RevPAR alone is working from a number that is routinely a third too high.
A third mistake is applying a flat occupancy assumption across the whole year. DemandSage's data, cited in multiple rental industry sources, puts average US host revenue near $15,600 annually at an average nightly rate close to $137, but that annual average conceals occupancy that swings hard by season, by city, and sometimes street to street within the same city. A host who takes an annual RevPAR and divides it evenly across twelve months will badly misjudge both the slow months, when cash flow gets tight, and the peak months, when pricing power is being left on the table.
A fourth mistake, and the one most specific to this metric, is comparing a personal RevPAR directly against a hotel RevPAR benchmark in the same market without adjusting for what each number includes. KeyData's Q3 2026 data shows short-term rental RevPAR growing faster than hotel RevPAR in every region it tracked, by a wide margin in some cases, but that comparison is only meaningful once both numbers are stripped down to the same basis: room or unit revenue only, ancillary income excluded on both sides, occupancy measured the same way. Pulling a headline STR RevPAR figure and a headline hotel RevPAR figure from two different data providers that define "available" differently is comparing two different things wearing the same label.
A fifth mistake is letting stale comp data sit unchecked for months. Short-term rental comp sets change faster than hotel competitive sets, because new listings can go live in a market within days and existing listings can drop off the platform just as fast. A comp set built in January is frequently out of date by the summer peak season, and a host still benchmarking against it is measuring performance against a market that no longer exists.
A sixth mistake is letting a restrictive minimum stay quietly suppress RevPAR without anyone noticing why. A host who sets a four-night minimum during a shoulder season with mostly two and three-night demand can watch occupancy fall from a reachable 60 percent down to 35 percent, taking RevPAR down with it, and assume the market simply went soft when the real cause was a calendar setting made months earlier and never revisited.
A seventh mistake is skipping the owner-block adjustment when reporting RevPAR to a partner, lender, or co-host. Blocked nights that are not cleanly excluded from the available-night count, as the earlier example in this article showed, can inflate RevPAR by double digits in percentage terms without a single extra night sold, and a host who reports that inflated figure during a refinance or a buyout negotiation is working from a number that will not hold up once anyone checks the booking calendar directly.
An eighth mistake is letting stacked discounts erode ADR without anyone tracking the combined effect. A weekly-stay discount, a last-minute discount, and a new-listing discount can each look small in isolation, five percent here, ten percent there, but stacked together on the same booking they can cut realized ADR by 20 percent or more against the rate a host believes they are charging. RevPAR calculated from the discounted booked-night revenue will always be accurate to what was actually collected, but a host comparing that RevPAR against their own posted base rate, rather than against the realized rate after every discount applied, will chronically misjudge how much pricing power they actually have left to use.
Bottom line: Gross-versus-net confusion alone routinely inflates a host's perceived RevPAR by 25 to 35 percent, and that single mistake feeds every bad decision that follows it, from pricing to underwriting to renovation budgeting.
Tracking RevPAR Across a Portfolio
Tracking RevPAR across a multi-property short-term rental portfolio means standardizing the available-night count across every unit first, then layering a consistent cadence on top, because the metric only becomes useful for comparison once every property is measured the same way. Portfolio operators who skip the standardization step end up comparing a fully booked unit against a half-blocked one and drawing conclusions neither property's numbers actually support.
The sensitivity table below shows why both ADR and occupancy need to be tracked together rather than separately. It uses the same cabin from earlier in this article, run across a range of realistic ADR and occupancy combinations, to show how much RevPAR can move from either lever alone.
| ADR | 50% Occupancy | 60% Occupancy | 70% Occupancy | 80% Occupancy |
|---|---|---|---|---|
| $180 | $90.00 | $108.00 | $126.00 | $144.00 |
| $220 | $110.00 | $132.00 | $154.00 | $176.00 |
| $260 | $130.00 | $156.00 | $182.00 | $208.00 |
| $300 | $150.00 | $180.00 | $210.00 | $240.00 |
Read across any row and a ten-point occupancy swing moves RevPAR by roughly the same dollar amount as an $18 to $30 ADR change, depending on the row. That is the practical argument for tracking both levers on a dashboard rather than optimizing one in isolation: a host fixated on pushing ADR from $220 to $260 while occupancy slides from 70 percent to 50 percent has actually moved RevPAR from $154 down to $130, a worse outcome despite the higher posted rate.
A five-property portfolio dashboard, reviewed monthly, might look like this once standardized:
| Property | ADR | Occupancy | RevPAR | RevPAN |
|---|---|---|---|---|
| Blue Pine Cabin | $220 | 66.7% | $146.67 | $174.00 |
| Desert Rose Condo | $195 | 72.0% | $140.40 | $162.50 |
| Lakeview Loft | $265 | 58.0% | $153.70 | $181.90 |
| Harbor Street Flat | $175 | 80.0% | $140.00 | $158.00 |
| Ridgeline Chalet | $310 | 51.0% | $158.10 | $196.40 |
A dashboard built this way surfaces the properties worth management attention immediately. Harbor Street Flat has the highest occupancy in the portfolio but the lowest RevPAR, which usually means it is priced too conservatively relative to demand. Ridgeline Chalet has the opposite profile, the highest RevPAR but the lowest occupancy, which is worth testing with a modest rate reduction to see whether occupancy recovers faster than rate erodes.
On implementation, a realistic timeline for a portfolio adopting this kind of tracking for the first time runs about a quarter. In the first week, pull twelve months of booking history per property and establish each unit's own available-night baseline, accounting for owner blocks. In weeks two through four, start a weekly RevPAR and RevPAN snapshot per property, logged the same day every week to avoid mid-week booking pace distorting the comparison. By month two, build the comp set for each property following the process in the section above, and start comparing portfolio RevPAR against those comp sets rather than against a generic market average. By the end of the quarter, the portfolio should have enough weekly data points to separate seasonal noise from a genuine pricing or demand problem at any one property, which is the point where RevPAR tracking actually starts changing pricing decisions instead of just describing the past.
Measurement cadence matters as much as the metric itself. A weekly RevPAR check catches pricing mistakes while there is still time to fix the calendar. A monthly comp-set comparison catches a property drifting away from its market. A quarterly review against the kind of regional benchmark data covered next is what catches a market-wide shift before it shows up as a surprise in annual revenue.
Who looks at which number also matters. An on-the-ground property manager benefits most from the weekly RevPAR snapshot, since that is the figure that should be driving same-week pricing adjustments on the calendar. A portfolio owner or investor is better served by the monthly RevPAN view, since that figure reflects the actual cash flow the business is generating once fees are included. A lender or a partner evaluating the portfolio for financing should see both numbers side by side with the comp set attached, because a RevPAR figure presented without its comp set is a number with no way to judge whether it is good or bad.
A short rollout checklist for a portfolio starting this process for the first time:
- Pull twelve months of booking history per property and establish each unit's true available-night baseline.
- Start a weekly RevPAR and RevPAN snapshot, logged on the same day every week.
- Build a comp set per property using the process described earlier in this article, not a market-wide average.
- Flag any property whose RevPAR sits more than 10 percent below its comp set average for a pricing review.
- Revisit the entire process quarterly, since comp sets and seasonal demand both shift faster in this industry than in hotels.
Bottom line: A standardized, weekly RevPAR and RevPAN tracking cadence across a portfolio takes about a quarter to fully implement, and it reliably surfaces the specific properties that are mispriced long before an annual revenue review would catch them.
What's a Good Airbnb RevPAR in 2026?
A good Airbnb RevPAR in 2026 depends entirely on the region, and the gap between the strongest and weakest performing markets this year is wide enough that a single national number is close to meaningless for judging any individual property. KeyData's Q3 2026 Key Data Index, built from anonymized reservation data across roughly 1.3 million US short-term rental properties, put national RevPAR growth at 24 percent year over year in September alone, driven by paid occupancy up 13 percent and ADR up 10 percent to $276. July came in at 11 percent RevPAR growth and August slowed to 2 percent, which shows how much month-to-month variation sits inside even a single strong quarter.
Month to month, the trend was anything but a straight line. KeyData's finalized figures showed RevPAR growth of 11 percent in July, slowing sharply to 2 percent in August, then accelerating to 24 percent in September, with forward on-the-books figures pointing to a steadier finish to the year:
| Month (2026) | RevPAR growth YoY | Occupancy growth YoY | ADR growth YoY |
|---|---|---|---|
| July | +11% | n/a | n/a |
| August | +2% | n/a | n/a |
| September (final) | +24% | +13% | +10% (to $276) |
| October (forward) | +8% | +2% | +6% |
| November (forward) | +11% | +6% | +4% |
| December (forward) | +10% | +12% | -2% (to $473) |
A host reading only the September headline would reasonably expect that pace to continue, and would have been wrong by October. That kind of swing inside a single quarter is exactly why a trailing twelve-month average, the number most revenue calculators default to, flattens out information a weekly or monthly tracking habit would have caught in real time.
Regionally, the picture splits hard. Sally Henry, KeyData's vice president of market intelligence and insights, highlighted Q3 RevPAR growth of just 6 percent in Hawaii against 16 percent in the Mid-Atlantic, with New England at 12 percent and the Midwest at 15 percent. A host in a slow-growth region should not benchmark their own RevPAR trajectory against a national average built heavily on faster-growing regions, and a host in a hot regional market should be cautious about assuming that growth rate is sustainable once supply catches up to the demand driving it.
| Region | STR RevPAR growth (Q3 2026) | Hotel RevPAR growth (Q3 2026) |
|---|---|---|
| Hawaii | +6% | not reported |
| New England | +12% | not reported |
| Midwest | +15% | not reported |
| Mid-Atlantic | +16% | +5% |
Hawaii's 6 percent growth and the Mid-Atlantic's 16 percent growth happened in the same quarter, in the same country, under the same national headline figure. Treating a single national RevPAR growth number as something that applies evenly everywhere would badly mislead a host in a slower region and badly undersell one in a faster region, which is the whole argument for building a regional, comp-set-based benchmark instead of reaching for the nearest headline.
The comparison to hotels is where 2026 gets genuinely interesting for anyone trying to argue short-term rentals are losing ground to hotels. KeyData's data showed short-term rental RevPAR outgrowing hotel RevPAR in every one of the seven regions where both figures were available, with the widest gap again in the Mid-Atlantic: short-term rental RevPAR up 16 percent against hotel RevPAR up roughly 5 percent in the same region. That is a meaningfully different growth rate, and it undercuts the narrative that short-term rental performance has been collapsing relative to hotels this year, even though individual host anecdotes about a slower season are not necessarily wrong for their specific property or market.
Looking ahead, KeyData's forward-looking, on-the-books figures as of early October showed RevPAR growth continuing into the fourth quarter: 8 percent in October, 11 percent in November, and 10 percent in December, with occupancy accelerating faster than rate into the holiday season. December ADR was actually pacing slightly below the prior year, at $473 against $481, which suggests hosts were leaning on volume rather than rate to drive RevPAR growth into year-end, a reasonable response to a holiday calendar when demand is strong but guests are comparison shopping harder on price.
Property type adds another layer most national benchmarks flatten out entirely. A studio or one-bedroom unit in a walkable urban market tends to run a lower ADR but a much higher occupancy ceiling than a four-bedroom house in a drive-to leisure market, and the two often land at a similar RevPAR through very different paths. Large group homes, the kind that sleep ten or more, see sharper seasonal swings since they depend on big-group travel occasions like weddings, reunions, and holiday gatherings rather than steady weekday demand, so a single annual RevPAR figure on that property type hides more volatility than it does on a studio renting mostly to solo business travelers. Anyone underwriting a new purchase in either category should build a month-by-month revenue forecast before closing rather than dividing a trailing twelve-month RevPAR evenly across the calendar, since that even split is exactly the assumption that breaks down hardest on seasonal, large-group inventory.
None of this means a specific number like "$150 RevPAR is good" is a safe takeaway. A $150 RevPAR in a slow-growth coastal market with high ADR and modest occupancy is a different story from a $150 RevPAR in a fast-growing inland market built on strong occupancy at a modest rate. The right benchmark for any one property is never the national figure. It is the comp set built the way the earlier section in this article describes, tracked over the same multi-month window these regional figures cover.
Bottom line: National short-term rental RevPAR grew roughly 24 percent year over year in September 2026, but regional growth ranged from 6 percent to 16 percent in the same quarter, so a property-level benchmark has to come from a regional and comp-set comparison, never a national average.
Frequently Asked Questions
What is a good Airbnb RevPAR?
There is no single good RevPAR number across all short-term rentals, since it depends on local ADR levels, seasonality, and comp set. A property is performing well when its RevPAR sits at or above the average of its three to five closest comparable listings over the same rolling period, not when it clears some fixed national figure that was never built with that property's market in mind.
A $150 RevPAR means something different in a market where the comp set averages $120 than in one where it averages $190. Track the gap between your own number and your comp set's average every month rather than chasing a fixed figure pulled from a national headline, since that gap is the only version of "good" that actually reflects your specific competition.
How do you calculate RevPAR for a short-term rental?
Multiply average daily rate by occupancy rate for the period, or divide total room revenue by total available nights, which produces the same result. A $220 ADR at 66.7 percent occupancy, for example, produces a RevPAR of $146.67 using either method.
The two formulas always agree because they describe the same arithmetic from different directions. If the two numbers you calculate don't match, the available-night count used in one calculation differs from the other, usually because owner-blocked nights were counted inconsistently between the two methods.
Is RevPAR the same as RevPAN?
No. RevPAR counts only nightly room revenue, while RevPAN, revenue per available night, adds in cleaning fees, pet fees, and other ancillary charges. On a typical short-term rental, RevPAN runs 15 to 25 percent higher than RevPAR because of that ancillary income.
Track both side by side rather than picking one. RevPAR is the cleaner figure for comparing against a hotel or market benchmark since it isolates room revenue the way those benchmarks do, while RevPAN is the more honest figure for understanding what the property is actually generating for its owner.
Why is my RevPAR lower than nearby listings on a data platform?
The most common cause is a mismatched comp set rather than an actual pricing problem. A wide search radius or a comparison against listings with different bedroom counts, amenities, or review history will produce a RevPAR benchmark that was never a fair match in the first place.
Before assuming a pricing problem, pull the specific listings in the comparison and check bedroom count, review score, and whether any of them allow pets or large groups when the subject property does not. A mismatched comp set is a far more common explanation than an actual rate gap.
Does Airbnb show hosts their own RevPAR?
Airbnb's own host dashboard surfaces earnings, occupancy, and average nightly rate, but it does not label a calculated RevPAR figure directly. Hosts who want the metric generally calculate it themselves from their booking history or pull it from a third-party data platform like AirDNA.
Most hosts build it themselves from the earnings and nights-booked figures already in their dashboard export, divided by the number of nights the calendar was actually open for booking that period, not simply the number of days in the month.
Should I compare my short-term rental RevPAR to hotel RevPAR in my market?
Only after adjusting both figures to the same basis, room or unit revenue only, with ancillary income stripped from both sides. KeyData's 2026 data shows short-term rental RevPAR growing faster than hotel RevPAR in most US regions, but the two figures are calculated by different methodologies and are not directly interchangeable without that adjustment.
Even after adjusting both figures to the same basis, treat the comparison as directional rather than exact, since hotel RevPAR benchmarks are built from a standardized competitive set that short-term rental data providers cannot fully replicate given how individually owned and managed most rental inventory still is.
Do I need a revenue manager to track RevPAR for one Airbnb listing?
Usually not for a single, simple listing. A solo host with one property and a stable comp set can track RevPAR and RevPAN manually with a spreadsheet and a monthly review. The case for outsourced revenue management strengthens once a host is running three or more units, operating across multiple markets, or finds they do not have the time to rebuild their comp set and adjust pricing on a weekly basis.
The math changes once a host is managing pricing across multiple markets or multiple booking channels at the same time, since the comp-set work alone starts eating hours that could go into guest experience or acquisition instead. That is usually the point where hiring an Airbnb revenue manager starts paying for itself, and where outsourced revenue management consulting replaces a spreadsheet nobody has time to keep current.
How often should I recalculate my Airbnb RevPAR?
Weekly for the raw number, so pricing mistakes get caught while there is still calendar time to fix them, and monthly for a full comparison against the comp set, since comp sets and local demand both shift faster in short-term rental markets than in most hotel competitive sets.
Set a recurring weekly calendar reminder rather than relying on memory, since the comp set itself drifts constantly as new listings launch and others go inactive, and a monthly cadence alone will miss a pricing problem for weeks before it shows up in the numbers.
Conclusion
RevPAR earned its place as the standard hotel performance metric because it forces rate and volume into one honest number, and that same logic holds up reasonably well for a short-term rental, as long as the host remembers everything the number leaves out: ancillary revenue, cost structure, owner-blocked nights, and a comp set that has to be built by hand rather than pulled from a clean, standardized competitive set. 2026's regional data makes the case even more clearly, with RevPAR growth ranging from 6 percent to 16 percent depending on where a property sits, which means the only benchmark worth trusting is the one built from a property's own comp set and tracked on a consistent weekly cadence. The hosts who get the most out of this metric are the ones who treat it as one input next to RevPAN, occupancy, and a clean comp set rather than as a verdict on its own, and who revisit all of it on a calendar cadence instead of waiting for an annual review to notice something has drifted. If building that comp set, reconciling RevPAR against RevPAN, or making sense of a growing portfolio's numbers feels like more than a spreadsheet should have to carry, talk to a revenue strategist about what the data actually says before the next pricing decision gets made on a number that was never measuring what it looked like it was measuring.
Revenue management in the markets in this article
Written by
Revenuenaire ExpertThe Revenuenaire revenue management team: hotel and short-term rental pricing specialists writing practical, data-backed guidance on dynamic pricing, OTA optimization and revenue strategy.


