← My Auto Racer All cars MG 0-60 Comparisons Answers
The MG F 1.8i VVC 145 reaches 60 mph in 6.51 s (100 km/h in 7.34 s) and covers a standing quarter mile in 15.22 s, tripping the lights at 93.8 mph. It clears the first 60 ft in 2.55 s and the eighth mile in 9.94 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 | MG F 1.8i VVC 145 |
|---|---|
| 0–60 mph | 6.51 s |
| 0–100 km/h | 7.34 s |
| 0–100 mph | — |
| 60 ft | 2.55 s |
| 1/8 mile | 9.94 s |
| 1/4 mile | 15.22 s |
| Trap speed | 93.8 mph |
The 1995 MG F 1.8i VVC 145 is a rear-drive naturally aspirated coupe of 1,035 kg with 143 bhp, which works out at 139 bhp per tonne. Rear drive and 139 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.55 s. Against the 14,946 cars in the set it is the 3,908th quickest to 60 mph, and the 11th quickest of the 61 MGs here. Its 93.8 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 2 of 2 published acceleration figures for this car.
| Specification | MG F 1.8i VVC 145 |
|---|---|
| Year | 1995 |
| Power | 143 hp (107 kW) |
| Kerb mass | 1,035 kg |
| Power to weight | 139 bhp/t |
| Drivetrain | Rear drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 130 mph (209 km/h), quoted |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Fiat Coupe 16V Turbo | 1994 | 6.45 s | 15.10 s | 91.1 mph | 188 bhp |
| Mazda 323 GT-R | 1992 | 6.61 s | 15.23 s | 93.1 mph | 182 bhp |
| Honda Civic SI | 2006 | 6.50 s | 14.99 s | 93.8 mph | 194 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-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.