Enter the VIN
Paste any 17-character VIN. We strip whitespace and reject the letters I, O, and Q (none of which appear in a valid VIN).
Decode any VIN, straight from the NHTSA federal database. Paste any 17-character VIN: commercial tractor, straight truck, trailer, bus or car. We hit the federal NHTSA vPIC database and return year, make, model, trim, body class, GVWR weight class, engine, fuel, transmission, drive type and manufacturer plant, in one card.
Every manufacturer that sells a vehicle in the United States files the VIN pattern for that model with NHTSA when it is certified, so a decode is a read of the federal record, not a guess. Seventeen characters go in and the filed attributes come out, and for a commercial unit four of them do most of the underwriting work.
One VIN at a time is a lookup. A fleet schedule of two hundred VINs decoded overnight, matched to the ACORD 129 rows in your AMS, and flagged where the GVWR class disagrees with the prior dec page is a build: the kind of custom insurance software we put together for commercial auto agencies and MGAs on top of their AMS data.
How the decode runsPaste any 17-character VIN. We strip whitespace and reject the letters I, O, and Q (none of which appear in a valid VIN).
NHTSA’s Vehicle Product Information Catalog is the federal source of truth: every U.S.-registered manufacturer files VIN patterns here. We hit the decodevinvaluesextended endpoint and parse 150+ attributes per VIN.
Year, make, model, trim, body class, GVWR class, doors and seats, engine displacement and cylinders, fuel type, transmission, drive type, brake system, and the manufacturer plant, grouped into a single card.
A trailer VIN decodes the same way a truck VIN does: 17 characters, the same check digit in the ninth position, and the same manufacturer filing with NHTSA. The first three characters identify the trailer builder, so a Great Dane, Wabash, Utility or Hyundai Translead VIN resolves to its maker even where NHTSA holds no model name for it, which is common for trailers and low-volume builders. This decoder treats a make with no model as a valid decode rather than an error.
Paste the VIN into the box at the top of this page. The card labels the unit as a trailer and adds the trailer type, body type and length where the manufacturer filed them. If the VIN fails the check digit, the card flags it; on a real trailer that usually means a plate read wrong, so check the characters against the title or the registration.
Where to find it: the VIN plate is usually on the front of the trailer, on the nose, or on the tongue of a smaller trailer. The title and the registration card carry it too.
NHTSA files VIN patterns per manufacturer, and the first three characters tell you which one. Each page below is built from that filing for one maker: the WMI codes vPIC lists for it, a real VIN of its read position by position, the GVWR classes it registered, and worked decodes of its units from FMCSA roadside inspection records.
The data is the same. Every decode here calls the public vPIC endpoint NHTSA runs at vpic.nhtsa.dot.gov, so there is no attribute on this card that the official decoder does not have. If you searched for vPIC and wanted the government tool, it is at vpic.nhtsa.dot.gov/decoder and nothing here replaces it.
What differs is the reading. vPIC returns the raw record as a long table of fields, most of them empty for any given VIN. This card keeps the ones an insurance schedule needs, in reading order, with the empty rows dropped, and it sits next to the rest of the stack: check the same VIN against the FMCSA crash file with the VIN crash check, or start from a USDOT number and prefill the vehicle schedule for the whole fleet.
A VIN (Vehicle Identification Number) is the 17-character serial number every U.S. road vehicle carries since 1981. The first 3 characters identify the country and manufacturer (the WMI), the next 5 describe the vehicle (model, body, engine, restraint system), the 9th is a check digit, the 10th is the model year, the 11th is the assembly plant, and the last 6 are the production sequence. The Native Base free VIN decoder feeds the 17-character VIN to the NHTSA Vehicle Product Information Catalog (vPIC) and surfaces the federally-filed year, make, model, trim, body class, GVWR class, engine, fuel type, transmission, drive type, brake system, and manufacturer plant.
The Native Base free VIN decoder pulls live from the NHTSA vPIC API at vpic.nhtsa.dot.gov. NHTSA requires every manufacturer that sells vehicles in the U.S. to file the VIN-pattern decoder for every model, so vPIC is the federal source of truth for VIN attributes. The lookup is anonymous, no data is stored or modified, and every decode returns the federally-filed attributes for that VIN.
The 9th character of every valid VIN is a check digit computed from the other 16. If the math doesn’t line up, NHTSA flags it with "Check Digit (9th position) does not calculate properly". This usually means a typo (a 0 confused with a Q, or a 1 confused with an I or L). NHTSA still decodes what it can from the WMI and the vehicle attributes, but a real production VIN should always pass the check-digit math, so if you see this warning on a VIN from a real vehicle, double-check the characters against the door jamb or the dashboard plate.
Yes. The NHTSA vPIC database covers the full commercial vehicle universe: tractors, straight trucks, trailers, buses, motor coaches, and school buses. The Native Base free VIN decoder surfaces the GVWR class (the federal weight-class bucket used on commercial registration), the body class (Truck-Tractor, Trailer, Motorcoach, etc.), the engine model, the brake system type (air vs. hydraulic), and the drive configuration (6x4, 6x2, etc.): fields commercial-auto insurance agents read directly off the dec page or off the ACORD 129 vehicle schedule.
CARFAX and AutoCheck are vehicle history reports: they aggregate accident reports, title transfers, odometer readings, and service records around a VIN. The Native Base free VIN decoder is not a history report. It returns the federally-filed vehicle attributes (the same data a manufacturer files with NHTSA when the vehicle is built) from the public vPIC database. Free, no signup, no payment, no account linking. If you need accident or title history, that’s a different (paid) class of product.
Without an email you get 3 full decodes a day on this tool (8 a day across all the free tools). A work email lifts that to 25 a day, with no account to create or password to set. There is also a limit of 5 per IP address per minute. Insurance agencies and commercial-auto underwriters that need higher-volume programmatic access can contact Native Base for API access; we can also wire the same NHTSA vPIC decode (plus our FMCSA, MOTUS, and SOS stack) directly into an AMS to pre-fill the ACORD 129 vehicle schedule from a list of VINs.
Year, make, model, body, GVWR: those are the ACORD 129 per-vehicle fields that today get hand-keyed off the prior dec page. We can wire NHTSA vPIC plus our FMCSA, MOTUS, and SOS stack directly into your AMS to pre-fill the entire vehicle schedule from a VIN list, before the producer opens the packet.
Book a 20-min call →