ADR, Occupancy, and RevPAR: The Three Numbers That Actually Matter

The three metrics, defined plainly

• ADR (Average Daily Rate): the average nightly price actually collected across booked nights in a given period. It's not the listed nightly price — it's what guests actually paid, averaged, including any discounted or premium nights.
• Occupancy rate: the percentage of available nights that were actually booked. A property available 365 nights a year that was booked for 200 of them has a 55% occupancy rate for that period.
• RevPAR (Revenue Per Available Room/Rental): ADR multiplied by occupancy rate. It expresses revenue per available night rather than per booked night, which makes it useful for comparing properties with different occupancy patterns on equal footing.

Annual revenue is, at its simplest, ADR × occupied nights — or equivalently, RevPAR × total available nights. Every projection you'll ever see is some version of this same multiplication, just presented with more or less detail about the assumptions behind each factor.

It's worth being precise about what "available nights" actually means, since it isn't always simply 365. A night the owner blocked off for personal use, a night taken offline for maintenance, or a night the property wasn't actively listed all reduce the denominator in an occupancy calculation. Two properties can have identical booked-night counts and very different occupancy rates, purely because one had more nights genuinely available to book in the first place.

Why looking at all three catches things the headline number hides

Two properties can land on the identical annual revenue total while getting there in very different ways — one through a high rate and thin occupancy, the other through a lower rate and near-constant bookings. Neither approach is automatically better, but they carry different risk profiles: a high-ADR/low-occupancy property is more sensitive to losing just a handful of bookings, while a high-occupancy/low-ADR property is more sensitive to rate compression across the whole market.

This is exactly why a single annual revenue number, on its own, tells you less than it seems to. A revenue total that looks solid on the surface might be resting on an occupancy assumption that's genuinely difficult to sustain, or an ADR that only a handful of comparable properties are actually achieving. Breaking the number back down into its two components is the fastest way to spot whether the underlying assumptions are the kind that hold up in a normal year or the kind that only work in an unusually strong one.

How to use this when reviewing any projection

Whenever you're given an annual revenue figure, ask for the ADR and occupancy assumptions behind it before accepting the total. An occupancy rate that looks unusually high for the market, or an ADR that looks unusually high for the property type and comp set, is a specific, checkable claim — far easier to evaluate than a single opaque annual number.

A useful habit is to picture the calendar itself rather than just the percentage. An occupancy rate translates directly into a number of booked and unbooked nights across the year — visualizing it that way often makes an unrealistic assumption more obvious than staring at a percentage alone. It's one thing to see "70% occupancy" on a page; it's another to picture roughly eleven unbooked nights in an average month and ask whether that actually matches what you'd expect for the property and location in question.

The same habit works well for ADR. A single annual average nightly rate hides the fact that a property likely has a genuine peak-season rate, a genuine off-season rate, and something in between during shoulder months. If a projection only shows you one blended ADR figure, ask whether it's a true average across a realistic seasonal curve or whether it's implicitly anchored to a stronger part of the year. The same underlying number can be produced by very different rate curves, and the curve itself is often the more informative thing to understand.