MOT Status
ValidMileage
50,719 miSignificantly above average — investigate
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
Nearside Front Suspension arm ball joint likely to become detached (5.3.4 (a) (ii)) DANGEROUS
Offside Front Tyre has ply or cords exposed (5.2.3 (d) (ii)) DANGEROUS
Offside Rear Tyre tread depth below requirements of 1.6mm (5.2.3 (e)) DANGEROUS
Fluid leak, but not excessive coolant (8.4.1 (a) (i))
Front Brake disc worn, pitted or scored, but not seriously weakened both sides (1.1.14 (a) (ii))
Nearside Front 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 heavily perished (5.2.3 (d) (ii))
under tray fitted to most of underside of vehicle
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Rear Nail in tyre ()
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))
under tray fitted to vehicle
Nearside Windscreen wiper does not clear the windscreen effectively (3.4 (b) (ii))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Headlamp aim too low (4.1.2 (a))
Nearside Rear Nail in tyre ()
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))
Offside Windscreen wiper blade defective (3.4 (b) (i))
under tray fitted to vehicle
How Reliable is the Smart (mcc) Forfour?
Based on 256,394 MOT tests across 26,709 vehicles.
Top MOT Failure Points
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.
BL17 CLZ is a 2017 Smart (mcc) Forfour in White with a 999cc petrol engine. This vehicle has been through 9 MOT tests with a personal pass rate of 77.8%.
Across all 2017 Smart (mcc) Forfour models, the average MOT pass rate is 83.6% with a typical mileage of 29,279 miles. This particular vehicle has a lower pass rate than the average for its year, which may indicate maintenance issues worth investigating.
The most common reason a Smart (mcc) Forfour fails its MOT is windscreen wiper does not clear the windscreen effectively, accounting for 2,304 recorded failures. If you're considering buying BL17 CLZ, it's worth having these areas checked by a mechanic before committing.
The Smart (mcc) Forfour typically stays on UK roads for around 22 years. At 9 years old, this Smart (mcc) Forfour is still in the earlier part of its expected life.
Frequently Asked Questions
How do I check the history of BL17 CLZ?
You can check the full history of BL17 CLZ by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was BL17 CLZ registered?
BL17 CLZ is a 2017 Smart (mcc) Forfour, first registered on 4 May 2017.
Is BL17 CLZ safe to buy?
The MOT history for BL17 CLZ 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 BL17 CLZ 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 BL17 CLZ. 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.