Today, live
Every ride's wait and whether it's running, the weather, opening hours, shows and events, logged around the clock for nearly 200 parks. This is what today's plans use, and the counts above grow every few minutes.
Lapbar isn't a list of wait times with a plan stuck on top. It's a planning model we built from scratch, fed by our own data pipeline that watches nearly 200 parks around the clock, and it marks its own homework every night. Right now we're building the global model: one model that learns from every park, every day, and from years of history. The counts and accuracy record below update themselves from our database.
17quintillion possible vectors for the model to draw on
A vector is one data point read through one combination of factors. We hold 8.1 million data points going back to 2015, and each can be read through any combination of the 41 factors we log or test, from weather and holidays to exchange rates: 2.1 trillion combinations. Every new data point adds trillions more vectors, and every new factor doubles the lot. This is the space the model searches when it decides which factors earn their place. It's a theoretical maximum: a factor is only used if it improves forecasts on days held back for checking.
Straight from our database and refreshed every 10 minutes, so these only ever go up.
Most planners read today's wait times and stop there. Lapbar keeps everything, because a forecast is only as good as the history behind it. Our servers log all of this for every park we track, and keep the raw responses too, so the model can always be rebuilt from what was actually seen.
Live from our database: how much history is loaded, what we're testing, how honest our chances are, and the two decades of background the global model learns from. All the charts.
Loading live data…
Loading live data…
Lapbar gives each ride a chance it'll be running when you get there. Here's how those chances held up.
Loading live data…
Loading live data…
Loading live data…
Lapbar is training one model across every park it logs, so what it learns in one park helps all the others. It learns from two kinds of data at once: what's happening in the parks today, and years of history about how busy parks get and why.
Because a queue is never just a queue. How long you'll wait at 2pm depends on far more than the number on the sign at 10am: whether it's a school holiday, and not only where the park is but where its visitors fly in from; whether a storm is coming; whether a big ride nearby has just broken down; whether flights into town are full this month, or money is tight and families are staying home.
Every one of those things changes how busy a park gets. The more of them Lapbar understands, the better it can tell you when to ride, what to skip and where to go next. Better predictions mean shorter queues, less walking back and forth, and more of the rides you came for. That's the whole point.
Every ride's wait and whether it's running, the weather, opening hours, shows and events, logged around the clock for nearly 200 parks. This is what today's plans use, and the counts above grow every few minutes.
Over a year of past wait times for the biggest parks is loading now, so each park's model starts with seasons it hasn't lived through yet. Beneath that sit two decades of travel, tourism and attendance trends.
One past day in five is locked away and never used for tuning. New information only changes your plan if it makes the forecasts better on those locked days. Anything that doesn't help stays switched off.
"In plans" means today's plans use it. "Learning" means the model is learning from it now. "In testing" means it has to prove it makes forecasts better before it can change one.
Today's plans use the live layer and Lapbar's own per-ride models built from it. The rest joins the plans only once it proves itself on the locked days, and the accuracy record above will show it when it does. See the live counts.
Lapbar's forecasts and plans come from a mathematical model we built ourselves: statistics fitted to millions of real recordings, the odds of each ride breaking down, measured walking times, and a search through thousands of possible days. It isn't ChatGPT, Claude or any other AI chatbot, and no chatbot sits between the data and your plan.
Every few minutes we record every ride's wait and whether it's running at nearly 200 parks, plus the weather.
Every 15 minutes the model writes down what each wait will be, up to four hours ahead, before anyone knows the answer.
Every 30 minutes those predictions are scored against what really happened. The scores are on this page, good or bad.
The model is a set of named parts (wait times, ride breakdowns, storms, crowd ripples and more), and a change touches one part at a time. It goes live only if it beats the current model on days it has never seen, and a change that makes plans worse is turned down. Any part can be put back on its own.
Watch simulated visitors follow Lapbar's plans on today's live park data
A chatbotWrites whatever sounds likely, from text it has read.
LapbarWorks it out from real recordings: queue times, breakdowns and weather, logged every few minutes.
A chatbotCan give you a different answer each time.
LapbarSame park, same moment, same live data: exactly the same plan, every time.
A chatbotCan invent things that sound right but aren't.
LapbarCan't. Every ride, wait and walk comes from real park data and our map of the paths, and every forecast is checked against what really happened.
Give Lapbar the same park, the same moment, the same live data and the same wish list, and it gives exactly the same plan, down to the minute. Run it a hundred times and you get the same answer a hundred times. Your plan only changes when something real changes: a queue, a ride, the weather, or where you are.
Our tests work the same way. The test visitors we play through past days make their choices from fixed, numbered starting points, so a rerun is identical move for move. That's how we compare one version of the model with the next fairly.
Because it's maths, every recommendation can say why in plain words, worked out from the numbers behind it, like "In the morning: it often goes down in the rain, and rain is likely from about 14:00." If a call doesn't pan out, you can still see why it was made.
Where AI does appear: behind the scenes, an AI assistant helps our team suggest experiments to test overnight. It can only pick from a fixed list of settings, never sees anyone's plans or personal details, never forecasts a queue or makes a plan, and nothing it suggests reaches the app unless it passes the same tests as every other change.
The planning engine is our own work, written from the ground up for theme parks. It runs on our servers, and these are the parts that make up every plan.
Each ride's wait for every minute of the day, built from the day's crowd level, the ride's usual shape through the day and learned hour-by-hour corrections. A live "nowcast" blends in the latest readings, every forecast comes with a range, and posted times are corrected to how long people really wait.
Every ride has its own track record: how often it stops, how long repairs usually take and how queues surge when it reopens. When a big ride goes down, the model knows which nearby queues will swell, learned from past breakdowns. Every night it also compares rides across every park by type, maker, age, climate and weather, to see which kinds of ride stop most, and when. The results go in the app's Stats tab. Coming soon When one ride's own record shows it stops far more in the rain or at one part of the day, the day plan moves it to when it's more likely to be running and says why on that stop. Coming soon
Lightning risk closes outdoor rides, rain and heat change who's queuing where, and every plan carries a storm version ready to go. Lapbar measures how each ride's queue moves in rain and heat, rather than guessing: on a hot afternoon, outdoor queues thin out most and water rides hold up.
Magic Kingdom alone is 3,523 points and 4,088 path segments, with every ride's entrance and exit mapped separately. Main Street and the hub slow down as crowds build, parade routes are blocked while a parade runs, and the railroad counts as a way to get around when it's quicker. Next, it learns real walking times from walks visitors choose to share anonymously, to see how much crowds really slow each path. Coming soon
The planner simulates your whole day minute by minute, then searches thousands of possible orders in about a second (a beam search, then simulated annealing, then a final polish) for the one that gets you the most of what you ranked highest. It re-optimises from wherever you are whenever the park changes, without flip-flopping on noise.
For each park, how long queues stay short after you get in, measured from our own five-minute queue records (with Early Entry measured separately), and which rides often open late. Every day plan uses each ride's own opening record: a ride that usually opens late is planned for after its usual start, and the stop says why. Coming soon Frenzy mode uses it to put your must-do whose queue builds fastest first, then short queues close by, so you don't cross the park for a short line. Coming soon The windows are early measurements from a few weeks of days, and they're refitted as the history grows.
Nightly, Lapbar works out how every ride behaves by weekday, month, heat, rain, holidays, ticketed parties and evenings. It even learns which rides empty out during the fireworks and parade, ride by ride, so the plan can send you there.
Every 15 minutes the model writes down what it thinks each ride's wait will be in 15 minutes, half an hour, an hour, two hours and four hours. Every 30 minutes it compares those forecasts with what actually happened.
It also trains on each park's past year, the way it would have been used: at the start of every month a version is fitted only on the days before it and then scored on that month, so it never sees what happens next. It learns the crowd by month and weekday, each ride's usual shape through the day, and how long a live reading stays useful. Only if those versions win on the locked days does the fit go live, and the forecasts then keep being scored on new days.
Every day, and again the same day whenever a new experiment is added, it also replays the past 400 days at sixteen parks, one day at a time: the four Walt Disney World parks, the two at the Disneyland Resort, and ten in Asia and Europe (the Disney and Universal parks in Japan, China, Hong Kong and Singapore, both Disneyland Paris parks and Europa-Park). Each day is replayed as if it were live: refit on everything before the day, forecast it, score it against what happened and against simply assuming the wait stays the same, then step on to the next day. Every experiment says what it is for: better waits, better waits in the next half hour, earlier warning that a ride will close, or better plans. It has to win at that, without making anything else clearly worse, in three tests before it can change a plan: on that replay, on the locked days, then in a shadow run on live park days, where its forecasts are scored but never shown. With parks in Asia, Europe and the US in the tests, some park is open at every hour of the day, so live checks never stop. A park where it lost keeps its current settings. Every version of the model, and every experiment, gets its own two-word name, like Peculiar Pickle or Swooping Corkscrew, drawn at random by the system the moment it's made and kept for good. Every named model stays on our internal leaderboard for good, scored on each part of the tests above, so an old model that was the best at one thing can be found again. You can see which one is planning today on the live page.
The replay also plans real past days for a fixed panel of 96 test visitors, from young families and show lovers to coaster fans and foodies. Each visitor keeps the same settings in every test, so every version of the model is judged on the same people. Each one's day is also played without the app, by the same person with the same wish list, meals and hours. Like real people, they end the day in different ways: many stay for the fireworks, some head home once their list is done, and a fireworks fan spending several days at the park on a longer trip only stays for the show on some nights. Each visitor's habit is the same with and without the app. Without the app, while they're in the park they keep going, re-riding favourites and joining queues as they find them. Some follow a simple plan: their wish list in order, a loop round the park clockwise or anticlockwise, the back of the park first, the headliners first, or always the nearest ride. Others play it like enthusiasts, with a rope-drop plan from online advice or chasing the shortest posted wait. Days are graded from calm to disaster by how much ride time was lost to breakdowns and storms, so we can see how much Lapbar adds on a smooth day and how well it protects a bad one. An experiment that makes forecasts better but plans worse is turned down.
Changes to the planner itself go through a fixed test bench: the same frozen real days at the six Disney parks in Florida and California and the ten test parks in Asia and Europe, from calm to disaster, with all 96 visitors and their no-app days. Each change is scored the same way against the last accepted version and has to pass the same checks. Plans can't get worse overall or for any kind of visitor, day or park, and must-dos, meals and wasted trips are watched too. A second set of locked days, never used for tuning, has to confirm a win. The days where Lapbar still does worse than a typical visitor without the app are ranked by cost, and the biggest one is the next thing we fix. Each night yesterday's real day at every park is added as a fresh test. Real days also go wrong for human reasons, so each new version is tested a second way too: the same visitors meet the same seeded mishaps, like arriving late, an unplanned toilet or snack stop, a child refusing a ride at the door, going home early or a phone that dies for an hour. Lapbar and the same person without the app meet exactly the same ones, and we measure how much of Lapbar's head start survives them. The rates of those mishaps are our own estimates for now; this test reports, it doesn't decide.
Each night it re-learns from the last 28 days, tests the new version on yesterday (which it wasn't allowed to see) and only switches over if the new version is at least as accurate. Then 100 made-up visitors, from young families to coaster fans, replay yesterday with the plan Lapbar would have given them, and each day is scored against the best plan possible with perfect hindsight.
Every forecast is scored against the wait the park went on to post. This is the running record for Magic Kingdom, with nothing left out, and it grows by a day every night.
Lapbar's forecast against the simplest possible guess: that the wait in an hour will be whatever the park is posting now. Lower is better.
Scored forecasts by how far ahead they were made: how far off they were on average, and how often the posted wait landed inside the forecast's 80% range.
| Made | Off by, on average | Inside the range | Checked |
|---|
These charts draw themselves from our own database each time you load the page. We started logging in November 2026, so they show what's happening now rather than long-run averages.
Every 15 minutes Lapbar forecasts each ride's wait an hour ahead, with a likely range. Here's that forecast against the wait the park actually posted today: the closer the two lines, the better the forecast. Pick a ride to see another.
An hour ahead, Lapbar forecasts the chance every ride will be running. Here's that forecast against whether it actually was, with the gap marked.
The posted waits at the three nearest rides, an hour before, during and after the breakdown. One event, not an average: queues move for other reasons too.
Rides closed with lightning about, and the average posted wait at the rides still open.
When thunder next closes rides, this chart will show how many closed and what it did to the queues at the rides still open.
Lapbar plans days at 36 parks in the beta, and logs every other park it tracks so their models start with real history.
Since November 2026 a Magic Kingdom plan can also include Lightning Lane, meals and breaks, and trips of several days. The app gets these in its next update.
Live wait times are powered by ThemeParks.wiki and Queue-Times.com. Includes weather data from MET Norway. Historical weather from the Iowa Environmental Mesonet and lightning from NOAA's GOES satellites. Storm outlooks from NOAA's Storm Prediction Center and hurricane tracks from the National Hurricane Center. Radar and lightning probability from NOAA MRMS, storm forecasts from NOAA HRRR, wildfire smoke from the NOAA Hazard Mapping System, and storm chances outside the US from ECMWF open data (Copyright ECMWF, CC BY 4.0). Rail disruption messages from SNCF Voyageurs (ODbL). Exchange rates: source ECB. Our research also uses Wikipedia page views from Wikimedia and news data from The GDELT Project. Walking paths and ride details © OpenStreetMap contributors. Ride types and makers also from Wikidata. Height limits from each park's published rider rules, via DeepArrival. Every provider keeps ownership of its own data. The model, the learning, the calculations and the plans are proprietary to Lapbar, a trading name of Aethus Limited.
This product uses the FRED® API but is not endorsed or certified by the Federal Reserve Bank of St. Louis. This product uses the Census Bureau Data API but is not endorsed or certified by the Census Bureau. BLS.gov cannot vouch for the data or analyses derived from these data after the data have been retrieved from BLS.gov.
Lapbar is independent. It is not affiliated with, endorsed by or sponsored by Walt Disney World, Universal, Merlin or any other park operator. Park and ride names are used only to describe where Lapbar works. Your location and personal details are never part of the data: the learning uses park data and anonymous plans with location removed. The one exception is walks you choose to share, which are kept anonymously and matched to the park's paths. Coming soon Privacy policy.