Skip to the guide

Trip planning

Simulate a multi-country itinerary

Build a sequence of proposed stays and inspect the combined result.

6 min readIntermediateChecked on app v3.10Updated

Before you start

  • Nomad Tracker for iPhone, iOS 17.1 or later.
  • No subscription needed to build a simulation. Saving one as a named group is PRO.
  • A logged travel history, so the simulated days have something to add to.
  • Verified on an iPhone 17 Pro running iOS 26.2.
On this page

What you’ll achieve

By the end of this guide a trip with two stops sits in your calendar as two ghost trips, and every counter it touches shows what the whole itinerary would cost you.

One rule decides everything here: one leg, one ghost trip. A single ghost trip with two countries in its Location list does something else entirely, and it is the mistake worth avoiding before you make it.

The example plans three weeks in Japan followed by two in Taiwan. Plan your first trip with Ghost Trips covers a single trip in more detail.

Step 1: Build the first leg

Open the Calendar tab, tap Add in the top right, then Add Ghost Trip.

Move to the month you are planning, tap the first day of the leg and then its last day. In Location, tap the minus button to drop the country the sheet filled in, tap Add Country, and pick the first stop.

The Add Ghost Trip sheet with June 1 to 21 selected in the grid and Japan in the Location list

One country in the list. Tap Add.

The Start and End boxes above the calendar print a day earlier than the days you tapped. Trust the grid: the highlighted days are the days the app saves.

Step 2: Build the second leg

Tap Add, then Add Ghost Trip again, and repeat for the next stop: first day, last day, then its country.

The sheet with the Japan leg already showing as dashed rows across the first three weeks, and June 22 to July 5 selected with Taiwan in the Location list

The leg you already added is visible in this sheet as dashed rows labelled with its country, which is how you check the new leg starts where the last one ended rather than overlapping it.

A leg can run past the end of the month. Select into the next month and the sheet follows.

Tap Add.

Step 3: Read the itinerary in the calendar

Move the Calendar tab to the month you planned.

The June calendar with Japan dashed rows over the first three weeks and Taiwan over the last, a chip counting 30 ghost trip days, and a THIS MONTH row reading 0 of 30 days with Jun 1 to 21 Japan and Jun 22 to 30 Taiwan

Both legs sit in the grid with their own colour and a dashed outline, each row labelled with its country. The chip above counts them together: 30 ghost trip days in June.

THIS MONTH still reads 0 of 30 days, because none of these days is logged. Underneath, the stay list splits the month by leg: Jun 1 - 21 Japan 21 days, Jun 22 - 30 Taiwan 9 days.

That second row is the interesting one. The Taiwan leg is 14 days long, but only 9 of them are in June.

The July calendar with a Taiwan dashed row over the first five days, a chip counting 5 ghost trip days, and a Jul 1 to 5 Taiwan row

The other 5 are in July, where the same trip appears again. Each month shows the part of the itinerary that falls inside it.

Step 4: Read the combined total

Open the Dashboard tab.

The dashboard with Year Distribution gaining a Ghost trips entry of 35 days and Remaining falling to 197, and a Simulation tile counting 2 ghost trips in your numbers and 35 planned days

Year Distribution gains a single Ghost trips entry for the whole itinerary, 35 days, and Remaining falls from 232 to 197.

The Simulation tile at the front of the widget strip counts the legs rather than merging them: 2 ghost trips in your numbers, 35 planned days.

Check your result

Scroll to Countries and read the cards for the countries you routed through.

The Taiwan card at 34 of 90 with 14 simulated and 56 days remaining, above the Japan card at 25 of 90 with 21 simulated and 65 days remaining

Each card grew by its own leg and no more. Japan reads 25 / 90 with 21 simulated under the bar, Taiwan 34 / 90 with 14 simulated.

Add each leg to the country’s real total and you should land on the number the card shows. That is the check: an itinerary that spreads one period across two countries would add the same days twice, and the arithmetic would not hold.

If something looks different

One trip covers both countries. You put two countries in one Location list. That spreads the same period across all of them, so both counters gain every day. Delete it and build one trip per leg. Edit or clear a simulation covers the deletion.

The legs overlap by a day. The first leg’s last day is also the second leg’s first day. The app lets you do it, and both countries then count that day. Decide which country the travel day belongs to, and leave it with one of them.

A leg is missing from the month you are looking at. It falls entirely in another month. The chip and the stay list only cover the month on screen.

A card did not move. The country is not in any leg’s Location list, or the leg lands in a different year from the one the dashboard is showing.

Remaining did not fall by the full total. Days simulated into next year belong to next year. The dashboard shows one fiscal year at a time.

The simulation disappeared. The active simulation lasts for the session. Save and reload a trip simulation keeps an itinerary you want to come back to.

Next steps

Save and reload a trip simulation stores the itinerary under a name so a session end does not lose it.

Edit or clear a simulation removes one leg or all of them.

Preview a future Schengen trip is the version of this to read when a leg crosses the Schengen area.