lentesta
Premium Member
Illuminating the bat signal for @lentesta . On his latest podcast he was talking about the capacity of the parks. I don't remember everything he said, but I think he was saying the 2 stage shows really need almost constant shows for the park to have decent capacity.
Offenders of low capacity attractions included Dragon Racer's Rally, Fyre Drill, and Minecart Madness.
@Andrew25 is also doing good work here.
Below is my spreadsheet with upper limits on per-hour ride capacity. Comments welcome. The items in beige are things I'm not sure about. The items in gray are calculated from the other columns:
I'm using a couple of different ways to determine park capacity.
The first one, shown above, first calculates hourly capacity. Then it uses ratios of "guests on rides and in line" to "everyone in the park" from one of Disney's internal documents for DLR, MK, MGM, and Epcot. That's the 46 to 60% range shown above, giving a max capacity of somewhere between 30K and 40K. (If we used the MK's ratio it'd be almost exactly in the middle - 35K guests at any time.)
The second way I'm doing it looks like this:
- Determine the avergage wait in line across the park that Universal's willing to accept (e.g., 30, 45, 60, 75 minutes)
- Figure out how many guests would need to be in lines for that to happen
- Use the same 46-60% ratios from above.
I used DAK's peak ride numbers from last Christmas as a guide. (For example, what was the upper limit on wait times at Adventurers Outpost - a character greeting? Kali River Rapids - a water ride? Kilimanjaro Safaris vs Flight of Passage, etc.)
In this method, the park's peak capacity is somewhere between 33K and 44K, with a middle around 38K.
I would be surprised if Universal's going to accept an average actual wait in line of more than 70 minutes. Ministry and Monsters don't seem reliable enough yet for that scenario.
So both calculations put park capacity in the 35K to 38K range at any given time of day.
The other big dependency here is the ride cycle time. I haven't been back to measure unload/load time, and some of those numbers were pretty bad. Hopefully that's something they can work down.