Multi-City Trip Budget Calculator

1. 01Set travellers and a bufferEnter how many people are going and an optional buffer percentage for surprises. The daily spend and onward transport are counted per traveller.
2. 02Add each cityFor every stop, type the city name and the number of nights you will stay there. Use one row per city on your route.
3. 03Enter the numbers for each cityGive the lodging per night, the daily spend per traveller, and the onward transport to the next stop. There are no built-in prices, so use your own quotes.
4. 04Add or remove citiesAdd a row for each extra stop, or remove one you have dropped from the plan. The totals update as you go.
5. 05Read and copy the budgetSee the trip total, cost per traveller, the per-night figure, and the biggest city. Copy the breakdown to share or save.

• A Europe rail tripPlan three or four cities in a fortnight, with a train leg between each, and see the combined cost before you book anything.
• Comparing two routesTry a longer stay in fewer cities against a faster hop through more of them, and see which total fits your budget.
• Splitting the plan with friendsSet the number of travellers to see the per-traveller cost, then copy the breakdown so everyone works from the same figures.
• Setting a savings targetUse the total plus a buffer as the amount to save before departure, and track progress against it.

• Paris, three nightsAt 150 lodging per night, 80 daily per traveller with two travellers, and 60 onward transport per traveller, the city works out to 450 plus 480 plus 120, which is 1050.
• A three-city tripParis at 1050, Rome at 890, and Barcelona at 540 give a subtotal of 2480. A 10 percent buffer adds 248, for a total of 2728.
• Per traveller and per nightThat 2728 total across two travellers is 1364 each, and across eight nights it is 341 per night. Paris is the biggest single city.

• Keep one currencyThe tool does no currency conversion, so convert every figure to a single currency first and set the label to match.
• Use real quotesThere are no built-in prices. Pull lodging from a booking site and transport from a rail or flight search so each number reflects your dates.
• Add a bufferA buffer of 10 to 15 percent covers tickets, tips, and the odd splurge that a plain line-by-line plan tends to miss.
• Watch the intercity legsOnward transport is charged per traveller, so extra stops multiply quickly. Keep the number of legs sensible for the time you have.

Each city total is the lodging per night times the nights, plus the daily spend per traveller times the travellers times the nights, plus the onward transport times the travellers. The subtotal is the sum of every city total. The buffer is the subtotal times the buffer percentage, and the grand total is the subtotal plus the buffer. Cost per traveller is the total divided by the number of travellers, and the per-night figure is the total divided by the sum of all nights. The biggest city is simply the city with the largest total, which shows where most of the budget goes.

Inputs are the number of travellers, an optional buffer percentage, and one row per city with its name, nights, lodging per night, daily spend per traveller, and onward transport. Outputs are the total for each city, the subtotal, the buffer, the grand total, the cost per traveller, the per-night figure, the total nights, and the biggest city. The tool assumes lodging is a nightly rate for the whole party, that daily spend and onward transport are per traveller, and that every figure is entered in the same currency.

The calculator works as a live planner rather than a fixed form. Duplicate a plan and change one thing to compare scenarios: fewer nights in a pricey city, an extra stop, a bigger group, or a larger buffer. Because lodging is a party rate while daily spend scales with people, adding travellers raises some lines faster than others, and the per-traveller figure shows the effect at a glance.

As a rule of thumb, lodging is usually the largest share of a city stay, followed by daily spend, with intercity transport a smaller but real line. Keep the number of legs sensible: three to four cities in two weeks tends to balance travel time against seeing each place, while more stops mean more transport cost and more time in transit. Give pricier or slower-to-reach cities a night or two more so the onward transport is worth it. These are general planning ideas, not prices. The tool holds no built-in costs, so every figure you compare comes from your own research.

The estimate is only as good as the numbers you enter, and it does not know real prices for any city. A common mistake is mixing currencies, since the tool does no conversion, or entering a nightly lodging rate as a per-traveller figure. It also does not model one-off costs like visas, insurance, or the flights into the first city and home from the last, so add those separately if they apply.

Everything runs in your browser. The cities, nights, and amounts you type are not uploaded, not saved to storage, and not sent to analytics beyond a general usage signal. Refreshing the page clears the plan, and copying the summary is the only way anything leaves the tool.

Does it include prices for cities?

No. There are no built-in prices for any city. You enter your own lodging, daily spend, and transport figures, so the budget reflects your actual plan.

Does it convert currencies?

No. The tool does no currency conversion. Convert every figure to a single currency first, then set the currency label to match.

How is the cost per traveller worked out?

It is the grand total divided by the number of travellers. Daily spend and onward transport are counted per traveller, while lodging is a nightly rate for the whole party.

What does the buffer do?

The buffer adds a percentage of the subtotal to cover tickets, tips, and the unexpected. Set it to zero if you want the plain sum of your cities.

How many cities can I add?

Add a row for each stop on your route and remove any you drop from the plan. The subtotal, total, and biggest city update as you edit.

Is my plan saved?

No. Nothing is stored or uploaded, and refreshing the page clears your inputs. The maths runs entirely in your browser.