If you want an authoritative picture of how a Scion was built and what it’s been through since leaving the assembly line, start with the Vehicle Identification Number (VIN). This 17-character code is the vehicle’s fingerprint, linking it to its model year, manufacturing details, and other factory-recorded information that can be checked independently rather than taken at face value from a listing or seller.
Using our free Scion VIN lookup, you can decode models like the tC, xB, or FR-S and quickly access key details from trusted data sources. It allows you to confirm fundamental specifications and original equipment, review an estimate of current market value, and examine longer-term indicators such as depreciation trends and expected lifespan. When both sides of a transaction are grounded in the same documented facts, conversations about pricing, condition, and features are less ambiguous and more productive.
For a deeper level of verification, expanded reports can uncover more meaningful background information, including NMVTIS-based title data that may reveal salvage or other branded title issues, access to original window sticker details to validate factory-installed options, and reported accident history.
Whether you’re evaluating a Scion before purchasing or preparing one for sale, starting with the VIN helps eliminate guesswork and reduces the chance of running into expensive surprises or legal complications. Enter a Scion VIN to get immediate results at no cost and without creating an account, so you can move forward with better clarity and confidence.
Scion VIN Lookup FAQ
What is a VIN lookup, and why would I do one?
A VIN lookup is the act of entering that 17-character identifier into a decoder, recall database, or vehicle history system to confirm the vehicle’s original configuration. For a Scion, that matters when you are checking whether a seller described the car correctly, confirming the model year and build plant, screening for open recalls, narrowing down parts compatibility, or separating a simple VIN typo from something more serious.
Did Scion ever use pre-1981 VIN formats?
No. In the U.S., Scion launched in 2003, and the federal decoder ecosystem for standardized VINs applies to 1981-and-newer vehicles. So every U.S.-market Scion belongs to the 17-character VIN era.
Where can I find the VIN on a Scion?
Start with the lower driver’s-side area of the dash, as viewed through the windshield. You should also find the VIN on the driver-side door jamb label, and it is commonly repeated on registration and insurance documents.
What information is encoded in a Scion VIN?
At minimum, it has the manufacturing entity/brand, model year, plant, and serial sequence. Depending on the model and year, it may also encode body style, engine family, restraint system, series, and model line; some Scion VIN documents are quite explicit about those fields, especially for models like the tC and FR-S.
What can’t a VIN tell me by itself?
A VIN is not a complete biography of a car. By itself it does not prove accident history, odometer accuracy, title brands, maintenance quality, current vehicle condition, undisclosed flood damage, or every installed option package; that information requires searching through additional databases and records, along with a mechanic’s in-sperson inspection.
What is the difference between VIN decoding, recall lookup, and a vehicle history report?
VIN decoding identifies what the VIN itself encodes. A recall lookup checks whether a specific VIN has unrepaired safety recalls or manufacturer campaigns. A vehicle history report, especially one drawing from title history systems, is about ownership/title events, brands, and other historical records rather than the VIN’s internal structure.
Are all Scion VINs 17 characters?
Yes, for U.S.-market Scions. A proper U.S. Scion VIN is 17 characters long, uses capital letters and digits, and does not use the letters I, O, or Q in the standard VIN character set. If you see a shorter “VIN”, you are usually looking at a truncated listing entry, an internal stock/reference number, or bad data.
How is a Scion VIN structured?
All U.S.-market Scions follow the federal 17-character framework used for modern VINs.
| Positions | Meaning |
|---|---|
| 1-3 | World Manufacturer Identifier (WMI) |
| 4-8 | Vehicle descriptor section |
| 9 | Check digit |
| 10 | Model year |
| 11 | Assembly plant |
| 12-17 | Sequential production number |
What do the first three characters mean?
They are the WMI, the section that identifies the manufacturer/type context. For Scions, that is where many people get tripped up, because the WMI on different models can point to different manufacturing entities: many classic Scions use Toyota-associated WMIs, the FR-S uses a Subaru/FHI WMI, and the 2016 iA uses a Mexico-built Mazda-associated WMI.
Do all Scion VINs start with JTK?
No. Many Scions do, but not all of them. Documented U.S.-market examples show the iQ under JTN, the FR-S under JF1, and the 2016 iA under 3MY.
What do characters 4 through 8 mean on a Scion?
Those five characters are the vehicle descriptor section, and on Scions they can encode body type, engine, restraint system, series, grade, and model line depending on the year and model. The important point is that the meaning is not brand-wide; it is model- and year-specific, so a valid 4-8 pattern for a tC is not a valid pattern for an FR-S or iQ.
What is the check digit in position 9?
It is a mathematically derived verification character used to catch many transcription errors. It is not a theft detector, not a title history report, and not a guarantee that the VIN was never cloned; it is simply a mathematical validity check built into the VIN format.
What does the 10th character mean?
It is the model year code. One nuance matters: the year code repeats on a 30-year cycle, so the code alone is not always enough; for passenger cars and light trucks, position 7 helps distinguish whether the 10th character is being interpreted in the 1980-2009 range or the 2010-2039 range. If the character in position 7 is numeric, then the 10th character should be interpreted in the 1980-2009 range; if it’s a letter, then the 10th character should belong to the 2010-2039 range.
What does the 11th character mean?
It is the plant code, which identifies the assembly plant within the manufacturer’s coding scheme. On some Scions this is just a plant identifier; on others, it can also line up with transmission-specific production variants at the same plant.
What do the last six characters mean?
They are the sequential production number for high-volume passenger vehicles in this modern VIN structure. They make the VIN unique once the earlier positions have defined the manufacturer, descriptor, year, and plant.
Which model year codes matter for U.S.-market Scions?
For practical Scion lookup work, these are the year codes that bracket the Scion era you will encounter in U.S. databases. The important ceiling is G for 2016, because Toyota announced that beginning in August 2016, MY2017 former Scions would be badged as Toyotas.
| Model year | Code |
|---|---|
| 2003 | 3 |
| 2004 | 4 |
| 2005 | 5 |
| 2006 | 6 |
| 2007 | 7 |
| 2008 | 8 |
| 2009 | 9 |
| 2010 | A |
| 2011 | B |
| 2012 | C |
| 2013 | D |
| 2014 | E |
| 2015 | F |
| 2016 | G |
Which WMI prefixes commonly appear on U.S.-market Scions?
These are the most useful documented examples to know. They are not an exhaustive list of every Scion VIN ever assigned, but they cover the cases that most often confuse lookup tools and buyers.
| WMI | Documented Scion use | Why it matters |
|---|---|---|
| JTK | Early xA, xB, tC, and documented xD populations | Many “classic” Scion VINs live here |
| JTN | iQ | Not every Scion starts with JTK |
| JF1 | FR-S | Subaru/FHI-built Scion |
| 3MY | 2016 iA | Mazda-built Mexico sedan sold as a Scion |
Treat this as a practical decoder table, not a claim that one prefix covered the whole brand.
What changed with xD and iQ VINs?
The xD and iQ are a good reminder that Scion VIN logic changed over time. Documented recall populations show the 2008-2010 xD under JTK with VDS patterns such as KU104 and KU4B4, while the 2012 to early 2013 iQ appears under JTN with VDS JJXB0.
That means a decoder that only acknowledges older xA/xB/tC assumptions will age badly. A lookup that treats every Scion as a JTK hatchback from the mid-2000s is not decoding; it is guessing.
Why does the FR-S have a Subaru-style VIN?
Because it is not Toyota-built in the usual Scion sense. The official FR-S VIN coding document shows JF1 as the WMI, which identifies Fuji Heavy Industries/Subaru as the manufacturer, and uses ZNAA1 in positions 4-8 for the documented 2014 Scion FR-S example.
That same document also makes the FR-S especially useful for VIN study because its 11th character distinguishes documented manual and automatic production variants at the Ota, Gunma plant: 9 for 6MT and 8 for 6AT in the cited 2014 scheme.
Why can 2016 iA and 2016 iM lookups be confusing?
Because they arrived late in the brand’s life and then immediately got caught in the Scion-to-Toyota transition. Toyota announced in 2016 that beginning in August of that year, MY2017 Scion vehicles would be rebadged as Toyotas, specifically the FR-S, iA, and iM, while the tC would end production.
The iA adds a second complication: Toyota service literature documents 3MY as the WMI on 2016 Scion iA vehicles, and Toyota’s North American manufacturing report states that Mazda began producing the Scion iA/Toyota Yaris in Salamanca, Guanajuato. So one decoder may surface the car through a Scion lens while another catalogs it through Toyota or Mazda-adjacent production data.
The iM is confusing for a different reason. Toyota introduced it as a 2016 Scion model, then moved the line into Toyota badging for MY2017, which is why parts catalogs and title systems may flip between Scion iM and Toyota Corolla iM terminology around the transition period.
Can a VIN confirm trim, engine, transmission, and airbags exactly?
Sometimes, but not universally. The official 2015 tC VIN document explicitly maps positions 4-8 to body type, engine, restraint package, series, and model line, and the FR-S document goes so far as to distinguish documented manual versus automatic variants via the 11th character.
What a VIN usually cannot do by itself is exhaustively confirm every dealer-installed accessory, every appearance package, every wheel option, or every running change without a build sheet or OEM database behind the decoder. Commercial sites often blur that line and make the VIN look more omniscient than it really is.
Can a VIN tell me where a Scion was built?
Yes, often very well. The federal decoder framework exposes build plant information, the 11th character is the plant code, and model-specific documents can make the answer especially clear; for example, the 2015 tC document names Takaoka and Tsutsumi plant codes, while the FR-S document identifies Fuji Heavy Industries’ main plant at Ota, Gunma.
It can also correct assumptions about brand identity. Many shoppers assume a Scion is automatically a Toyota-built Japanese VIN, but the iA is a documented Mexico-built exception and the FR-S is a documented Subaru/FHI-built exception.
Can a VIN prove whether a Scion has open recalls?
It can identify open unrepaired safety recalls when you use the federal recall tool, and Toyota’s own recall site can also surface Toyota, Lexus, and Scion safety recalls and service campaigns for vehicles intended for sale or sold in the U.S. since 1999.
Do not confuse that with a complete lifetime issue log. The federal recall lookup does not show every possible manufacturer campaign, and may omit some very old recalls beyond its normal scope. Some newly announced recalls may not yet have all VINs populated.
Can a VIN decode prove accident history, mileage, or title problems?
No. Those are history questions, not VIN-structure questions. For title and brand screening, the correct source is a NMVTIS-based history report plus whatever inspection, maintenance records, and seller documentation you can obtain.
How should I decode a fictional Scion xB VIN, step by step?
Use this as a constructed example, not as a real-vehicle reference: JTKKT324664000001. It is fictional, but it follows a documented early xB code pattern and uses a correct check digit under the federal formula.
| Chunk | Meaning |
|---|---|
| JTK | Documented Toyota passenger car WMI used on early Scion examples |
| KT324 | Documented early xB-style descriptor: 5-door wagon/MPV 2WD, 1NZ-FE engine, NCP31L series, grade 2, line 4 |
| 6 | Check digit |
| 6 | 2006 model year |
| 4 | Documented Sagamihara plant code in the cited xB example set |
| 000001 | Sequential production number |
This is the kind of VIN where a weak decoder may just say “Scion xB”, while a good one should provide body/engine/series context from the descriptor.
How should I decode a fictional Scion tC VIN, step by step?
Use this constructed example: JTKJF5C73FJ123456. It is fictional, but it uses the documented 2015 tC coding pattern and a correct calculated check digit.
| Chunk | Meaning |
|---|---|
| JTK | Documented Toyota passenger car WMI |
| JF5C7 | Documented 2015 tC descriptor: 3-door liftback 2WD, 2AR-FE 2.5L gasoline engine, coded restraint package, AGT20L series, Scion tC line |
| 3 | Check digit |
| F | 2015 model year |
| J | Documented Takaoka plant code for one 2015 tC configuration |
| 123456 | Sequential production number |
This is a good example of how much detail some Scion VINs really can carry.
How should I decode a fictional Scion FR-S VIN, step by step?
Use this constructed example: JF1ZNAA17E9700001. It is fictional, but it follows the documented 2014 FR-S VIN pattern and uses a correct check digit.
| Chunk | Meaning |
|---|---|
| JF1 | Documented Fuji Heavy Industries/Subaru passenger car WMI |
| ZNAA1 | Documented FR-S descriptor: Scion FR-S coupe, 2.0L naturally aspirated engine, standard trim, documented restraint configuration |
| 7 | Check digit |
| E | 2014 model year |
| 9 | Documented Ota, Gunma plant / 6MT variant |
| 700001 | Sequential production number |
How do I verify a Scion VIN’s check digit myself?
The federal VIN algorithm is simple in concept: convert each letter to its assigned value (numbers remain numbers), multiply each position by its weight, add the products, divide by 11, and use the remainder as the check digit; if the remainder is 10, the check digit becomes X.
| Character | Value |
|---|---|
| A | 1 |
| B | 2 |
| C | 3 |
| D | 4 |
| E | 5 |
| F | 6 |
| G | 7 |
| H | 8 |
| J | 1 |
| K | 2 |
| L | 3 |
| M | 4 |
| N | 5 |
| P | 7 |
| R | 9 |
| S | 2 |
| T | 3 |
| U | 4 |
| V | 5 |
| W | 6 |
| X | 7 |
| Y | 8 |
| Z | 9 |
| Pos | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Wt | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 10 | 0 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 |
For the fictional 2015 tC example JTKJF5C73FJ123456, the weighted total is 300. Dividing by 11 leaves a remainder of 3, so the check digit is 3, which matches position 9. Also remember that I, O, and Q are not used in standard VINs.
What should I check before buying a used Scion from its VIN?
Run the basic VIN decode first so you know exactly what the vehicle is supposed to be. Then run the federal recall lookup, run Toyota’s recall/campaign lookup, pull an NMVTIS-based history report, and physically compare the windshield VIN, the driver-door jamb VIN label, and the paperwork; if those do not line up cleanly, don’t treat it as a minor clerical issue until you prove otherwise.
What should I do if different decoders give conflicting results?
Start with the car itself and the official tools. Confirm the full 17-character VIN from the windshield and door jamb label, verify that the check digit is valid, then compare the federal decoder, the federal recall tool, and Toyota’s campaign lookup; third-party sites are useful, but when they disagree with the physical VIN and the official systems, the third-party site is likely the source of the discrepancy.