Every chart in this report is computed from raw DIMO telemetry the vehicle owner authorized us to read. Here's exactly how each number was derived, what signals we used, and where the limitations are.
A DIMO-compatible OBD device plugs into the vehicle's OBD-II port and reads signals from the engine computer roughly every ten seconds. Those signals — speed, fuel level, coolant temperature, RPM, odometer reading, and others — are aggregated and timestamped, then pushed to the DIMO telemetry API.
The observation window for this report is . All analytics in this report are derived exclusively from signals collected in that window.
The fuel economy figure in this report is a telemetry estimate: fuel burned is reconstructed from changes in the dash fuel-level gauge between refuels, and distance comes from the odometer signal. The result tracks pump receipts closely but is not a pump-receipt log.
Gallons burned per tank are estimated by converting fuel-level percentage changes against the 31-gallon rated tank capacity. Partial fill-ups and gauge noise introduce a small amount of error.
Distance comes from the odometer signal sampled at 10-second intervals. Because the snapshots don't capture every instant, they tend to undercount total miles by a few percent compared to the dashboard odometer — particularly on short trips with frequent stops. The fuel estimate is generally within ~1–2% of receipts; distance can run ~3–5% low.
Trips are detected using frequency analysis: a period of driving is defined as a window where signals update at a high rate, with gaps of less than 300 seconds merged together. This approach works across the full observation window regardless of whether the ignition signal is available.
Hard-brake and harsh-cornering events are detected by a separate behavior analyzer that processes driving sessions independently. The first and last event timestamps in the hotspots data reflect the window the behavior detector actually analyzed — this may be narrower than the full telemetry window shown above if the detector was applied to a subset of sessions.
The device's odometer signal arrives in 10-second snapshots. Each snapshot captures the odometer at a point in time; the distance driven between consecutive snapshots is computed by subtraction. On smooth highway driving the snapshots align well. In stop-and-go or on short trips, the 10-second cadence misses micro-movements and the per-trip total runs a few percent below what the dashboard odometer would show.
Across the full observation window, the cumulative undercount is typically in the 3–5% range. Fuel-level derived gallons are generally more accurate than the distance signal, which is why the telemetry MPG estimate skews slightly below pump-receipt figures.
This report is private to the vehicle owner: trip start and end points are shown as raw GPS coordinates, and each trip's full route trace is available on the trips page. Nothing here is published anywhere — any future shared version of this report will blur start and end locations to neighborhood scale before it goes out. Short trips under 2 miles are excluded from the trip list.