VIN Decode Plus OBD2: The Two-Step Pre-Purchase Check

A BMW 530d on autoscout24.de is advertised as a 2014 facelift with the 258 hp engine and the full M-Sport package. The seller in Cologne has priced it 1,200 euros above the others in the same listing band and explains the difference as "the higher-output engine and the sport spec." You decode the VIN before driving out to see it, and the build data comes back as the 2013 pre-facelift car with the 245 hp engine and the standard suspension.

Nothing here is necessarily fraud. Sellers get years wrong, trims blur together, and a previous owner may have added M-Sport bits after the fact. But the price was justified on a spec the car does not have, and you now know that before you have spent a euro of fuel driving to Cologne.

That is the whole point of decoding the VIN first. It is a one-minute check that tells you whether the car is even the thing the advert describes, before the slower, more revealing OBD2 scan tells you what condition that car is in.

What is the difference between decoding a VIN and a VIN history report?

This is the confusion that trips up most first-time buyers, so it is worth settling before anything else.

Decoding a VIN means reading the 17-character number itself. Every character has a defined meaning: the manufacturer, the plant, the model year, the body style, the engine family. Run it through a decoder and you get the factory specification of that exact car. It is free, instant, and it comes straight from the number.

A VIN history report is a completely different product. It takes the same VIN and looks it up in databases that nobody can read from the number alone: insurance claims, auction records, national mileage registers, title and write-off records. That is where odometer history, accident records, total-loss branding and the count of previous owners come from. In the EU that means a paid service like carVertical or autoDNA, or a national register such as Poland's historiapojazdu.gov.pl and Lithuania's records via DEKRA or TÜV cross-checks.

The short version: the decode tells you what the car is, the history report tells you what has happened to it. They are not substitutes. A clean decode on a flood-damaged write-off still decodes clean, because the flood is in the history, not in the number.

What does decoding the VIN actually tell you?

Three concrete things, and they are more useful than they sound.

First, the factory specification: model year, make, model, engine code, transmission type, body style and the assembly plant. This is the part that catches the BMW above. When the advert and the decoded build data disagree on the engine or the trim, you have found something the seller either does not know or hopes you will not check.

Second, open safety recalls. A recall lookup by VIN queries the manufacturer and safety-authority databases and returns any recall that is still open on that specific car. Recalls are not cosmetic. They cover fuel-system fire risk, faulty airbag inflators, brake and steering failures. An open recall on a car you are about to buy gives you a clean argument at the table: either the seller had it done and can show the paperwork, or you factor a dealer visit into your offer.

Third, the engine-match check. Decode the VIN to learn the engine family the car left the factory with, then confirm the engine physically in the bay matches. A stamped engine number that disagrees with the VIN points to an engine swap, which is not automatically bad but is always something you want priced into the deal rather than discovered after.

Here is where the OBD2 side earns its place. An app like Skanyx reads the VIN straight off the ECU over Mode 09 and matches it against its own vehicle database of around 17,000 configurations, so what the VIN encodes appears on your phone while you are standing at the car. Skanyx also runs an NHTSA recall lookup against that VIN. You are confirming the car physically is the spec the advert claims, and surfacing open recalls, in the same minute it takes to plug in the adapter.

What the decode and the recall lookup do not give you is the car's history: mileage, accidents, owners, title status. For that you need a paid VIN history report from carVertical, autoDNA or the relevant national vehicle database. The decode confirms the car IS the spec it claims. A full history report tells you what that car has been through.

What does the OBD2 scan show that a VIN decode cannot?

Everything about condition. The decode is a static fact about how the car was built. The OBD2 scan reads what the engine control unit knows about how the car has been running lately, and that is where the real money lives.

The scan pulls stored, pending and permanent fault codes. It opens the freeze frame data attached to each code, which includes the mileage at which the code set. A car showing 90,000 km on the cluster with a stored P0300 misfire frozen at 240,000 km is caught by the freeze frame, not by the decode. It checks readiness monitor status, the single best tell for codes cleared the morning of the viewing. And it reads live data during the test drive: fuel trims, coolant temperature, mass airflow, oxygen sensor switching.

None of that is in the VIN. A perfectly decoded VIN on the right engine in the right trim can still be a tired, abused, freshly-cleared car. The full procedure for the condition half lives in the canonical German used car OBD2 checklist, and the deeper pre-purchase inspection guide covers the structured test-drive version. If the car is a diesel, the used diesel import red flags post covers the emissions-system traps the decode is blind to.

A manual VIN decode and an OBD2 scan are two tools and two windows of attention while you are trying to assess a car you might buy. The Skanyx app folds both into one 8-step Pre-Purchase Inspection: it reads the VIN over Mode 09, matches it to the vehicle database, runs the NHTSA recall lookup, then scans codes, freeze frame, readiness monitors and live data across an idle, cruise and acceleration sequence, and returns a Buy / Negotiate / Caution / Walk Away verdict with a PDF and a negotiation script. Run it on the car before you pay

Does a VIN tell you the mileage or the accidents?

No, and this is the most common misunderstanding about VIN checks. The 17-character number encodes the build specification, not the life story. Decode it and you get the exact spec the car left the factory with. You never get an odometer reading or a crash record out of the number itself.

Mileage history, accident and insurance claims, total-loss branding and ownership count all come from a paid history report that cross-references the VIN against registers, insurers and auction feeds. That is carVertical, autoDNA, or a national register depending on the country. In Poland, historiapojazdu.gov.pl can return recorded mileage readings from inspection dates. In Lithuania, mileage history sometimes surfaces through DEKRA or TÜV records on German-registered cars.

This is exactly why the OBD2 scan matters even after a clean history report. The freeze frame mileage stamps inside stored codes are written by the ECU at the moment a fault sets, and they are far harder to roll back than the cluster reading, because they live in the powertrain module rather than the instrument cluster. A history report and a freeze frame check that disagree is a rollback you would otherwise have missed. The dedicated odometer fraud detection guide walks through the cross-references in full.

How do you actually run the two-step check at the kerb?

A practical order of operations, built so each step gates the next.

1. Before you drive out to see the car, get the VIN from the advert and decode it. Confirm the year, engine and trim match what the seller is charging for. If the decode contradicts the advert and the price was justified on that spec, raise it before you spend an afternoon travelling.

1. Optionally pull a paid history report on the same VIN. carVertical or autoDNA for mileage and accident records, or the state register where one exists. This is the only step that costs more than the price of an adapter, and on an expensive import it is worth the 15 to 30 euros.

1. At the car, plug your own ELM327 adapter into the OBD2 port and read the VIN off the ECU. Confirm the on-screen VIN matches the windscreen and the documents. A mismatch here is a serious flag: it can mean a cloned car or a re-shelled write-off.

1. Run the recall lookup. Skanyx does this by VIN against NHTSA. Any open recall is either fixed with paperwork or money off the price.

1. Run the full OBD2 condition scan during the test drive: codes, freeze frame, readiness monitors, live data. This is the slow, revealing part covered in the German used car checklist.

The decode and recall lookup take a minute each. The condition scan takes the length of a proper test drive. Together they answer both questions you actually have about the car: is it what the advert says, and has it been looked after.

Which codes turn a clean decode into a negotiation?

The decode and recall lookup get you to the car with eyes open. The codes you find on the scan are what move the price.

A stored P0420 catalyst-efficiency code on a petrol car the decode confirmed as a 180,000 km example is normal aging, and worth 350 to 1,800 euros off depending on the vehicle. A P0171 lean code alongside it points to an active fuel or vacuum leak rather than a tired catalyst, which is a different conversation. On a diesel, a stored P2002 or P244A means the particulate filter system is past threshold, and on an imported EU diesel that is a delete-or-repair question worth several thousand euros. None of those codes appear in a VIN decode. They appear in the scan, and they are the reason the scan is the second step rather than the only one.

A perfectly decoded VIN with the right engine, the right trim, no open recalls and a clean history report can still throw a P0299 underboost code on the test drive. That is the car telling you something the paperwork could not.

What does the two-step check still not catch?

The same things any OBD2-based check misses. Suspension wear, rust under the sills, repainted accident repair, interior condition, tyre age and brake wear are all invisible to both the decode and the scan. The VIN decode confirms the spec. The OBD2 scan reads the powertrain and emissions condition. A paid history report fills in mileage and accidents. None of them replaces walking around the car with your eyes and crawling underneath it with a torch. Use all of them.

Make the decode the first thing you do

Decode the VIN before you arrange the viewing, so you know whether the car is even the spec the advert is charging for. Read it again off the ECU at the kerb, run the recall lookup, then run the OBD2 scan on the drive. The decode tells you what the car is, the scan tells you how it has been treated, and the two together cost you a minute and an afternoon instead of a wired transfer and a regret.