28 July 2026
Here's a problem anyone who travels properly will recognise. You fly to Bangkok, catch a train to Chiang Mai, bus it up to Pai, fly to Phuket, then home. In most flight trackers, that shows up as three separate, disconnected flights sitting in a list. No trains. No buses. No sense that it was actually one three week adventure through Thailand. That's the gap Journeys is built to close.
Journeys lets you group everything from a trip together, not just the flights. One journey can include your flights, sure, but also your trains, buses, ferries, the hotels you stayed in, how many nights you were away, and which countries you actually set foot in.
So instead of your Bangkok to Pai to Phuket adventure showing up as three unrelated flight entries buried in your logbook, it becomes one journey called "Thailand 2024" or whatever you want to name it. Open it up and you see the whole thing laid out. The flights, the overnight train, the minibus to Pai, the four different hotels, the eighteen nights away, and the fact you crossed through one country the whole time (or three, if you added a side trip to Laos).
It's the difference between a spreadsheet of flight numbers and an actual travel diary.
A lot of people don't realise how disconnected their flight history actually looks until they see it grouped properly. You might have twelve flights logged from a single year of overseas work, and looking at them individually, they just look like a person who flies a lot. Group them into journeys and suddenly you can see it was actually four separate work trips and one proper holiday. Completely different story.
It's also just more honest about what travel actually is. Nobody's trip is only the flight. The flight is the boring bit in the middle. The journey is the trains, the ferries, the two nights in a hostel in Chiang Mai you'll never forget, the week in a rental in Byron Bay. Journeys treats all of that as part of the record, not just the aviation bits.
You can add trains, buses, and ferries to a journey the same way you'd add a flight. Departure, arrival, date, that sort of thing. It doesn't need to be exhaustive. If you took the overnight train from Bangkok to Chiang Mai and you remember roughly when, that's enough to add it.
This matters for anyone doing proper multi-modal travel. Europe by rail. Southeast Asia by bus and boat. Someone who island hops around the Whitsundays on ferries. None of that is a flight, but all of it is genuinely part of how you got around, and now it's part of the record instead of a gap in your history.
You can log the hotels or accommodation for a journey too, along with how many nights you were actually away. This is one of those stats that people don't think to track until they see it. Add up every journey you've logged and you'll get a genuine answer to "how many nights have I actually spent away from home this year." Most people guess wrong. Usually low.
It's also handy for anyone who needs this for practical reasons. Working out tax related travel time. Remembering how long a particular trip actually was when someone asks. Settling an argument with a partner about whether that Bali trip was one week or two (it was ten days, the data doesn't lie).
Each journey shows you a breakdown of which countries were involved. For a simple return flight to New Zealand, that's obviously just one country. But for a multi-leg overland trip through Southeast Asia, or a European trip where you flew into Paris and trained through four more countries, this is where Journeys becomes genuinely useful. You get an honest count of where you actually went, not just where you flew into and out of.
This feeds into your overall country count too, which is one of the more satisfying numbers in Jetmap for a lot of people. Grouping trips into journeys makes sure that count reflects everywhere you actually travelled through, not just the airports you landed at.
Journeys isn't only for looking backward. You can set up a journey for a trip that hasn't happened yet. Got a flight booked for December and you're already planning the trains and hotels around it? Build the journey now. Add the confirmed flight, the accommodation you've booked, the legs you're still deciding on.
It's a genuinely useful way to keep the whole plan in one place instead of scattered across email confirmations, a notes app, and a half finished spreadsheet. And when the trip actually happens, the journey's already there waiting, ready for you to fill in anything that changed.
Head to the Journeys section and create a new one. Give it a name, something like "Japan Winter 2025" or "Contiki Europe" or whatever makes sense to you. Then start adding to it. Pull in flights you've already logged, add any train, bus, or ferry legs, note down accommodation, and Jetmap handles the rest, working out nights away and country counts automatically.
You don't need to build it all in one sitting. Add flights as you log them, come back and add the ferry from Koh Samui once you remember the date, throw in the hotel details when you dig up the booking confirmation. It grows as you fill it in.
Flight logging on its own tells you where you flew. Journeys tells you what you actually did. For most people, that second version is the one that actually matches their memory of a trip. Nobody looks back on a holiday and thinks about the flight number. They think about the sixteen nights, the three countries, the overnight train they nearly missed, and the ferry that turned up two hours late.
That's the record Journeys is trying to build. Give it a go with your next trip, or better yet, go back and group up some of your past ones. You might be surprised how different your travel looks once it's the whole story instead of just the flights.
Track every flight you take and build a complete record of your aviation journey.
Get started on Jetmap