MOT Status
ExpiredMileage
97,609 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
Oil leak, but not excessive (8.4.1 (a) (i))
Horn not working (7.7 (a) (ii))
Nearside Rear Tyre has a tear, caused by separation or partial failure of its structure (5.2.3 (d) (ii)) DANGEROUS
Nearside Rear Tyre tread depth below requirements of 1.6mm (5.2.3 (e)) DANGEROUS
Offside Rear Tyre has a tear, caused by separation or partial failure of its structure (5.2.3 (d) (ii)) DANGEROUS
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 worn close to legal limit/worn on edge (5.2.3 (e))
Oil leak, but not excessive (8.4.1 (a) (i))
Nearside Front Suspension arm ball joint has slight play (5.3.4 (a) (i))
Nearside Front Track rod end ball joint dust cover damaged or deteriorated, but preventing the ingress of dirt (2.1.3 (g) (i))
Nearside Front Track rod end ball joint has slight play (2.1.3 (b) (i))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Front Suspension arm ball joint has slight play (5.3.4 (a) (i))
Offside Front Track rod end ball joint dust cover damaged or deteriorated, but preventing the ingress of dirt (2.1.3 (g) (i))
Offside Front Track rod end ball joint has slight play (2.1.3 (b) (i))
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))
Nearside Windscreen wiper does not clear the windscreen effectively (8.2.2)
Offside Windscreen wiper does not clear the windscreen effectively (8.2.2)
Offside Front Suspension arm has slight play in a ball joint (2.4.G.2)
Offside Front Track rod end ball joint has slight play (2.2.B.1f)
Front brake disc worn, pitted or scored, but not seriously weakened (3.5.1i)
Offside Front Track rod end ball joint has slight play (2.2.B.1f)
Offside Rear Registration plate lamp not working (1.1.C.1d)
Front brake disc worn, pitted or scored, but not seriously weakened (3.5.1i)
Offside Front Track rod end ball joint has slight play (2.2.B.1f)
Engine covers fitted obscuring some components in the engine bay
Front brake disc worn, pitted or scored, but not seriously weakened (3.5.1i)
Rear registration plate deteriorated but not likely to be misread (6.3.1d)
Under-trays fitted obscuring some underside components
fuel cap o ring starting to perish
Nearside Front Track rod end ball joint dust cover excessively deteriorated so that it no longer prevents the ingress of dirt (2.2.C.1c)
Offside Front Suspension arm ball joint dust cover excessively deteriorated so that it no longer prevents the ingress of dirt (2.4.G.2)
Offside Front Track rod end ball joint dust cover excessively deteriorated so that it no longer prevents the ingress of dirt (2.2.C.1c)
Engine covers fitted obscuring some components in the engine bay
Front brake disc worn, pitted or scored, but not seriously weakened (3.5.1i)
Rear registration plate deteriorated but not likely to be misread (6.3.1d)
Under-trays fitted obscuring some underside components
fuel cap o ring starting to perish
Under-trays fitted obscuring some underside components
Offside Headlamp not working on dipped beam (1.7.5a)
Under-trays fitted obscuring some underside components
Front Windscreen wiper does not clear the windscreen effectively (8.2.2)
Nearside Rear Tyre worn close to the legal limit (4.1.E.1)
Offside Front Headlamp not working on dipped beam (1.7.5a)
Offside Rear Registration plate lamp not working (1.1.C.1d)
Offside Rear Tyre worn close to the legal limit (4.1.E.1)
both front tyres perished and cracked
Nearside Rear Tyre worn close to the legal limit (4.1.E.1)
Offside Rear Tyre worn close to the legal limit (4.1.E.1)
both front tyres perished and cracked
Nearside Front Anti-roll bar linkage has slight play in a ball joint (2.4.G.2)
Offside Front Anti-roll bar linkage has slight play in a ball joint (2.4.G.2)
Registration plate lamp not working (1.1.C.1d)
Nearside Front Anti-roll bar linkage has slight play in a ball joint (2.4.G.2)
Offside Front Anti-roll bar linkage has slight play in a ball joint (2.4.G.2)
Nearside Front Brake pad(s) wearing thin (3.5.1g)
Offside Front Brake pad(s) wearing thin (3.5.1g)
Offside Front Headlamp not in good working order but not adversely affecting beam image (1.2.4a)
Nail in nearside rear tyre
How Reliable is the Smart (mcc) Roadster?
Based on 33,271 MOT tests across 2,102 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.
RX53 JDK is a 2003 Smart (mcc) Roadster in Silver with a 698cc petrol engine. This vehicle has been through 22 MOT tests with a personal pass rate of 68.2%.
Across all 2003 Smart (mcc) Roadster models, the average MOT pass rate is 73.7% with a typical mileage of 56,714 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 Smart (mcc) Roadster fails its MOT is registration plate lamp not working, accounting for 713 recorded failures. If you're considering buying RX53 JDK, it's worth having these areas checked by a mechanic before committing.
The Smart (mcc) Roadster typically stays on UK roads for around 23 years. At 23 years old, this Smart (mcc) Roadster is approaching the upper end of the typical lifespan for this model.
Frequently Asked Questions
How do I check the history of RX53 JDK?
You can check the full history of RX53 JDK by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was RX53 JDK registered?
RX53 JDK is a 2003 Smart (mcc) Roadster, first registered on 5 September 2003.
Is RX53 JDK safe to buy?
The MOT history for RX53 JDK shows 22 tests with a 68.2% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does RX53 JDK 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 RX53 JDK. 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.