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

Peugeot 407 Coupe 2.0 HDiF 136

The Peugeot 407 Coupe 2.0 HDiF 136 reaches 60 mph in 9.11 s (100 km/h in 9.70 s) and covers a standing quarter mile in 16.99 s, tripping the lights at 82.1 mph. It clears the first 60 ft in 2.58 s and the eighth mile in 10.92 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.

Peugeot 407 Coupe 2.0 HDiF 136 Honda Civic Coupe 1.6i CVT 105

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 Peugeot 407 Coupe 2.0 HDiF 136
0–60 mph9.11 s
0–100 km/h9.70 s
0–100 mph—
60 ft2.58 s
1/8 mile10.92 s
1/4 mile16.99 s
Trap speed82.1 mph

About the 407 Coupe 2.0 HDiF 136

The 2005 Peugeot 407 Coupe 2.0 HDiF 136 is a front-drive turbodiesel coupe of 1,550 kg with 134 bhp, which works out at 87 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.58 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 8,633rd quickest to 60 mph, and the 132nd quickest of the 456 Peugeots here. Its 82.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 Peugeot 407 Coupe 2.0 HDiF 136
Year2005
Power134 hp (100 kW)
Kerb mass1,550 kg
Power to weight87 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed129 mph (207 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Honda Civic Coupe 1.6i CVT 10519969.07 s16.98 s80.5 mph103 bhp
Citroen C4 Coupe 1.6 16V 12020089.11 s16.94 s83.3 mph118 bhp
Chrysler Sebring Coupe 2.4 14120019.11 s16.97 s82.9 mph139 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 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Peugeot 0-60 timesevery modelFastest coupes911 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 Peugeot 407 Coupe 2.0 HDiF 136 0-60 time?
The Peugeot 407 Coupe 2.0 HDiF 136 reaches 60 mph in 9.11 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,633rd quickest of the 14,946 cars in the set.
What is the Peugeot 407 Coupe 2.0 HDiF 136 quarter mile time?
16.99 s at 82.1 mph. It reaches the eighth mile in 10.92 s and clears the first 60 ft in 2.58 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 407 Coupe 2.0 HDiF 136 have?
134 bhp and 1,550 kg, which is 87 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 207 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 407 Coupe 2.0 HDiF 136?
Closest here on pace: Honda Civic Coupe 1.6i CVT 105 (9.07 s), Citroen C4 Coupe 1.6 16V 120 (9.11 s), Chrysler Sebring Coupe 2.4 141 (9.11 s). Each one can be raced against the Peugeot 407 Coupe 2.0 HDiF 136 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 Peugeot 407 Coupe 2.0 HDiF 136 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.