Plan peak movement with confidence, not guesswork. Adjust speed, step width, and loading instantly here. See practical hourly capacity to support safe flow planning.
This model estimates how many people can ride per hour, based on step spacing and speed.
Use the practical value for design checks, because it reflects real rider behavior.
These sample scenarios show how speed and loading assumptions change throughput.
| Scenario | Speed (m/s) | Pitch (m) | Width (mm) | Persons/step | Occupancy (%) | Efficiency (%) | Theoretical (p/hr) | Practical (p/hr) | Practical (p/min) |
|---|---|---|---|---|---|---|---|---|---|
| Standard mall | 0.50 | 0.40 | 800 | 2 | 70 | 95 | 9,000 | 5,985 | 99.8 |
| Transit peak | 0.65 | 0.40 | 1000 | 2 | 85 | 97 | 11,700 | 9,647 | 160.8 |
| Office lobby | 0.45 | 0.40 | 600 | 1 | 60 | 95 | 4,050 | 2,309 | 38.5 |
| Event venue | 0.60 | 0.40 | 800 | 2 | 80 | 95 | 10,800 | 8,208 | 136.8 |
Escalator capacity matters when you size vertical circulation for stations, malls, and mixed‑use towers. Peak passenger demand is usually expressed as persons per hour per direction. This calculator converts mechanical settings into a comparable throughput number so you can validate whether a single unit or a bank is adequate. It also helps you communicate assumptions early, before cores and openings are finalized.
Speed and step pitch determine how many steps pass a reference point each second. Step width influences whether one or two riders can stand on a step, especially when people carry bags. Occupancy represents how often steps are actually filled, reflecting gaps, hesitation at landings, and uneven arrivals. Manual persons‑per‑step is useful when local behavior reserves one side for walking.
Theoretical values assume every step is fully loaded and the escalator runs continuously. In real operations, stops, safety trips, merging conflicts, and rider behavior reduce sustained flow. The efficiency factor models that reduction, while occupancy captures crowding quality. Together they deliver a practical capacity you can defend in coordination meetings. For planning, many teams test occupancies between 60% and 90% to reflect different crowd disciplines.
Compare the practical capacity against your demand model for each time period. If demand exceeds capacity, consider adding an adjacent escalator, increasing staffing for queue control, or improving approach geometry to reduce hesitation. Verify landing clearances and holding areas so the discharge can spread without back‑spill. Daily capacity is helpful for planning event egress windows, but design checks should focus on peak intervals.
Run multiple scenarios to bracket uncertainty: a conservative case (lower occupancy and efficiency) and a best‑case peak case. Record results in the built‑in history, then export CSV for schedules or cost plans. Use the PDF export as a quick appendix in method statements, traffic studies, or stakeholder presentations. Rerun scenarios after any design revision for traceability.
It assumes every step is occupied and the unit never slows or stops. Use it as an upper bound only, then apply occupancy and efficiency to estimate the sustained practical flow.
Start with observed behavior at similar sites. Conservative planning often uses 60–75% for mixed crowds, while disciplined commuter peaks may reach 80–90%. Test several values to see sensitivity.
Use manual mode when riders commonly stand single‑file, when luggage reduces usable width, or when walking/standing rules limit two‑abreast use. Keep auto mode for early feasibility studies.
Stops, alarms, crowd merging, and landing hesitation reduce throughput even if steps are available. Efficiency captures those operational losses so the practical figure aligns better with real performance.
It is a planning calculator, not a substitute for jurisdictional requirements. Confirm final speed limits, load assumptions, and arrangement rules with applicable standards and the project authority.
CSV supports quick scenario comparison in spreadsheets and dashboards. The PDF creates a clean snapshot of inputs and outputs for meeting minutes, method statements, and design coordination packages.
Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.