← My Auto Racer All cars BMW 0-60 Comparisons Answers

BMW M2 3.0 480 Auto

The BMW M2 3.0 480 Auto reaches 60 mph in 3.54 s (100 km/h in 3.70 s) and covers a standing quarter mile in 11.79 s, tripping the lights at 117.0 mph. It clears the first 60 ft in 1.80 s and the eighth mile in 7.58 s, reaching 100 mph in 8.27 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.

BMW M2 3.0 480 Auto Mercedes-AMG C 63 (W205) S 4.0 V8 510

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start BMW M2 3.0 480 Auto
0–60 mph3.54 s
0–100 km/h3.70 s
0–100 mph8.27 s
60 ft1.80 s
1/8 mile7.58 s
1/4 mile11.79 s
Trap speed117.0 mph

About the M2 3.0 480 Auto

The 2025 BMW M2 3.0 480 Auto is a rear-drive turbocharged saloon of 1,573 kg with 473 bhp, which works out at 301 bhp per tonne. Rear drive and 301 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.80 s. Against the 14,946 cars in the set it is the 681st quickest to 60 mph, inside the fastest five per cent, and the 44th quickest of the 1324 BMWs here. Its 117.0 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 2 of 2 published acceleration figures for this car.

On paper

Specification BMW M2 3.0 480 Auto
Year2025
Power473 hp (353 kW)
Kerb mass1,573 kg
Power to weight301 bhp/t
DrivetrainRear drive
Gears8
EngineTurbocharged
Top speed155 mph (249 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mercedes-AMG C 63 (W205) S 4.0 V8 51020153.54 s11.88 s115.0 mph503 bhp
Nissan GT-R R3520083.44 s11.78 s120.3 mph473 bhp
Jaguar F-Pace SVR P57520233.51 s11.98 s115.2 mph567 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.

Head to head

BMW M140i vs BMW M2 3.0 480 AutoFull comparison

Where these times sit

0-60 under 4 seconds1,060 cars0-100 km/h under 4 seconds881 carsQuarter mile under 12 seconds780 cars0-100 under 9 seconds871 carsTraps over 110 mph1,380 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
BMW 0-60 timesevery modelFastest saloon cars3,808 carsFastest cars of the 2020s867 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the BMW M2 3.0 480 Auto 0-60 time?
The BMW M2 3.0 480 Auto reaches 60 mph in 3.54 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 681st quickest of the 14,946 cars in the set.
What is the BMW M2 3.0 480 Auto quarter mile time?
11.79 s at 117.0 mph. It reaches the eighth mile in 7.58 s and clears the first 60 ft in 1.80 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the BMW M2 3.0 480 Auto have?
473 bhp and 1,573 kg, which is 301 bhp per tonne. It is rear-drive, turbocharged, with 8 gears and a quoted top speed of 249 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the BMW M2 3.0 480 Auto?
Closest here on pace: Mercedes-AMG C 63 (W205) S 4.0 V8 510 (3.54 s), Nissan GT-R R35 (3.44 s), Jaguar F-Pace SVR P575 (3.51 s). Each one can be raced against the BMW M2 3.0 480 Auto in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The BMW M2 3.0 480 Auto is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

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.