Maserati VIN Decoder: Three Codes, One Country, One Company

The phrase “VIN decoder” suggests a tool built for one marque. No such thing exists. It does not. The number stamped into a Maserati is built to the same federal standard as the number on a hatchback or a delivery van, and the register that turns the first three characters into a manufacturer is the same register for every one of them.

What is worth reading is the register entry itself, and on this make the entry is small enough to print in full without abbreviating anything. This page works from one archived read of NHTSA’s vPIC register, taken on 5 September 2026: three manufacturer codes, one registered company name, one country, two vehicle types and fifteen models. That is the complete federal picture of the make. Everything below is drawn from it, and where the register is silent this page says so rather than filling the gap from memory.

A compact entry changes what a page like this can honestly be. There is no long list of codes to untangle, no parent group hiding behind the badge, no cluster of unrelated companies to subtract. What is left is the more useful question: given that the decode of a Maserati number resolves cleanly, what does it actually tell a buyer, and what does it leave untouched? The untouched part is the larger one, and it is the part this page spends most of its length on.

One federal system reads every VIN, this make included

The vehicle identification number is a federal standard and its layout does not change with the badge. Positions one to three are the world manufacturer identifier, assigned to the legal entity that builds the vehicle. Positions four to eight describe the vehicle in a scheme each manufacturer designs for itself. Position nine is a check digit, computed arithmetically from the other sixteen characters. Position ten carries the model year. Position eleven identifies the assembling plant. The final six are the serial number.

Our guide to reading a VIN position by position sets out the full layout, and the by-make index collects what the register holds for every make we have read.

The federal system also decides what a decode can return. It resolves the manufacturer prefix against the register, returns the make, the model and the model year, and returns the vehicle class the code was filed under. It does not return anything the register does not hold, and a great deal of what a buyer wants falls into that category. Anything offered beyond that is coming from somewhere other than the number.

Three codes, one company name, one country

The register lists three world manufacturer identifiers for the make: ZAM, ZC2 and ZN6. Every one of them carries the same registered entity name, MASERATI S.P.A., and every one of them is recorded against Italy.

That uniformity is worth stating plainly, because it removes the single most common source of confusion on decoder pages. On many makes the registrant field returns a company name that has little visible relationship to the badge, and readers reasonably conclude that the lookup has gone wrong. Here it cannot happen. Whichever of the three codes issued a number, the entity name a decode reports back is the same one, and it matches the name on the car.

The country field deserves a more careful reading than it usually gets. It records the country in which the registering entity filed, not the building in which a vehicle was screwed together. Those two things frequently coincide, and on an entry with a single country recorded there is nothing to contradict the obvious reading — but the field is still a fact about a filing. The register holds no relationship at all between a manufacturer code and a production line, so it cannot confirm where any individual car was assembled, and this page will not pretend otherwise.

Because the entry is three rows deep, it can be printed rather than summarised, which is what the figure below does. Code, registered name, filed vehicle type, country and registration date — those five fields are everything the register holds against a manufacturer code. There is no sixth column being withheld.

All three begin with Z, and the rest of each code is not a mnemonic

The first character of a VIN is widely described as a geography tell, and on some makes it does real work. On this entry it does none, because all three codes open with the same letter: ZAM, ZC2 and ZN6. Reading the leading character of a Maserati number therefore separates nothing. It cannot distinguish one code from another, and it cannot tell you which of the three issued the number in front of you.

The characters that follow are worth a note of their own, because they invite a guess that the register does not support. ZAM continues with letters. ZC2 and ZN6 each end in a digit. There is no pattern in that which a reader can extend, and nothing in the entry explains why any particular combination was assigned. A manufacturer code is an allocation, not an abbreviation, and it is not decoded by treating its letters as initials.

What that leaves is a narrow, dependable use for the first three characters. They identify the entity that issued the number, and they are what the register indexes. Everything more specific about a particular car sits from position four onward, in fields that only a decode of that car’s own number can return. The register holds nothing that would turn a leading character into a factory, a market or a specification, so no table of that kind appears on this page.

Two filed as Passenger Car, one as Multipurpose Passenger Vehicle

The register files every code under a vehicle type, and this entry uses two of them. Two codes are filed as Passenger Car. One is filed as Multipurpose Passenger Vehicle, the federal class that catches a large part of what the market calls an SUV or a crossover.

Read those words as classifications rather than as descriptions and they stop being puzzling. Multipurpose Passenger Vehicle is a regulatory category with a definition attached to it and consequences for which safety standards a vehicle is certified against. It is not a body style, not a door count and not a seating layout. Two vehicles that look nothing like one another can sit under the same word, and a decode returning it is telling you how the vehicle was certified rather than what it looks like on a driveway.

Two practical consequences follow. The first is that a body-class result which surprises you is not evidence that a lookup has failed or that a seller has misdescribed a car. That kind of dispute is settled by the vehicle in front of you and by the paperwork, never by a category word inherited from a manufacturer code. The second is that the split does not describe a product range. It describes how three filings were categorised, and the register offers no explanation for the split beyond the fact of it.

The join the register does not hold: models to codes

Here is the limitation that a compact entry makes unusually visible. The register holds three codes, filed under two vehicle types. It separately holds fifteen model names for the make. It does not hold any connection between the two lists.

So the entry cannot answer the question a reader naturally asks next. Which of the fifteen models were issued numbers under the code filed as Multipurpose Passenger Vehicle? The archived data has no field for it. The model list is attached to the make, the vehicle type is attached to the code, and nothing joins a row in one list to a row in the other. A mapping of that kind cannot be built out of this entry, so none is offered here.

This matters because the join is exactly what makes a code look meaningful. Without it, knowing that a number opens with one code rather than another tells you the entity that issued it and the class that code was filed under, and stops there. The model for a specific vehicle comes from decoding that vehicle’s own number, where the federal system resolves the manufacturer’s own descriptor fields and returns a model name directly. That is a different and far more reliable route to the answer than reasoning backwards from a three-character prefix, and it is the route worth using.

Fifteen models, spelled as the register spells them

The register holds fifteen models for the make: 228, 430, Biturbo, Coupe, Ghibli, Grancabrio, Granturismo, Grecale, Levante, MC20, MCPura, Merak, Quattroporte, Spyder and TC. They are printed here exactly as the register spells them, including the two that are numbers and the capitalisation that does not always match the way the names are styled elsewhere.

That spelling point is not pedantry. It is what a decode will hand back to you, and it is what a search against the decoder will and will not match. A name written one way in an advert and another way in a filing is the same model; the difference is a data-entry convention, not a variant. The two numeric names are worth noting for the same reason, since a model called 228 or 430 is awkward to search for and easy to mistake for a trim designation, an engine size or a chassis number in a listing.

What the list is not is a catalogue. It is the decoder’s vocabulary for the make — the set of names a decode can return when it resolves a specific number. A name appears because it was filed. Its presence says nothing about how many vehicles carried it, which years it spans, or whether one is within reach of any particular buyer, and the archived entry carries none of that.

The reverse trap is the expensive one. The register knows the model line; it does not know which engine, which gearbox, which drivetrain, which interior or which options package a particular car left the line with, and on a car of this kind those distinctions can be the difference between two very different vehicles wearing the same model name. Our pages on trim level by VIN and build sheets set out how far that can be pushed and precisely where it stops.

Three registration dates, and what they cannot be read as

Each code carries a date. ZAM is recorded on 5 March 2015. ZN6 follows on 29 April 2016. ZC2 comes last, on 30 November 2016. All three sit within a span of about twenty-one months, and the code filed as Multipurpose Passenger Vehicle sits chronologically between the two filed as Passenger Car.

Before anyone builds a narrative out of that ordering, the field needs stating for what it is. A date here is the date the code was registered. It is not the date a vehicle carrying it was built, sold or first titled, and it is not a model year. Codes can be registered ahead of use, and the register records no volume against any of them, so the dates rank three filings and do nothing else.

There is a stronger reason to be careful, and it comes from counting the whole file rather than this entry. The archived read behind this cluster holds 513 code rows across 46 makes. The earliest date anywhere in it is 4 March 2015, and 363 of the 513 rows carry a date in 2015 — 343 of them between March and August of that year alone. Not one row predates that first week of March 2015. ZAM’s date sits one day after the earliest date in the entire read.

A field where nothing at all is older than a single week in 2015, and where most of the file clusters in the months that follow, is recording something about the register rather than about the companies in it. Read these dates as filing metadata and they are informative. Read them as a company’s history and they will mislead you, because the register simply does not reach back far enough to carry one. If you want the age of a specific car, that is position ten of its own number, read against our model-year chart.

The part of the number the register does not publish

A brand-specific decoder would earn its keep in one place, and it is worth being straightforward about the gap. Positions four to eight of a VIN are the manufacturer’s own descriptor scheme, and the federal register does not publish the key to it. What the register records is who holds a prefix, which vehicle class the prefix was filed under, which country the entity filed in, and when the code was opened. It does not record that a given character in position five means one thing on one model and something else on another.

So this page prints no position-by-position breakdown for the make, and no plant-code list. Position eleven of an individual number is the plant character, but the key that turns it into the name of a facility belongs to the manufacturer’s scheme rather than to the register, and we hold no such key from a source we would defend. A decode of a real number returns those descriptor fields as the federal system resolves them for that specific vehicle, which is worth considerably more than a printed table assembled from somewhere unattributable.

Position nine is the one piece of the middle of the number you can check yourself with nothing but arithmetic. It is a check digit computed from the other sixteen characters, which means a mistyped number usually fails before it has cost anyone a journey. Our validator page explains how to run that check by hand, and it is worth doing on any number that arrived by text message or was read off a photograph of a screen.

No parent group, and no unrelated matches

Two facts about the entry mean it can be read at face value. The make holds its codes in its own right rather than sitting beneath a parent group in the register, so a search on the badge name returns the codes that actually issue its numbers. And a register query on that name returns zero unrelated matches.

The second fact is worth explaining, because it is the mechanism rather than the result that is useful. The register’s name endpoint matches company names as text rather than resolving brands. Ask it for a string that appears inside other registered company names and it will return those companies too — small builders, converters and trailer shops whose filings happen to contain the same characters. Where that happens, a raw result has to be filtered by hand before the count means anything.

Here the query is unambiguous, so there is nothing to subtract. Three codes come back, all three belong to the make, and a reader who runs the same query themselves will see the same three rows. That is the whole of it, and the count in this page is the count in the register.

What the decode will not tell a buyer

This is the section that does the most work, because on a make with a compact and unambiguous register entry the decode is the easy part. The number is a build identity. It exists so that a regulator can tie a recall campaign to a batch of vehicles, an insurer can tie a policy to an object and a state can tie a title to that same object. It was never designed to describe a car’s condition today, and it has no field for any of the following.

Service history. Nothing about oil changes, fluid changes, brake work or belt and tensioner service is encoded in the number, and none of it reaches the register. Where a car has been maintained outside a franchised network there may be no central record anywhere — only a folder of invoices, which is worth asking for and worth reading line by line rather than weighing.

Whether a recall was actually carried out. The federal recall lookup will tell you whether a campaign is recorded as open or remedied against a specific number, which is free and genuinely useful. What no decode does is prove that a previous keeper ever presented the car. A campaign showing as remedied means a remedy was recorded; one showing as open means the work is outstanding as far as the system knows. Our guide to checking a car for open recalls covers how to read the result properly, including the cases where the flag and the reality diverge.

Specification, then and now. A build record can describe how a car was configured when it was made, and how much of that is recoverable varies by manufacturer. What no historical decode shows is a change made afterwards — a component swapped, an exhaust replaced, a wheel and tyre package changed, a module reprogrammed. Original specification and current specification are two different claims, and only the first has any chance of living in a record. Our page on options by VIN makes the same argument across all makes.

Condition, mileage and damage that never reached a file. A decode reads the build. Damage enters a record only where an insurer or a state filed something, and a well-repaired collision paid for privately leaves no trace at all. Our page on accident checks by VIN sets out which events reach the record and which never do.

Reading the number off the car

Whatever the listing says, the number to work from is the one on the vehicle. Read it yourself rather than copying it from an advert, and read it from more than one place.

The usual locations on a passenger vehicle are the plate visible through the base of the windscreen on the driver’s side and the certification label in the driver’s door aperture. That label is a federal requirement rather than a manufacturer courtesy, which is what makes it a dependable second reading: it carries the number, and it carries the certification information the vehicle was built to. Our guide to where the VIN is on a car covers the wider set of locations, including the ones worth checking on a car you suspect has been apart.

Two readings that disagree is a finding rather than a transcription problem to be shrugged off. So is a label that looks newer than the aperture around it, or fixings that have clearly been disturbed. Where the numbers on a car do not agree with each other, or do not agree with the paperwork, our page on VINs that do not match covers what that means and what to do next.

The records that sit around the number

The decode is the cheap part and the fast part. The record is where used-car money is won and lost, and a record is retrieved rather than decoded — it lives in title files, insurer reports and recall databases, keyed to the number rather than encoded inside it.

Three retrievals do most of the work. The federal recall lookup is free, per-vehicle and authoritative on open campaigns. The theft check is also free and answers a question that ends a purchase outright; how to check if a car is stolen covers running it. And the title history — the brands, the state-by-state chain, the odometer readings that entered the record at each titling — is the one that repays paying for. Our title-check page explains what comes back and, just as usefully, what structurally cannot.

Know the boundaries of the free tools before leaning on them. Our page on what a free VIN check actually returns sets out what each one covers, because a clear result from a database that only includes participating members is a weaker statement than it looks. Free checks start an enquiry rather than finishing it.

Where a car carries a brand on its title, the brand is the purchase. What a branded title means ranks the brands by how much each should worry a buyer, and water damage deserves its own note because it reaches wiring, connectors and modules in ways that surface months later — our page on flood checks by VIN covers what the record shows and, more importantly, the cars it never sees.

A sequence for a used Maserati

Put together, the order looks like this, and none of the first four steps requires leaving home.

Get the full seventeen characters from the seller and validate the check digit. A number that fails is a transcription error until proved otherwise, and finding that out early costs nothing.

Decode it, and check the returned model and model year against the advert. A disagreement there ends the conversation before anyone has driven anywhere. Note which of the three codes issued the number and read the registrant line for what it is: the entity that issued the number, which on this make is the same name on all three codes.

Run the free lookups. Recalls and the theft flag are per-vehicle, free and quick, and either can settle the matter from a kitchen table.

Buy the title history once and read the chain rather than the headline. Which states, in what order, with what readings and what brands against them. A short chain with long ownerships reads well. A car that has crossed several states quickly is asking a question the seller should be able to answer without hesitating.

Then do the part no record covers. Read the number off the car with your own eyes, from the windscreen and the door aperture, and compare it character by character with the number you decoded and the number on the title. Ask for the service folder and read it properly. And book a pre-purchase inspection, because the condition and the specification of one particular car are exactly what this whole page has been telling you the number cannot carry.

Common questions

Is there an official Maserati VIN decoder?

Not a separate one, and none is needed. These vehicles carry the same seventeen-character number as everything else built for this market, and the federal register resolves the manufacturer prefix for every make on the same terms. A general decoder handles the marque.

How many manufacturer codes does Maserati have?

Three: ZAM, ZC2 and ZN6. All three are filed under one registered company name, MASERATI S.P.A., and all three are recorded against Italy.

What do the first three characters of a Maserati VIN mean?

They are the world manufacturer identifier, which names the entity that issued the number. On this make all three codes begin with the same letter, so the leading character separates nothing here, and the characters after it are an allocation rather than an abbreviation. Nothing in the register explains why a particular combination was assigned.

Does the register say which models each code covers?

No. One of the three codes is filed as Multipurpose Passenger Vehicle and the other two as Passenger Car, but the entry holds no link between a model name and a manufacturer code. Decoding a specific number returns the model and the body class for that vehicle, which is the answer worth having.

Does a Maserati VIN tell me which factory built the car?

Not from the federal data. Position eleven of an individual number is the plant character, but the register does not publish the key that turns it into a facility name, so this page prints no plant table. The country recorded against a code describes where the registering entity filed, not where a vehicle was assembled.

How many Maserati models does the register hold?

Fifteen: 228, 430, Biturbo, Coupe, Ghibli, Grancabrio, Granturismo, Grecale, Levante, MC20, MCPura, Merak, Quattroporte, Spyder and TC, spelled as the register spells them. That is the decoder’s vocabulary for the make, not a catalogue, and it carries no years, volumes or availability.

What do the registration dates on the codes mean?

They record when each code was registered: March 2015, April 2016 and November 2016. They are not build dates or model years. Across the whole archived read of 513 code rows nothing predates 4 March 2015, so the field describes the register rather than any company’s history.

Will a decode tell me the trim, engine or options?

It will confirm the model line as filed. Trim, engine, gearbox and fitted equipment belong to the build record rather than to the model name, and how much of that is recoverable varies by manufacturer. Anything added, removed or swapped after the car was built sits outside every historical decode.

Can a VIN check show whether a recall was completed?

It shows whether a campaign is recorded as open or remedied against that number, which is free and worth running. It does not prove that a previous keeper presented the car, and it does not show work done outside the campaign system. Read the campaign text rather than only the flag.

Does Maserati register under a parent company?

No. It holds its three codes in its own right, and a register query on the name returns zero unrelated matches, so nothing needs filtering out. The three codes are the whole set.