← My Auto Racer All cars MG 0-60 Comparisons Answers
The MG TF 1.6 (116 hp) reaches 60 mph in 8.93 s and covers a standing quarter mile in 16.84 s, tripping the lights at 83.7 mph. It clears the first 60 ft in 2.82 s and the eighth mile in 10.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 TF 1.6 (116 hp) |
|---|---|
| 0–60 mph | 8.93 s |
| 0–100 mph | — |
| 60 ft | 2.82 s |
| 1/8 mile | 10.94 s |
| 1/4 mile | 16.84 s |
| Trap speed | 83.7 mph |
The 2002 MG TF 1.6 (116 hp) is a rear-drive naturally aspirated roadster of 1,095 kg with 114 bhp, which works out at 104 bhp per tonne. Rear drive and 104 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.82 s. Against the 2,939 cars in the set it is the 2,794th quickest to 60 mph, and the 14th quickest of the 20 MGs here. Its 83.7 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 1 of 1 published acceleration figures for this car.
| Specification | MG TF 1.6 (116 hp) |
|---|---|
| Year | 2002 |
| Power | 114 bhp |
| Kerb mass | 1,095 kg |
| Power to weight | 104 bhp/t |
| Drivetrain | Rear drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 190 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Nissan Bluebird 1.8 ZX Turbo Pre-Facelift T12 | 1986 | 8.94 s | 16.80 s | 86.5 mph | 133 bhp |
| BYD Seal 6 DM-i Touring Boost | 2025 | 8.84 s | 16.77 s | 83.1 mph | 181 bhp |
| Subaru XT Turbo | 1985 | 8.97 s | 16.83 s | 84.1 mph | 134 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.