---
title: "Alfa Romeo VIN Decoder: Two Codes, and the Entry Is Complete"
description: "Alfa Romeo holds 2 manufacturer codes and they are not filed the same way. What the federal vehicle type actually means, and what a decode does not reach."
url: "https://baronauto1.com/vehicle-history/alfa-romeo-vin-decoder/"
type: "article"
published: "2026-09-06"
modified: "2026-09-06"
site: "Baron Auto"
disclaimer: "This site is under new ownership and is not affiliated with Baron Auto Emporium dealership."
---

# Alfa Romeo VIN Decoder: Two Codes, and the Entry Is Complete

> Alfa Romeo holds 2 manufacturer codes and they are not filed the same way. What the federal vehicle type actually means, and what a decode does not reach.

*VIN & Vehicle History · 20 min read · 4,458 words*

## The short version

- There is no Alfa Romeo-only decoder, and none is needed. Every vehicle certified for this market carries the same 17-character number, and one federal register resolves the manufacturer prefix on all of them.
- The whole entry is two world manufacturer identifiers, ZAR and ZAS. That is short enough to print in full rather than summarise, and this page prints it.
- The two are not filed the same way. One is filed as Passenger Car and the other as Multipurpose Passenger Vehicle — MPV in most decoders. That word is a federal classification, not a description of the car.
- One registered company name holds both codes: ALFA ROMEO S.P.A. A decode reports the registrant, not the badge.
- Italy is recorded against both. That field says where the registering entity filed, which is a different question from where a car was assembled.
- The two filings were recorded in April 2015 and May 2017. Those are registration dates — not build dates, not model years, not sale dates.
- The decoder holds nine model names for the make, and this page quotes all nine exactly as filed. What no decode carries, here or anywhere: service history, present condition, and whether a recall that was issued was ever actually carried out.

The phrase “VIN decoder” makes it sound as though each marque has a tool of its own. None does. The number stamped into an Alfa Romeo is built to the same federal standard as the number on a pickup or a horse trailer, and the register that turns its first three characters into a manufacturer is the same register that does the job for every other make on the road.

What is worth reading closely is the register entry itself, because this one is unusually short. Many of the makes in this series have to be summarised: an entry with thirty or forty registered codes gets counted and grouped, because printing the list would fill a screen without teaching anything. The Alfa Romeo entry contains two codes. The whole of it fits in a small table, so rather than describing it we can show it and then spend the page on what each column actually means.

And there is something in those two rows worth stopping on. The two codes are not filed under the same vehicle type. One sits in the federal system as a passenger car and the other as a multipurpose passenger vehicle, which means a decode run on two cars wearing the same badge can come back with two different-sounding classifications, both of them correct. That is the part of an entry shaped like this one that most needs explaining, and it is what this page is built around.

**Figure: Alfa Romeo world manufacturer identifiers by vehicle type**

A bar per vehicle type showing how many World Manufacturer Identifiers NHTSA has registered to Alfa Romeo for that type.

Alfa Romeo holds 2 world manufacturer identifiers in NHTSA’s register, covering 1 country of manufacture, against 9 models the decoder holds for the make. A WMI is registered by a corporate entity rather than by a brand, so the count reflects how the group organises its registrations rather than how many vehicles it builds — which is why some familiar names return only one.

## 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 on the bonnet. Positions one to three are the world manufacturer identifier, assigned to the legal entity that issues numbers. Positions four to eight are a descriptor block the manufacturer designs for its own purposes. 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 last six are the serial.

Our guide to [reading a VIN position by position](https://baronauto1.com/vehicle-history/how-to-read-a-vin/) walks the full layout, and the [by-make index](https://baronauto1.com/vehicle-history/vin-decoder-by-make/) collects what the register holds for each manufacturer we have read.

Where a genuinely brand-specific decoder would earn its keep is the middle block, and here honesty serves better than another table. Positions four to eight are the manufacturer’s own descriptor scheme, and the federal register does not publish the key to it. The register records who holds a prefix, which vehicle class the prefix is filed under, the country the entity filed in, and the date the code was opened. It does not record what a given character in position six means on one body style as against another.

So this page prints no position-by-position breakdown for Alfa Romeo and no plant-code list, because we do not hold either from a source we would stand behind. Decoding a real number returns the descriptor fields as the federal system resolves them for that specific vehicle, which is a different and far more dependable thing than a printed key assembled from nowhere in particular. Position ten, the model-year character, is the one part of the middle of the number standardised across every make, and our [VIN year chart](https://baronauto1.com/vehicle-history/vin-year-chart/) covers it.

## ZAR and ZAS: the entry printed rather than summarised

A VIN opens with three characters the manufacturer does not choose for itself. They are assigned centrally, published in full, and they identify the entity that filed for the right to issue numbers. Under Alfa Romeo there are two of them: ZAR and ZAS.

**Figure: The manufacturer codes registered to Alfa Romeo**

A row per world manufacturer identifier in the Alfa Romeo entry, showing what each code is filed as.

Two codes and the entry is complete. The vehicle type against each is a federal classification rather than a description, so a car the market calls one thing can be filed as another. Read from NHTSA’s vPIC register and archived in data/vin-makes.json.

That table is not an excerpt. It is the entry. Every code the federal register holds under this make is on it, together with the class each is filed under and the month the filing was recorded. There is no second page, no continuation, and nothing has been trimmed for reasons of space.

It is worth being explicit about that, because it is not the normal state of affairs on a page like this. On a make with thirty registered codes, the honest version of this section is a set of counts and a note that the list runs long. Here the counts and the list are the same object. Anyone who wants to check this page against its source can do it by reading two rows.

Notice also how little separates the codes themselves. ZAR and ZAS share their first two characters and differ only in the third. What the leading character does not do is tell you which building a car was assembled in. That is a separate question, and the federal data does not answer it.

Two codes is a small entry, though not a unique one. Counting across all fifty-six make entries in the file behind this series — we counted rather than estimated — four of them hold exactly two registered codes, and Alfa Romeo is one of the four. The others are Porsche, Lamborghini and Ducati. A small number here reflects how a group organises its filings, not how many vehicles it builds, and that caveat is written into the source data itself rather than being our gloss on it.

## “Vehicle type” is a classification, not a description

This is the column that does the separating on this entry, and it is also the one carrying a word out of the regulations rather than out of ordinary speech, so it is worth taking slowly.

Every world manufacturer identifier is filed under a vehicle type. On this make the two codes divide one and one: ZAR is filed as Passenger Car, and ZAS is filed as Multipurpose Passenger Vehicle, which most decoders abbreviate to MPV. Those are not adjectives someone chose in order to describe the vehicles. They are categories out of the federal motor vehicle safety standards, and they exist because the rules a vehicle must meet depend on which category it falls into.

The distinction the regulations draw turns on construction and capability rather than on marketing. A passenger car, in that scheme, is a motor vehicle with motive power, excluding the other defined categories. A multipurpose passenger vehicle is also designed for ten or fewer, but is constructed either on a truck chassis or with special features for occasional off-road operation. The test asks how the vehicle is built and what it is engineered to do, and the answer settles which safety standards apply to it.

Nothing in that definition mentions price, prestige, performance, body shape as a buyer would describe it, or the word an owner would use in conversation. A vehicle can be classed as a multipurpose passenger vehicle and be nothing whatsoever like the mental image the phrase produces. The category is a regulatory bucket. The register writes down which bucket the filing sits in, and stops there.

## What a one-and-one split does to a decode

The practical consequence follows directly from the split. Run a number that opens with ZAR and a decoder faithfully reporting the register will return “Passenger Car” in the vehicle type field. Run a number that opens with ZAS and the same decoder will return “Multipurpose Passenger Vehicle”. Both answers are correct. Neither is evidence that a lookup has gone wrong, that a number has been mistyped, or that a seller has misdescribed what is on offer.

What makes this entry instructive is that the split falls at the level of the manufacturer code rather than deeper in the number. On a make whose codes are all filed the same way, the vehicle type field carries no information at all about the individual car: it says the same thing every time. Here the third character alone changes the answer, which means the field is doing a small amount of genuine work — it separates the entry into two halves — while still not being a description of any particular vehicle.

The same pattern appears on two other entries in this series, and only two: counted across the fifty-six makes in the file, three hold exactly one code filed as Passenger Car and one filed as Multipurpose Passenger Vehicle. Alfa Romeo is one; the other two are [Porsche](https://baronauto1.com/vehicle-history/porsche-vin-decoder/) and [Lamborghini](https://baronauto1.com/vehicle-history/lamborghini-vin-decoder/). The [Ferrari entry](https://baronauto1.com/vehicle-history/ferrari-vin-decoder/) divides across the same two classes on a slightly larger set of codes. In every case the effect on a reader is identical: a word out of the regulations lands in a field being read as a description, and the mismatch looks like an error when it is nothing of the kind.

The useful habit is to read the vehicle type field as metadata about the code rather than as a statement about the car in front of you. If you want to know what you are looking at, look at the car. If you want to know which federal category the manufacturer filed that prefix under, read the field. They are different questions, and the register answers only the second.

## One registered name stands behind both codes

The register records, against every code, the name of the entity that filed for it. On this make there is one such name, and it is recorded against both codes: ALFA ROMEO S.P.A.

A decode returns that registered name character for character, because reporting the registrant is exactly what the field is for. It tells you which filed entity is entitled to issue that number. It does not tell you who designed the vehicle, who sold it, who warrants it, or whose name is above the showroom door. On many makes those are visibly different things and the gap is the whole story of the page. Here the registered name contains the badge, so the distinction passes almost unnoticed — but it is still a distinction, and it is still the reason the field says S.P.A. rather than simply “Alfa Romeo”.

We are not going to narrate anything past that, because the register does not carry it. A filing supplies a name, a country and a date. It does not record how entities relate to one another, who owns what, or why a second code was opened at all, and this site does not supply that sort of detail from memory. What can be said with confidence is what is written down: one registered name, two codes, both held by it.

## Italy against both codes, and what that field records

The country column asks a narrower question than it appears to, so here is the correct reading of it. Both codes have Italy recorded against them. There is one country in this entry and no blanks.

What that records is where the registering entity filed. It is a fact about a filing, not a fact about a production line. A code can be registered by an entity in one country and used on vehicles assembled somewhere else, and the register neither prevents that nor comments on it. Read as a statement about paperwork it is exact; read as a statement about where vehicles were assembled it is being asked to carry weight it was never given.

Two codes, one country, no gaps — it invites the conclusion that the register has just told you where every car under this badge was built. It has not. It has told you where two filings sit.

The practical upshot for a buyer is narrow. Do not treat the country against a manufacturer code as an assembly location. If where a particular car was built matters to you, that belongs to the documentation and to the physical certification label on the vehicle, not to this field.

## Two filing dates, and the boundary they set

Each code carries the date its registration was recorded. In order, this entry runs April 2015 and May 2017 — the passenger car code first, the multipurpose passenger vehicle code second.

Those are registration dates. They are not build dates, they are not model years, and they are not the date any vehicle went on sale. A code has to exist before numbers can be issued under it, so a filing date sets an outer boundary and nothing finer. It does not say that vehicles began appearing that month, and it says nothing at all about volumes.

Reading the dates as an ordering is legitimate and mildly useful. They tell you which of the two filings is older, and that the later of the two is the one filed under the multipurpose passenger vehicle class. That is a fact about the sequence of filings. It is not a fact about the sequence of cars, and the two should not be run together.

If you want the model year of a specific vehicle, that is position ten of the individual number rather than anything in the register entry, and it is standardised across manufacturers. The [year chart](https://baronauto1.com/vehicle-history/vin-year-chart/) converts the character.

## Nine model names, quoted exactly as the decoder holds them

Separately from the manufacturer codes, the federal decoder holds a roster of model names for each make. For Alfa Romeo that roster runs to nine entries, and because it is short enough to print without editing, here it is in full, spelled as filed:

- 164
- 4C
- 8C Competizione Spider
- GTV6
- Giulia (952)
- Milano
- Spider
- Stelvio
- Tonale

Two things about that list are worth flagging before anyone reads more into it than it holds. The first is that it is what the decoder holds across all years rather than any current line-up — that qualification is written into the source data itself, and it applies to every make in this series. A name being present says the decoder knows it. A name being absent says only that the decoder does not.

The second is that one of the nine carries a parenthetical: Giulia (952). We have reprinted it exactly as filed rather than tidying it into something that reads better, because tidying a field is the first step towards quietly rewriting it. If a decode returns that string, it has returned what the register holds, and the parenthesis is part of the record rather than a formatting accident on this page.

Printing the roster at all is unusual across this series. Counted across the fifty-six entries in the file, twelve carry the model names themselves rather than only a count; the rest carry the number and nothing else, and on those pages we say so instead of reconstructing a list from somewhere we cannot cite. Alfa Romeo happens to be one of the twelve, so the list above is quotation rather than reconstruction.

## Two codes against nine names

The gap between the two figures is the part worth taking away. A manufacturer code is a registration: an entity files for the right to issue numbers, and the filing sits under one vehicle class. A model name is a catalogue entry the decoder holds for the make. There is no requirement that the two scale together, and on this entry they very obviously do not.

That mismatch is the reason counting codes tells you almost nothing about a manufacturer’s size or range. Two registered prefixes can carry a great many distinct vehicles, because the characters that distinguish one model from another sit in the descriptor block rather than in the prefix. The prefix is a doorway. What is behind it is decided further along the number.

It also explains why the model field on a real decode is more useful than any roster. Decoding an actual number returns the model for that specific vehicle, resolved by the federal system from the characters in front of it. The nine names above tell you what the decoder is capable of returning under this make. Only a decode of a real number tells you what it returns for the car you are looking at.

## No parent entry, and nothing to filter out

Two administrative points, both of which can be stated flatly.

First, this make registers under its own name. Some makes covered on this site do not: their codes are held by a parent group, and querying the badge alone returns nothing at all, which is a genuine source of confusion on those pages. That situation does not arise here. Both codes are filed under a name containing the make name, and there is no parent entry sitting behind them.

Second, a name query against the register returns zero unrelated matches for this make. Because the register matches company names as text, a query on a short or common word can drag in small builders whose own names merely contain it, and counting those in or filtering them out changes the total a make appears to hold. On this entry the figure is zero, which is the ordinary outcome rather than a remarkable one — counted across the fifty-six entries in the file, forty-three return zero. The two codes above are the complete set, with nothing to filter out.

## What the decode does not carry

Everything above concerns what the register holds. This section concerns what it does not, and for anyone about to hand over money it is the more important half.

A VIN decode does not carry service history. It will not tell you when the car was last looked at, what was done, whether it was done by someone competent, or whether anything was skipped.

A decode does not carry condition. It resolves what the vehicle was specified as when the number was assigned, and says nothing about what has happened since — wear, damage, repairs, replacements, or anything fitted, removed or swapped after the vehicle left the factory. A number is a fixed record of an origin, not a live description of an object.

A decode does not tell you that a recall was carried out. It is worth separating these two, because the recall lookup and the VIN decode feel like the same operation. They are not. A recall check against a specific number shows whether a campaign is recorded as open or as remedied against that vehicle, which is free, quick and always worth running — our guide to [checking a car for open recalls](https://baronauto1.com/vehicle-history/how-to-check-a-car-for-open-recalls/) covers how. What it cannot show is whether a previous owner ever actually presented the car, nor any work done outside the campaign system. Read the campaign text rather than only the status flag.

And a decode does not carry title status, mileage history, or the record of what has been reported against the vehicle over its life. Those live in different systems and have to be asked separately. A [free VIN check](https://baronauto1.com/vehicle-history/free-vin-check/) is a reasonable first pass, and a [title check by VIN](https://baronauto1.com/vehicle-history/title-check-by-vin/) covers the branding questions a decode is structurally incapable of answering.

## Working through a specific car

Put together, the sensible sequence on an individual vehicle is short.

Start by checking that the number on the car matches the number on the paperwork, in every character, on every document.

Then decode the number and read the result for what it is. The manufacturer prefix will resolve to ZAR or to ZAS, and the decode will return a registered company name and a federal vehicle class. Expect the company name to be a registered entity rather than the badge. Expect the vehicle class to be a regulatory word, and expect it to differ between two cars that look to you like the same sort of thing. Neither is a fault.

Then check the model-year character against the advert, run the recall lookup, and run the title check. Between them those take a few minutes and they address the questions that actually decide whether a car is worth pursuing.

Finally, treat everything the decode cannot reach as a documentation problem rather than a data problem. Service records, evidence that recall work was done, and an inspection by somebody who knows the marque are what fill the gap.

## If you are the one selling

The same material is useful from the other side of the transaction. A buyer who runs a decode and gets back a registered company name, or a vehicle class that reads oddly against the car in the driveway, may well arrive with a question that sounds like an accusation.

The answer is the one this page has been making throughout: the register records a registrant and a federal classification, and neither is a description of the car. Being able to say that calmly, and to point at the entry it comes from, tends to close the question rather than open it. A seller who understands their own paperwork looks like a seller worth dealing with, which is a useful impression to have established before the price comes up.

## Common questions

### Is there an official Alfa Romeo VIN decoder?

Not a separate one, and none is needed. Vehicles carry the same 17-character number regardless of badge, and the federal register resolves the manufacturer prefix on the same terms for every make. A general decoder handles this marque.

### How many manufacturer codes does Alfa Romeo have?

Two: ZAR and ZAS. That is the complete entry, not a selection from a longer list.

### What is the difference between ZAR and ZAS?

They are filed under different federal vehicle types. ZAR is filed as Passenger Car and ZAS as Multipurpose Passenger Vehicle. Both are registered to the same company name and both record Italy as the country of filing, so the vehicle class is the only field in the entry that separates them.

### Why does my decode say “Multipurpose Passenger Vehicle”?

Because the code your number opens with is filed under that federal classification, and a decoder reporting the register faithfully will return it. It is a regulatory category defined by how a vehicle is constructed and what it is engineered to do, not a description of body shape or character. Seeing it is not evidence of an error, a wrong number, or a misdescribed car.

### What is the difference between Passenger Car and MPV in a decode?

They are two categories in the federal safety standards. Both cover vehicles. The multipurpose category additionally requires construction on a truck chassis, or special features for occasional off-road use, and the classification settles which standards apply. On this make, one code is filed under each.

### Which company name will a decode return?

ALFA ROMEO S.P.A., on both codes. A decode reports the registered entity entitled to issue the number rather than the badge on the car. The register gives that entity a name, a country and a date, and nothing more, so nothing more is claimed here.

### Does the country field tell me where my car was built?

No. Both codes have Italy recorded against them, and the field records where the registering entity filed. A code registered in one country can be used on vehicles assembled elsewhere, and the register does not comment on that. Where a specific car was built belongs to the documentation and the certification label on the vehicle.

### What do the registration dates mean?

They record when each code’s filing was entered: April 2015 for the passenger car code and May 2017 for the multipurpose passenger vehicle code. They are not build dates, model years or sale dates. They order the filings and set an outer boundary on when numbers could be issued under each, and that is the whole of their meaning.

### Which models does the decoder hold for Alfa Romeo?

Nine, listed in full on this page: 164, 4C, 8C Competizione Spider, GTV6, Giulia (952), Milano, Spider, Stelvio and Tonale. That is what the decoder holds across all years rather than a current line-up, and it is quoted exactly as filed, including the parenthetical on one of them.

### Does an Alfa Romeo 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 converts it into a plant name, so no plant-code table appears on this page. The country recorded against a code describes the registrant’s filing instead.

### Will a decode tell me the specification or options?

No. It resolves what the federal system holds for the number — manufacturer, class, model year and the model line as filed. Options, fitted equipment and anything changed after the vehicle was built sit outside every historical decode, on this make and on all others.

### Can a VIN check prove a recall was completed?

It can show whether a campaign is recorded as open or remedied against that specific number, which is free and worth running. It cannot prove a previous owner presented the vehicle, and it does not capture work done outside the campaign system. Read the campaign text, not just the flag.

### Does Alfa Romeo register under a parent company?

No. Both codes are filed under the make’s own registered name, and a register query on the name returns zero unrelated matches, so the two codes listed here are the complete set with nothing to filter out.

## Sources and further reading

- [NHTSA VIN decoder](https://vpic.nhtsa.dot.gov/decoder/)
- [NHTSA recall lookup](https://www.nhtsa.gov/recalls)
- [NMVTIS (US Department of Justice)](https://vehiclehistory.bja.ojp.gov/)
- [49 CFR Part 567 — Certification](https://www.ecfr.gov/current/title-49/subtitle-B/chapter-V/part-567)

Recall, complaint and safety-rating figures on this page were retrieved from the federal databases above on August 19, 2026. Federal data changes — re-check any VIN before you rely on it.

---

*This site is under new ownership and is not affiliated with Baron Auto Emporium dealership.*

Canonical source: https://baronauto1.com/vehicle-history/alfa-romeo-vin-decoder/