Distance units become important the moment a road trip crosses a border, a rental car uses a different dashboard, or a tyre calculator asks for kilometres while your route planner shows miles. The conversion itself is exact; the challenge is keeping every related input in the same unit.
The relationship behind the number
Kilometres = miles × 1.609344. Miles = kilometres ÷ 1.609344.
Numbers on a real vehicle
A 60-mile journey is 60 × 1.609344 = 96.56064 km, normally displayed as 96.56 km. A 100 km route is 100 ÷ 1.609344 = 62.1371 miles. If fuel economy is 8 L/100 km, apply it to 96.56 km—not to the unconverted 60 as though they were the same unit.
Before you compare two results
Statute miles are used for ordinary road distances; nautical miles belong to navigation and equal 1.852 km. For a driving budget, convert the route distance, then check that fuel economy and price are expressed in compatible volume units too.
Where estimates commonly go wrong
Rounding 1.6 too early can create a noticeable difference on a multi-day route. Also check whether a vehicle’s trip computer is set to miles or kilometres before copying the reading into a calculator.
Keep the numbers useful over time
Conditions change. Fuel prices move, tyres wear, a battery loses usable energy in cold weather, and a vehicle’s mileage changes its resale value. Date your estimate and note the market or unit standard it uses. A dated, explainable estimate is more useful than a highly precise number with no trail back to its assumptions.
For comparisons, change one variable at a time. That reveals what is actually driving the result and avoids the false confidence that comes from changing distance, price and efficiency together.
A small habit that improves every estimate
Use a notebook or phone note with four columns: input, number, unit and source. It takes longer than typing three figures from memory, but it makes later corrections straightforward. You can replace a fuel price without accidentally replacing the MPG standard, or update an odometer reading without losing the earlier baseline.
For comparisons, keep the method fixed. Compare two cars with the same route, passengers, price date and ownership period. That is more informative than collecting impressive-looking figures from different adverts and hoping the labels line up.
Use a second scenario, not a second guess
Once the first answer is on screen, change one assumption that could realistically move. For a journey that might mean adding a detour; for a tyre calculation it may mean comparing an approved alternative; for finance it may mean a shorter term. Keeping every other input unchanged tells you how much that single choice matters. Write down the result and the assumption beside it.
This is also a useful way to spot implausible inputs. If doubling a distance barely changes a fuel bill, something is wrong. If a small tyre-profile change produces an enormous diameter difference, check the rim conversion and percentage calculation. A quick sense check often catches a typo before it becomes an expensive decision.
One detail worth carrying forward
Rental cars deserve an extra check because the odometer, speedometer and trip computer may not all use the same display setting. Photograph the starting mileage and note the unit before leaving the depot. It prevents an innocent unit error from becoming a disputed fuel or mileage charge.
Convert the route first, then use the fuel-cost or consumption calculator with matching units. For official specifications, safety limits and contract terms, use the responsible manufacturer, professional or lender document as the final authority.
Questions drivers often ask
Is one mile exactly 1.6 kilometres?
No. 1.6 is a convenient approximation; the exact statute-mile conversion is 1.609344 km.
Why do maps sometimes differ slightly?
Mapping services round routes, choose different roads or include different access roads and detours.
Can I convert fuel economy at the same time?
Yes, but distance and volume conversions must be handled together; changing only the distance unit gives a false result.
Updated September 10, 2026