← My Auto Racer All cars BMW 0-60 Comparisons
The BMW M3 E46 reaches 60 mph in 4.66 s and covers a standing quarter mile in 13.35 s, tripping the lights at 107.0 mph. It clears the first 60 ft in 2.14 s and the eighth mile in 8.65 s, reaching 100 mph in 11.82 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 E46 |
|---|---|
| 0–60 mph | 4.66 s |
| 0–100 mph | 11.82 s |
| 60 ft | 2.14 s |
| 1/8 mile | 8.65 s |
| 1/4 mile | 13.35 s |
| Trap speed | 107.0 mph |
The 2000 BMW M3 E46 is a rear-drive naturally aspirated roadster of 1,565 kg with 338 bhp, which works out at 216 bhp per tonne. Rear drive and 216 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.14 s. Against the 2,929 cars in the set it is the 1,197th quickest to 60 mph, and the 111th quickest of the 297 BMWs here. Its 107.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 10 of 10 published acceleration figures for this car.
| Specification | BMW M3 E46 |
|---|---|
| Year | 2000 |
| Power | 338 bhp |
| Kerb mass | 1,565 kg |
| Power to weight | 216 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 280 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Chrysler Crossfire SRT-6 Roadster | 2015 | 4.66 s | 13.26 s | 105.3 mph | 330 bhp |
| Opel Speedster Turbo | 2015 | 4.69 s | 13.31 s | 103.0 mph | 197 bhp |
| K1 Roadster | 2008 | 4.64 s | 13.24 s | 103.8 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-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.