MOT Status
ValidMileage
111,588 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 Play in steering rack inner joint(s) ()
Offside Front Play in steering rack inner joint(s) ()
Brake lever has insufficient reserve travel (1.1.2 (a))
Parking brake efficiency below requirements (1.4.2 (a) (i))
Nearside Front Play in steering rack inner joint(s) ()
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Front Play in steering rack inner joint(s) ()
Offside Rear Registration plate lamp inoperative in the case of multiple lamps or light sources (4.7.1 (b) (i))
Front Track rod end ball joint has slight play BOTH SIDE (2.1.3 (b) (i))
Nearside Front Tyre has a cut but not deep enough to reach the ply or cords (5.2.3 (d) (i))
Nearside Front Track rod end ball joint has slight play (2.1.3 (b) (i))
Nearside Front Tyre has a cut but not deep enough to reach the ply or cords (5.2.3 (d) (i))
Offside Front Track rod end ball joint has slight play (2.1.3 (b) (i))
Front Outer Tyre worn close to legal limit/worn on edge Both (5.2.3 (e))
Offside Front Drag link end ball joint has slight play (2.1.3 (b) (i))
Offside Front Outer Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Rear Brake disc worn, pitted or scored, but not seriously weakened (1.1.14 (a) (ii))
Play in steering rack inner joint(s) ()
Rear Registration plate deteriorated but not likely to be misread (0.1 (b))
both rear tyres ae going out of shape on the inside edge
Slight brake bind on both rear brakes
Front Brake pad(s) less than 1.5 mm thick (3.5.1g)
Front Windscreen wiper does not clear the windscreen effectively (8.2.2)
Nearside Rear Tyre tread depth below requirements of 1.6mm (4.1.E.1)
Offside Rear Tyre tread depth below requirements of 1.6mm (4.1.E.1)
How Reliable is the Lexus Ct?
Based on 304,916 MOT tests across 32,361 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.
BV12 DVP is a 2012 Lexus Ct in Grey with a 1,798cc other engine. This vehicle has been through 15 MOT tests with a personal pass rate of 86.7%.
Across all 2012 Lexus Ct models, the average MOT pass rate is 84.7% with a typical mileage of 68,054 miles. This particular vehicle has performed better than the average for its year.
The most common reason a Lexus Ct fails its MOT is tyre tread depth below requirements of 1.6mm, accounting for 1,016 recorded failures. If you're considering buying BV12 DVP, it's worth having these areas checked by a mechanic before committing.
The Lexus Ct typically stays on UK roads for around 15 years. At 14 years old, this Lexus Ct is approaching the upper end of the typical lifespan for this model.
Frequently Asked Questions
How do I check the history of BV12 DVP?
You can check the full history of BV12 DVP by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was BV12 DVP registered?
BV12 DVP is a 2012 Lexus Ct, first registered on 26 March 2012.
Is BV12 DVP safe to buy?
The MOT history for BV12 DVP shows 15 tests with a 86.7% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does BV12 DVP 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 BV12 DVP. 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.