Count the Hotel Changes Before They Consume the Trip.
Add each base, its nights and the moving time to the next city. The checker exposes one-night stops and transfer load before the route becomes a chain of check-outs.
Is the multi-city route still enjoyable?
The calculation stays on this page. It does not know your exact trains, airports or mobility needs, so use the result as an editorial warning and verify every live connection.
Moving time should include the realistic hotel-to-hotel journey: check-out, station or airport access, waiting, the service itself and onward transfer. The final base has no onward move.
Time on a train is not the whole transfer.
The checker deliberately asks for hotel-to-hotel time. A two-hour rail journey can still occupy half a day after packing, local transport, station navigation and check-in.
Keep it only when it earns the move.
A single night can be justified by a specific experience, an early departure or a route break. Otherwise, test it as a day trip or remove it.
Do not spend it twice.
If the move arrives late, that date cannot also carry a full sightseeing plan. Add the real arrival and check-in time before assigning attractions.
Protect at least one stable base.
Longer stays absorb weather, fatigue, laundry and missed reservations. A route with no margin is fragile even when every connection is technically possible.
Now verify the connections.
Use the pace verdict to simplify the shape, then check exact stations, airports, luggage rules and booking windows.
Route-planning references.
Official itinerary libraries establish realistic route shapes. The pace thresholds themselves are Trawoa editorial prompts, not operator rules.