← My Auto Racer All cars MG 0-60 Comparisons Answers
The MG Montego EFi reaches 60 mph in 9.09 s and covers a standing quarter mile in 16.96 s, tripping the lights at 84.8 mph. It clears the first 60 ft in 2.87 s and the eighth mile in 11.11 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 Montego EFi |
|---|---|
| 0–60 mph | 9.09 s |
| 0–100 mph | — |
| 60 ft | 2.87 s |
| 1/8 mile | 11.11 s |
| 1/4 mile | 16.96 s |
| Trap speed | 84.8 mph |
The 1984 MG Montego EFi is a front-drive naturally aspirated car of 1,215 kg with 117 bhp, which works out at 96 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.87 s — so most of what it has to give arrives once it is already moving. Against the 2,939 cars in the set it is the 2,808th quickest to 60 mph, and the 15th quickest of the 20 MGs here. Its 84.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 7 of 9 published acceleration figures for this car.
| Specification | MG Montego EFi |
|---|---|
| Year | 1984 |
| Power | 117 bhp |
| Kerb mass | 1,215 kg |
| Power to weight | 96 bhp/t |
| Drivetrain | Front drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 187 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Honda CR-Z | 2010 | 9.00 s | 17.03 s | 82.0 mph | 122 bhp |
| Hyundai Veloster 1.6 GDi 140 PS | 2011 | 9.15 s | 17.19 s | 83.2 mph | 138 bhp |
| Opel Kadett GTE | 1983 | 9.19 s | 17.04 s | 85.8 mph | 114 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-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.