A multi-city trip planner that keeps the legs straight
Six cities, four flights, two trains and a hire car belong on one timeline, in the order they actually happen. Each leg keeps its own dates and details, layovers appear as their own arrival and departure on the day they occur, and the whole route is visible at once on a single map.
Six cities, one timeline
A long trip is not a list of destinations, it is a sequence. What you need to see is which night you are where, which morning you are moving, and which afternoon has nothing in it yet — across the whole trip rather than one city at a time.
Every item sits on the day it happens, so the shape of the trip is legible: the three nights in one place, the travel day with nothing else in it, the two cities that are somehow only eleven hours apart because the flight is at dawn.
Layovers are their own rows
This is the detail most planners get wrong. A flight with a connection is not one event from A to C — it is an arrival at B, a wait, and a departure from B, and those can straddle midnight or a date line.
A multi-leg journey keeps its connections: each stopover is expanded into its own arrival and departure, placed on the day it actually happens. So a Sydney–Singapore–London itinerary shows you the Singapore ground time as a thing you have, on the correct date, rather than burying it inside a single fourteen-hour block.
Why it matters more than it sounds
Ground time is the difference between a connection you can leave the airport for and one you cannot. If the plan collapses it into a single leg, you have to reconstruct it from the booking every time somebody asks.
One booking, several destinations
Bookings do not respect the structure of a trip. A single confirmation email can contain an outbound, a return and two internal flights; a rail pass can cover a fortnight. Forwarding one of those in produces the individual legs rather than one undifferentiated blob, so each lands on its own day.
The return direction is handled too, which sounds trivial until you have used something that files the outbound and quietly loses the way home.
Costs across borders
Multi-city almost always means multi-currency. Costs are recorded in whatever they were actually paid in, and the settle-up resolves the whole set at the end rather than asking you to convert as you go.
For a trip through three countries with four people, that is the difference between a budget you can trust and a spreadsheet somebody abandoned on day two.
On the day, with no signal
Long multi-country trips are exactly where connectivity is least reliable and where having the plan matters most — a new SIM, an airport with no free wifi, a border crossing at 6am.
The itinerary is stored on the phone, so the whole sequence opens with no signal. What you lose offline is map imagery and looking up new places, not access to your own plan.
Questions people ask
How many stops can one trip have?
There is no practical limit for a normal trip. Long multi-country routes with a dozen or more legs sit on one timeline in date order.
Does it handle layovers properly?
Yes. Each stopover becomes its own arrival and departure on the day it happens, rather than being hidden inside a single leg from origin to final destination.
Can one booking cover several legs?
Yes. A confirmation containing multiple flights produces the individual legs, each on its own date, including the return direction.
What about crossing the date line?
Items are placed by their own dates and times, so an arrival on the other side of the date line lands on the date it actually happens rather than the date you departed.
Can I plan a multi-city trip with other people?
Yes, and it is free. Shared itineraries, voting and cost splitting are all on the free tier and collaborators do not need a subscription.
Get the whole route on one screen
Every leg, every layover and every night, in the order they happen — and on the map at the same time.