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

Peugeot 407 2.2 16V 158

The Peugeot 407 2.2 16V 158 reaches 60 mph in 8.20 s (100 km/h in 8.64 s) and covers a standing quarter mile in 16.34 s, tripping the lights at 87.6 mph. It clears the first 60 ft in 2.64 s and the eighth mile in 10.62 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 2.2 16V 158 Ford Mondeo Sedan 1.5 EcoBoost 160 Auto

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 2.2 16V 158
0–60 mph8.20 s
0–100 km/h8.64 s
0–100 mph—
60 ft2.64 s
1/8 mile10.62 s
1/4 mile16.34 s
Trap speed87.6 mph

About the 407 2.2 16V 158

The 2004 Peugeot 407 2.2 16V 158 is a front-drive naturally aspirated saloon of 1,455 kg with 156 bhp, which works out at 107 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.64 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,913th quickest to 60 mph, and the 71st quickest of the 456 Peugeots here. Its 87.6 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 2.2 16V 158
Year2004
Power156 hp (116 kW)
Kerb mass1,455 kg
Power to weight107 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed137 mph (220 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ford Mondeo Sedan 1.5 EcoBoost 160 Auto20158.18 s16.36 s85.0 mph158 bhp
Maserati Quattroporte II 3.0 V6 19019748.19 s16.25 s87.0 mph188 bhp
Ford Fusion 1.5 EcoBoost 18120188.18 s16.36 s85.0 mph178 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 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 Peugeot 407 2.2 16V 158 0-60 time?
The Peugeot 407 2.2 16V 158 reaches 60 mph in 8.20 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,913th quickest of the 14,946 cars in the set.
What is the Peugeot 407 2.2 16V 158 quarter mile time?
16.34 s at 87.6 mph. It reaches the eighth mile in 10.62 s and clears the first 60 ft in 2.64 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 407 2.2 16V 158 have?
156 bhp and 1,455 kg, which is 107 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 220 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 407 2.2 16V 158?
Closest here on pace: Ford Mondeo Sedan 1.5 EcoBoost 160 Auto (8.18 s), Maserati Quattroporte II 3.0 V6 190 (8.19 s), Ford Fusion 1.5 EcoBoost 181 (8.18 s). Each one can be raced against the Peugeot 407 2.2 16V 158 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 2.2 16V 158 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.