Data licensing
Years of queue data,
cut to your question.
Per-ride wait times sampled from every park's own feed since January 2024, delivered as a file and licensed for research, consultancy and publication.
Who it is for
Consultancies, researchers, journalists, park operators, investors, and anyone else whose output is a report, a chart or a deliverable that someone else pays for. If the numbers leave your own systems and end up in front of a client, a reader or a reviewer, this is the licence for that.
It is not the right fit for building an app or running your own analysis. The self-serve API plans license exactly that: reading the data into your own product, storing it, transforming it and deriving your own forecasts from it. What they do not license is supplying the data onward, and that is the line between the two.
What you get
- Per-ride hourly averages and peak waits, with reading counts alongside every figure. A closed ride, a ride that was open but publishing nothing, and a genuine walk-on are three different things, and the file keeps them apart rather than collapsing them into a zero.
- Daily and monthly park-level averages, weighted by observation so a ride that ran all day counts for more than one that opened for an hour. One number per park per month, derived once, the same way every time.
- Opening hours, downtime and crowd levels for the same parks and dates.
- Any park list, any grain, any date range we hold. Hourly, daily or monthly, per ride or per park, cut to the question you are actually asking.
- A CSV on a private download page with a column dictionary and the coverage for every park in the file, so nobody has to guess what a column means or where a series starts.
- One refresh within three months, at the same address, so a study that runs past its first cut does not need a second purchase.
- A signed licence, an invoice and a named contact.
Coverage
History runs from January 2024 for the parks we have tracked longest: Walt Disney World, Disneyland Resort, Disneyland Paris, Universal Orlando, Chessington and Gardaland, with Alton Towers, Legoland Windsor and Thorpe Park from the start of their 2024 season. Most of the North American regional chains, including Cedar Fair, Six Flags, SeaWorld and Legoland, begin in mid 2025, and the parks added since then start on the day we added them.
We confirm exact coverage for your park list before quoting, so a gap is never a surprise after payment. If you would rather see it yourself first, anyone with a free API key can read per-ride coverage for any park at the coverage endpoint, which is free on every plan and shows the first and last date we hold for every ride.
What it is licensed for
Internal analysis, client deliverables, published reports and charts, and academic work. Published work carries an attribution to ParkQueueTimes.com.
The licence does not cover re-supplying the data itself as a feed, a dataset or an API to others. Using it in your work is the point; becoming another source of it is not. The full wording is in section 8 of our terms.
Pricing
From £1,500 per project. The quote depends on three things: how many parks, what grain, and how long a date range. A typical defined study sits between £1,500 and £5,000. No VAT is added.
You can pay by card link or by invoice. Delivery is automatic on payment: the download page is ready the moment the payment clears, with no one in the loop to wait for.
How to ask
Email us with the parks you need, the period, the grain, and where the numbers will end up. Expect a reply with a sample cut of one or two parks in the real file's columns before any price, so you can see exactly what you would be buying.
Questions
Can I get a sample first?
Yes, and you should. Every enquiry gets a sample cut of one or two parks in the real file's columns before we quote, so the shape of the data and the coverage are in front of you before any money is.
Do you have data before 2024?
No. Collection began in January 2024 for the longest-tracked parks and later for the rest, and the file says where each series starts. We do not extrapolate backwards.
Is minute-level data available?
Not as a standard deliverable. Hourly is the finest grain we deliver: per-ride averages and peaks for every hour the park was open, with the number of readings behind each one.
Can I just use the Archive API plan instead?
Only if the numbers stay inside your own product or your own analysis. The moment they become a deliverable, a data room file or a published series, that is this licence, whatever route the data took to get there. The plans page draws the same line.
Do you do ongoing feeds?
Yes. A file that is refreshed on a schedule is priced as a recurring licence rather than a one-off project. Say how often you need it and we will quote for that.
Who owns the analysis I produce?
You do. Charts, models, findings and forecasts built on the data are yours to publish and sell. The licence only reserves the raw series itself.