MOT Status
ValidMileage
79,980 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
Minor chips & scratches to windscreen.
Offside Front Outer Drive shaft joint constant velocity boot severely deteriorated (6.1.7 (g) (i))
Front Brake disc worn, but not excessively (1.1.14 (a) (i))
Minor stone chips to windscreen
Nearside Rear Seat belt webbing slightly damaged or frayed (7.1.2 (b) (ii))
Front Brake disc worn, but not excessively (1.1.14 (a) (i))
Nearside Rear Seat belt webbing slightly damaged or frayed (7.1.2 (b) (ii))
Rear Brake pad(s) wearing thin (1.1.13 (a) (ii))
Front Brake disc worn, but not excessively (1.1.14 (a) (i))
Nearside Rear Tyre slightly damaged/cracking or perishing SIDEWALL PERISHING. (5.2.3 (d) (ii))
Offside Rear Nail in tyre
Tyre slightly damaged/cracking or perishing Both front & O/S/R tyres perishing. (5.2.3 (d) (ii))
Nearside Front Suspension arm ball joint excessively worn (5.3.4 (a) (i))
Offside Front Suspension arm ball joint excessively worn (5.3.4 (a) (i))
Front Brake disc worn, but not excessively (1.1.14 (a) (i))
Nearside Rear Tyre slightly damaged/cracking or perishing SIDEWALL PERISHING. (5.2.3 (d) (ii))
Offside Rear Nail in tyre
Tyre slightly damaged/cracking or perishing Both front & O/S/R tyres perishing. (5.2.3 (d) (ii))
Nearside Front Tyre has a bulge, caused by separation or partial failure of its structure (5.2.3 (d) (ii)) DANGEROUS
Nearside Front Tyre tread depth below requirements of 1.6mm (5.2.3 (e)) DANGEROUS
Nearside Front Windscreen wiper does not clear the windscreen effectively (3.4 (b) (ii))
Rear Brake pad(s) wearing thin (1.1.13 (a) (ii))
Front Brake pad(s) less than 1.5 mm thick (1.1.13 (a) (ii)) DANGEROUS
Rear Brake pad(s) wearing thin (1.1.13 (a) (ii))
Offside Front constant velocity joint gaiter deteriorated to the extent that it no longer prevents the ingress of dirt etc (2.5.C.1a)
Front brake disc worn, pitted or scored, but not seriously weakened (3.5.1i)
plastic sill covers fitted limiting inspection
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.
RJ12 NTN is a 2012 Nissan Juke in Blue with a 1,598cc petrol engine. This vehicle has been through 15 MOT tests with a personal pass rate of 66.7%.
Across all 2012 Nissan Juke models, the average MOT pass rate is 76.3% with a typical mileage of 61,532 miles. This particular vehicle has a lower pass rate than the average for its year, which may indicate maintenance issues worth investigating.
The Nissan Juke typically stays on UK roads for around 16 years. At 14 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 RJ12 NTN?
You can check the full history of RJ12 NTN by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was RJ12 NTN registered?
RJ12 NTN is a 2012 Nissan Juke, first registered on 31 July 2012.
Is RJ12 NTN safe to buy?
The MOT history for RJ12 NTN shows 15 tests with a 66.7% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does RJ12 NTN 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 RJ12 NTN. 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.