How Ride Ready's wait-time data works
Every number on our park pages, strategy guides and crowd calendars comes from posted wait times we collect ourselves. This page covers where they come from, how we turn them into typical waits and crowd levels, and where they fall short.
These pages are generated from the data each night. Code builds the park pages, hourly wait tables and crowd calendars, and nobody edits the numbers by hand. The written guides are by Kevin Schneider.
What we collect
While a park is open, we read each ride's posted standby wait and its status (open, closed or down) from the park's public queue data every few minutes.
The same readings drive the app and a public feed at cdn.rideready.app/public/waits/, which the live boards on our park pages read.
Our own collection at the four Walt Disney World parks is recent, so their older history comes from an archive of the same posted waits.
What we don't collect:
- How long people actually wait. A posted wait is the park's own estimate. The real wait can be shorter or longer.
- Anything about park guests. No user reports, locations or accounts feed the numbers on these pages.
Coverage
The table shows how much history sits behind each park. Readings counts every posted wait above zero we hold for that park. Crowd history is the month of the first measured day on the park's crowd calendar. Seasonal parks only add readings on days they're open. The last two columns are the day-of-week check explained under The forecast.
Data through November 8, 2026, from the nightly feeds built that morning between 5:00 and 5:28 AM ET. This table is a snapshot. Each park page carries its current numbers.
| Park | Readings | Crowd history from | Days checked | Within 1 level |
|---|---|---|---|---|
| Animal Kingdom | 179,194 | Jan 2025 | 120 | 48% |
| Busch Gardens Tampa Bay | 751,744 | Jun 2022 | 120 | 49% |
| Busch Gardens Williamsburg | 386,833 | Jul 2022 | 90 | 49% |
| Canada's Wonderland | 582,942 | Jun 2022 | 87 | 33% |
| Carowinds | 730,264 | Jun 2022 | 75 | 45% |
| Cedar Point | 1,060,250 | Jun 2022 | 91 | 43% |
| Dollywood | 464,208 | Jun 2022 | 111 | 39% |
| EPCOT | 356,501 | Jan 2025 | 120 | 47% |
| Epic Universe | 1,391,975 | Mar 2025 | 120 | 34% |
| Hollywood Studios | 307,297 | Jan 2025 | 120 | 43% |
| Islands of Adventure | 2,176,507 | Jul 2021 | 120 | 46% |
| Kings Dominion | 642,612 | Jun 2022 | 75 | 57% |
| Kings Island | 800,838 | Jun 2022 | 72 | 49% |
| Magic Kingdom | 814,728 | Jan 2025 | 120 | 45% |
| SeaWorld Orlando | 822,184 | Sep 2021 | 120 | 56% |
| Six Flags Great Adventure | 310,074 | Sep 2022 | 83 | 48% |
| Six Flags Great America | 791,078 | Sep 2022 | 73 | 36% |
| Six Flags Over Georgia | 225,896 | Sep 2022 | 60 | 35% |
| Universal Studios Florida | 1,654,863 | Jul 2021 | 120 | 41% |
Typical waits by hour
The hourly wait curves on each park page are medians. For each ride and each hour of the day, we take every posted wait from the last 90 days while the ride was open and report the middle value. Hours are park local time.
Curves are grouped by day of the week, so a Saturday curve comes from Saturdays. At seasonal parks a single weekday often has too few open days, so we pool all weekdays, or both weekend days, and the page says which days it used. An hour needs at least 30 readings (18 in the last two hours before close) or we leave it off instead of guessing. The typical wait range on each ride card spans that ride's hourly medians, from its quieter hours to near its peak.
A ride card shows an accuracy badge only when the app's pre-opening forecast for that ride landed within 10 minutes of the real median wait on at least 65% of days, over at least 60 days (or within 15 minutes on 70%). Most rides don't clear that bar yet, so most cards have no badge.
Crowd levels 1 to 10
A crowd level says how busy a day was compared with the same park's own year. For each measured day we score how high posted waits ran across the park, then rank that day against the park's previous 365 days. A 10 sits in the busiest tenth of that park's year and a 1 in the quietest tenth. Each park is ranked against itself, so a 6 at Cedar Point and a 6 at Magic Kingdom are not the same crowd.
- 1 to 2: quiet
- 3 to 4: light
- 5 to 6: moderate
- 7 to 8: busy
- 9 to 10: packed
Past days on a calendar are measured. Today and later days are forecasts.
The forecast
Each upcoming day's level is forecast from the park's own history: month and day-of-week patterns, the same dates last year, how busy recent weeks have run, and known events and operating seasons. The forecast is put on the same 1 to 10 scale, runs about a year ahead, and is recomputed every night, so a date can move as it gets closer.
How we check it. One simple check runs on every park. Over the last 120 days (fewer at seasonal parks, which only count days they were open), we compare each day's level with the typical level for that day of the week. The table above shows how often the two land within one level. It's a baseline, not a score for the forecast: it shows how much the day of the week explains on its own, and it uses a simpler crowd score built from each park's top five headliners. We don't publish a scored accuracy record for the calendar forecast yet.
"No forecast" on a calendar day means we have no forecast for that date. The park may be closed, its schedule may not be out yet, or the date may be past the forecast's reach. It does not mean the park is closed, so check the park's hours.
How the pages refresh
- Nightly. Each morning before the parks open, a job rebuilds every park's data feed and regenerates the park pages, strategy guides and crowd calendars. Yesterday becomes a measured day and upcoming days get the latest forecast.
- Live. The live boards on park pages read the public feed directly, so they move during the day. Everything else on a park page is typical or historical and changes overnight.
- Monthly. The 2027 printable calendars and the 2027 best-days guides use a snapshot of the forecast taken on the first nightly run of each month, labelled "Forecast as of", so the image, the PDF and the page agree.
Known gaps and limits
- Posted waits are the park's estimates, not measured time in line. A ride that is down drops out of the data until it reopens.
- Seasonal parks have short seasons, so their curves pool more days and their late-evening hours are often thin or missing.
- Weather, ride closures, private events and new attractions can't be forecast from history. Special event nights that close a park early show on the calendar, but their crowds are hard to call.
- A crowd level compares a park with itself, not with other parks.
- Forecasts for dates far out lean on past years and move as real days get measured.
In the app
The Ride Ready app shows the same live waits, plus SkipIQ forecast curves for the rest of the day and a day planner that uses them. For rides with long multi-room queues, the app's queue estimates are projected from queue capacity and room usage, and actual waits vary. We test the planner by replaying real park days: our first benchmark, in February 2026, ran 14,826 simulated plans across 353 real park days at three parks.
Ride Ready is an independent application and is not affiliated with, endorsed by, or sponsored by Universal Destinations & Experiences, The Walt Disney Company, Six Flags Entertainment Corporation, United Parks & Resorts, Herschend, or any other theme park operator. All park and ride names and related trademarks are the property of their respective owners. Information is provided for informational purposes only and is subject to change without notice.