Virtuosos of Price

Revenue Metrics Explained

Most Airbnb hosts track the number that appears most obviously in their dashboard: how much a booking paid, or whether the calendar is filling up. Both observations are real, but neither one on its own tells you whether your pricing strategy is working. A calendar that fills early every month can mean you are priced too low. A high nightly rate with long gaps between stays can mean you are priced too high. Without a way to hold both facts at once, you are making decisions from half the picture.

The three metrics that let you hold both facts at once are Average Daily Rate (ADR), occupancy rate, and Revenue Per Available Night (RevPAR). They are not complicated, but the relationship between them is where most hosts go wrong. This guide explains each metric, shows you how to calculate it from data you already have, and walks through the decisions each one should and should not drive.

Understanding the Core Metrics: ADR, Occupancy, and RevPAR

Before you can use these metrics together, you need a clean definition of each one. The definitions below use only data that Airbnb's host dashboard already gives you.

Average Daily Rate (ADR) is the average amount you earned per booked night over a given period. It does not include nights the listing sat empty. To calculate it, take your total accommodation revenue for a period (excluding cleaning fees, which are not a rate signal) and divide it by the total number of nights that were actually booked during that same period.

Occupancy rate is the share of available nights that were booked during a period. To calculate it, divide your total booked nights by your total available nights. A night is available if it was not blocked by you for personal use or maintenance. If you block nights for reasons unrelated to guest demand, those nights should be excluded from your available count, or your occupancy figure will understate true demand.

RevPAR stands for Revenue Per Available Night. It is the single number that combines rate and occupancy into one figure. To calculate it, multiply your ADR by your occupancy rate. Alternatively, divide your total accommodation revenue by your total available nights. Both methods produce the same result. RevPAR is the metric that answers the question: across every night this listing could have been earning, how much did it actually earn on average?

A worked calculation

Suppose you want to measure a single calendar month. Pull these three numbers from your Airbnb earnings summary for that month:

1. Total accommodation revenue (the sum of nightly rates paid, not including cleaning fees or Airbnb service fees returned to you)
2. Total nights booked
3. Total nights available (nights in the month minus any nights you personally blocked)

From those three numbers:

• ADR = total accommodation revenue divided by total nights booked
• Occupancy rate = total nights booked divided by total nights available
• RevPAR = total accommodation revenue divided by total nights available

Write these down in a simple spreadsheet, one row per month. After three months you will have enough data to see a direction. After twelve months you will have a seasonal baseline.

Checklist: what to record each month

• Total accommodation revenue (excluding cleaning fees)
• Total nights booked
• Total nights available (personal blocks removed)
• ADR for the month
• Occupancy rate for the month
• RevPAR for the month
• Any pricing changes made during the month and the date they took effect
• Any external events (local festivals, school holidays, construction nearby) that may have affected demand

That last two items matter because a metric without context is just a number. If RevPAR rose in a month when a major local event drove unusual demand, that rise is not repeatable by changing your pricing. Knowing why a number moved is as important as knowing that it moved.

Why ADR Alone Does Not Tell the Whole Story

ADR is the metric hosts most often optimise for in isolation, and it is the one most likely to mislead when read without its companions.

Consider two versions of the same listing in the same month. In version A, the listing earns a high nightly rate and books twelve nights. In version B, the listing earns a lower nightly rate and books twenty-two nights. Version A has a higher ADR. Version B has a higher RevPAR. If your goal is total revenue from the listing, version B outperformed version A, despite the lower rate.

This is not a hypothetical edge case. It is the most common pattern when a host raises rates without adjusting for demand sensitivity. The rate goes up, the calendar thins out, and ADR looks healthy while actual revenue falls.

Where ADR is genuinely useful

ADR is not a useless metric. It tells you:

• Whether your rate strategy is moving in the direction you intended after a pricing change
• Whether your listing is attracting a different type of booking (longer stays at lower rates will pull ADR down even if RevPAR holds steady)
• Whether seasonal rate adjustments are being applied correctly

ADR becomes a problem when it is used as a proxy for success. A rising ADR that coincides with falling occupancy is a warning sign, not a win.

Decision rule for ADR

If your ADR rises in a given month, check occupancy before concluding the change was positive. If occupancy held steady or rose alongside ADR, RevPAR improved and the rate increase was well calibrated. If occupancy fell, calculate whether the higher rate per booked night offset the lost nights. If RevPAR fell despite the higher ADR, the rate increase cost you more than it returned.

Occupancy: More Than Just a Filled Room

Occupancy is the metric hosts most often treat as a goal in itself. A full calendar feels like success. It is not always success.

High occupancy at a rate that is too low for the demand period means you left revenue on the table. If your listing fills completely in the first week of a month that historically draws strong demand, that is a signal your rate was set below what the market would have paid. You cannot go back and reprice nights that already sold.

Conversely, low occupancy is not always a pricing failure. If you blocked a significant number of nights for personal use, your occupancy figure will look low even if every night you offered to guests was taken. This is why cleaning your available night count before calculating occupancy matters.

What occupancy actually measures

Occupancy measures the relationship between supply (nights you made available) and demand (nights guests wanted to book at your price). It does not measure demand alone. If you raise your price and occupancy falls, you do not know from occupancy alone whether demand fell or whether demand held but guests chose a competitor at a lower price. Both produce the same occupancy number.

This is an important limitation. Occupancy tells you the outcome of the supply and demand interaction at your price point. It does not tell you what demand looked like independent of your price.

Checklist: diagnosing an occupancy drop

When occupancy falls month over month, work through these questions before changing your price:

• Did you add blocked nights this month that were not blocked last month?
• Did a competitor listing open nearby at a lower price point?
• Did a local demand driver (event, season, employer) change?
• Did your listing receive a review that may have affected click-through? (Check your listing's review score trend.)
• Did Airbnb make any changes to your listing's status, such as a superhost flag change or a policy flag?
• Did you change your minimum stay requirement, which would reduce the pool of eligible bookings?

Only after ruling out these factors should you treat an occupancy drop as a pure price signal.

Decision rule for occupancy

If occupancy is consistently high across multiple months and your calendar fills well before the arrival date, test a rate increase on future dates only. If occupancy is consistently low and you have ruled out non-price causes, a rate reduction may recover nights, but verify the effect on RevPAR before making it permanent. A rate reduction that recovers nights but reduces RevPAR is only worth making if you have a specific reason to prefer volume over per-night yield (for example, maintaining review frequency to support listing visibility, though the mechanism by which reviews affect visibility is not fully public).

RevPAR: The Combined Picture and Its Pitfalls

RevPAR is the closest thing to a single summary metric for short-term rental performance. Because it accounts for both rate and occupancy, it is harder to game with a one-sided change. You cannot raise ADR and call it progress if RevPAR fell. You cannot fill the calendar and call it progress if RevPAR fell.

That said, RevPAR has its own blind spots.

RevPAR does not account for costs

RevPAR measures revenue, not profit. A listing with a high RevPAR and high cleaning costs, frequent maintenance, or a high platform fee structure may net less than a listing with a lower RevPAR and lower operating costs. RevPAR is a revenue metric. Use it alongside your cost data, not instead of it.

RevPAR does not distinguish between booking patterns

Two listings can have identical RevPAR figures produced by very different booking patterns. One might achieve it through a small number of long, high-rate stays. Another might achieve it through many short, lower-rate stays. The operational load of those two patterns is different. The review frequency is different. The exposure to last-minute gaps is different. RevPAR does not capture any of that.

RevPAR is only comparable to itself over time

Comparing your RevPAR to another host's RevPAR is not meaningful unless the listings are genuinely comparable in location, size, amenities, and available night count. The most useful comparison is your own listing's RevPAR this month versus the same month last year, or this quarter versus last quarter after a pricing change.

Checklist: using RevPAR correctly

• Calculate RevPAR for the same period each year to build a seasonal baseline
• Record the RevPAR figure before and after any significant pricing change, with at least four weeks of data on each side
• Do not compare RevPAR across listings with different available night counts without adjusting for the difference
• Treat a RevPAR figure in isolation as uninformative. It only becomes useful when compared to a prior period or a baseline

Using All Three Metrics for Informed Decisions

The three metrics are most useful when read as a system. Each one answers a different question, and the combination of answers points toward a specific action.

Use this table as a starting diagnostic, not a final answer. Every cell in the "what it suggests" column is a hypothesis to test, not a conclusion to act on immediately.

How to run a pricing test you can actually measure

Changing your price and waiting to see what happens is not a test. A test requires a before period, a change, an after period, and a record of what else changed during both periods.

To run a basic pricing test:

1. Record ADR, occupancy, and RevPAR for the four weeks before the change.
2. Make one change only. If you change your base rate, do not simultaneously change your minimum stay or your discount settings.
3. Record ADR, occupancy, and RevPAR for the four weeks after the change.
4. Note any external factors in both periods (holidays, local events, competitor changes you are aware of).
5. Compare RevPAR across the two periods. If RevPAR improved and no external factor explains the improvement, the change was likely positive. If RevPAR fell, reverse the change or adjust it.

One four-week period is a short window. Seasonal effects can distort it. Where possible, compare the same four-week window across two years to separate your pricing effect from the seasonal effect.

What This Means in Practice

The metrics described above are only useful if you build a habit of recording them. A single month's figures tell you almost nothing. A year of monthly figures tells you your seasonal pattern. Two years tells you whether your pricing strategy is improving your baseline or holding it flat.

Here is a practical operating rhythm that requires less than thirty minutes per month:

On the first of each month, pull the prior month's earnings summary from Airbnb. Record total accommodation revenue, total nights booked, and total nights available (after removing personal blocks). Calculate ADR, occupancy, and RevPAR. Add one row to your tracking spreadsheet.

At the same time, note any pricing changes you made during the prior month and any external factors you are aware of. This context column is the part most hosts skip, and it is the part that makes the numbers interpretable six months later.

Once per quarter, look at the trailing three months as a block. Compare RevPAR to the same three months in the prior year if you have the data. If RevPAR is trending upward over comparable periods, your pricing strategy is working in the direction of higher yield. If it is flat or falling, identify which of the three metrics is driving the trend and use the diagnostic table above to form a hypothesis.

Before making any significant pricing change, record the current state of all three metrics. This gives you a clean baseline to measure against. Without a recorded baseline, you cannot know whether the change helped.

What good record-keeping looks like

A tracking spreadsheet does not need to be complex. The minimum useful version has one row per month and these columns:

• Month
• Total accommodation revenue
• Nights booked
• Nights available
• ADR
• Occupancy rate
• RevPAR
• Pricing changes made this month
• External factors noted

That is nine columns. You can build it in ten minutes and maintain it in five minutes per month. The value compounds over time as the dataset grows.

A note on cleaning fees and their effect on ADR

Cleaning fees are not part of your nightly rate and should not be included in your ADR calculation. However, they do affect booking conversion, because Airbnb displays total trip cost to guests. A listing with a low nightly rate and a high cleaning fee may show a high total cost for short stays, which can suppress bookings for one and two-night reservations. If your occupancy is low and your stays are predominantly short, check whether your cleaning fee is disproportionate to your nightly rate for those stay lengths. This is a presentation issue, not a rate issue, but it will show up in your occupancy figures if it is suppressing short-stay bookings.

Related Articles

• How to read your Airbnb earnings summary
• Setting a minimum stay: when it helps and when it costs you bookings
• Seasonal pricing: building a rate calendar from your own data
• Cleaning fees and total trip cost: what guests see before they book

Where this becomes someone else's job

Tracking these metrics yourself is achievable. Acting on them consistently, across multiple listings or across a busy season when you have other demands on your time, is where the system tends to break down. If you find that you are recording the numbers but not acting on them, or acting on them without a clear process, that is the point at which a managed service changes the outcome.

Revande offers two products for hosts at this stage.

Performance gives you a full software stack for dynamic pricing with daily adjustments made by experienced rate strategists, Airbnb listing performance monitoring, and email alerts when visibility or booking conversion falls below expected levels, plus monthly reports so you have a record of what changed and why.

Maestro includes everything in Performance and adds done-for-you listing optimization. Proactive Airbnb listing performance monitoring means that visibility and booking conversion issues are not just flagged to you but handled for you. Maestro works with Airbnb directly or with your existing channel manager, and includes ongoing listing refinements as the platform and your market evolve.

The difference between the two is not the quality of the monitoring. It is who does the work after the data identifies a problem.