SpareRadar Toyota Hiace GCC spec check

Toyota Hiace: reading the VIN

The Hiace exposed a real defect in this decoder, and the fix is the reason a Gulf Hiace now dates correctly instead of arriving thirty years early.

Is a Toyota Hiace GCC spec?
The honest answer, before anything else on this page.

GCC specification is decided per vehicle, not per model. Two cars of the same model and the same year, built in the same factory in the same week, can go to different markets. So no page can tell you whether yours is a Gulf car, and this one does not try. What it can do is show you exactly what your own VIN encodes and where that stops.

A Hiace carrying the filler 0 at position 10 was not built to the American model-year rule. A Hiace carrying a real year letter there gives a year but no market.

What this decoder reads from a Toyota Hiace VIN
Specific to this model, not to the brand.

A 2015 Gulf-market Hiace used to decode as a 1985 vehicle, and the cause is worth understanding because it affects other export cars too. The universal rule for reading position 10 picks between two thirty-year bands by looking at whether position 7 is a letter or a digit. Gulf Hiace VINs carry a real year letter at position 10 while position 7 is a digit, which sends the rule into the 1980 to 2009 band. The decoder now checks the year against the matched variant's production window and, where the reading is impossible, re-reads the same character in the band the window allows. Australian market Hiaces carry the filler 0 instead and correctly stay year-less. The line letter P at position 8 identifies the Hiace across both the H200 and the H300 on the van WMI JTF and the bus WMI JTG, so an unknown variant still names the vehicle.

Codes this decoder resolves
Descriptors the decoder resolves. The H300 rows resolve model and generation only: the variant and engine split is not yet sourced and nothing was invented to fill it.
CodeModelChassisBodyEngineBuilt
JTF HT02PprovisionalHiace (H200)KDH201Van LWB1KD-FTV 3.0 turbodiesel2005-
JTF HX02PprovisionalHiace (H200)TRH201Van LWB2TR-FE 2.7 petrol2005-
JTG SX23PprovisionalHiace (H200) CommuterTRH223Bus (high roof)2TR-FE 2.7 petrol2005-
JTG JX02PprovisionalHiace (H200)TRH2xxBus/van2TR-FE 2.7 petrol2005-
JTF LMFCPprovisionalHiace (H300)2019-
JTF RMFAPprovisionalHiace (H300)2019-
How a Toyota VIN is laid out
Summary. The full explanation of each position is on the Toyota page.
4 to 8
Model and grade descriptor, read together with the WMI
9
A real check digit on modern Toyotas
10
Usually the filler 0, which is not a year
11
Plant
What the VIN cannot tell you here
Stated because a decoder that never says this is not worth trusting.
  • The H300 variant and engine split is unresolved. Those rows give model and generation and leave the rest null.
  • No trim or seating configuration.

A VIN describes how a vehicle was built. It cannot describe where it was shipped, and no decoder anywhere changes that. The free GCC spec check reads your VIN, gives a verdict with a certainty score and the evidence behind it, and lists the physical and documentary checks that settle what the VIN cannot, starting with the GSO conformity lookup. The full VIN decoder returns every attribute the decode resolves, and the Toyota page explains the scheme above position by position.

Common questions

Why do some VIN decoders date a Gulf Hiace thirty years early?

Because the standard rule for reading the tenth character chooses between two thirty-year cycles based on whether position 7 is a letter or a digit, and Gulf Hiace VINs break that assumption by carrying a digit at position 7 alongside a genuine year letter at position 10. The rule lands in the wrong cycle and a 2015 van reads as 1985. This decoder cross-checks the result against the variant's production window and corrects it.

Other Toyota models