Two different questions, two honest tools
“Occupancy” means two things that should never be blended. For a hotel, rental or facility it is a rate: how much of what could have been sold was sold, counted in unit-nights. For a room or venue it is a capacity question: how many people a floor area supports under a code load factor, which this page estimates and clearly labels an estimate, because legal capacity is set by your local code and your exits, not by any calculator.
Disclaimer: This calculator gives estimates for general information only. It is not financial, medical or other professional advice. The capacity mode produces a planning estimate from a published load factor; it is not a legal occupancy limit, a code compliance check or a fire safety determination, all of which belong to your local authority and your building’s actual exits and layout.
What this calculator does
The rate mode answers the property question properly: occupancy counted in unit-nights over a period, with out-of-service units removed from what was available, because a room that could not be sold should not drag the rate down or be quietly left in to flatter it, depending on which story suits the teller. It adds the two figures operators actually steer by (average units filled per night, and revenue per available room when you supply a rate) and a target solver that turns “we want 85%” into the unit-nights that target demands. The capacity mode answers the space question with equal care: an occupant load estimate from a published code load factor, shown next to the same area costed at every other common factor, so you can see how much of the answer is the room and how much is the use you declared for it.
How to use it
- Count in unit-nights, not in snapshots. “We were full on Saturday” is not an occupancy rate. The rate for a period is unit-nights sold divided by unit-nights available, which time-weights everything correctly: a unit filled for 20 of 30 nights contributes 20, whether those nights were weekends or not.
- Decide the out-of-service rule once and keep it. Removing long-term out-of-service units from available raises the reported rate, legitimately, because they were never sellable. Removing a room for one slow night is gaming the denominator. The field here assumes units out for the whole period; consistency over time matters more than the choice itself.
- Occupancy without rate is half a story. A hotel can fill itself by discounting and be worse off. That is why the average daily rate field exists: revenue per available room (RevPAR) combines the two, and a rising occupancy with a falling RevPAR is a warning, not a win.
- Capacity: the factor is the answer’s biggest input. The same 3,000 sq ft room is 600 people standing, 200 at tables and chairs, and 20 as a warehouse. Choose the factor that matches the real use, then read the comparison table to see how sensitive your number is before you print it on a poster.
- Net versus gross area. Some code factors apply to the net room area and some to gross area including corridors and support space. Measure the area the way your factor’s basis expects; mixing a gross factor with a net measurement understates capacity on paper and can overstate the crowd in the room.
How it is calculated
- Available unit-nights = (total units – units out of service) x days in the period.
- Occupancy rate = unit-nights sold / available unit-nights x 100. Vacancy = 100 – occupancy. Average units per night = unit-nights sold / days.
- Room revenue = unit-nights sold x average daily rate. RevPAR = room revenue / available unit-nights, which is the same as ADR x occupancy.
- Target solver: unit-nights needed = target % x available unit-nights, rounded up to a whole unit-night (you cannot sell a fraction), and the shortfall is needed minus sold.
- Occupant load estimate = floor area / load factor, rounded down to a whole person. Square metres are converted at 1 sq m = 10.7639 sq ft before the division, so both unit choices divide by the same published factors.
Worked examples
The hotel month. 120 rooms over 30 days, 5 rooms out of service for the whole month, 2,760 room-nights sold: available is 115 x 30 = 3,450 room-nights, occupancy is 2,760 / 3,450 = 80.00%, and the hotel averaged 92.00 rooms filled a night. At a $150 average rate, revenue is $414,000 and RevPAR is $120.00. A target of 85% needs 2,933 room-nights, so the month fell 173 room-nights short of target: a gap small enough to chase, stated in the units a revenue meeting can act on.
The function room. 3,000 sq ft set with tables and chairs at the 15 sq ft factor: 200 people. The same room as standing space at 5 sq ft would estimate 600, and as chairs-only assembly at 7 sq ft, 428: the comparison table shows all of them, because the honest answer to “how many does it hold” is always “doing what”.
The metric office. 200 sq m is 2,152.78 sq ft; at the business factor of 150 sq ft per person the estimate is 14 people. Offices surprise people here: the code factor is generous because it is gross, covering desks, meeting rooms and circulation, not a measure of how many desks physically fit.
Reading your results
For the rate: judge occupancy against your own target and your break-even, not against a headline average for your city. Eighty percent with strong rates may beat ninety percent bought with discounts, and RevPAR is the line that tells you which happened. If the shortfall figure is small and specific (173 room-nights, about 6 a night), it converts a vague ambition into a staffing and marketing task of a known size, which is the entire point of the solver.
For capacity: read the estimate as the start of a conversation with the rules, not the end of one. Legal occupant load also depends on the number, width and arrangement of exits, on whether the space is sprinklered, on the use classification your local code assigns, and on furniture and layout. Two rooms of identical area and factor can carry different legal limits because one has a second exit. The estimate tells you the scale of the answer; the authority having jurisdiction tells you the answer.
Area alone cannot certify legal capacity. Nothing on this page, and no area calculation anywhere, overrides a posted occupant load, a fire code determination or a local licensing limit. Where a legal figure exists, it governs, even when it is lower than the estimate here, especially then.
Limitations
- Out-of-service is modelled as all-or-nothing (out for the whole period). Units out for part of the period should be prorated by hand into the unit-nights sold and available figures before entering, or the period should be split.
- Load factors are the published IBC values offered as the common reference. Local codes amend them, some uses are classified differently in different editions, and factors for the same use can differ between jurisdictions. The custom factor field exists for the figure your local code actually specifies.
- Egress is not modelled. Exit count, width, travel distance and accessibility decide real legal capacity alongside area; none of them are inputs here, by design, because faking them would be worse than omitting them.
- Revenue figures assume the ADR you enter is the average achieved across the sold nights. A rate that was high on weekends and low midweek still works, because revenue is sold nights times the true average; an aspirational rack rate does not.
Frequently asked questions
How is occupancy rate calculated?
Unit-nights sold divided by unit-nights available, times 100. The unit-night counting is what makes it correct across periods and property sizes: a 10 room inn and a 400 room hotel, a week and a quarter, all reduce to the same honest ratio. The worked example shows the full chain, including the step most quick calculators skip: taking out-of-service rooms out of the available count first.
What is a good occupancy rate for a hotel?
There is no single good number, because occupancy bought by discounting can be worse than lower occupancy at strong rates. Operators therefore judge the pair together through RevPAR, which this page computes when you enter your average rate. As rough context, many full-service hotels run somewhere in the 60 to 80 percent range across a year, with strong seasonal swings; a property should compare itself with its own break-even occupancy and its local competitive set, not with a universal figure.
Can I use the capacity estimate as my legal maximum?
No. It is a planning estimate from a published load factor, useful for comparing layouts, uses and venues at the same honest standard. Legal occupant load is determined under your local code and fire authority, considering exits and layout that a floor area cannot describe, and where a legal load has been posted or issued it overrides any estimate, including this one. The page says this in its results and its disclaimer because the distinction is the whole point of the mode.
Why does the same room get such different capacities?
Because people doing different things need different amounts of room and make different demands on exits. Standing crowds pack at 5 sq ft a person; seated dining needs 15; an office’s 150 is a gross figure covering the whole support ecosystem. A capacity figure without a declared use is meaningless, which is why this calculator makes you declare the use and shows you the alternatives side by side.
Related calculators
Method: occupancy as occupied unit-days over available unit-days; occupant load as floor area over the published load factors of IBC Table 1004.5 (custom factor available), estimates only as defined on this page. Last reviewed: 13 October 2026.