The host problem
A one-night booking at $120 produces $120 in accommodation revenue. It also triggers a full turnover — cleaning labor, supplies, restocking, time cost, and coordination. If turnover costs $100, that one-night booking nets $20 before any other expense.
A two-night booking at $100 per night produces $200 with one turnover. After the same $100 cost, it nets $100.
RevPAR does not show you this. Net RevPAR does. This calculator runs the math before you set your minimum-stay rules.
What the tool helps you decide
The calculator answers two questions:
- What does each booking actually cost me after turnover, expressed as a drag on every occupied night?
- Does my current minimum-stay rule protect Net RevPAR, or does it allow short stays that undermine it?
Inputs required
- Live Accommodation Revenue: total accommodation charge from live bookings in the period (exclude cleaning fees, taxes, platform fees)
- Available Nights: calendar nights the listing stayed open and bookable
- Live Booked Nights: total occupied nights from surviving bookings
- Live Bookings: count of reservations that produced booked nights
- TCP — Turnover Cost Proxy: the total cost of one cleaning turnover, including labor, supplies, restocking, and your time estimate
The STR Signals canonical TCP is $174 per booking. Use that figure if you have not benchmarked your own. If your actual cleaning cost, supply cost, and time value differ materially, re-benchmark before relying on the output.
Outputs produced
- RevPAR = Live Accommodation Revenue ÷ Available Nights
- Turnover Drag per Occupied Night = (Live Bookings × TCP) ÷ Live Booked Nights
- Net RevPAR = RevPAR minus Turnover Drag per Occupied Night
- ALOS = Live Booked Nights ÷ Live Bookings (shown as context)
The gap between RevPAR and Net RevPAR is the cost your minimum-stay structure either controls or fails to control.
Example
A host logs a month with the following numbers: $3,600 accommodation revenue, 30 available nights, 24 booked nights, 8 bookings, TCP of $174.
- RevPAR = $3,600 ÷ 30 = $120
- ALOS = 24 ÷ 8 = 3 nights per booking
- Turnover Drag per Occupied Night = (8 × $174) ÷ 24 = $58
- Net RevPAR = $120 minus $58 = $62
Now the host runs an alternative scenario: if the same $3,600 revenue came from 4 bookings instead of 8, ALOS rises to 6, turnover drag drops to $29, and Net RevPAR rises to $91. The difference is $29 per available night — without changing the rate.
That gap is what minimum-stay rules protect.
What most hosts get wrong
Most hosts benchmark turnover cost by cleaning fee alone. Cleaning fees reimburse the cleaner. Your actual TCP includes supplies, restocking (toiletries, coffee, small consumables), and the coordination cost of scheduling and confirming each turnover. If you manage your own cleaning, include an honest estimate of your time at a reasonable hourly rate.
The second mistake is treating a full calendar as success without checking ALOS. Eight one-night bookings that fill 24 nights look similar to four three-night bookings on the surface. Net RevPAR shows the difference.
How to use it this week
- Pull last month’s accommodation revenue, available nights, booked nights, and booking count.
- Enter your TCP — use $174 if you have not benchmarked your own.
- Calculate Turnover Drag per Occupied Night and Net RevPAR using the formulas above.
- Run the same calculation with a hypothetical lower booking count (longer ALOS) and see how Net RevPAR changes.
- Compare the result to your current minimum-stay setting and decide whether the rule is protecting Net RevPAR.
Connected articles
- Net RevPAR and Turnover Drag
- Why Short Airbnb Stays Might Be Costing You More Than You Think
- ALOS Explained for Airbnb Hosts
- When to Reshape Minimum Nights Instead of Cutting Price
- Airbnb Minimum Stay Strategy
Educational note
This page is educational. It is not tax, legal, investment, or guaranteed-income advice.