MOT Status
ValidMileage
14,328 miBelow or average mileage for this year
Not all car check providers offer a guarantee. Don't risk buying from services that can't back their data. CarVerify reports include a £30,000 finance data guarantee.
Vehicle Details
All premium checks include
50+ data pointsMOT History
Rear Registration plate deteriorated but not likely to be misread (0.1 (b))
Nearside Front Tyre has a tear, caused by separation or partial failure of its structure (5.2.3 (d) (ii)) DANGEROUS
Nearside Rear Tyre has a tear, caused by separation or partial failure of its structure (5.2.3 (d) (ii)) DANGEROUS
Offside Front Tyre has a tear, caused by separation or partial failure of its structure (5.2.3 (d) (ii)) DANGEROUS
Offside Rear Tyre has a tear, caused by separation or partial failure of its structure (5.2.3 (d) (ii)) DANGEROUS
Rear Registration plate deteriorated but not likely to be misread (0.1 (b))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Headlamp aim too far to the right (4.1.2 (a))
Nearside Headlamp aim too low (4.1.2 (a))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
How Reliable is the Peugeot 208?
Based on 1,882,992 MOT tests across 192,984 vehicles.
Don't risk it. Know before you buy.
Not all vehicle check providers are the same. Some don't offer a data guarantee, which means if their information is wrong, you're on your own. Every CarVerify report is backed by a £30,000 finance data guarantee.
FJ67 TKZ is a 2017 Peugeot 208 in White with a 1,200cc petrol engine. This vehicle has been through 9 MOT tests with a personal pass rate of 77.8%.
Across all 2017 Peugeot 208 models, the average MOT pass rate is 83.4% with a typical mileage of 36,111 miles. This particular vehicle has a lower pass rate than the average for its year, which may indicate maintenance issues worth investigating.
The Peugeot 208 typically stays on UK roads for around 14 years. At 9 years old, this Peugeot 208 is well into its expected lifespan but still has years ahead.
Frequently Asked Questions
How do I check the history of FJ67 TKZ?
You can check the full history of FJ67 TKZ by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was FJ67 TKZ registered?
FJ67 TKZ is a 2017 Peugeot 208, first registered on 24 September 2017.
Is FJ67 TKZ safe to buy?
The MOT history for FJ67 TKZ shows 9 tests with a 77.8% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does FJ67 TKZ have outstanding finance?
Finance checks require a premium vehicle report. This checks against all major UK finance providers to see if there is any outstanding finance on FJ67 TKZ. If you buy a car with outstanding finance, the finance company can repossess it.
No warranty or guarantee of accuracy is provided for any free data on this page. The data guarantee applies only to information obtained through the purchase of a full check.