A ten-night trip can look generous on a calendar and crowded in practice. Arrival day may be foggy. Departure day is mostly spoken for. Every change of hotel consumes more than the train time shown in a search result.
The short answer
Begin with two bases and earn the third. Add another stop only when the route is unusually efficient or that place matters more than the unhurried time you would give up.
Count usable days first
Write the trip as days, not as cities. Ten hotel nights span eleven calendar days. Arrival and departure take up part of two days; count hotel changes against the nine days between them. Then mark every day that includes a hotel change.
I divide the calendar into three kinds of time:
- Full days: you wake up and go to sleep in the same place, with the day available to experience it.
- Transition days: you check out, move, orient yourself and check in again. Even a short transfer changes the rhythm.
- Edge days: the arrival and departure dates, which should not be treated like ordinary touring days.
If the draft has more transition days than full days in a destination, the route is probably describing a collection of places rather than a satisfying trip.
What two bases can make possible
Two bases can give each place enough time for a major day, a slower day and some margin for weather, fatigue or discovery. They also make better hotels more valuable because you are there long enough to enjoy them.
A day trip can extend the reach without another move, but it should not be used to pretend that one base serves an entire country. The question is whether the outing adds something distinct without creating another dawn departure and late return.
When three stops can work
Three can work when the geography forms a clean line, the transfers are dependable and each stop has a clear purpose. A gateway city, a smaller intermediate place and a final city can feel coherent. Three destinations connected by awkward flights usually do not.
Jeremiah's routing test:
Can you explain why each move improves the trip? “It is nearby” is not enough. The next place should offer an experience the current base cannot, and the transfer should not consume the experience it is supposed to create.
Use the flights to protect the route
An open-jaw itinerary, arriving in one city and departing from another, can remove a backtrack. It is often worth comparing even when the airfare is not the lowest visible option. The fair comparison includes the hotel night, train or flight, transfer and vacation time needed to return to the first city.
The same principle applies to the first day. If a traveler is joining a cruise or a fixed event, I would rather protect that commitment with appropriate arrival margin than squeeze in one more place beforehand.
What I would ask before choosing
- Which two experiences would make the trip feel worthwhile even if nothing else were added?
- Does anyone in the party find packing, stairs, stations or early departures especially tiring?
- Are the travelers energized by constant novelty, or do they settle into a place on the second day?
- Is the trip trying to sample destinations for the future, or enjoy this trip fully now?
- Can an open-jaw flight or a well-chosen day trip remove a hotel change?
The point is not to travel slowly as a rule. It is to spend vacation time on the experience the traveler actually values, rather than on a route that looked efficient from a distance.