most accurate wait times?

No worries :)

Looking forward to the feedback! Keep in mind "surge" times and I think it'll work great for you :)

mjhannaf - a clarification please... is the wait time the expected wait time if you immediately got in line? or is it the theoretical amount of wait time that someone getting off the ride just experienced? (I'm assuming it's the estimate if you immediately get in line) In other words, does it take into account the surge?

Hope this question makes sense. Sorry if you already addressed it. For some reason, I just can't wrap my mind around this. On the other hand, I totally "understand" the red tags that WDW give people waiting in line. Scan it at the beginning and end, and poof, the amount of time that person waited. And, just because someone 10 minutes ago waited 10 minutes, doesn't mean I'll wait 10 minutes. That's a flaw with their system, but also not sending those red tags through often enough. I'm sure there's other flaws and details, but the basic premise, I understand.
 
In other words, does it take into account the surge?

Hope this question makes sense. Sorry if you already addressed it. For some reason, I just can't wrap my mind around this. On the other hand, I totally "understand" the red tags that WDW give people waiting in line. Scan it at the beginning and end, and poof, the amount of time that person waited. And, just because someone 10 minutes ago waited 10 minutes, doesn't mean I'll wait 10 minutes. That's a flaw with their system, but also not sending those red tags through often enough. I'm sure there's other flaws and details, but the basic premise, I understand.

I don't take into account the surge. That would require a lot of historical data and educated guesses which I don't have.

You can think of my data as being like the red cards. For example, when I say it's an actual wait of 22 minutes that means that it was 22 minutes the last time I pulled the data. It could be 25 minutes, 18 minutes, or 45 minutes if there is a surge. I would rather display the data I have then try and guess when a surge will be and what kind of impact it will have. That's just the nature of the beast.

In my experience my actual wait times have been within an average of 2 minutes of when I actually timed myself standing in a queue (with the exception of surges).

I hope that clarifies the data and how you can use it. Remember, if you're standing at the entrance to Splash Mountain next to another family and you're both looking at the 60 minute posted wait, but you pull out your phone and see it's only 32 minutes you might ride it when the other family walks over to Big Thunder or Pirates ;)
 
Putting in a fix for Entertainment times. They showed incorrectly after 8pm due to timezone differences. Should be fixed in less than 15 minutes
 

I don't take into account the surge. That would require a lot of historical data and educated guesses which I don't have.

You can think of my data as being like the red cards. For example, when I say it's an actual wait of 22 minutes that means that it was 22 minutes the last time I pulled the data. It could be 25 minutes, 18 minutes, or 45 minutes if there is a surge. I would rather display the data I have then try and guess when a surge will be and what kind of impact it will have. That's just the nature of the beast.

In my experience my actual wait times have been within an average of 2 minutes of when I actually timed myself standing in a queue (with the exception of surges).

I hope that clarifies the data and how you can use it. Remember, if you're standing at the entrance to Splash Mountain next to another family and you're both looking at the 60 minute posted wait, but you pull out your phone and see it's only 32 minutes you might ride it when the other family walks over to Big Thunder or Pirates ;)

This helps a bunch. Thank you.
 
The only way it could be more accurate is to have a person on each ride that just loops through the queue and reports back.

Without being at HS right now, I would bet that people are eating lunch. I know that it sounds like an impossibly simple answer, and maybe it is, but I'm pretty confident in these numbers.

TSMM dropped to 10 minutes from 34 minutes at 12:25pm. I wish I could be there right now to "test" it ;)

tumblr_lp11352xkP1qdeq5f.gif
 














Save Up to 30% on Rooms at Walt Disney World!

Save up to 30% on rooms at select Disney Resorts Collection hotels when you stay 5 consecutive nights or longer in late summer and early fall. Plus, enjoy other savings for shorter stays.This offer is valid for stays most nights from August 1 to October 11, 2025.
CLICK HERE













DIS Facebook DIS youtube DIS Instagram DIS Pinterest

Back
Top