← My Auto Racer All cars MG 0-60 Comparisons Answers
The MG ZT 260 reaches 60 mph in 6.33 s (100 km/h in 6.69 s) and covers a standing quarter mile in 14.80 s, tripping the lights at 95.9 mph. It clears the first 60 ft in 2.45 s and the eighth mile in 9.60 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 ZT 260 |
|---|---|
| 0–60 mph | 6.33 s |
| 0–100 km/h | 6.69 s |
| 0–100 mph | — |
| 60 ft | 2.45 s |
| 1/8 mile | 9.60 s |
| 1/4 mile | 14.80 s |
| Trap speed | 95.9 mph |
The 2005 MG ZT 260 is a rear-drive naturally aspirated saloon of 1,774 kg with 256 bhp, which works out at 144 bhp per tonne. Rear drive and 144 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.45 s. Against the 14,946 cars in the set it is the 3,652nd quickest to 60 mph, inside the fastest quarter, and the 9th quickest of the 61 MGs here. Its 95.9 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 9 of 10 published acceleration figures for this car.
| Specification | MG ZT 260 |
|---|---|
| Year | 2005 |
| Power | 256 hp (191 kW) |
| Kerb mass | 1,774 kg |
| Power to weight | 144 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 155 mph (250 km/h), quoted |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Rover 600 620ti 2.0 Turbo | 1994 | 6.32 s | 14.88 s | 96.0 mph | 197 bhp |
| Cadillac CTS 3.6 V6 253 | 2002 | 6.34 s | 14.90 s | 96.6 mph | 253 bhp |
| Lexus IS 2.0 241 | 2020 | 6.41 s | 14.85 s | 95.0 mph | 237 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.