MOT Status
ValidMileage
49,693 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
Rear Brakes imbalanced across an axle Axle 2 (1.2.1 (b) (i))
Nearside Front Brake disc worn, but not excessively (1.1.14 (a) (i))
Nearside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Front brake pads getting low
Nearside Rear Brake disc worn, pitted or scored, but not seriously weakened (1.1.14 (a) (ii))
Offside Front Brake disc worn, but not excessively (1.1.14 (a) (i))
Offside Front Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Front brake pads getting low
Offside Rear Brake disc worn, but not excessively this brake disc is in poor condition only braking on part of disc (1.1.14 (a) (i))
Front Brake disc worn, pitted or scored, but not seriously weakened (1.1.14 (a) (ii))
Front Brake pad(s) wearing thin (1.1.13 (a) (ii))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Front Tyre has a cut in excess of the requirements deep enough to reach the ply or cords (5.2.3 (d) (i))
Offside Front Tyre has a cut in excess of the requirements deep enough to reach the ply or cords (5.2.3 (d) (i))
Rear Brake pad(s) less than 1.5 mm thick (1.1.13 (a) (ii)) DANGEROUS
Front Brake disc worn, pitted or scored, but not seriously weakened (1.1.14 (a) (ii))
Front Brake pad(s) wearing thin (1.1.13 (a) (ii))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
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))
Rear Brake pad(s) wearing thin to limit-suggest replacement (1.1.13 (a) (ii))
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))
Rear Brake pad(s) wearing thin (1.1.13 (a) (ii))
Windscreen washer provides insufficient washer liquid (3.5 (a))
Front Brake pad(s) wearing thin (1.1.13 (a) (ii))
Rear Brake pad(s) wearing thin (1.1.13 (a) (ii))
How Reliable is the Nissan Juke?
Based on 3,002,435 MOT tests across 287,290 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.
BD62 XFU is a 2013 Nissan Juke in White with a 1,598cc petrol engine. This vehicle has been through 14 MOT tests with a personal pass rate of 78.6%.
Across all 2013 Nissan Juke models, the average MOT pass rate is 75.6% with a typical mileage of 56,745 miles. This particular vehicle has performed better than the average for its year.
The Nissan Juke typically stays on UK roads for around 16 years. At 13 years old, this Nissan Juke is approaching the upper end of the typical lifespan for this model.
Frequently Asked Questions
How do I check the history of BD62 XFU?
You can check the full history of BD62 XFU by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was BD62 XFU registered?
BD62 XFU is a 2013 Nissan Juke, first registered on 30 January 2013.
Is BD62 XFU safe to buy?
The MOT history for BD62 XFU shows 14 tests with a 78.6% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does BD62 XFU 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 BD62 XFU. 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.