← My Auto Racer All cars Rover 0-60 Comparisons
The Rover Metro GTI reaches 60 mph in 8.43 s and covers a standing quarter mile in 16.50 s, tripping the lights at 85.0 mph. It clears the first 60 ft in 2.71 s and the eighth mile in 10.67 s.
Simulated, not measured — computed from published kerb mass, rated power, gearing and drivetrain, then fitted to this car’s own published acceleration figures. Dry asphalt, 20 °C, sea level, 1 ft rollout.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Rover Metro GTI |
|---|---|
| 0–60 mph | 8.43 s |
| 0–100 mph | — |
| 60 ft | 2.71 s |
| 1/8 mile | 10.67 s |
| 1/4 mile | 16.50 s |
| Trap speed | 85.0 mph |
The 1990 Rover Metro GTI is a front-drive naturally aspirated car of 884 kg with 95 bhp, which works out at 108 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.71 s — so most of what it has to give arrives once it is already moving. Against the 2,929 cars in the set it is the 2,722nd quickest to 60 mph, and the 4th quickest of the 4 Rovers here. Its 85.0 mph trap speed sits about where its 0-60 puts it, so it launches and pulls in roughly equal measure. The simulation is trimmed to 8 of 9 published acceleration figures for this car.
| Specification | Rover Metro GTI |
|---|---|
| Year | 1990 |
| Power | 95 bhp |
| Kerb mass | 884 kg |
| Power to weight | 108 bhp/t |
| Drivetrain | Front drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 185 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Mitsubishi Lancer 2.0 | 2008 | 8.36 s | 16.58 s | 83.6 mph | 152 bhp |
| De Lorean DMC-12 European spec | 1978 | 8.40 s | 16.47 s | 89.1 mph | 168 bhp |
| Isuzu Piazza Turbo | 1985 | 8.57 s | 16.51 s | 86.0 mph | 148 bhp |
Picked for a fair race, not just a matching 0-60: pace, power-to-weight and body shape all count, and at most one is from the same maker.
Figures regenerated 2026-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.