MOT Status
ValidMileage
77,785 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
Front Brake disc worn, but not excessively (1.1.14 (a) (i))
Front Brake disc worn, but not excessively Both sides (1.1.14 (a) (i))
Offside Rear Coil spring fractured or broken (5.3.1 (b) (i))
Front Brake disc worn, but not excessively Both sides (1.1.14 (a) (i))
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))
Front Brake disc worn, but not excessively lipped and worn (1.1.14 (a) (i))
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 (5.2.3 (d) (ii))
Rear Brake pad(s) wearing thin 3mm (1.1.13 (a) (ii))
Nearside Rear Coil spring fractured or broken (5.3.1 (b) (i))
Front Brake disc worn, but not excessively lipped and worn (1.1.14 (a) (i))
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 (5.2.3 (d) (ii))
Rear Brake pad(s) wearing thin 3mm (1.1.13 (a) (ii))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Rear Tyre has a cut but not deep enough to reach the ply or cords (5.2.3 (d) (i))
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 has a cut in excess of the requirements deep enough to reach the ply or cords (5.2.3 (d) (i))
Front Brake pad(s) wearing thin (1.1.13 (a) (ii))
How Reliable is the Mazda 3?
Based on 2,040,939 MOT tests across 164,053 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.
WG64 CZZ is a 2014 Mazda 3 in Blue with a 1,998cc petrol engine. This vehicle has been through 12 MOT tests with a personal pass rate of 75%.
Across all 2014 Mazda 3 models, the average MOT pass rate is 82.0% with a typical mileage of 52,266 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 Mazda 3 fails its MOT is tyre tread depth below requirements of 1.6mm, accounting for 40,716 recorded failures. If you're considering buying WG64 CZZ, it's worth having these areas checked by a mechanic before committing.
The Mazda 3 typically stays on UK roads for around 22 years. At 12 years old, this Mazda 3 is well into its expected lifespan but still has years ahead.
Frequently Asked Questions
How do I check the history of WG64 CZZ?
You can check the full history of WG64 CZZ by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was WG64 CZZ registered?
WG64 CZZ is a 2014 Mazda 3, first registered on 14 November 2014.
Is WG64 CZZ safe to buy?
The MOT history for WG64 CZZ shows 12 tests with a 75% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does WG64 CZZ 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 WG64 CZZ. 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.