Methodology
Data and Editorial Methodology
Last updated: 2026-11-09
1. Data source
VinUnpack uses the National Highway Traffic Safety Administration's Vehicle Product Information Catalog (vPIC). Manufacturers submit information about the vehicles they build, and vPIC publishes it as tables that map manufacturer identifiers, VIN patterns, model years and vehicle attributes.
vPIC is a catalog, not a history database. It does not contain accidents, mileage, liens, theft records or ownership. The dataset is described in more detail in where VIN data comes from.
2. Snapshot and build
The current decoder uses the vPIC 2026-10 snapshot, extracted on 2026-10-21. The source tables are curated into country, make, manufacturer, WMI, model, schema and engine tables, then built into a static file served with the site. The browser loads that file once and matches the VIN locally.
The snapshot is dated on purpose. A decoder that mixes live data from several sources is harder to audit and harder to reproduce. When a new snapshot is published, the site can be rebuilt against it without changing the decoding rules.
3. How a VIN is decoded
The decoder reads the world manufacturer identifier from positions 1–3, extends it when the third character is 9, and looks up the make, manufacturer, country and coverage tier. It resolves the model year from position 10 using the 30-year cycle and the vehicle-type rule. It then builds a pattern key from positions 4–8 and 10–17 and checks the schema patterns linked to that WMI and year range.
The most specific matching pattern supplies the model, engine, plant city, state and country. If no pattern matches, the field is labelled Not decoded. If the make is outside the current coverage tier, model and engine are labelled Not supported in v1. The decoder does not guess.
4. Coverage tiers
Tier A makes have broad public pattern coverage for year, make, model, engine and plant. Tier B makes generally have year, make and plant, with model and engine when the data covers them. Tier C makes have year, make, plant code and country only. The tier is a statement about data coverage, not about vehicle quality.
5. How the guides are researched
Each guide starts from a question users ask. The explanation is checked against the vPIC tables, 49 CFR Part 565 or the manufacturer's public information. Claims that cannot be checked are removed. Sources are listed at the bottom of each guide, and the “Updated” date is the revision date.
The guides are written in small batches, not generated in bulk. There is no per-brand page for every make and no auto-generated article set. A page is added when a question is common enough to deserve a permanent answer.
6. Corrections
If you find an error, email the VIN or the sentence and the source you are checking against. Confirmed errors are corrected and the guide's updated date is changed. A correction is not hidden in a silent edit; the point of a dated page is that the reader can see when it was last reviewed.
Contact: [email protected].
7. Editorial independence
Advertising is sold by Google and displayed on pages with content. Advertisers do not review, approve or influence the guides, and there is no paid placement inside a guide. The coverage tiers and the “Not decoded” labels are product decisions, not advertiser preferences.
The site does not sell vehicle history reports and does not accept payment to recommend a product. When a guide mentions a category of service, such as a history report or a pre-purchase inspection, it describes what the service does, not a specific vendor.
8. Update log
- 2026-11-09 — published the VIN guides library and this methodology page.
- 2026-11-09 — expanded the About page and added the Terms of Service.
- 2026-10-27 — added privacy, contact and about pages; launched the decoder.
- 2026-10-21 — extracted the vPIC 2026-10 snapshot.