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

Peugeot 4007 2.2 HDi 156

The Peugeot 4007 2.2 HDi 156 reaches 60 mph in 8.77 s (100 km/h in 9.59 s) and covers a standing quarter mile in 16.72 s, tripping the lights at 80.9 mph. It clears the first 60 ft in 2.48 s and the eighth mile in 10.66 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 4007 2.2 HDi 156 Honda Mobilio 1.5 CVT 110

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 4007 2.2 HDi 156
0–60 mph8.77 s
0–100 km/h9.59 s
0–100 mph—
60 ft2.48 s
1/8 mile10.66 s
1/4 mile16.72 s
Trap speed80.9 mph

About the 4007 2.2 HDi 156

The 2007 Peugeot 4007 2.2 HDi 156 is an all-wheel-drive turbodiesel SUV of 1,770 kg with 154 bhp, which works out at 87 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.48 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 8,010th quickest to 60 mph, and the 105th quickest of the 456 Peugeots here. It leaves better than it pulls: 80.9 mph at the lights is only the 9,566th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Peugeot 4007 2.2 HDi 156
Year2007
Power154 hp (115 kW)
Kerb mass1,770 kg
Power to weight87 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed123 mph (198 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Honda Mobilio 1.5 CVT 11020048.77 s16.82 s79.9 mph109 bhp
MINI Countryman Cooper 1.5 136 (2021)20218.76 s16.79 s82.5 mph134 bhp
Subaru Outback 2.0D CVT 15020148.71 s16.73 s81.7 mph148 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 SUVs2,049 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 4007 2.2 HDi 156 0-60 time?
The Peugeot 4007 2.2 HDi 156 reaches 60 mph in 8.77 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,010th quickest of the 14,946 cars in the set.
What is the Peugeot 4007 2.2 HDi 156 quarter mile time?
16.72 s at 80.9 mph. It reaches the eighth mile in 10.66 s and clears the first 60 ft in 2.48 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 4007 2.2 HDi 156 have?
154 bhp and 1,770 kg, which is 87 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 198 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 4007 2.2 HDi 156?
Closest here on pace: Honda Mobilio 1.5 CVT 110 (8.77 s), MINI Countryman Cooper 1.5 136 (2021) (8.76 s), Subaru Outback 2.0D CVT 150 (8.71 s). Each one can be raced against the Peugeot 4007 2.2 HDi 156 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 4007 2.2 HDi 156 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.