Journeys and multi-leg journeys

A journey is Point A to Point B. Direct trips have one leg. Multi-leg trips keep every airside connection on the same journey.

Layovers vs stopovers

Ask whether you left the airport and cleared immigration.

• Yes. Split the trip into separate journeys. You were present in that country.
• No. Keep one journey. Add each airside connection as a leg.

Example. NYC → Dubai (overnight, you left the airport) → Bangkok is two journeys. NYC → Dubai (2 hour airside layover) → Bangkok is one journey with two legs.

Domestic hops that never leave a country still belong in the ledger. Day-count tools ignore them because they do not change country presence.

Local time, not UTC

Enter the local time at the origin for departure and the local time at the destination for arrival. Do not convert either clock. The app applies timezones from the cities you pick. Check daylight saving when a city looks wrong.

Days spent only in transit (on a plane or ferry, between the departure date and the arrival date) do not count toward any country.

How presence is stored

Each international journey stores country-departure and country-arrival stamps from its legs. Residency, Schengen, and travel summaries use those stamps. The list view uses the first-leg departure and last-leg arrival as display bookends. On a multi-leg journey those two clocks can differ.

Create and edit require the full legs list you want. Replacing the route replaces every existing leg.