← My Auto Racer All cars BMW 0-60 Comparisons
The BMW M4 G82 reaches 60 mph in 3.82 s and covers a standing quarter mile in 12.08 s, tripping the lights at 118.1 mph. It clears the first 60 ft in 1.99 s and the eighth mile in 7.89 s, reaching 100 mph in 8.70 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 M4 G82 |
|---|---|
| 0–60 mph | 3.82 s |
| 0–100 mph | 8.70 s |
| 60 ft | 1.99 s |
| 1/8 mile | 7.89 s |
| 1/4 mile | 12.08 s |
| Trap speed | 118.1 mph |
The 2020 BMW M4 G82 is a rear-drive turbocharged coupe of 1,775 kg with 473 bhp, which works out at 267 bhp per tonne. Rear drive and 267 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.99 s. Against the 2,929 cars in the set it is the 691st quickest to 60 mph, inside the fastest quarter, and the 55th quickest of the 297 BMWs here. Its 118.1 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 | BMW M4 G82 |
|---|---|
| Year | 2020 |
| Power | 473 bhp |
| Kerb mass | 1,775 kg |
| Power to weight | 267 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 290 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Cadillac ATS-V Coupe | 2016 | 3.66 s | 12.07 s | 115.7 mph | 464 bhp |
| Toyota Supra Final Edition A90 | 2024 | 3.65 s | 11.97 s | 117.5 mph | 429 bhp |
| Aston Martin Vantage AMR Mk II | 2019 | 3.86 s | 12.07 s | 118.7 mph | 503 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.