2000 Cagiva Mito 0.1L Petrol · W789 WTU
2000 Cagiva Mito (0.1L, petrol). First registered 01/04/2000. Recorded mileage 7,396 miles. MOT status: Expired.
- Make & Model
- CAGIVA MITO
- Year / Origin
- 2000 · Exeter
- Safety Recall
- Unknown
- MOT Status
- Valid until 18/06/2021
- Road Tax
- Untaxed (01/07/2021)
- Recorded Mileage
- 7,396 mi
- ULEZ Compliance
- Check Required (Pre-Euro 4 Petrol)
- Fuel & Engine
- PETROL · 0.1L
- Reliability Guide
- Common Faults
- Fuel Type
- PETROL
- Year
- 2000
- Engine
- 124cc
W789 WTU Key Findings
- 2 MOT tests recorded
- Latest MOT passed on 19/06/2020
- 7,396 miles recorded at latest MOT
- 1 historical MOT failure
- No defects recorded at the latest MOT
Derived directly from the recorded DVSA and DVLA data shown on this page.
MOT Roadworthiness: Below Average
This rating reflects historical MOT pass rates and recurring advisory wear patterns from official DVSA test logs. Note that roadworthiness does not verify outstanding finance, insurance write-offs, or stolen records.
Verify lender finance agreements, insurance write-offs, police stolen registers, and mileage rollback.
Technical Specifications
Core Specifications
Identification & Status
Dimensions & Weights
Diagnostic & Valuation Intelligence
Estimate current market value
Generate an instant valuation benchmark based on live market listings, vehicle mileage, and recent dealer auction figures.
W789 WTU Mileage History
- 19/06/20207,396 mi
- 19/06/20207,396 mi
Average of roughly 0 miles per year across 2 recorded odometer readings.
W789 WTU MOT History
Interpretation generated from the recorded test data above — not an official DVSA statement and not a substitute for an independent inspection.
2 MOT tests are recorded for this 2000 Cagiva Mito (W789 WTU) between June 2020 and June 2020.
The record contains 1 pass and 1 failure.
The most recent test on 19 June 2020 was a pass, although the earlier record includes 1 failure that buyers may want to investigate.
Recorded failure items include: “Offside Front Direction indicator not working (4.4.1 (a) (ii))”.