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

Peugeot 407 SW 2.2 HDi 170

The Peugeot 407 SW 2.2 HDi 170 reaches 60 mph in 8.15 s (100 km/h in 8.63 s) and covers a standing quarter mile in 16.29 s, tripping the lights at 86.4 mph. It clears the first 60 ft in 2.51 s and the eighth mile in 10.50 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 SW 2.2 HDi 170 Vauxhall Vectra Estate 2.2i 155

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 SW 2.2 HDi 170
0–60 mph8.15 s
0–100 km/h8.63 s
0–100 mph—
60 ft2.51 s
1/8 mile10.50 s
1/4 mile16.29 s
Trap speed86.4 mph

About the 407 SW 2.2 HDi 170

The 2004 Peugeot 407 SW 2.2 HDi 170 is a front-drive turbodiesel estate of 1,580 kg with 168 bhp, which works out at 106 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.51 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 6,817th quickest to 60 mph, and the 69th quickest of the 456 Peugeots here. Its 86.4 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 SW 2.2 HDi 170
Year2004
Power168 hp (125 kW)
Kerb mass1,580 kg
Power to weight106 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed137 mph (221 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Vauxhall Vectra Estate 2.2i 15520058.09 s16.34 s85.7 mph153 bhp
Ford Mondeo Wagon 2.2 TDCi 15520058.15 s16.31 s86.1 mph153 bhp
Renault Talisman Estate 1.3 TCe 16020168.19 s16.37 s84.1 mph158 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 estate cars1,484 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 SW 2.2 HDi 170 0-60 time?
The Peugeot 407 SW 2.2 HDi 170 reaches 60 mph in 8.15 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,817th quickest of the 14,946 cars in the set.
What is the Peugeot 407 SW 2.2 HDi 170 quarter mile time?
16.29 s at 86.4 mph. It reaches the eighth mile in 10.50 s and clears the first 60 ft in 2.51 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 407 SW 2.2 HDi 170 have?
168 bhp and 1,580 kg, which is 106 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 221 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 407 SW 2.2 HDi 170?
Closest here on pace: Vauxhall Vectra Estate 2.2i 155 (8.09 s), Ford Mondeo Wagon 2.2 TDCi 155 (8.15 s), Renault Talisman Estate 1.3 TCe 160 (8.19 s). Each one can be raced against the Peugeot 407 SW 2.2 HDi 170 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 SW 2.2 HDi 170 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.