About the Data

Every wait time, crowd forecast, and ride-by-ride recommendation on Thoosie is built from publicly posted wait data. Thoosie polls the public ride-status feed at each park about every minute and stores every reading. We own no in-park hardware and no sensors.

19M
qualifying readings per month
60+
US and Canadian parks covered
1 min
polling interval
3 months
of monthly baselines, June 2026 onward

How We Collect Wait Times

Thoosie's data pipeline polls publicly available ride status feeds about every minute across 60+ covered parks in the US and Canada. Every reading captures ride name, current posted wait, and operational status. These are the same signals that appear on park apps and in-park kiosks. We read them independently, store every data point, and build historical baselines from the accumulated record. A reading qualifies for our published statistics when the ride was open and the park had a wait posted for it: about 600,000 a day, roughly 19 million a month. Raw stored rows are higher, but no figure we publish is derived from them, so the qualifying count is the one we quote.

Thoosie started recording in June 2026, so the baseline record is three months deep, not three years. Raw readings are kept on a rolling 31-day window and rolled up into permanent per-ride monthly baselines before they age out, which is why the month tables on ride pages show three months. Where a park was added recently, its baseline is shallower still, and the page says so rather than padding the number.

We have no data agreement with any park operator, we take no numbers from park marketing, and we have no commercial relationship with any park that would affect what we publish. Everything we store, we read from the feeds each park publishes to the public. The data reflects the wait each park had posted at the moment we recorded it.

No park pays for better coverage, better ratings, or higher placement in our guides. Our data independence is the product. It's what makes the crowd forecasts and best-time recommendations accurate instead of promotional.

How Baselines and Forecasts Are Built

After each reading is stored, it feeds into per-ride, per-hour baselines that capture typical wait behavior for each day of week and season. These baselines power the "typical for this time of day" comparisons on crowd-report pages and the best-visit-day recommendations in planning guides.

Forecasts are not guesses. They are weighted averages of historical readings for the same park, same ride, same hour of day, and same day of week, filtered by seasonal pattern. A forecast for Cedar Point's Millennium Force at 2 PM on a Saturday in July is built from dozens of actual 2 PM Saturday readings in July, not a model trained to please.

What the Numbers Mean

Posted wait times at theme parks are the operator's estimate of how long a guest joining the queue now will wait. Parks have incentives to manage these numbers, and real standby times sometimes differ from posted times. Thoosie records the posted figure and flags systematic divergence where our crowd-sourced observations reveal it.

When a guide says "Cedar Point averages 22 minutes park-wide on a Tuesday in June," that average is computed from all open-ride readings taken at Cedar Point on Tuesdays in June across our full historical record, not from a single day or a sample.

Coverage and Updates

We currently cover 60+ US and Canadian theme parks with live data and historical baselines. Parks are added when reliable public feeds become available. Coverage depth varies. Major parks with frequent data have richer baselines than smaller parks added more recently.

Guide articles are reviewed and updated when underlying data shows a meaningful shift in a park's patterns: a new ride opening, a scheduling change, or a structural change in crowd distribution. The dateModified field in each article reflects the last substantive content update, not an automatic timestamp.

Data License and Citation

Thoosie's measured wait-time figures, crowd levels, and the data tables published in our guides are free to cite for personal, journalistic, academic, and research use with attribution to "Thoosie (thoosie.app)" and, where practical, a link to the page you referenced. The underlying live feed and bulk historical exports are available for commercial licensing through the Thoosie data API.

Every published average states its measurement window and includes zero-minute waits recorded while rides were open, so cited figures are all-day numbers rather than peak-only figures.

Questions

If you have questions about our data methodology, coverage gaps, or want to report an inaccuracy, reach out at hello@thoosie.app.

ThoosieThoosie