Every chart on this site is computed from raw DIMO telemetry the vehicle owner cryptographically granted us the right to read. Here's exactly how each number was derived, what signals we used, and what we deliberately didn't show.
DIMO's telemetry API exposes five trip-detection mechanisms. We used frequency analysis, which detects activity by signal-update rate rather than relying on the isIgnitionOn signal (which didn't start reporting until 25 Oct 2025). This gave us a consistent view across the full observation window.
Physical tank on this Laramie is 26 gallons (the standard size; the build sheet does not include the optional Max Fuel Tank package). But the dash gauge's 0–100% range does not span all 26 gallons. The needle holds at 100 for the first few gallons of consumption (top buffer), and the low-fuel warning triggers with roughly 3 gallons still in the tank (reserve below 0%). The actual fuel transit across the 0–100 dash swing is closer to 20 gallons.
We do gallons-from-percent math because the dash percentage is the only fuel-level signal exposed — the truck's own in-dash MPG matches the EPA sticker because it reads injector flow directly, not the gauge. Using the effective 20-gallon dash range reconciles our lifetime number to within 0.04 mpg of EPA combined.
Our first detector relied on a single signal: the ratio of engine revolutions per mile per hour. For a Ram 1500 with the Hurricane I-6 and 8HP70 transmission, unloaded highway cruise sits at roughly 26 RPM per MPH. When hauling, that ratio climbs because the transmission holds a lower gear. Simple, mostly correct — except it flagged one February trip where the driver had bumped the steering-wheel gear-limiter down a notch. Same elevated ratio, no trailer.
V2 requires two signals to agree. A real tow burns obviously more fuel (7–10 MPG vs. 17–22 unloaded) and spikes RPM hard when accelerating from stops. Either alone is noise. Both together are unambiguous.
The vehicle owner granted us specific signal permissions via an on-chain SACD document, including exact GPS. For privacy in this public write-up we: