---
title: "Keystone RV VIN Decoder: One Code, and Seven Strangers"
description: "Keystone holds 1 manufacturer code of its own, while a raw name query returns 7 unrelated companies and the decoder holds no models at all. Why a name search is the wrong way to count."
url: "https://baronauto1.com/vehicle-history/keystone-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."
---

# Keystone RV VIN Decoder: One Code, and Seven Strangers

> Keystone holds 1 manufacturer code of its own, while a raw name query returns 7 unrelated companies and the decoder holds no models at all. Why a name search is the wrong way to count.

*VIN & Vehicle History · 21 min read · 4,754 words*

## The short version

- There is no Keystone-only decoder and none is needed. Every vehicle certified for this market carries the same seventeen-character number, and one federal register resolves the manufacturer prefix on all of them.
- The register holds exactly one manufacturer code under this make: 4YD, filed under the registered name KEYSTONE RV.
- Query that register for the string “Keystone” and seven further codes come back, held by seven separate companies whose registered names also contain the word. Treat the query as the entry and you count eight. The entry holds one.
- 4YD is filed under the vehicle type Trailer, with the United States recorded as the country the registrant filed in, and a registration date of 29 August 2017. That date records when the filing was received, not when anything was built.
- Five of the seven name matches are also filed as trailers, all eight records name the same country, and four of the seven share one registration date — so none of those fields separates them. Only the registered name does.
- The decoder holds no model names at all under this make. The model count is zero, which means no floorplan, no series name and no layout can be sourced from this entry.
- What no decode carries, here or on any make: service history, present condition, and whether a recall that was issued was ever actually carried out.

The phrase “Keystone RV VIN decoder” implies a tool built for one badge. There is no such tool, and there is no gap where one ought to be. The number stamped into a travel trailer is built to the same federal standard as the number on a saloon car, and the register that turns its first three characters into a manufacturer is the same register that does that job for every other make certified for sale here.

What is worth reading closely is the register entry itself, because on this make it is unusually short and unusually easy to miscount. The entry holds one manufacturer code. A query on the brand name returns eight records. Those two numbers describe the same register, and the gap between them is not an error in either — it is the difference between asking which company holds a code and asking which registered names happen to contain a particular word.

This page works from that federal entry and nothing else. One code of its own, seven unrelated name matches, one country, one registration date, one vehicle type and a model roster of zero. There is no company history here, no product commentary and no ownership advice, because the filing does not carry any of it. What follows is a public record read line by line, with the limits pointed at rather than smoothed over.

**Figure: Keystone RV world manufacturer identifiers by vehicle type**

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

Keystone RV holds 1 world manufacturer identifier in NHTSA’s register, covering 1 country of manufacture, against 0 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, and this make is not an exception

The vehicle identification number is a federal standard, and its layout does not change with the badge on the front of the unit. 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 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 characters are the serial.

Because that structure is identical across everything certified for sale here, a general decoder handles a Keystone RV number as readily as it handles anything else. Our guide to [reading a VIN position by position](https://baronauto1.com/vehicle-history/how-to-read-a-vin/) works through 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 make-specific decoder would earn its keep is the middle block, and this is the point at which honesty serves a reader 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, which country the entity filed in, and the date the code was opened. It does not record what a particular character in position six means on one build as against another.

So this page prints no position-by-position breakdown 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 somewhere else. Position ten, the model year character, is the one part of the middle of a number that is standardised across makes, and our [VIN year chart](https://baronauto1.com/vehicle-history/vin-year-chart/) converts it.

## One code, and 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 this make there is one of them, and it is 4YD.

Here is the whole record attached to it. The registered name is KEYSTONE RV. The vehicle type is Trailer. The country recorded is the United States. The registration date is 29 August 2017. There is no second code, no continuation and nothing omitted for reasons of space — four fields and a single row is the complete federal entry for this make.

That brevity is worth pausing on, because it sets the ceiling for everything a decode can tell you here. On a make with forty registered codes, the prefix carries real discriminating power: it can separate one arm of a group from another, one class of product from another, one country of filing from another. With one code, it cannot. Every number issued under this make opens with the same three characters, so the prefix confirms the builder and the broad category and then has nothing further to say. Everything that distinguishes one unit from the next lives in the descriptor block, in the paperwork, and in the vehicle itself.

What that leading character does not do is tell you which building a unit was assembled in. That is a separate question, and the federal data does not answer it.

## What a name query actually does, and why it is not a count

The register can be queried by company name, and this is where the counting goes wrong on this make. The query is a text match against the registered name field. It returns every filing whose company name contains the string, and it makes no judgement whatever about whether those companies are related to one another, because it has no way to make one. The field it searches is a name. It is not a corporate structure.

Run that query for “Keystone” and eight records come back: 4YD, plus seven others. Counting across all 56 make entries archived for this site, 43 return no unrelated name matches at all, so the empty result is the ordinary one. Six entries return more name matches than the make holds codes of its own, and this is one of the six. Only two of the 56 carry a larger name-match figure than the seven counted here.

**Figure: What the register holds under Keystone**

Three counts from the Keystone RV entry: codes registered under the brand name, models the decoder holds, and unrelated companies returned by a name query.

One code of its own against a name query that returns several unrelated companies, and no models at all. Seven unrelated companies against one real code is the reason a raw name search is the wrong way to count anything. Read from NHTSA’s vPIC register and archived in data/vin-makes.json.

The three numbers in that figure are the argument of this page in miniature. One code registered under the make. Zero models held by the decoder. Seven records returned by a name query that has nothing to do with either. Read the middle row as a subtotal of the third and you have built a total that no field in the register supports.

None of this makes the query useless. It makes it a tool for finding candidate filings rather than a tool for counting them, and the counting step — deciding which of the returned rows belong to the make you asked about — is not something the query performs. It is left entirely to whoever reads the output.

## The seven companies the string catches

It is easier to see the problem when the matches are named rather than totalled, so here they are as the register carries them: KEYSTONE CHOPPERS, filed as a motorcycle; KEYSTONE OILFIELD FABRICATION, LLC, filed as a trailer; KEYSTONE TRAILERS INC., filed as a trailer; KEYSTONE KABINS, filed as a trailer; KEYSTONE VENDING CART CO., INC., filed as a trailer; KEYSTONE TRAILER CO, filed as a trailer; and KEYSTONE LSV CO., filed under the class the register writes as Low Speed Vehicle (LSV).

Seven filings, seven registered names, and every one of them a separate record from 4YD. The register does not say that any of these companies is connected to any other, and this page will not say it either. What the register does say is that each of them filed under a name containing the same word, which is the whole reason they appear in the same result set.

Two of the seven are easy to set aside on sight, because a motorcycle filing and a low speed vehicle filing are not going to be confused with a travel trailer by anyone reading the vehicle type column. The remaining five are the difficulty. They are filed under the same vehicle type as 4YD, they are registered in the same country, and two of them carry the word “trailer” in the registered name. Nothing in the shape of those rows announces that they are different companies. Only the name, read exactly and in full, does that.

## Three characters against six, and the tell that is actually reliable

Look at the identifiers themselves and a mechanical difference appears that the vehicle type column cannot give you. The code held under this make, 4YD, is three characters long. Every one of the seven name matches runs to six: 1K9230, 1K9243, 1K9286, 1K9312, 1K9338, 1K9354 and 1K9449. All seven open with the same three characters, 1K9.

That is not a formatting quirk in the archive.The register prints the two parts as a single six-character string, which is why a shared opening block followed by a distinct three-character tail is what those filings look like from outside.

The practical consequence matters more than the mechanism. A number issued under any of those seven opens with 1K9, and is distinguished from the other six only at positions twelve to fourteen. A number issued under this make opens with 4YD, and there is nothing to disambiguate because the make holds one code. So if you are holding an actual seventeen-character number, the first three characters settle the question immediately: 4YD or not 4YD. No name query is involved, and no judgement about which rows to keep is required.

This is the general shape of the answer to “what should I do instead”. Start from a number and resolve it. Do not start from a word and try to count what comes back.

## The fields that will not separate them

If you are working from the register rather than from a specific number — checking a claim, say, or trying to establish what the federal system actually holds — it is worth knowing which columns help and which do not.

The country field does not help at all. All eight records, the make’s own code and every one of the seven matches, record the United States. Whatever else that field is doing, it is not distinguishing these filings from one another.

The registration date does not help either. Four of the seven matches carry the same date, 21 July 2015. The remaining three are dated 11 December 2015, 20 December 2017 and 10 October 2024, and the make’s own code is dated 29 August 2017 — which falls between two of them. There is no chronological boundary to draw.

The vehicle type field helps, but only partly. It removes two of the seven and leaves five standing, all filed as trailers alongside 4YD. Anyone using vehicle type as the filter will still be over-counting this entry by five.

Which leaves the registered name and the length of the identifier as the two fields that do the work. Read the name in full rather than scanning for the keyword, and check whether the identifier is three characters or six. Those two checks resolve the entry completely, and they are the only two that do.

## How to count this entry properly

Pulled together, the method is short enough to state as a sequence.

First, decide what question you are asking. “How many manufacturer codes does this make hold?” and “how many register records contain this word?” are different questions with different answers, and conflating them is the specific failure this page exists to describe. Here the answers are one and eight.

Second, if you have a VIN, do not use the name route at all. Resolve the first three characters. They will either be 4YD, in which case the record above is the record you want, or they will be something else, in which case the make is not this one whatever the badge on the side says.

Third, if you are working from the register, read every returned name to its end. A registered name is a legal entity’s name and it is carried in full. The difference between the record you want and the record you do not is often nothing more than the word that follows the one you searched for.

Fourth, check the identifier length before you add a row to a total. Three characters and six characters are different objects in this register, and a six-character record will never be the prefix a VIN opens with.

Fifth, do not treat a total assembled this way as a fact about a company. The register describes filings. It does not describe corporate relationships, and no amount of careful counting will make it do so.

## “Trailer” is a classification, not a description

The vehicle type against 4YD is Trailer. That word is a federal classification rather than a description of any particular unit, and it is worth being clear about how little it undertakes to tell you.

Every world manufacturer identifier is filed under a vehicle type drawn from the federal categories, and those categories exist because the rules that apply to a vehicle depend on which one it falls into. The distinction that matters most in this part of the register is between something that is towed and something that drives itself. A trailer filing describes a unit without its own motive power. That is a genuine and useful distinction, and it is one of the few things the prefix here settles outright.

What the word does not carry is everything a buyer is actually choosing between. It does not carry length, weight, axle count, floorplan, sleeping capacity, the fit-out, or whether a given unit is a conventional tow-behind or a fifth wheel. Those distinctions are real, they matter enormously to whether a particular trailer suits a particular vehicle and a particular household, and not one of them is present in a single-word classification field. Our [trailer VIN lookup guide](https://baronauto1.com/vehicle-history/trailer-vin-lookup/) covers what the number does settle on a towed unit, and the [RV VIN lookup guide](https://baronauto1.com/vehicle-history/rv-vin-lookup/) and [camper VIN lookup guide](https://baronauto1.com/vehicle-history/camper-vin-lookup/) deal with the wider category.

The related trap is the weight and capacity question. A decode will not give you a gross vehicle weight rating or a tongue weight. Those are printed on the federal certification label fixed to the unit itself, and that label is the authority for them. If a listing quotes figures that the label contradicts, the label wins.

## The country field, and what it records

The country recorded against 4YD is the United States. That field records where the registering entity filed. It is a fact about a filing, and it is not a statement about where a unit was assembled.

The distinction sounds pedantic until someone tries to lean on it. A code can be registered by an entity in one country and used on vehicles built somewhere else, and the register neither prevents that nor comments on it. Counting across the 56 make entries archived here, nine record only the United States against every code they hold, and this is one of the nine — but that is a statement about nine sets of filings, not about nine production networks.

If where a unit was built matters to you, that question belongs to the certification label and to the documentation, not to this field. The label is physically on the vehicle, it carries the manufacturer name as certified, and it is the record to read when the answer has to be right.

## One registration date, and what it does not mean

The entry carries a single date: 29 August 2017, recorded against 4YD.

That is a registration date. It is not a build date, not a model year, and not the date any unit was sold. A code has to exist before numbers can be issued under it, so the filing date sets an outer boundary and nothing finer. It does not establish that anything appeared that month, it says nothing about volumes, and it does not license any inference about what the company was doing at the time. The register records that a filing was received and when. Everything past that is guesswork, and this page does not offer any.

The point to guard against is the temptation to read a 2017 filing date as though it bounded the age of the units you might encounter. It does not do that in either direction with any precision. If you want the model year of a specific trailer, that is position ten of its own number, standardised across manufacturers, and the [year chart](https://baronauto1.com/vehicle-history/vin-year-chart/) converts the character. The registration date on the prefix is not a substitute for it and should never be used as one.

## No model roster at all

Separately from the manufacturer codes, the federal decoder holds a roster of model names for many makes. Under this one it holds none. The model count is zero.

Of the 56 make entries archived for this site, two hold no models at all, and this is one of the two. It is a genuinely restrictive fact and it deserves to be stated flatly rather than worked around. It means there is no series name, no floorplan designation and no product line in the federal entry for this make.

This page therefore prints no model names, because it has none to print from a source it would stand behind. That is not a small omission and we would rather name it than paper over it. Reconstructing a roster from somewhere else and letting it sit beside sourced data, as though the two carried equal weight, is exactly the failure this site tries not to commit.

It matters less on a specific unit than it looks. Decoding an actual number returns whatever the federal system resolves for that number, which is the answer worth having and does not depend on any roster being reprinted here. Where the entry is silent, the paperwork and the certification label carry the identifying detail instead. For a comparison, our page on [Forest River](https://baronauto1.com/vehicle-history/forest-river-vin-decoder/) covers an entry that holds several hundred model names against four codes — the same register, the same category of product, and a completely different amount of detail on file.

## Registered under its own name, with nothing behind it

Two administrative points, both flat statements of what the entry holds.

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 a query on the badge alone returns nothing at all, which is a real source of confusion on those pages. That situation does not arise here. The code is filed under a name that contains the make name, and there is no parent entry sitting behind it — the parent field is empty and the parent code count is zero.

Second, and this is the tension the page has been working through, registering under its own name is not the same as owning the word. The register carries no exclusivity in the name field. Seven other companies filed under names containing the same word, and the register accommodated all of them without comment, because a name field is a name field. A make can hold a perfectly clear entry of its own and still be impossible to count by name search, and this make is the demonstration of it.

## 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 a unit was last inspected, what was done to it, whether it was done competently, or whether anything was skipped.On a towed unit that gap covers the running gear, the brakes, the bearings, the roof and the seals — which is to say most of what determines whether it is sound.

A decode does not carry condition. It resolves what a vehicle was specified as when its number was assigned. It says nothing about what has happened since: wear, damage, water ingress, repairs, replacements, or anything fitted, removed or swapped afterwards. 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. This is the one to be explicit about, 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 unit, 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 a 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.

## Using all of this on a specific trailer

On an individual unit the sensible sequence is short, and none of it involves a name search.

Start by finding the number on the vehicle and checking it against the number on every document, character by character. On a towed unit the number is stamped or plated on the frame and repeated on the certification label, and the two should agree with each other and with the paperwork.

Then read the first three characters. If they are 4YD, the record on this page is the record behind them, and what it tells you is the registered name, the federal vehicle class and the country the registrant filed in. If they are anything else, the make is not this one, and that is worth establishing before anything else is discussed.

Then read the certification label properly rather than glancing at it. The weight ratings, the tyre and rim specification and the certified manufacturer name are all there, and they are the figures that decide whether a given tow vehicle is adequate. No decode supplies them.

Then check the model year character against the advert, run the recall lookup, and run the title check. Those three take a few minutes between them and they address the questions that actually decide whether a unit 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, a damp meter and an inspection by somebody who knows towed vehicles are what fill the gap.

## Common questions

### Is there an official Keystone RV VIN decoder?

Not a separate one, and none is needed. Vehicles carry the same seventeen-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 one.

### How many manufacturer codes does this make hold?

One: 4YD. That is the complete entry rather than a selection from a longer list.

### Why does a register search for “Keystone” return eight results?

Because the search matches company names as text. Seven other companies have filed under registered names containing the same word, so their records come back alongside 4YD. The query is telling you which names contain a string; it is not telling you which filings belong to a make, and it has no way to do so.

### How do I tell the real record from the others?

Two checks settle it. Read the registered name in full rather than scanning for the keyword, and look at the length of the identifier. The code held by this make is three characters, 4YD.

### Will the vehicle type column filter the false matches out?

Only partly. It removes two of the seven — one motorcycle filing and one low speed vehicle filing. The other five are filed as trailers, exactly as 4YD is, so anyone filtering on vehicle type alone is still counting five records that do not belong to this make.

### Does the registration date tell me when a trailer was built?

No. 29 August 2017 is when the filing for the code was recorded. It is not a build date, not a model year and not a sale date. For the model year of a specific unit, read position ten of its own number against the year chart.

### What does “Trailer” mean in the decode?

It is a federal classification, and its main content is that the unit has no motive power of its own. It does not carry length, weight rating, axle count, floorplan, sleeping capacity or whether a unit is a conventional tow-behind or a fifth wheel. Those come from the certification label and the documentation.

### Does the country field tell me where a trailer was assembled?

No. It records where the registering entity filed. The United States is recorded here, and the same country is recorded against all seven name matches as well, so the field does not even separate those records from one another. Assembly location is a documentation question.

### How many models does the decoder hold for this make?

None. The model count is zero, which is why no model names appear anywhere on this page. Two of the 56 make entries archived for this site hold no models at all, and this is one of them. Decoding a specific number returns what the federal system resolves for that number.

### Does this make register under a parent company?

No. The parent field is empty and the parent code count is zero. The single code is filed under the make’s own registered name, so a brand-name query does return the right record — it simply returns seven others alongside it.

### Will a decode tell me the specification or the fit-out?

No. It resolves what the federal system holds for the number: manufacturer, class, and whatever the descriptor block yields for that specific vehicle. Options, fitted equipment and anything changed after the unit 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.

## 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/keystone-vin-decoder/