Why we built Ride Guide
Planning a theme park trip with other people is a coordination problem, not just a scheduling one. Ride Guide exists to make the "who's going where and when" part effortless, so you can spend your day riding instead of texting your group about it.
Groups rarely want to split up
Most theme park apps are built for a single visitor. Ride Guide is built for the party: everyone shares one itinerary, so when someone re-orders the day or adds a ride, it updates for the whole group instantly, no forwarding screenshots in a group chat.
One trip, multiple parks and resorts
A single resort's own app only knows about that resort. If your trip spans several parks, or even several resorts, Ride Guide is the one place tracking every day of it, instead of juggling a different app per park.
Families have different needs
Set each member's height once, and every ride shows whether they can go solo, need supervision, or don't meet the restriction, so you find out before you're stood in the queue.
Live wait times, in your plan
Queue times and showtimes sit next to the itinerary you're actually building, rather than in a separate wait-times app you have to cross-reference by hand.
Where the data comes from
Live queue times, operating status, showtimes, and the catalogue of resorts and parks are all provided by the ThemeParks Wiki API, a free, community-run project. Ride Guide couldn't offer real-time wait times or interactive park maps without it, and we're grateful to the people who maintain it.
Party data syncs peer-to-peer in real time between members' devices, which is what lets an itinerary update everywhere at once without waiting on a slow refresh.
Frequently asked questions
Ready to plan your next trip? Browse resorts