MOT Status
ExpiredMileage
116,867 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 Rear Tyre not fitted in accordance with side wall instructions (4.1.D.1f)
Offside Front suspension has excessive play in a lower suspension ball joint (2.5.B.1a)
Offside rear brake binding (3.7.B.1)
Rear Exhaust has a major leak of exhaust gases on top of rear box (7.1.2)
Nearside Front position lamp(s) not working (1.1.A.3b)
Nearside Rear Brake hose twisted fouling on suspension (3.6.B.4c)
Nearside Registration plate lamp not working (1.1.C.1d)
Nearside Front Anti-roll bar damaged and seriously weakened (2.4.G.1)
Offside Front Front constant velocity joint gaiter damaged to the extent that it no longer prevents the ingress of dirt etc (2.5.C.1a)
Front Brake pad(s) wearing thin (3.5.1g)
Nail in offside front tyre
Offside Front Front constant velocity joint gaiter damaged, but preventing the ingress of dirt (2.5.C.1a)
Parking brake lever has little reserve travel (3.1.6b)
Rear Brake pad(s) wearing thin (3.5.1g)
Nearside Front Tyre has a cut in excess of the requirements deep enough to reach the ply or cords (4.1.D.1a)
Nearside Rear Tyre has a cut in excess of the requirements deep enough to reach the ply or cords (4.1.D.1a)
Offside Front Tyre has a cut in excess of the requirements deep enough to reach the ply or cords (4.1.D.1a)
Parking brake: parking brake efficiency only just met. It would appear that the braking system requires adjustment or repair. (3.7.B.7)
Service brake: service brake efficiency only just met. It would appear that the braking system requires adjustment or repair. (3.7.B.7)
Offside Front Tyre worn close to the legal limit (4.1.E.1)
How Reliable is the Mitsubishi Lancer?
Based on 382,912 MOT tests across 33,260 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.
CP56 MDK is a 2006 Mitsubishi Lancer in Silver with a 1,997cc petrol engine. This vehicle has been through 13 MOT tests with a personal pass rate of 69.2%.
Across all 2006 Mitsubishi Lancer models, the average MOT pass rate is 76.1% with a typical mileage of 59,624 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 Mitsubishi Lancer fails its MOT is tyre tread depth below requirements of 1.6mm, accounting for 9,095 recorded failures. If you're considering buying CP56 MDK, it's worth having these areas checked by a mechanic before committing.
The Mitsubishi Lancer typically stays on UK roads for around 30 years. At 20 years old, this Mitsubishi Lancer is well into its expected lifespan but still has years ahead.
Frequently Asked Questions
How do I check the history of CP56 MDK?
You can check the full history of CP56 MDK by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was CP56 MDK registered?
CP56 MDK is a 2006 Mitsubishi Lancer, first registered on 4 December 2006.
Is CP56 MDK safe to buy?
The MOT history for CP56 MDK shows 13 tests with a 69.2% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does CP56 MDK 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 CP56 MDK. 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.