How we compute estimates
Methodology
This page documents the exact method used to produce every estimate published on InstantTripCost. It's written for readers who want to understand or challenge the numbers, and for journalists or researchers who might cite the site.
Page last updated June 12, 2026.
The four data layers
Every published estimate combines four layers that together cover the six expense categories of a trip: flights, lodging, food, local transport, activities, and miscellaneous. Each layer is computed independently.
Layer 1: Flights
Flight prices are queried in near real time via specialized aggregator APIs. For each origin-destination airport pair, we retrieve the median round-trip economy fare observed over the selected window.
When the user specifies an exact date, we query that date. When the user specifies only a month, we query the whole month and keep the median across possible departures. The displayed price is a realistic anchor, not the day's best deal nor a marketing-grade average.
Layer 2: Lodging
Hotel rates are aggregated via specialized hotel-pricing APIs. For each city, we retrieve all observed prices over the last 90 days, then compute the median nightly rate per establishment category.
Three tiers are distinguished: hostel or budget hotel (1-2 star equivalent), mid-range hotel (3-4 star equivalent), premium hotel (4-5 star equivalent). The split relies on the official classification of the property and its observed rate.
A 90-day median smooths short-term swings and gives a fairer picture than a single point-in-time price.
Layer 3: Food and local transport
Food and local transport costs are not queried via API: they are calibrated from cost-of-living indices aggregated from public sources, then adjusted city by city by the editorial team.
Cost-of-living indices themselves are based on publications from international and national economic organizations (official statistics, purchasing-power comparisons, macroeconomic data). We normalize the Paris index to 1.00 and express every other city relative to it.
Manual adjustment kicks in when a generic index fails to capture a local specificity: unusual urban transit pricing, structural tipping system, typical meal price that differs from the standard statistical basket.
Layer 4: Activities
Activity recommendations come from a leading travel-experiences platform. Two filters are applied before publication.
Quantitative filter: minimum 4.3 rating out of 5, minimum 100 cumulative reviews. Below those thresholds, the experience is excluded.
Qualitative filter: we drop generic activities loosely tied to the destination, and tours that come across as tourist traps. The goal is to surface experiences characteristic of the place, not a universal catalog.
Why median, not mean
The travel market is skewed. A handful of extremely expensive or extremely cheap offers pull the arithmetic mean up or down, producing a number that doesn't represent what a traveler will actually pay.
The median (the price that splits offers into two equal halves) is insensitive to those extreme values. It better represents the price observed by most buyers. It's the default metric used on InstantTripCost for flights, hotels, and activities.
Refresh frequency
Each data layer has its own refresh cadence.
| Scope | Frequency | Note |
|---|---|---|
| Flight prices | Every estimate | Live API call. |
| Hotel medians | Every 90 days | Automatic recompute on a rolling window. |
| Cost-of-living indices | Annual | Full audit every January. |
| Curated activities | Quarterly | Ratings and new entrants reviewed. |
| Editorial pages | Case by case | Last-verified date shown on each page. |
Declared error margins
The stated target is an error margin below 15 % on the total trip cost, excluding categories explicitly not covered by the estimate.
This target accounts for the inherent variability of each layer: flights can vary 10 to 30 % depending on booking timing, hotels 15 to 25 % depending on availability, activities 5 to 15 % depending on season. Across a 5 to 10 night trip, these swings partly cancel out and the cumulative margin stays under 15 %.
The target is monitored internally by regular sampling against real cases.
External sources used
Estimates rely on three families of external sources.
Specialized commercial APIs for live-ish flight and hotel prices (professional aviation and hospitality aggregators with access to operator inventories).
Cost-of-living indices published by international and national economic organizations for food and local transport: official statistics, purchasing-power comparisons, macroeconomic data. Specific sources are cited as footnotes on the relevant destination pages.
Climate data from the European ERA5 reanalysis program (1991-2020 normals) for the temperatures, conditions, and best windows shown in the monthly calendar.
What the estimate doesn't cover
A number of categories are intentionally excluded from the calculation, either because they depend too much on individual choices, or because no source allows them to be estimated correctly at scale:
- personal shopping (souvenirs, clothing, equipment)
- emergency medical care or unscheduled consultation
- visa fees and administrative procedures
- culturally variable tipping
- unforeseen events (cancellation, lost luggage, equipment replacement)
- travel insurance (covered on request but not in the default total)
The user remains responsible for adding these categories to their personal budget when they apply.
Validation against real cases
Estimates are validated by cross-checking with real traveler reports. When a significant gap is observed between a published estimate and a real reported cost, the editorial team examines the cause:
- Error in the estimate: the data is corrected and the change documented.
- Edge case for the traveler: the gap is documented as normal variation, no change to the published estimate.
- Out of scope: the gap concerns a category not covered by the estimate (see section above).
This validation process is continuous. The frequency of significant gaps serves as an internal quality indicator.
Methodology evolution
The methodology evolves. When a significant change occurs (new source added, change to the hotel-tier split formula, revision of the activity filter threshold), the change is documented and the page's last-updated date is refreshed.
Minor changes (typo fixes, clarity rewrites) are not tracked. Structural changes are.
Reproducing our calculations
Someone who wants to reproduce a published calculation can do so from the following elements:
- the hotel median per tier published on the destination page
- the city's cost-of-living index (published on each destination page)
- the trip length and number of travelers
- the flight median available from the cited sources
The general formula is: total cost = flight per traveler + nightly rate per tier × nights × rooms + cost index × days × travelers × style coefficient + selected activities × travelers.
The editorial team can provide the calculation breakdown for a specific estimate on request at contact@instanttripcost.com.