How Ride Ready's wait-time data works

By Kevin Schneider · Updated November 8, 2026

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:

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.

ParkReadingsCrowd history fromDays checkedWithin 1 level
Animal Kingdom179,194Jan 202512048%
Busch Gardens Tampa Bay751,744Jun 202212049%
Busch Gardens Williamsburg386,833Jul 20229049%
Canada's Wonderland582,942Jun 20228733%
Carowinds730,264Jun 20227545%
Cedar Point1,060,250Jun 20229143%
Dollywood464,208Jun 202211139%
EPCOT356,501Jan 202512047%
Epic Universe1,391,975Mar 202512034%
Hollywood Studios307,297Jan 202512043%
Islands of Adventure2,176,507Jul 202112046%
Kings Dominion642,612Jun 20227557%
Kings Island800,838Jun 20227249%
Magic Kingdom814,728Jan 202512045%
SeaWorld Orlando822,184Sep 202112056%
Six Flags Great Adventure310,074Sep 20228348%
Six Flags Great America791,078Sep 20227336%
Six Flags Over Georgia225,896Sep 20226035%
Universal Studios Florida1,654,863Jul 202112041%

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.

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

Known gaps and limits

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.

Get it on the App Store Get it on Google Play All parks Crowd calendars

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.