What happened to the actual wait times?

[nkereina]

Do you have a link to that? The link above goes to some sort of wait time graph which doesn't look very helpful and I can't find a location for actual times on their site anywhere?

I believe you have to pay for a Touring Plans subscription to view their wait times.

 

[Dan Murphy]

Do you have a link to that? The link above goes to some sort of wait time graph which doesn't look very helpful and I can't find a location for actual times on their site anywhere?

http://touringplans.com/disney-world-app

 

[BradChristian]

This makes me want to cough up the $13 bucks a bit... because the actual times were often way different than the posted

 

[Dan Murphy]

This makes me want to cough up the $13 bucks a bit... because the actual times were often way different than the posted

20% discount through www.mousesavers.com.

http://www.mousesavers.com/discount-disney-shopping-mall/#touringplans

 

[gottaluvPluto]

I just went to easywdw website and they had wait times posted. Are they now using MDE wait times? I guess when I get time I could figure it out.

 

[nkereina]

This makes me want to cough up the $13 bucks a bit... because the actual times were often way different than the posted

I'm not sure when the last time you used the actual times were, but we used them in November and didn't find the posted and actual to be very different. When there was a substantial difference (say 15 minutes or more between the two times), we often found that the TRUE wait time fell between the posted and the actual.

I just went to easywdw website and they had wait times posted. Are they now using MDE wait times? I guess when I get time I could figure it out.

The wait times they have are the posted wait times - the same ones that have always been in the MDE app. What they used to show in addition to those were the ACTUAL wait times - the time people actually spent waiting in line. Those have recently been cut off.

 

[gottaluvPluto]

The wait times they have are the posted wait times - the same ones that have always been in the MDE app. What they used to show in addition to those were the ACTUAL wait times - the time people actually spent waiting in line. Those have recently been cut off.

Okay, I get it now. Thanks! We have never had to use these apps before with the old FP system. FP+ has really thrown our game off and we don't get to ride as many things, so we were thinking about using them. Oh Well! We will still have fun.

 

[NJlauren]

Is touring plans posting actual and listed or just listed?

Is anyone posting actual anymore? Trying to decide if I should just use MDE app.

 

[nkereina]

Is touring plans posting actual and listed or just listed?

Is anyone posting actual anymore? Trying to decide if I should just use MDE app.

I believe Touring Plans uses real time user submitted data for actual wait times, which we've never found to be accurate. The other sites had a script built in that somehow pulled real actual wait time data and reported it. That loophole has since been cut off, so now every site will be the same as MDE which are just the posted times. I think Touring Plans still has the user submitted times, but there's no telling if people are reporting accurate info or how often.

 

[berkeleykel06]

Touring plans shows both actual and listed. I used it two weeks ago and thought it was helpful and more accurate than the posted wait times. Even just knowing that a 20 minute posted wait was really closer to 10 minutes could affect our plans, like if we were trying to squeeze a ride in before a fp or an adr, or if it was a ride we were so-so about (so not willing to wait 20 mins, but willing to wait 10 mins). Also helpful on the super in-demand ride like Peter Pan and SDMT, where the posted times were often considerably different than actual wait.

I'm not sure that the real time data is just the submitted data--right now I'm looking at the user-submitted data they've received recently for a few rides and that doesn't match up with the actual wait times they have for those rides.

 

[nkereina]

Touring plans shows both actual and listed. I used it two weeks ago and thought it was helpful and more accurate than the posted wait times. Even just knowing that a 20 minute posted wait was really closer to 10 minutes could affect our plans, like if we were trying to squeeze a ride in before a fp or an adr, or if it was a ride we were so-so about (so not willing to wait 20 mins, but willing to wait 10 mins). Also helpful on the super in-demand ride like Peter Pan and SDMT, where the posted times were often considerably different than actual wait.

I'm not sure that the real time data is just the submitted data--right now I'm looking at the user-submitted data they've received recently for a few rides and that doesn't match up with the actual wait times they have for those rides.

Hmmm I wonder if they've found a way around the block then. If they are reporting actual wait times like other sites were doing before, we still found that the TRUE wait time for us was somewhere between the actual and the posted. For instance, Splash was posted at 45 with the actual listed online as 25, so we got in line. Ended up being about 35. This happened on multiple occasions for us. Don't let the actual times be gospel, but use it as a guide to give you an idea.

 

[berkeleykel06]

I'm guessing they rely on historicals at least to some extent, because in the app they also give projections of what they think will happen later in the day.

 

[Imagineer22]

Stupid question time...how does anyone (3rd party or Disney) calculate 'actual wait time' vs 'posted wait time'??? Why would the posted wait time not be as close to accurate as possible? I understand there are a LOT of factors that can affect sudden fluctuations of wait times. However, if Disney can calculate ACTUAL wait time why not post that time? Furthermore, how does one calculate actual wait time and distribute it so quickly for it to be 'accurate' on an app?

I really am curious how this all works.

 

[Trinity88]

I've used the Touring Plans app and love it. You get in line for a ride, click a timer in the app, then click a timer again when you're about to ride. So it has real data on wait times.

 

[HydroGuy]

Stupid question time...how does anyone (3rd party or Disney) calculate 'actual wait time' vs 'posted wait time'??? Why would the posted wait time not be as close to accurate as possible? I understand there are a LOT of factors that can affect sudden fluctuations of wait times. However, if Disney can calculate ACTUAL wait time why not post that time? Furthermore, how does one calculate actual wait time and distribute it so quickly for it to be 'accurate' on an app?

I really am curious how this all works.

The posted wait times are Disney estimates based (usually) on cards they pass out to people in line. They are attempting to post actual wait times. But the person who just waited 30 minutes actualyl to get on a ride does mean that the person getting in line right then will have to wait for 30 minutes. It might be shorter or longer or the same.

Thus Disney might post the wait time as 30 minutes based on a person who just actually waited 30 minutes. When in the actual wait time has changed.

The touring plan sites and apps try to predict the difference in what Disney posts and what is actually experienced.

 

[Disney_Princess83]

If you use the MDE app, you have the wait times straight from Disney. This would be the most accurate wait time app.

We were at WDW for weeks and using the app and we found many times the app was entirely wrong. Space had a posted wait time of 40 minutes, app stated 110. Big Thunder had a posted 30 minute wait, app stated 10

 

[BrittyRo]

Real time wait times should be part of MDE so they have the most accurate info...

 

[mesaboy2]

Real time wait times should be part of MDE so they have the most accurate info...

I'm sorry, that's proprietary information.

 

[Laketravis]

The posted wait times are Disney estimates based (usually) on cards they pass out to people in line. They are attempting to post actual wait times. But the person who just waited 30 minutes actualyl to get on a ride does mean that the person getting in line right then will have to wait for 30 minutes. It might be shorter or longer or the same.

Thus Disney might post the wait time as 30 minutes based on a person who just actually waited 30 minutes. When in the actual wait time has changed.

The touring plan sites and apps try to predict the difference in what Disney posts and what is actually experienced.

It depends on the website. Some predict, others used the Disney API.

The "actual" wait times that some apps/web pages were presenting was simply labeled as actual - they were derived from the "last sampled" data field of the Disney API and could have been the SB queue or the FP queue since both are periodically measured via those red cards that help make little kids feel very important and the value is used by Disney to calculate (1) the posted wait time and (2) the FP to SB admittance ratio.

Disney removed the "last sampled" data field from the API thus it's recent absence.


.

 

[Lovetherodent]

With discount, the touringplans subscription is $10.36, about the cost of a movies, depending on where you live (or cheap seats admission with popcorn and drink). Anyway, roughly 2 hours of entertainment. I'm going to get way more than 2 hours worth of fun out of that subscription, even with a very short time to go until my trip. Well worth the money if you ask me.