NHTSA vPIC DIRECT ENDPOINT / 49 CFR PART 565 · CMVSS 115 COMPLIANT / FREE · NO LOGIN · UNLIMITED
MOD-11 CHECK-DIGIT VALIDATOR READY / CLIENT-SIDE QUERIES ONLY

18 Sample VINs, Decoded: Only 3 Pass the Check Digit

Type "sample VIN" into any search engine and you'll find the same handful of 17-character strings copied across developer docs, decoder demos and blog posts. We took 18 of the most widely circulated ones — every VIN we could find that appears on multiple independent sites — and ran each through the official NHTSA vehicle database on October 24, 2026. The result surprised us: only three pass the check digit.

The dataset

Each VIN below was decoded live against the NHTSA vPIC registry. "Check" is the 9th-character checksum that US and Canadian regulation — NHTSA 49 CFR Part 565 and CMVSS 115 — requires for 1981-and-later vehicles sold in those markets; it is the same mod-11 math our decoder runs in your browser. Vehicles built for other markets follow the same 17-character frame but were never required to implement the check, so a Fail on one of those is not an accusation.

VINDecodes toPlantCheck digit
1HGCM82633A004352Honda Accord EX-V6, 2003Marysville, USAPass
2T1BURHE0FC320645Toyota Corolla L/LE, 2015Cambridge, CanadaPass
1G1JC5444R7252367Chevrolet Cavalier, 1994Lordstown, USAPass
1FTFW1ET5DFC10312Ford F-150, 2013Dearborn, USAFail
3VWN57BU0KM147976Volkswagen Jetta S, 2019Puebla, MexicoFail
5YJ3E1EA8KF304550Tesla Model 3, 2019Fremont, USAFail
1C4RJFAGXFC812345Jeep Grand Cherokee Laredo, 2015Detroit, USAFail
JTHBW1GG7D2001559Lexus ES 300h, 2013Miyawaka, JapanFail
WBA3B5C59DF603123BMW 328i, 2013Munich, GermanyFail
WP0AA2A92ES106086Porsche 911 Carrera, 2014Stuttgart-Zuffenhausen, GermanyFail
JN1AZ4EHXHM950144Nissan 370Z, 2017Tochigi, JapanFail
1FA6P8TH4J5107932Ford Mustang I4, 2018Flat Rock, USAFail
3FA6P0H73HR139766Ford Fusion SE, 2017Hermosillo, MexicoFail
2C3CDXGJ7HH592173Dodge Charger R/T 392, 2017Brampton, CanadaFail
WDDGF8BB3BR123456Mercedes C300 4MATIC, 2011East London, South AfricaFail
5NPD84LF8JH333456Hyundai Elantra, 2018USA (plant not reported)Fail
1GC1KVEY8FF671234Chevrolet Silverado LT, 2015Flint, USAFail
MLHMC4430K5001034Honda motorcycle, 2019Bangkok, ThailandFail (partial data)

How we ran the test

Each VIN was sent to the public NHTSA vPIC endpoint exactly as our decoder sends it — a single DecodeVinValues call, no caching, no third-party enrichment. The checksum verdicts come from the same mod-11 math defined in 49 CFR Part 565 that the decoder runs client-side, and we cross-checked them against NHTSA's own error codes; the two agreed on all eighteen VINs. Raw responses are kept in our QA archive so the table above can be re-verified line by line.

Finding 1: fifteen of eighteen fail the checksum — and that's mostly sloppiness, not crime

The check digit is a modulo-11 checksum over the other sixteen characters. The failures in this table are not one story but three. ① Sanitized placeholders: strings like 1C4RJFAGXFC812345 and 5NPD84LF8JH333456 are anonymized demos — someone masked a real VIN to protect the owner and never recomputed the check digit afterward. ② Single-character drift: a demo VIN mutated for an example, or an honest transcription typo that then got copied a thousand times. ③ Vehicles that never had the check: the Thai-built Honda motorcycle was not required to implement a North American checksum at all, and fails the math by design. The three survivors — the Accord, the Corolla and the Cavalier at the top of the table — are famous precisely because they were copied correctly.

On a real car, the stakes are different — and so is the reasoning. A VIN read off an actual North American-market vehicle that fails the checksum usually means one of three things: someone misread a stamped character (B/8, G/6, S/5 are the classic confusions), someone transcribed it wrong into the listing you're reading, or the VIN was altered. The first two are common and harmless; the third is why you re-read the number off the car itself — windshield base and door jamb — before paying for any history report. Keep the scope straight, though: the check digit is a US/Canada regulatory requirement, so a VIN built for the European, Japanese or Southeast Asian market can fail the math and still be a perfectly legitimate, unaltered vehicle. A failed checksum outside North America is a shrug, not a red flag.

Finding 2: the data decodes anyway

Here's the part most people miss: NHTSA does not reject a VIN over a bad check digit. The database returned a full record for fourteen of the fifteen failures — engine, plant, body class, all of it — with an error note attached. (Our decoder mirrors this: it shows the data and flags the check.) So a checksum failure is a warning light, not a wall. The exception in this dataset is the Thai-built Honda motorcycle: NHTSA returned no model at all, flagging "unable to provide information for some of the characters" — coverage on non-US-market bikes is thin. (On a motorcycle the VIN itself is stamped at the steering head or the frame neck — never on the engine alone, which carries its own separate number.)

Finding 3: the registry is genuinely global — with gaps

The plants in this table span seven countries: the USA, Canada, Mexico, Germany, Japan, Thailand and South Africa. The last one surprises people — the Mercedes C-Class has been built in East London, South Africa for decades, and the registry knows it. The gaps are just as instructive: the Hyundai Elantra came back with no plant city at all (the manufacturer didn't submit one for that VIN), and the motorcycle shows how quickly coverage thins outside passenger cars. The database is deep where US regulations reach and patchier everywhere else.

What this means for a buyer

Three practical rules fall out of the data. First, validate before you spend: the checksum is free and instant, and no paid report can fix a VIN that was wrong at the source. Second, a flagged check digit with coherent data is usually a transcription problem — re-read the stamp. Third, "no data" is not "no car": motorcycles, imports and older vehicles routinely return sparse records, which says nothing about their condition or history.

Run the check yourself: the free decoder validates the checksum and decodes the full record in one pass. If you want to see the math worked through on clean VINs, read our companion piece on reading a VIN by hand — and remember that whatever the decode says, factory data is only one layer of the story.