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

BMW 3 Series (F30) 328d 184

The BMW 3 Series (F30) 328d 184 reaches 60 mph in 6.86 s (100 km/h in 7.26 s) and covers a standing quarter mile in 15.26 s, tripping the lights at 91.5 mph. It clears the first 60 ft in 2.35 s and the eighth mile in 9.83 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 3 Series (F30) 328d 184 Mercedes-Benz S-Class S300 BlueTEC Hybrid Long 231

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 3 Series (F30) 328d 184
0–60 mph6.86 s
0–100 km/h7.26 s
0–100 mph—
60 ft2.35 s
1/8 mile9.83 s
1/4 mile15.26 s
Trap speed91.5 mph

About the 3 Series (F30) 328d 184

The 2012 BMW 3 Series (F30) 328d 184 is a rear-drive turbodiesel saloon of 1,505 kg with 181 bhp, which works out at 120 bhp per tonne. Rear drive and 120 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.35 s. Against the 14,946 cars in the set it is the 4,421st quickest to 60 mph, and the 637th quickest of the 1324 BMWs here. Its 91.5 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 3 Series (F30) 328d 184
Year2012
Power181 hp (135 kW)
Kerb mass1,505 kg
Power to weight120 bhp/t
DrivetrainRear drive
Gears8
EngineTurbodiesel
Top speed143 mph (230 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mercedes-Benz S-Class S300 BlueTEC Hybrid Long 23120136.86 s15.22 s92.0 mph228 bhp
Chrysler 300C 3.0 V6 CRD 21520046.83 s15.37 s90.6 mph215 bhp
Mercedes-Benz G-Class 5-door 500 V8 29620076.77 s15.30 s90.4 mph292 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.

Where these times sit

0-60 under 7 seconds4,651 cars0-100 km/h under 8 seconds5,602 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 2010s4,541 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 3 Series (F30) 328d 184 0-60 time?
The BMW 3 Series (F30) 328d 184 reaches 60 mph in 6.86 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,421st quickest of the 14,946 cars in the set.
What is the BMW 3 Series (F30) 328d 184 quarter mile time?
15.26 s at 91.5 mph. It reaches the eighth mile in 9.83 s and clears the first 60 ft in 2.35 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the BMW 3 Series (F30) 328d 184 have?
181 bhp and 1,505 kg, which is 120 bhp per tonne. It is rear-drive, turbodiesel, with 8 gears and a quoted top speed of 230 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the BMW 3 Series (F30) 328d 184?
Closest here on pace: Mercedes-Benz S-Class S300 BlueTEC Hybrid Long 231 (6.86 s), Chrysler 300C 3.0 V6 CRD 215 (6.83 s), Mercedes-Benz G-Class 5-door 500 V8 296 (6.77 s). Each one can be raced against the BMW 3 Series (F30) 328d 184 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 3 Series (F30) 328d 184 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.