What Is RevPASH? Revenue Per Available Seat Hour Explained

RevPASH is short for revenue per available seat hour. It tells you how much revenue each seat in your dining room produces for every hour you keep the doors open — counting empty seats and full ones alike. Divide your revenue by the number of seat-hours you had available to sell, and you get a single dollar figure that measures how efficiently you turn physical capacity and time into money.

Here is why that matters more than it first appears. Most operators judge a night by one of two numbers: how many times the tables turned, or what the average check came to. Both are half-truths. Turnover ignores how much each party spent and how many seats sat empty at 6:15. Average check ignores whether the room was full or a ghost town. RevPASH refuses to let either blind spot survive, because it folds occupancy, check size, and speed of service into one metric that hotels have used for decades and that Cornell's hospitality researchers formalized for restaurants years ago.

Think of your restaurant not as a set of tables but as a fixed inventory of seat-hours that expire the moment they pass. A 100-seat room open five hours has exactly 500 seat-hours to sell tonight, and any one it does not sell is gone forever, exactly like an empty airline seat at takeoff. RevPASH is how you measure whether you are selling that perishable inventory well. Below is the formula, a worked example, honest benchmarks, and the three levers that actually move the number.

The RevPASH Formula, Worked Through Once

The math is refreshingly simple, which is part of why the metric is so useful:

RevPASH = Revenue ÷ (Number of seats × Hours of operation)

The denominator — seats multiplied by hours — is your available seat-hours, the total inventory you had to sell. Say a 100-seat restaurant is open for a five-hour dinner service and rings $6,000 in food and beverage. That is 100 × 5 = 500 available seat-hours, so RevPASH is $6,000 ÷ 500 = $12.00. Every seat, on average, earned twelve dollars per hour of that service.

The number only means something when the inputs are honest. Two rules keep you out of trouble:

• Count the seats you actually operate. If you have 120 chairs but staff and open only 100 on a Tuesday, your denominator is 100. Padding it with seats you never intended to sell will quietly depress a RevPASH that is actually fine.
• Use the hours you were genuinely open for that revenue. If lunch runs 11 to 2 and dinner 5 to 10, do not blend the dead 2-to-5 stretch into a single all-day figure — it drags the average down and hides where the real problem is. Measure dayparts separately, then roll them up.

Why the "available" in the name is the whole point

Plenty of operators track revenue per occupied seat or per cover, and that is a different, less demanding number. RevPASH deliberately uses available seat-hours in the denominator so that an empty seat counts against you. That is the design choice that makes it honest. A dining room that is packed for ninety minutes and dead for the other three and a half hours will post a mediocre RevPASH, and it should — because you paid rent, utilities, and a scheduled staff for all five hours, not just the good ninety minutes.

RevPASH vs. Turnover vs. Average Check: Three Views of One Night

The fastest way to understand RevPASH is to watch it catch what the other two metrics miss. Each answers a different question, and only RevPASH answers the one that pays the bills.

Picture two Fridays at the same 100-seat restaurant. On the first, tables turned 2.5 times on a $48 average check — impressive on paper. But service dragged, and each party held a four-top for two full hours, so at any given moment a third of the seats sat idle waiting on kitchen tickets. On the second Friday, turnover was an identical 2.5 and the check dipped to $45, yet tighter pacing kept seats occupied and cut dead time between parties. The second night's RevPASH came out higher despite the lower check, because the seats were working more of the time. Turnover and check average both told you the first night won. RevPASH told you the truth.

What Counts as a Good RevPASH in 2026

Here is the honest answer operators rarely get: there is no universal RevPASH benchmark, and anyone who quotes you one without asking about your seat count and price point is guessing. The metric scales with your average check and your service model, so a white-tablecloth room and a counter-service concept live in different universes. Rough, real-world ranges look like this:

1. Fast-casual and quick-service: roughly $8–$14 per seat-hour. Lower checks, but seats churn fast and hours are long.
2. Full-service casual dining: roughly $10–$18. The broad middle, where pacing and check-building both matter.
3. Upscale and fine dining: roughly $18–$30 or higher. Slow turns, but a high check and often a beverage program carry the number.

Treat those bands as loose orientation, not targets. The comparison that actually earns you money is your restaurant against its own history, and specifically your peak-hour RevPASH against your off-peak RevPASH. If your 7 p.m. hour runs $22 and your 5 p.m. hour runs $6, you have just located a large, recoverable pool of revenue — not by working the packed hour harder, but by filling the empty one. That same "compare against yourself, not a stranger" discipline is what makes comp sales a trustworthy growth signal, and it applies just as forcefully here.

The Three Levers That Actually Move RevPASH

Because RevPASH is revenue over seat-hours, only three inputs can change it, and every tactic you will ever try rolls up into one of them. Naming them keeps you from chasing motion that feels productive but doesn't move the number.

1. Occupancy — fill more of the seat-hours you already have

This is almost always the highest-return lever, because empty seats are pure lost inventory. Reservations and waitlist management smooth demand into your slow windows; targeted promotions pull traffic into the 3 p.m. valley; and even modest events — a trivia night, a prix-fixe early seating — convert dead seat-hours into paid ones. Since RevPASH is measured by hour, the math strongly favors attacking your weakest daypart rather than your busiest. Getting your softest hours right is the same problem as staffing to actual hourly demand — both start from knowing exactly when your seats sit empty.

2. Check average — earn more from each occupied seat-hour

With the seat filled, the question becomes how much it produces. Menu engineering that steers guests toward high-margin dishes, disciplined upselling of appetizers and beverages, and thoughtful menu design all raise the numerator without touching the denominator. A beverage program is often the single biggest lever here, because a well-run bar can add several dollars of RevPASH across the whole room without slowing a single table.

3. Dining duration — recover the dead time between parties

This is the most misunderstood lever, and the one operators most often get wrong. The goal is not to rush guests — a hurried meal lowers checks and kills repeat visits. The goal is to shrink the non-dining time: the gap between a table clearing and the next party sitting, the wait for a check drop, the ticket that took eleven minutes to fire. Shave five minutes of dead time off each seating and you have effectively added inventory without adding a single chair. Improving these turns is where RevPASH and table turnover optimization reinforce each other — done right, you serve more parties and each one enjoys an unrushed meal.

How to Start Tracking RevPASH This Week

You do not need new software to begin — a POS export and a spreadsheet will get you a first read in an afternoon. The sequence:

1. Fix your seat count honestly. Use the seats you actually staff and open, not the fire-code maximum. If it varies by day, record it per day.
2. Pull net revenue by hour. Export sales in hourly buckets for the same period, using net revenue — after discounts and comps — so the number reflects real money earned.
3. Compute RevPASH per hour, not just per shift. Divide each hour's revenue by that hour's available seat-hours. The per-hour view is where the insight lives; the blended shift number mostly hides things.
4. Chart the day and hunt the valley. Plot RevPASH across the operating day and find your weakest hours. That valley is your opportunity, quantified in dollars.
5. Re-measure after every change. Ran an early-evening promotion? Check whether the target hour's RevPASH actually rose. This is the same close-the-loop habit behind every reliable forecast, which is why it pairs naturally with disciplined sales forecasting methods.

Doing this by hand is illuminating the first time and tedious every time after, because the joining of hourly revenue to hourly seat inventory is exactly the kind of repetitive assembly software should own. Everything the calculation needs — timestamped tickets, net sales, cover counts — already sits in your point-of-sale data. KwickView keeps RevPASH current by hour, section, and day of week on top of your KwickOS POS, and operators on a third-party register can get the same seat-hour view through the reporting app that layers on top of an existing POS. For context on where a healthy RevPASH should land alongside your other margins, the profitability benchmarks restaurants are hitting in 2026 are a useful companion read.

Where RevPASH Can Mislead You

No single metric is complete, and RevPASH has real blind spots worth naming so you don't over-trust it:

• It says nothing about profitability. A high RevPASH built on discounted, low-margin volume can be less profitable than a lower RevPASH on full-price checks. Read it beside food and labor cost, never alone.
• It can reward over-seating. Cramming in seats raises capacity but can wreck the guest experience and long-run repeat business. RevPASH will applaud a decision your guests quietly punish.
• It is only as honest as your seat and hour inputs. Sloppy denominators — counting seats you never opened, or hours you were barely staffed — produce a number that feels precise and isn't.
• It flattens the outlier. A whole-service RevPASH can hide one brilliant section and one dead one, which is why section-level and hourly views matter more than a single daily figure.

Used with those caveats in mind, though, RevPASH earns its place as the best single scoreboard for how well a restaurant converts its most perishable asset — a seat and an hour — into revenue. It belongs on the short list of KPIs every owner should track, right next to prime cost and comp sales.

Frequently Asked Questions