What Is RevPASH and How Do You Use It?
Last updated: April 26, 2026
RevPASH stands for Revenue Per Available Seat Hour, and the formula is simple: take your total revenue for a given period, then divide it by the number of seats multiplied by the number of hours you were open. A 60-seat restaurant that does $3,600 during a five-hour dinner service has a RevPASH of $12. That number — $12 per seat per hour — tells you more about that shift than your total sales figure ever could. The reason that matters is this: two restaurants can both ring $3,600 in a Saturday dinner service, but if one has 40 seats and the other has 100 seats, they are not performing the same. The 40-seat place is running hard. The 100-seat place has a real problem it may not even know about yet. RevPASH makes that visible. Total revenue hides it. What RevPASH actually tells you is how hard your physical capacity is working. A full dining room at the wrong check average, or a dining room that empties out by 7:30 PM, both show up as problems in your RevPASH — even if the night felt busy. That's why operators who use it tend to make better decisions about table management, staffing, menu engineering, and when to run promotions versus when to push turnover. This post covers how to calculate RevPASH correctly (there are two ways, and they serve different purposes), how to break it down by time slot to actually find actionable opportunities, and what to do once you know your numbers. I'll also cover the most common mistake operators make when they first start tracking it. ---
What is RevPASH and how do you use it?
RevPASH (Revenue Per Available Seat Hour) = Total Revenue ÷ (Seats × Hours Open). It measures how efficiently your seating capacity generates revenue over time. A full dining room with a low RevPASH usually means short average checks, fast departures, or too much dead time between turns. Use it by time slot to find where you're losing revenue you should be capturing.
---
The Two Ways to Calculate RevPASH
The standard formula comes from the hospitality management research that Black Box Intelligence describes as one of the most important metrics for measuring seat productivity: Method 1 — Capacity-based: RevPASH = Total Revenue ÷ (Available Seats × Hours Open) Method 2 — Behavioral: RevPASH = Average Check × Seat Occupancy % ÷ Average Dining Duration (in hours) Method 1 is easier to pull from your POS end-of-day report. Method 2 is more diagnostic. It tells you *why* your RevPASH is what it is — because it isolates three separate variables: what people are spending, how full you are, and how long they're staying. If your RevPASH drops on a Thursday night, Method 1 tells you it dropped. Method 2 tells you whether it dropped because fewer tables were seated, because checks were lower, or because tables camped longer than normal. That distinction changes what you do about it. Here's a quick example. Say your 80-seat restaurant runs dinner service five nights a week, 5 PM to 10 PM. Tuesday dinner: $4,800 in revenue. Method 1: $4,800 ÷ (80 × 5) = RevPASH of $12.00. Wednesday dinner: $5,200. RevPASH of $13.00. Not a huge gap. But if you run Method 2 on both nights and find that Wednesday's higher RevPASH came entirely from longer dining times — tables sat an average of 2.5 hours instead of 1.8 — you now know something actionable: Wednesday isn't more profitable because people are spending more, it's more profitable because service slowed down enough to fill the time. That might mean you need to tighten ticket times on Wednesdays, not add a promotion. ---
Breaking It Down by Time Slot
Running RevPASH for the full shift is a starting point. Breaking it down by 90-minute windows is where it gets useful. Most restaurants see a predictable pattern: a slow opening hour, a strong mid-service peak, then a decline as the night thins out. What varies is *how sharp* the decline is and *how long* the trough runs. A restaurant that peaks at $20 RevPASH from 7:00–8:30 PM and drops to $4 RevPASH from 8:30–10:00 PM has a different problem than one that holds $14 from 6:00 PM all the way to close. SevenRooms puts it well: the goal isn't to eliminate variance, it's to understand it well enough to respond intelligently. Your 8:30 PM cliff-drop might mean you need earlier reservation slots, a bar program that keeps people spending after dinner, or tighter pacing in the kitchen so you can seat the next party before 9 PM. To do this analysis without any special software: pull your POS hourly sales report for two weeks. Divide each hour's revenue by the number of available seat-hours in that window (seats × 1 hour). Average them across the two weeks. You'll have a RevPASH curve. Look at where it falls off. That's your first target. ---
---
The Three Levers RevPASH Gives You
Once you know your RevPASH by time slot, you have three levers to pull. Each one operates differently and fits different times of the service.
Lever 1: Table Turnover
During your peak RevPASH window — say 6:30 to 8:30 PM — the goal is to turn tables without making guests feel rushed. The biggest drag on turnover isn't slow eaters; it's dead time: waiting to be greeted, waiting for the check, waiting for the terminal. Toast's analysis of RevPASH optimization points to "payment friction" as one of the most common and fixable sources of lost turns. A table that sits with finished dessert plates for 12 minutes waiting for a check is 12 minutes you can't use. That's real money. One thing that actually works: train your servers to drop the check within two minutes of the last plate being cleared — not when the guest asks, not "in a moment." Two minutes. If you don't want to go full tableside payment, at minimum have the terminal visible and ready.
Lever 2: Average Check
During your slower RevPASH windows — the 5:00–6:00 PM opening, or the post-9:00 PM stretch — turnover pressure is lower. Here the play is spend-per-seat. A $3 cocktail upsell on every table during happy hour doesn't feel pushy because the dining room is half empty and the server has time. But a $3 cocktail upsell across 30 covers at the opening hour of service is $90 you wouldn't have had. Across the week, that's $450. Across the year, that's meaningful. This is also where prix-fixe menus and limited-time early dinner formats pay off. If your RevPASH from 5:00–6:30 PM is $5 and you introduce a three-course early dinner at $38, you can push that window up to $12–$14 depending on how many tables you can fill. That one window change can be worth $30,000 or more in annual revenue on a 60-seat restaurant.
Lever 3: Seat Occupancy During Dead Periods
If your RevPASH is chronically low during weekday lunch or mid-afternoon, the problem isn't the check — it's that seats are empty. No amount of upselling fixes an empty room. Here you're looking at reservations strategy, local business lunch targeting, catering pickup, or even just better curb presence during those hours. This is the hardest lever to pull quickly, which is why it should be the last one you focus on. ---
---
RevPASH vs. Cover Count vs. Revenue: Which to Track?
A lot of operators track covers and total revenue and stop there. The problem is that neither number accounts for time or capacity, so they can mislead you. A Saturday where you do $11,000 on 200 covers looks great until you calculate that you're a 120-seat restaurant running an 8-hour service — meaning your RevPASH is $11.46, which is actually below where you should be. You're busy but not efficient.
| Metric | What It Tells You | What It Hides |
|---|---|---|
| Total Revenue | How much you made | Whether your capacity and time were used efficiently |
| Cover Count | How many guests you served | Whether they spent enough and sat long enough |
| Average Check | Spend per person | Whether your seat capacity is actually earning that average |
| RevPASH | Revenue efficiency per seat per hour | Guest experience quality (use alongside satisfaction data) |
The most useful pairing is RevPASH alongside your labor cost per hour. If your RevPASH during the 5:00–6:00 PM window is $6 but you're staffed at the same level as your $14 peak window, that's a direct labor efficiency problem you can fix with staggered starts. ---
The Most Common Mistake
Operators who start tracking RevPASH sometimes make one consistent error: they try to maximize it by rushing guests. They tighten turn times too aggressively, train servers to push the check, and crowd the room. RevPASH goes up briefly. Then Yelp reviews start mentioning "felt rushed." Then weekend reservations soften. Then RevPASH crashes. RevPASH is a diagnostic tool, not a target you chase at the expense of experience. The goal is to find *inefficiency* — dead time in the service, empty seats during windows that could be filled, low check averages during slow periods — and remove it without touching the guest experience. If you push RevPASH by making people feel like cattle, you've traded short-term efficiency for long-term revenue. ---
Real Kitchen Example: Full-Service Italian, Columbus, Ohio
A 78-seat Italian full-service restaurant in Columbus started tracking RevPASH after the owner noticed Friday revenue was flat year-over-year despite consistently full dining rooms. The calculation revealed that her RevPASH from 8:15 PM to close was $4.10 — a dramatic drop from her 6:30–8:15 PM peak of $17.80. The culprit: late seating. Her 8:00 PM reservations were rarely sat until 8:20 or later, because tables weren't turning in time. That 90-minute window at the end of the night was producing almost nothing. She made two changes: a hard 90-minute suggested dining time communicated at the host stand for prime-hour bookings, and payment terminals brought to the table at dessert so the check-close process took under three minutes. Within six weeks, her Friday closing-window RevPASH moved from $4.10 to $9.60, and total Friday revenue increased roughly $640 per night. That's over $33,000 annualized — from one time slot, two operational changes. ---
People Also Ask
What's a good RevPASH for a casual dining restaurant?
There's no universal benchmark because it depends heavily on your market, price point, and concept. A casual American grill in a mid-size city with a $22 average check should generally target $10–$16 per seat per hour during peak service. If you're consistently below $8 during what should be busy periods, the priority is diagnosing whether the problem is occupancy, check size, or table time — then addressing each one separately.
Should I calculate RevPASH for lunch and dinner separately?
Yes, always. Lunch and dinner have different occupancy rates, different average checks, and different table turn speeds. Combining them into a single daily RevPASH number obscures what's actually happening at each daypart. The most useful unit is the 90-minute time block during each service period. ---
Sources
- Toast POS — How to Maximize RevPASH
- SevenRooms — The Capacity Myth: Why RevPASH Matters More Than a Full Dining Room
- Black Box Intelligence — Revenue Per Available Seat Hour
- Revenue Hub — Grow Your Restaurant Revenue with the RevPASH Formula
- TouchBistro — 10 Essential Restaurant Benchmarks to Measure in 2026
