MOT Status
ValidMileage
60,984 miAbove 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
Stop lamp(s) all not working (4.3.1 (a) (iii)) DANGEROUS
Nearside Front Tyre has ply or cords exposed (5.2.3 (d) (ii)) DANGEROUS
Offside Front Suspension component ball joint dust cover severely deteriorated (5.3.4 (b) (i))
Rear Windscreen wiper blade defective (3.4 (b) (i))
Front Windscreen wiper does not clear the windscreen effectively Both wipers (3.4 (b) (ii))
Nearside Front Lower Suspension component ball joint dust cover no longer prevents the ingress of dirt Dust cover split (5.3.4 (b) (ii))
Nearside Front Macpherson strut top bush or bearing has excessive wear or free play Excess play (5.3.4 (a) (i))
Nearside Rear Stop lamp(s) not working (4.3.1 (a) (ii))
Offside Front Macpherson strut top bush or bearing has excessive wear or free play Excess play (5.3.4 (a) (i))
Offside Front Suspension component ball joint dust cover severely deteriorated (5.3.4 (b) (i))
Rear Windscreen wiper blade defective (3.4 (b) (i))
Nearside Front Lower Suspension arm ball joint dust cover severely deteriorated (5.3.4 (b) (i))
Nearside Front Windscreen wiper blade defective (3.4 (b) (i))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Front Windscreen wiper blade defective (3.4 (b) (i))
Offside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Rear Tyre slightly damaged/cracking or perishing badly perished (5.2.3 (d) (ii))
Offside Rear Tyre slightly damaged/cracking or perishing badly perished (5.2.3 (d) (ii))
Offside Stop lamp(s) not working (4.3.1 (a) (ii))
Nearside Front Tyre has ply or cords exposed (5.2.3 (d) (ii)) DANGEROUS
Offside Front Tyre has ply or cords exposed (5.2.3 (d) (ii)) DANGEROUS
Nearside Rear Tyre slightly damaged/cracking or perishing badly perished (5.2.3 (d) (ii))
Offside Rear Tyre slightly damaged/cracking or perishing badly perished (5.2.3 (d) (ii))
Nearside Front Tyre slightly damaged/cracking or perishing perishing (5.2.3 (d) (ii))
Nearside Rear Coil spring corroded (5.3.1 (b) (i))
Nearside Rear Tyre slightly damaged/cracking or perishing perishing (5.2.3 (d) (ii))
Offside Front Tyre slightly damaged/cracking or perishing perishing (5.2.3 (d) (ii))
Offside Rear Coil spring corroded (5.3.1 (b) (i))
Offside Rear Tyre slightly damaged/cracking or perishing perishing (5.2.3 (d) (ii))
Nearside Rear Coil spring corroded (5.3.1 (b) (i))
Offside Rear Coil spring corroded (5.3.1 (b) (i))
Nearside Rear Shock absorber has slight corrosion to the casing (2.7.2a)
Nearside Rear Braking system leaking around calipers (3.6.A.1)
Nearside Rear Shock absorber has slight corrosion to the casing (2.7.2a)
battery insecure
cracked rear number plate
front wiper blades in poor condition
Nearside Registration plate lamp not working (1.1.C.1d)
battery insecure
cracked rear number plate
front wiper blades in poor condition
front disc slightly scored
Offside Registration plate lamp not working (1.1.C.1d)
front disc slightly scored
Nail in nearside rear tyre
Nearside Headlamp damaged but light output not reduced (1.7.5a)
Nearside Rear Tyre worn close to the legal limit (4.1.E.1)
Offside Headlamp damaged but light output not reduced (1.7.5a)
Rear Brake pad(s) wearing thin (3.5.1g)
Nail in nearside rear tyre
Nearside Headlamp aim too low (1.8)
Nearside Headlamp damaged but light output not reduced (1.7.5a)
Nearside Rear Tyre worn close to the legal limit (4.1.E.1)
Offside Headlamp aim too low (1.8)
Offside Headlamp damaged but light output not reduced (1.7.5a)
Rear Brake pad(s) wearing thin (3.5.1g)
Nearside Front Macpherson strut has excessive movement at the upper attachment (2.5.A.1c)
Offside Front Macpherson strut has excessive movement at the upper attachment (2.5.A.1c)
How Reliable is the Hyundai I10?
Based on 2,829,935 MOT tests across 251,032 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.
EO09 MLN is a 2009 Hyundai I10 in Red with a 1,248cc petrol engine. This vehicle has been through 23 MOT tests with a personal pass rate of 60.9%.
Across all 2009 Hyundai I10 models, the average MOT pass rate is 76.7% with a typical mileage of 43,653 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 Hyundai I10 fails its MOT is tyre tread depth below requirements of 1.6mm, accounting for 15,951 recorded failures. If you're considering buying EO09 MLN, it's worth having these areas checked by a mechanic before committing.
The Hyundai I10 typically stays on UK roads for around 18 years. At 17 years old, this Hyundai I10 is approaching the upper end of the typical lifespan for this model.
Frequently Asked Questions
How do I check the history of EO09 MLN?
You can check the full history of EO09 MLN by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was EO09 MLN registered?
EO09 MLN is a 2009 Hyundai I10, first registered on 17 March 2009.
Is EO09 MLN safe to buy?
The MOT history for EO09 MLN shows 23 tests with a 60.9% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does EO09 MLN 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 EO09 MLN. 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.