How wait times work
What the posted number means, and how to actually use it.
Every number on this site is a posted wait time: the estimate the park itself publishes at the ride entrance and in its app. Understanding what that number is - and is not - makes it far more useful.
Posted vs. actual
Posted times are produced by the park operations team from ride throughput and queue length, and parks generally prefer to overstate them: a guest who waits less than the sign said is a satisfied guest, and an inflated posted time also thins demand for a ride the park needs to manage. Independent measurements across the industry consistently find actual waits run below posted ones for most of the day, with the gap widest at posted peaks. This site publishes the posted number and labels it as such, because that is the number that actually steers crowds.
Why waits move the way they do
Waits build through the morning as arrivals stack up, peak early afternoon, and fall through the evening as families leave - the shape you will see in the typical-day charts on park pages once our tracking covers a few days. Rides go down and come back; when a headliner reopens, its queue absorbs demand and nearby waits dip. Parades and shows pull crowds off rides for an hour at a time.
How to use the numbers here
Use the live board to decide what to ride next; use the typical-day curve to decide when to arrive; use the best-hour note on a ride page to plan a headliner. And always check the park's official app for operational announcements - a posted time cannot tell you a ride is about to close for weather.
What this site will not tell you
We do not predict future crowds, sell touring plans, or estimate actual (as opposed to posted) waits - we publish measured history and live posted numbers, each labelled with its time. When a section on this site is computed from our own tracking, it says how many days of data are behind it.