Theme Park Wait Times History - Disney, Universal, 100+ Parks

Takes a snapshot of live ride wait times for Disney, Universal, SeaWorld, Six Flags, Cedar Fair, Merlin and 100+ more parks, and builds the history the sources do not keep. After a few runs it tells you the best hour of the day to ride each attraction.

For trip planners, fan sites, bloggers and data journalists.

Data credit: wait times come from ThemeParks.wiki and Queue-Times.com. Queue-Times requires a credit: every row carries an attribution field ("Powered by Queue-Times.com") and the run summary lists the credit lines. Please keep them if you publish the data.

Input examples

1. Default ({}) - Magic Kingdom, now:

{}

2. Several parks from both sources, kept in your own history store

{ "source": "both", "parks": ["Epcot", "Universal Studios Florida", "Alton Towers"], "maxParks": 5, "historyStoreName": "my-park-waits" }

3. Every park of ThemeParks.wiki (capped)

{ "source": "themeparks.wiki", "parks": ["all"], "maxParks": 20 }

Input guide

• Parks are matched by part of the name (case-insensitive). all takes every park, limited by maxParks.
• History store is a named key-value store that accumulates readings between runs (per ride, per weekday and hour, newest 12 readings each, kept for historyDays). Use the same name every time.
• Schedule it every 15-30 minutes during park hours for a useful best-hour summary.

Output

Field	Meaning
type	wait-snapshot, best-hour, run-summary, error
parkName, rideName, land	Park and attraction
status, isOpen, waitMinutes	Current state and standby wait
localDay, localHour, timezone	Park-local time of the reading
bestHourLocal, bestHourMedianWait	Quietest hour of the day (median wait), from stored history
busiestHourLocal, busiestHourMedianWait	Busiest hour
samples, hoursCovered	How much history the summary rests on
attribution	Required data credit

Sample row:

{"type":"wait-snapshot","source":"themeparks.wiki","parkName":"EPCOT","rideName":"Spaceship Earth","status":"OPERATING","isOpen":true,"waitMinutes":5,"localDay":"Sun","localHour":17,"attribution":"Live data via ThemeParks.wiki (https://themeparks.wiki)"}

Use it with

Google Sheets / Looker Studio from the dataset; a Telegram or Slack bot that posts "best time to ride" for your trip park; pair with a weather Actor to study rain vs crowds.

FAQ

Why are there no best-hour rows? They need readings in at least two different hours of the day (two readings each by default). Schedule the Actor and they appear. Does it cover ride closures? Closed rides show isOpen: false when includeClosed is on; they are not charged.

Limits (honest)

• Waits are the standby queue only (no Lightning Lane / virtual queue prices). Sources may lag by several minutes.
• History is only as good as your schedule; the Actor cannot invent past waits.
• Park time-zone handling uses the source's time zone; a few small parks may lack one (UTC is used then).

Price

Pay per event: $0.0003 per ride wait recorded. Example: a park with 40 open rides, scheduled every 30 minutes for 12 hours = 24 runs x 40 x $0.0003 = $0.29 per park-day. Best-hour and summary rows are free.