← My Auto Racer All cars BMW 0-60 Comparisons Answers
The BMW 320d (F30) reaches 60 mph in 6.81 s and covers a standing quarter mile in 15.13 s, tripping the lights at 95.2 mph. It clears the first 60 ft in 2.43 s and the eighth mile in 9.89 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 320d (F30) |
|---|---|
| 0–60 mph | 6.81 s |
| 0–100 mph | — |
| 60 ft | 2.43 s |
| 1/8 mile | 9.89 s |
| 1/4 mile | 15.13 s |
| Trap speed | 95.2 mph |
The 2012 BMW 320d (F30) is a rear-drive turbodiesel saloon of 1,420 kg with 181 bhp, which works out at 127 bhp per tonne. Rear drive and 127 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.43 s. Against the 2,939 cars in the set it is the 2,319th quickest to 60 mph, and the 247th quickest of the 297 BMWs here. It traps higher than its 0-60 suggests — 95.2 mph, the 2,122nd highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.
| Specification | BMW 320d (F30) |
|---|---|
| Year | 2012 |
| Power | 181 bhp |
| Kerb mass | 1,420 kg |
| Power to weight | 127 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbodiesel |
| Top speed | 235 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Mercedes-Benz C 220 d (W205) | 2014 | 6.68 s | 15.10 s | 93.0 mph | 168 bhp |
| BMW 520d (G30) | 2017 | 6.77 s | 15.15 s | 92.3 mph | 188 bhp |
| Mercedes-Benz S 300 BlueTEC HYBRID | 2013 | 6.97 s | 15.38 s | 89.9 mph | 228 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-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.