MOT Status
ValidMileage
33,023 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
Front Registration plate deteriorated but not likely to be misread (0.1 (b))
Nearside Front Inner Suspension arm pin or bush worn but not resulting in excessive movement rear (5.3.4 (a) (i))
Offside Front Inner Suspension arm pin or bush worn but not resulting in excessive movement rear (5.3.4 (a) (i))
Offside Front Play in steering rack inner joint(s) also noise detected ()
Rear Brakes imbalanced requirements only just met. It would appear that the braking system requires adjustment or repair. (1.2.1 (b) (i))
Front Registration plate deteriorated but not likely to be misread (0.1 (b))
Nearside Front Suspension arm pin or bush worn but not resulting in excessive movement (5.3.4 (a) (i))
Offside Front Play in steering rack inner joint(s) ()
Offside Front Suspension arm pin or bush worn but not resulting in excessive movement (5.3.4 (a) (i))
Nearside Front Tyre has a bulge, caused by separation or partial failure of its structure (5.2.3 (d) (ii)) DANGEROUS
Nearside Front Suspension arm pin or bush worn but not resulting in excessive movement (5.3.4 (a) (i))
Offside Front Play in steering rack inner joint(s) ()
Offside Front Suspension arm pin or bush worn but not resulting in excessive movement (5.3.4 (a) (i))
Rear Brakes imbalanced across an axle (1.2.1 (b) (i))
Rear Tyre(s) of different sizes are fitted on the same axle. (5.2.3 (b))
Nearside Front Lower Anti-roll bar linkage ball joint excessively worn (5.3.4 (a) (i))
Offside Front Play in steering rack inner joint(s) ()
Nearside Front Brake disc worn, pitted or scored, but not seriously weakened disc and pads wearing (1.1.14 (a) (ii))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Front Headlamp aim too low both (4.1.2 (a))
Nearside Front Brake disc worn, pitted or scored, but not seriously weakened disc and pads wearing (1.1.14 (a) (ii))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
How Reliable is the Seat Mii?
Based on 178,602 MOT tests across 18,080 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.
CA62 FXT is a 2013 Seat Mii in Red with a 999cc petrol engine. This vehicle has been through 15 MOT tests with a personal pass rate of 73.3%.
Across all 2013 Seat Mii models, the average MOT pass rate is 81.5% with a typical mileage of 43,697 miles. This particular vehicle has a lower pass rate than the average for its year, which may indicate maintenance issues worth investigating.
The Seat Mii typically stays on UK roads for around 14 years. At 13 years old, this Seat Mii is approaching the upper end of the typical lifespan for this model.
Frequently Asked Questions
How do I check the history of CA62 FXT?
You can check the full history of CA62 FXT by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was CA62 FXT registered?
CA62 FXT is a 2013 Seat Mii, first registered on 31 January 2013.
Is CA62 FXT safe to buy?
The MOT history for CA62 FXT shows 15 tests with a 73.3% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does CA62 FXT 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 CA62 FXT. 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.