RevPASH shows how much revenue each available seat hour generates. That makes booking windows, weak hours and differences between locations visible. Alongside average spend and sales per labor hour, RevPASH is one of the KPIs every operator should know, with formulas.
The example below works with an increase from €8.40 to €10.00 RevPASH. That's around 19% more revenue per available seat hour, but it is a scenario calculation, not a measured promise. Whether that potential is achievable depends on demand, opening hours, dwell time and service capacity, among other things.
Simply by making better use of the capacity you already have.
Most restaurant operators know whether their place was "full". Few know whether it was efficient. That's the difference between gut feeling and controlling table utilization.
Contents
- What is RevPASH and why should you know it?
- Calculating RevPASH: formula and example
- Reference values: what is a good RevPASH?
- Five levers for better table utilization
- Managing dwell time without rushing guests
- Conclusion: table utilization is management
What is RevPASH and why should you know it?
RevPASH stands for Revenue per Available Seat Hour.
The metric originally comes from the hotel industry (RevPAR), but was adapted for restaurants and is today the most precise indicator of table utilization efficiency.
The basic idea: a table has limited capacity — not just in seats, but in time. A restaurant with 60 seats that is open for four hours in the evening has 240 available seat hours. What is each of those hours worth?
That's the question RevPASH answers. And the answer shows you where your real revenue potential lies.
Why is this better than simple occupancy?
"We were 90% full tonight" sounds good. But if that 90% hit you within 30 minutes and the room was empty afterwards, your RevPASH is still low. And if your guests sat for three hours even though they were finished after two, that costs money.
RevPASH combines both: how full you were and how long guests stayed.
Calculating RevPASH: formula and example
The formula:
RevPASH = net sales / (number of seats × opening hours)
A concrete example: a restaurant with 50 seats, Friday evening, 5 opening hours (18:00–23:00), net sales of €2,100.
RevPASH = 2,100 / (50 × 5) = 2,100 / 250 = €8.40
What does this number tell you? Every available seat hour brought in €8.40. That's your starting point.
Now you can set targets. What if you reached €10.00 per available seat hour?
10.00 × 250 = €2,500 — €400 more, every Friday evening. Over 50 Fridays a year: €20,000 of additional sales. Without a single new guest.
Breaking RevPASH down by hour
Even more revealing: calculate RevPASH per hour. It shows when your restaurant really performs and when it doesn't.
Same Friday evening, hour by hour:
| Time | Sales | RevPASH |
|---|---|---|
| 18:00–19:00 | €180 | €3.60 |
| 19:00–20:00 | €520 | €10.40 |
| 20:00–21:00 | €640 | €12.80 |
| 21:00–22:00 | €510 | €10.20 |
| 22:00–23:00 | €250 | €5.00 |
The pattern is clear: 18:00–19:00 is weak, 20:00–21:00 is the sweet spot. Why is the first hour so weak? Is it booking management? The timing of the first covers? Those are the questions RevPASH raises.
Reference values: what is a good RevPASH?
The range is wide and depends heavily on business type and price level. Orientation values for Germany in 2026:
Quick service / fast casual: €12–18 RevPASH High table turnover, short dwell times, standardised processes. If you're below €10 here, you have a process problem.
Casual dining: €8–14 RevPASH The typical range for upmarket bistros and mid-range restaurants. Good operators are above €11.
Fine dining: €15–30 RevPASH Long dwell times are offset by very high average spend. Here, table turnover isn't the goal — spend per cover is the lever.
The point isn't to hit the benchmark of a different business type. The point is to know your own benchmark and improve it systematically.
If your RevPASH is €4.20 on Monday and €11.80 on Friday — what separates the two days? That's the question that leads to real improvements.
Five levers for better table utilization
Lever 1: Spread bookings more evenly
The biggest problem in most restaurants: everyone comes at 19:30. Then it's packed, service is stressed, the kitchen is at its limit — and by 21:30 the room is empty.
The solution is active yield management for bookings. Concretely: make low-RevPASH hours (18:00–19:00) more attractive with small incentives — a glass of aperitif, earlier access to a good table. Overloaded hours could be priced slightly differently.
A seemingly small effect: if you move 10% of your Friday evening bookings from 19:30 to 18:30, RevPASH in the 18:00–19:00 hour rises noticeably — and you avoid bottlenecks at the peak.
Lever 2: Improve table turnover
Table turnover isn't the same as rushing guests. It's about reducing idle time.
Typical idle time between two covers: 12–18 minutes. Clear the table, clean it, reset it, then wait until the guests are seated. With a structured handover process, this time can be cut to 6–8 minutes.
What that delivers: for a restaurant with 20 tables, 1.8 cover changes per table per evening and a time saving of 7 minutes per change: 252 minutes less idle time per evening. Spread over 50 relevant evenings a year: 210 hours — with an average spend of €45, around €9,450 of potential additional sales.
Lever 3: Optimise table allocation
Not every table is equally efficient. A two-top that is always seated with pairs is efficient. A four-top regularly occupied by pairs loses 50% of its capacity.
Look at how often which tables are occupied by how many people. Then ask: how could you adjust booking allocation?
A different table allocation can increase usable capacity if group sizes and table combinations don't match today. The effect has to be calculated from the specific business's booking and occupancy data.
Lever 4: Increase spend per cover
RevPASH can also be raised through higher spend, not just more cover changes.
The simplest levers: drink recommendations with the food, a dessert recommendation as standard rather than an option, an aperitif offer when guests are seated. Sounds trivial — in practice it depends entirely on training and expectations in service.
If every server in your restaurant generates an average of €0.80 more in drinks sales per cover, and you do 80 covers an evening: €64 per evening, over 365 opening evenings €23,000 a year.
Lever 5: Measure and manage dwell time
What you don't measure, you can't manage. That applies especially to dwell time.
Average dwell time in German casual dining restaurants is 68–82 minutes per cover. If you don't know your own value, start measuring it now.
You don't need an expensive system. A simple sample of 20 tables a week, noting the time seated and the time paid, is enough for a reliable number.
Managing dwell time without rushing guests
This is the most common worry: "If I shorten dwell time, I'll rush my guests."
That's wrong — if you do it right.
The goal isn't to get guests out sooner. The goal is to cut unnecessary waiting: the ten minutes when the bill doesn't come even though the guest is already looking for it. The 15-minute gap between main course and dessert offer that nobody actively created.
Three concrete measures:
Ask about dessert proactively — don't wait for the guest to ask. Straight after the main course: "Would you like to see something sweet?"
Prepare the bill — as soon as it's clear a table has finished, prepare the bill and offer it at the next contact. Don't wait to be explicitly asked.
Communicate table timing — if you have a booking system, gently communicate table availability. "We have another booking for this table from 21:30 — that shouldn't be a problem for you, I just wanted to mention it." Most guests respond respectfully.
Whether these measures change dwell time depends on concept, demand and service flow. Measure the value before and after the change, and check guest feedback and average spend in parallel.
Conclusion: table utilization is management
A restaurant isn't an art gallery — it's a space with limited capacity and limited time. Every hour a table isn't optimally occupied is a loss you can't recover. If your sales fall despite unchanged opening hours, the step-by-step diagnosis in restaurant sales decline helps.
RevPASH gives you a number that quantifies this. And numbers you know, you can improve.
Three steps for this week:
Calculate RevPASH for last Friday — POS sales divided by (seats × opening hours). What's your value?
Break RevPASH down by hour — which hour performs, which doesn't?
Pick one lever — not all five at once. Start with idle time between cover changes. It's quick to measure.
Kiosa calculates RevPASH automatically from your POS data — daily, per location, with trend comparison. In 15 minutes you'll see where your table capacity really stands.
Related terms
- Table utilization — occupancy rate of available seats
- RevPASH — revenue per available seat per hour
- Average spend — average revenue per guest or transaction
- Dessert rate — share of guests who order dessert
From analysis to action
What this is about: calculating RevPASH and managing capacity with a scenario calculation.
Put it into practice: Analyse RevPASH in Kiosa One View