MOT Status
ValidMileage
43,428 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
Offside Front Driver's seat fore and aft adjustment mechanism not functioning as intended. (6.2.5 (b) (i))
Offside Front Seat belt not functioning as intended Not Returning Completely (7.1.2 (c))
Nearside Front Lower Suspension arm pin or bush worn but not resulting in excessive movement (5.3.4 (a) (i))
Offside Front Lower Suspension arm pin or bush worn but not resulting in excessive movement (5.3.4 (a) (i))
Nearside Rear Service brake excessively binding (1.2.1 (f))
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 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 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 Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Windscreen wiper does not clear the windscreen effectively (3.4 (b) (ii))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Offside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Fuel cap/sealing device component leaking (6.1.3 (b) (i))
Nearside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Nearside Windscreen wiper does not clear the windscreen effectively (3.4 (b) (ii))
Offside Rear Tyre slightly damaged/cracking or perishing (5.2.3 (d) (ii))
Front Brake pads getting low
Nearside Front Tyre worn close to the legal limit (4.1.E.1)
Nearside Rear tyre cracking in the tread
Offside Front Tyre worn close to the legal limit also slightly worn on the inner edge (4.1.E.1)
Offside Rear tyre cracking in the tread
fuel cap sealing ring starting to crack
How Reliable is the Skoda Citigo?
Based on 492,537 MOT tests across 53,626 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.
WJ63 HCX is a 2013 Skoda Citigo in Red with a 999cc petrol engine. This vehicle has been through 14 MOT tests with a personal pass rate of 71.4%.
Across all 2013 Skoda Citigo models, the average MOT pass rate is 84.4% with a typical mileage of 41,729 miles. This particular vehicle has a lower pass rate than the average for its year, which may indicate maintenance issues worth investigating.
The Skoda Citigo typically stays on UK roads for around 14 years. At 13 years old, this Skoda Citigo is approaching the upper end of the typical lifespan for this model.
Frequently Asked Questions
How do I check the history of WJ63 HCX?
You can check the full history of WJ63 HCX by running a full vehicle check. This shows you finance, stolen, write-off, MOT history, mileage records and more.
What year was WJ63 HCX registered?
WJ63 HCX is a 2013 Skoda Citigo, first registered on 19 September 2013.
Is WJ63 HCX safe to buy?
The MOT history for WJ63 HCX shows 14 tests with a 71.4% pass rate. To check for outstanding finance, stolen markers, write-off history and mileage discrepancies, run a full vehicle check.
Does WJ63 HCX 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 WJ63 HCX. 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.