What is a good RevPAR? How to benchmark your hotel

You pull up this month's RevPAR — $84 a night, say — and it tells you nothing on its own. Is $84 good? Most guides that promise an answer to what is a good RevPAR hand you a dollar range that sounds authoritative and falls apart the second you check it against your own market. RevPAR only means something sitting next to a comparable hotel's number, which is why the honest answer isn't a figure. It's a ratio — and building your own is more doable than the STR-report price tag makes it look.

Why There's No Universal "Good RevPAR" Number

Ask ten owners what counts as a good RevPAR and you'll get ten different numbers, and all ten could be right — for their hotel. A 40-room roadside property in a small secondary market and a 200-room hotel three blocks from a convention center aren't playing the same game, and pricing them to the same benchmark makes no sense.

Segment matters as much as location. An economy limited-service property and an upper-upscale full-service hotel post very different RevPAR even when both are performing exactly as they should, because their rate ceilings, cost structures, and guest expectations are built differently on purpose. Season adds a third variable: a beach property's July RevPAR and its February RevPAR aren't the same benchmark, and comparing across them tells you about the calendar, not your management.

Any article, tool, or consultant handing you a flat "aim for $X RevPAR" number is skipping the question that actually matters: X, compared to what?

What Is RevPAR, and How Is It Different From ADR?

Start with the formula. RevPAR — revenue per available room — is total room revenue divided by every room you had available to sell, occupied or not. You can also get there by multiplying average daily rate by occupancy: a hotel running a $200 average rate at 50% occupancy posts $100 RevPAR, the identical number a hotel running a flat $100 rate posts by selling every single room.

ADR — average daily rate — only counts the rooms you actually sold. That's the distinction that trips people up: ADR can climb steadily while RevPAR stays flat or drops, because RevPAR penalizes empty rooms and ADR doesn't notice them at all. Push your rate up 10% and lose 12 points of occupancy chasing it, and RevPAR just moved backward while the ADR chart looked great in the owner's meeting. That's why RevPAR, not ADR, is the number worth anchoring a benchmark to — it can't be flattered by rate alone.

The Honest Benchmark: Your RevPAR Index

The number that actually answers "is my RevPAR good" isn't a dollar figure — it's the RevPAR Index, sometimes called RGI (Revenue Generation Index). It's your RevPAR divided by the average RevPAR of a defined group of comparable hotels — your competitive set — multiplied by 100.

An index of 100 means you're capturing exactly your fair share of that competitive set's business, nothing more and nothing less. An index above 100 means you're outperforming the set: an RGI of 115 means you generated 15% more RevPAR than the set's average. Below 100 runs the other way — an RGI of 88 means you captured 12% less than your fair share, even if the raw RevPAR number looks perfectly respectable sitting on its own.

This is the framing hotels pay for when they buy an STR (STAR) report, the industry's standard benchmarking data. It answers "good compared to what" with math instead of a guess. The tradeoff is access: a full STR subscription usually means submitting your own performance data into the pool and paying for the privilege, which is a harder line item to justify for a 30-room independent than for a 300-room flagged property with a revenue team already built around reading it.

How to Build Your Own RevPAR Index Without an STR Subscription

If a full subscription isn't in the budget yet, or you want a number sooner than the next report cycle, you can build a rough version yourself. It won't carry STR's precision — you're sampling public rates instead of pooled actuals from every hotel in the set — but tracked consistently, it shows you direction, and direction is usually the part you're actually deciding on.

1. Pick five or six true comp-set hotels. Same class, similar size, genuinely fighting you for the same guest — not the aspirational property two tiers up the street. Building an accurate comp set is worth doing properly once; a stretched comp set makes every number downstream meaningless.
2. Sample their public rates more than once. Check each hotel's rate for the same future date, same room type, same length of stay, across a mix of weekday and weekend dates spread over two or three weeks. One Tuesday snapshot tells you nothing; six data points across different demand days start to look like a pattern.
3. Average what you collect into a proxy ADR, and note whenever a comp-set hotel shows "sold out" or heavily restricted availability — that's your only free occupancy signal, so use it. A hotel selling out at a high rate is telling you more than one sitting wide open at the same rate.
4. Calculate your own RevPAR the normal way: room revenue for the period divided by available room-nights.
5. Build the ratio. Your RevPAR divided by your proxy comp-set average, times 100. Track it the same way each month so the comparison holds up over time.

The number won't match what a real STR report would show — public rates aren't booked rates, and you're missing true occupancy on the other side. What it will show is trend: whether the gap between you and the market is widening or closing, month over month. For a lot of independent decisions, that's the more useful question anyway.

What to Do When Your Index Is Below 100

If you're here because you want to improve RevPAR rather than just diagnose it, the fix depends on which side of the ratio is actually broken — and a low index has two possible causes that call for opposite responses.

It might be a rate problem. Your occupancy is competitive but your ADR trails the set, meaning you're filling rooms at a discount relative to the market. This is usually fixable in the booking engine: tighter parity across channels, less reliance on OTA-only discounting, and a hard look at what commission you're handing an OTA on every third-party sale versus what a direct booking actually nets you.

Or it might be an occupancy problem. Your rate sits right in line with the set but rooms are going unsold, which points at distribution visibility, guest reviews, or a genuine product gap — dated rooms, a renovation two doors down, a new entrant with sharper amenities at your price point. No amount of rate discipline fixes an occupancy problem; discounting into weak demand just drags ADR down without moving the room count.

Pull ADR and occupancy apart before you touch pricing. A single blended RevPAR number can't tell you which problem you have — only the two components, looked at separately, can.

Make It a Habit, Not a One-Time Check

A RevPAR index calculated once answers one week's question. The value shows up when you track it consistently enough to see the line move — a rival undercutting rate, a renovation up the street pulling the set's average up, a slow month that isn't actually a market-wide slow month. That's a monitoring habit, not a monitoring event, and it's the easiest habit to drop during the exact season you have the least time and the most reason to keep it.

The Intel Club is built for owners who want that kind of ongoing market read without owning the checking themselves. Membership is $99/month with a 7-day trial, and a daily briefing folds competitor and market movement into a short morning read instead of a number you have to remember to go pull. A boutique hotel's daily intelligence briefing walks through what that looks like morning to morning, and the hotels page covers what a briefing watches for a property like yours more broadly.

Either way, stop asking whether $84 is a good number sitting by itself. Ask what it's sitting next to — and check that ratio on a schedule, not just the week a competitor's price catches your eye.