About halfway.travel
11,175 pairs · 150 cities · one build
What halfway.travel is
halfway.travel is one machine that answers road-trip questions with numbers. Type in two cities and it finds the town between them where you both spend about the same time behind the wheel. The registry behind it covers 150 US cities and 11,175 precomputed pairs, each with an estimated drive time, candidate meeting towns, and a fair-share score for each. Around that core sit stop planners for long drives, drive-or-fly comparisons, day-trip and one-tank indexes, hotels-near directories, six travel tools, and the state rule checkers — car seats, speed limits, tolls, chain laws and pets — that make up this section.
The mission is simple: one machine, one set of data, every page built the same way. When a page says a town is a 1 h 41 drive from each city, that number came from the same computation that powers every other page on the site.
What we are not
We are not a booking site. There is no account, no cart and no price feed on halfway.travel. When a page offers a hotel or flight search, it hands you to Kayak with an affiliate tag and lets you search there — see the affiliate disclosure for the plain-English version of that relationship. We never take payment to place a link, and we never publish prices, availability or ratings of our own. For the one analytics tool we do run and what it records, see privacy.
Who builds it
This is a founder-run site with no bylines and no invented experts. We do not believe in fake author pages, stock-photo teams or borrowed credibility. For a computed-data site, the honest substitute for author claims is method: the methodology page shows every formula, every data source and every limitation, so you can check the work instead of trusting a name. When we are wrong, the correction path is published — write to hello@halfway.travel and the fix ships with the next build.
The data promise
Every number on this site is either computed in public or cited to its source. Drive times in v1 are estimates from a road-factor model and are labeled as estimated everywhere they appear. Hotel counts are population-derived until the mapped-inventory upgrade lands. The rule checkers carry a citation and a retrieved date on every cell, plus a confidence level and a verify-with-the-state line — because laws change and we would rather be usefully cautious than falsely precise.
Contact and corrections
Write to hello@halfway.travel. Corrections are welcome and read; a correction that changes a number ships with the next build, and the methodology page records what changed. We cannot give legal advice — for anything riding on a rule, confirm with the state authority linked on each rules page.