Miles, kilometers and odometer records on imported project cars

Keep every imported car's odometer reading in its original unit, then convert a separate comparison column to one common unit. Order records by the date of the reading rather than the date you downloaded a report. A lower-looking number can be a unit difference; an orderly timeline still does not establish the car's total distance.

This is a blank reconciliation method. It contains no vehicle example, fraud finding or distance estimate for a real car. Import permission and registration belong in the existing cross-border guides.

Preserve the original evidence

For each record, retain the event date, exact number, stated unit, issuer and any qualifier attached to the reading. Keep the report-generation date separately. If the date or unit is unclear, record the ambiguity rather than choosing the interpretation that produces the neatest timeline.

Do not use the speedometer's speed scale as evidence of the unit attached to a particular historical distance entry. Ask what the original record actually states. For an instrument replacement or a reported unit change, request the dated supporting record and any recorded before-and-after readings; do not invent a starting value for the gap.

NHTSA recommends comparing the odometer with ownership, maintenance and inspection records. That US consumer guidance supports checking multiple records, not treating a single display or converted number as a complete history.

Convert a comparison column only

NIST's conversion table gives the international-foot mile as exactly 1609.344 meters. For ordinary road-distance comparisons:

kilometers = miles × 1.609344

miles = kilometers ÷ 1.609344

Keep the original reading unchanged. State any rounding used in the comparison column and do not imply greater precision than the source reading provides. A conversion factor does not improve the accuracy or authenticity of the underlying record.

If the unit is unknown, leave the normalized value unknown. You may write a question for the issuer, but neither possible conversion becomes a confirmed reading merely because it aligns with nearby entries.

Build the distance timeline

Copy this original blank sheet for the records you actually possess. The rows name evidence positions to fill, not events known to have occurred.

Add rows rather than compressing conflicting entries into an average. Preserve a record's wording about uncertain distance or disclosure status. Arithmetic cannot remove a qualifier, and a qualifier is not itself a measured distance.

Read the sequence without diagnosing fraud

Compare adjacent readings only after confirming the units and event order. If a later normalized reading is lower, identify the two conflicting records and ask their issuers to explain. If the readings are equal or very close, check whether the records refer to the same event before treating them as separate observations.

Do not apply an invented tolerance to dismiss a discrepancy. Rounding, a transcription issue, an instrument replacement or manipulation are possibilities to investigate, not conclusions established by the worksheet. Leave the cause unresolved until evidence addresses it.

A rising sequence also has limits. The NMVTIS consumer disclaimer lists the most recent odometer reading in the state's title record among available US data and notes differing reporting intervals. That is a dated administrative reading, not a live display or a complete international distance log.

Carry unresolved distance into the purchase decision

Write a short conclusion stating what records you have, the unit conversions made and the remaining gap. Do not advertise an exact total distance from a timeline whose instrument history or source units remain unresolved. Ask the relevant authority about any required treatment of uncertain readings for your transaction.

Keep the record-system limits in the NMVTIS, NICB and decoder comparison separate from your arithmetic. When comparing vehicle listings, request the missing dated evidence before using distance as a reason to prefer one project.