← My Auto Racer All cars BMW 0-60 Comparisons
The BMW M3 Competition G80 reaches 60 mph in 3.38 s and covers a standing quarter mile in 11.52 s, tripping the lights at 122.6 mph. It clears the first 60 ft in 1.88 s and the eighth mile in 7.50 s, reaching 100 mph in 7.64 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 | BMW M3 Competition G80 |
|---|---|
| 0–60 mph | 3.38 s |
| 0–100 mph | 7.64 s |
| 60 ft | 1.88 s |
| 1/8 mile | 7.50 s |
| 1/4 mile | 11.52 s |
| Trap speed | 122.6 mph |
The 2021 BMW M3 Competition G80 is a rear-drive turbocharged saloon of 1,765 kg with 503 bhp, which works out at 285 bhp per tonne. Rear drive and 285 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.88 s. Against the 2,929 cars in the set it is the 426th quickest to 60 mph, inside the fastest quarter, and the 23rd quickest of the 297 BMWs here. Its 122.6 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 8 published acceleration figures for this car.
| Specification | BMW M3 Competition G80 |
|---|---|
| Year | 2021 |
| Power | 503 bhp |
| Kerb mass | 1,765 kg |
| Power to weight | 285 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 293 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Audi RS6 C7 | 2012 | 3.40 s | 11.69 s | 121.9 mph | 553 bhp |
| Audi RS7 Sportback | 2013 | 3.24 s | 11.51 s | 123.3 mph | 553 bhp |
| Zeekr 7X Performance AWD | 2025 | 3.39 s | 11.63 s | 121.4 mph | 630 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.