94,022
HEALTH CHECKS.

Every few minutes for nine months, the Ruptela R1 dongle asked the Ram's engine computer: "Any problems?" The answer came back 94,022 times. Ninety-nine point seven percent of those answers were "No." That's not the absence of bad news — it's ninety-four thousand timestamped, verifiable receipts of good health. This is something no used-car listing, no Carfax report, and no dealer inspection can match: a cryptographically anchored engine-health diary, one reading every three minutes, for the life of the vehicle.

HEALTH CHECKS
94,022
READINGS OF obdStatusDTCCount
■ 93,724 CLEAN (99.68%) ■ 298 FAULT (0.32%)
DISTINCT DTCS
2
IN 263 DAYS
FAULT READINGS
298
OF 94,022 · ALL IN FIRST 24 HRS
MIL-ON DISTANCE
85 KM
53 MI · THEN CLEAR FOREVER
CLEAN STREAK
261 DAYS
28 JUL 2025 → 15 APR 2026
CURRENT MIL
OFF
NO DTC WITH DISTANCE
THE CODES

DECODED.

P068A
INFO · NON-CRITICAL

ECM/PCM Power Relay De-Energized Performance — Too Early

The engine-control module detected that its main power relay lost voltage earlier than expected after shutdown. On a 2025 Ram 1500, this fires routinely on the first key-cycle after any battery disconnect — including the one that happens when you plug in a new OBD dongle.

Implication: none. The code clears after one full drive cycle. It's the automotive equivalent of a router rebooting after you plug in a new Ethernet cable.

Reported: 6 times between 27 Jul 14:51 and 28 Jul 09:52, then never again.

P1DB1
INFO · MANUFACTURER

PCM — Keep-Alive Memory Reset (Stellantis)

A Stellantis-specific code that records when the powertrain-control module's long-term memory has been cleared. Same cause as P068A: battery interruption when the Ruptela R1 dongle was first installed.

Implication: none. The PCM relearns its adaptive values over the next 50–100 miles of driving. No warranty flag.

Reported: same 6-entry window as P068A. Paired together each time.

TIMELINE

EVERY APPEARANCE.

#TIMESTAMPCODES PRESENTMIL STATUS
12025-07-27 20:51:02 UTCP068A, P1DB1ON
22025-07-28 13:56:31 UTCP068A, P1DB1ON
32025-07-28 13:57:14 UTCP068A, P1DB1ON
42025-07-28 15:18:24 UTCP068A, P1DB1ON
52025-07-28 15:51:24 UTCP068A, P1DB1ON
62025-07-28 15:52:07 UTCP068A, P1DB1ON
2025-07-28 through 2026-04-15(cleared)OFF

The healthy summary: the Ram drove 10,000+ miles without throwing a single new diagnostic code. The two we caught were "the dongle got plugged in" codes, which is not a complaint about the truck — it's a complaint about us.

Imagine selling this truck in three years. Instead of saying “no problems,” you hand the buyer ninety-four thousand timestamped receipts that prove it. That's what data ownership actually means.
— ON THE VALUE OF PROVABLE HEALTH
THE NUMBERS

WHAT 94,022 LOOKS LIKE.

The Ram's OBD port was polled for diagnostic status roughly every three minutes, twenty-four hours a day, for two hundred sixty-three days. Every response was timestamped and pushed to the DIMO network. After the first day's install codes cleared, not one of the remaining 93,724 readings reported a fault. That's not "we didn't check." That's "we checked ninety-three thousand seven hundred twenty-four times, and every time the answer was the same: healthy."

SignalobdStatusDTCCount
Total readings94,022
Clean readings (dtcCount = 0)93,724 (99.68%)
Fault readings (dtcCount > 0)298 (0.32%)
Fault window27 Jul 20:45 → 28 Jul 15:52 (19 hours)
Clean streak since261 consecutive days
Distance driven with MIL on85 km (53 mi) — then zero
Polling frequency∼1 reading every 3 minutes

A traditional vehicle history report tells you what was reported. This is what was measured — ninety-four thousand times, by the engine itself, anchored to a blockchain-signed data stream. The difference is the difference between a claim and a receipt.