How we calculate our route figures
Every number on a route page is either measured, modelled, or derived from something we publish. This page states which, and where each figure falls short.
Last reviewed 2026-08-03
What we will and will not claim
We publish internal indices and label them as internal. We do not publish comparative or ranking claims — statements like “one of the busiest corridors in America” or “top 12% of US routes” — unless we have computed them against a stated population using a stated dataset.
Where a figure is a placeholder awaiting a real data load, we say so on the route page rather than presenting it as measured.
How we calculate costs
Route popularity score
0–100 internal index
Composite of estimated annual household moves on the corridor, origin and destination population, and our own quote volume.
Current status: Internal model — POC placeholder pending ONS international migration and first-party quote data load
Monthly demand index
0–100, where 100 is the busiest month
Seasonality curve for the corridor. The 12-month average and the peak-season label are computed from this series, never stored separately.
Current status: Internal seasonality model — POC placeholder pending own international quote volume by month
Average booking notice
Days
Median gap between quote submission and requested move date on the corridor.
Current status: Internal model — POC placeholder pending ONS international migration and first-party quote data load
Households moving annually
Count
Origin-to-destination migration volume, intended to be sourced from IRS Statistics of Income county-to-county migration data and Census ACS county migration flows.
Current status: Internal model — POC placeholder pending ONS international migration and first-party quote data load
Move complexity
Low / Medium / High
Distance band, typical building access at both ends, and the share of moves needing packing, storage, or vehicle transport.
Current status: Internal complexity model — customs, ocean transit, access at both ends, and service mix
How route scores work
Route scores combine distance, complexity, transit time and commercial signals from our corridor database. They are internal planning indices — not guarantees of service quality from individual movers.
Derived figures
Some figures are computed from others at render time so they cannot drift apart. For New York → London:
- Average demand index (72) — the mean of the twelve monthly values shown in the demand chart.
- Peak season (May–September) — the months scoring at or above 85% of the highest month.
- Transit window (14–28 days sea freight) — modelled door-to-door sea freight for international routes (14–28 days); air freight 3–7 days for smaller or urgent shipments. Domestic routes use 2 base days plus 1.5 days per 1,000 miles.
How the cost calculator works
The calculator applies configurable multipliers to a base cost band for your home size. It is deliberately simple and is not a quote.
| Input | Adjustment |
|---|---|
| Packing required | ×1.15 on the cost band |
| Peak-season move date | ×1.1 for May to August |
| Storage required | +$200–$450 |
| Recommended mover type | Selected by home size — sea freight consolidated load for international routes; rental truck, container, or van line for domestic |
Intended data sources
- IRS SOI county-to-county migration data ↗ — household and exemption counts between counties
- Census ACS migration flows ↗ — county-level in and out migration estimates
- Our own quote volume, seasonality, and buyer acceptance data
- Google Search Console impressions and clicks per route page
Known limitations
- Migration data is filed annually and lags the current year.
- County-level data does not distinguish a city move from a suburban one.
- Cost bands are national averages adjusted for distance, not carrier pricing.
- Our own quote volume reflects our traffic mix, not the whole market.
Spotted a figure that looks wrong? Tell us and we will check it.