A day at the park, with physical queues or a virtual queue.
The same people, the same day and the same breakdowns, run two ways. With the virtual queue, every booking goes through the queue engine your app would use.
- 1Pick the dayHow busy it is, how many people have the app and whether there's a long breakdown. Each combination is a whole day, already simulated, and loads in a few seconds.
- 2Watch the dotsEach dot is a group. Red means queuing; blue means holding a booking and out in the park. The day runs on its own: you can pause it or move the clock.
- 3Follow the engineAlongside, the live log: waves, notices to come earlier, stoppages and new times.
Loading the park data…
Five days that stand for the whole season.
A sample park with made-up data: take the 250 days it opens in a year, sort them by attendance and pick the middle day of each fifth. The average weights each day by its visitors: most people come on the busy days.
| Day | Visitors | Hours queuing, today | With a virtual queue | Rides, today | With a virtual queue |
|---|---|---|---|---|---|
| A Tuesday in March | 1,700 | 0.5 | 0.4 | 16.6 | 10.6 |
| A Thursday in May | 5,200 | 2.2 | 0.8 | 12.2 | 10.2 |
| A Monday in July | 10,200 | 4.6 | 1.5 | 11.1 | 10.7 |
| A Wednesday in August | 17,000 | 5.6 | 2.0 | 7.9 | 7.6 |
| A Saturday in June | 26,000 | 5.9 | 2.3 | 5.2 | 4.7 |
| Yearly average, per visitor | 5.1 | 1.9 | 7.9 | 7.2 |
On quiet days, the virtual queue means fewer rides: everyone waits for their time to come round, even if the ride is empty. The engine already has a rule for letting people in early when there's room; the park decides whether to switch it on.
A made-up park, running the real queue engine.
The map and the paths
Made up: a sample park drawn from scratch, with its rides, restaurants, shops and shows each in place.
Capacity and height
Made up too: 36 in the simulation, from 200 to 1,500 riders an hour in theory, plus a minimum height where one applies.
Calibrated to the posted waits
Without a virtual queue, the simulation reproduces the waits the sample park posts, taking the real wait as 85% of the posted one.
The real one
Waves, up to three bookings at once, notices to come earlier, stoppages, parent swap, the priority pass and the offline QR code. The days on this page were simulated with it in advance and load ready-made.
Everything else is an estimate: group sizes and children's heights, arrival times, how each group picks its next ride, how long people spend eating or shopping, how many have the app, and random breakdowns. With your data, the simulation becomes your park's.