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

BMW 5 Series 520d 177

The BMW 5 Series 520d 177 reaches 60 mph in 7.50 s (100 km/h in 7.94 s) and covers a standing quarter mile in 15.90 s, tripping the lights at 89.1 mph. It clears the first 60 ft in 2.61 s and the eighth mile in 10.30 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 5 Series 520d 177 Peugeot 408 1.6 THP 163

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 5 Series 520d 177
0–60 mph7.50 s
0–100 km/h7.94 s
0–100 mph—
60 ft2.61 s
1/8 mile10.30 s
1/4 mile15.90 s
Trap speed89.1 mph

About the 5 Series 520d 177

The 2007 BMW 5 Series 520d 177 is a rear-drive turbodiesel saloon of 1,485 kg with 174 bhp, which works out at 117 bhp per tonne. Rear drive and 117 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.61 s. Against the 14,946 cars in the set it is the 5,561st quickest to 60 mph, and the 837th quickest of the 1324 BMWs here. Its 89.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 2 of 2 published acceleration figures for this car.

On paper

Specification BMW 5 Series 520d 177
Year2007
Power174 hp (130 kW)
Kerb mass1,485 kg
Power to weight117 bhp/t
DrivetrainRear drive
Gears5
EngineTurbodiesel
Top speed144 mph (232 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Peugeot 408 1.6 THP 16320107.51 s15.88 s87.8 mph165 bhp
Opel Astra GTC 1.6 Turbo 18020117.52 s15.83 s89.2 mph177 bhp
Lexus ES 300h eCVT 20020167.51 s15.95 s84.0 mph200 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

Skoda Superb 2.0 115 (2006) vs BMW 5 Series 520d 177Full comparisonMazda 2 1.6 95 vs BMW 5 Series 520d 177Full comparisonSkoda Octavia 1.4 80 vs BMW 5 Series 520d 177Full comparison

Where these times sit

0-60 under 8 seconds6,514 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 2000s5,138 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 5 Series 520d 177 0-60 time?
The BMW 5 Series 520d 177 reaches 60 mph in 7.50 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,561st quickest of the 14,946 cars in the set.
What is the BMW 5 Series 520d 177 quarter mile time?
15.90 s at 89.1 mph. It reaches the eighth mile in 10.30 s and clears the first 60 ft in 2.61 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the BMW 5 Series 520d 177 have?
174 bhp and 1,485 kg, which is 117 bhp per tonne. It is rear-drive, turbodiesel, with 5 gears and a quoted top speed of 232 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the BMW 5 Series 520d 177?
Closest here on pace: Peugeot 408 1.6 THP 163 (7.51 s), Opel Astra GTC 1.6 Turbo 180 (7.52 s), Lexus ES 300h eCVT 200 (7.51 s). Each one can be raced against the BMW 5 Series 520d 177 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 5 Series 520d 177 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.