HOW WE MEASURE
WAIT TIME ACCURACY
Last updated:
WaitTimeTruth compares two numbers: the wait time a theme park posts on its signs and apps, and the wait time a guest actually experiences in line. The ratio of those two numbers is the posted-to-actual ratio — the core metric behind everything on this site.
THE FORMULA
If a ride posts a 90-minute wait and you actually wait 60 minutes, the ratio is 90 ÷ 60 = 1.50× — the posted time was 50% higher than reality. If you wait exactly 90 minutes, the factor is 1.0×. If you wait 120 minutes when the sign said 90, the factor is 0.75× — the posted time was lower than reality.
CLASSIFICATION THRESHOLDS
We classify every Inflation Factor into one of four categories based on how far the posted time deviated from reality:
| Ratio | Classification | What It Means |
|---|---|---|
| ≥ 1.50× | Significantly Off | Posted time was 50%+ higher than actual. The sign substantially higher than the actual wait. |
| 1.15× – 1.49× | Moderately Off | Posted time was 15–49% higher than actual. Noticeable gap between posted and actual. |
| 0.85× – 1.14× | Accurate | Posted time was within 15% of actual. Reasonably close. |
| < 0.85× | Understated | You waited longer than the sign said. The park underestimated the queue. |
The 1.15× threshold for "Moderately Off" allows for the inherent imprecision of wait time estimation. Wait times are dynamic — guests enter and leave queues constantly, ride capacity fluctuates with loading efficiency, and weather or ride stoppages create unpredictable changes. A small margin of error is expected. Our thresholds are designed to flag patterns, not one-off discrepancies.
DATA SOURCE: POSTED WAIT TIMES
Posted wait times are sourced from the Queue-Times.com Real Time API. This API pulls wait time data directly from parks' official systems — the same data that populates the My Disney Experience app, the Universal Orlando app, and the Six Flags app. The data updates every 5 minutes.
Queue-Times covers 80+ parks worldwide, including all four Walt Disney World parks, Disneyland Resort, all three Universal Orlando parks (including Epic Universe), Six Flags parks, Cedar Fair parks, SeaWorld parks, Busch Gardens, Dollywood, Hersheypark, and many more.
When a guest submits a report on WaitTimeTruth, we snapshot the posted wait time for their selected ride at the moment they indicate they entered the queue. This snapshot becomes the "posted" value in the ratio calculation.
DATA SOURCE: ACTUAL WAIT TIMES
Actual wait times are crowdsourced from two inputs:
1. Manual reports (waittimetruth.com/report)
Guests visit the report page, select their park and ride, and enter the time they actually waited. The posted wait is auto-populated from the Queue-Times API if the ride is currently operating. The guest can also manually enter the posted time they saw on the sign.
2. Apple Watch app (AmusementRating)
The AmusementRating Apple Watch app includes a Track mode that times the user's queue wait from wrist. The user long-presses "Ride It" when entering the queue, and taps "Done" when they board. The app snapshots the posted wait from the Queue-Times API at queue entry and calculates the ratio automatically.
AGGREGATION & PARK SCORES
The ratio displayed on our Park Accuracy Index is a weighted average of all individual ride-level ratios reported at that park. We calculate it as:
This approach — summing all posted minutes divided by summing all actual minutes — naturally weights rides with more reports more heavily. A ride with 200 reports influences the park score more than a ride with 10 reports. This is intentional: higher-volume rides are the ones guests care about most, and they produce more statistically reliable accuracy estimates.
Minimum report threshold
A park is not included in the public leaderboard until it has received at least 50 guest reports across at least 5 distinct rides. This prevents a single ride or a small handful of reports from producing a misleading park-wide score.
WHAT THIS IS NOT
WaitTimeTruth is a data comparison tool. It is not:
An assertion about intent. Posted-to-actual ratios are mathematical comparisons. A ratio above 1.0× means the posted time was higher than the reported actual wait. There are many legitimate reasons this can occur: guest satisfaction management (guests prefer waiting less than expected), queue management at park closing, capacity estimation challenges, manual reporting limitations, and ride downtime buffers. We make no claims about any park's motivations.
A guaranteed prediction. Our data is historical. The ratio for a ride today may be different tomorrow. Wait times are influenced by day of week, season, weather, special events, ride capacity changes, and many other variables we cannot control for.
A recommendation for or against any product. We do not advise guests to buy or not buy Lightning Lane, Express Pass, or any skip-the-line product. We provide data so guests can make their own informed decisions.
UPDATES & VERSIONING
This methodology document reflects the current state of our data pipeline. We will update it as our methods evolve — particularly as the Apple Watch app introduces automated queue detection (GPS geofencing, accelerometer pattern recognition) in future releases. All changes will be documented here with dates.
Questions about this methodology: [email protected]