What is the Peugeot 2008 1.5 BlueHDi 132 0-60 time?

The Peugeot 2008 1.5 BlueHDi 132 reaches 60 mph in 8.36 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,232nd quickest of the 14,946 cars in the set.

What is the Peugeot 2008 1.5 BlueHDi 132 quarter mile time?

16.53 s at 83.7 mph. It reaches the eighth mile in 10.65 s and clears the first 60 ft in 2.57 s. These are theoretical times from a physics simulation, not measured runs.

How much power does the Peugeot 2008 1.5 BlueHDi 132 have?

129 bhp and 1,270 kg, which is 101 bhp per tonne. It is front-drive, turbodiesel, with 8 gears and a quoted top speed of 196 km/h. These are theoretical times from a physics simulation, not measured runs.

What cars are comparable to the Peugeot 2008 1.5 BlueHDi 132?

Closest here on pace: Nissan X-Trail (T32) 1.6 DIG-T 163 (8.34 s), Jeep Compass 2.2 CRD 163 (2011) (8.36 s), Renault Koleos 2.0 dCI 175 (2007) (8.37 s). Each one can be raced against the Peugeot 2008 1.5 BlueHDi 132 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 2008 1.5 BlueHDi 132 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.

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

Peugeot 2008 1.5 BlueHDi 132

The Peugeot 2008 1.5 BlueHDi 132 reaches 60 mph in 8.36 s (100 km/h in 8.92 s) and covers a standing quarter mile in 16.53 s, tripping the lights at 83.7 mph. It clears the first 60 ft in 2.57 s and the eighth mile in 10.65 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 2008 1.5 BlueHDi 132 Nissan X-Trail (T32) 1.6 DIG-T 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	Peugeot 2008 1.5 BlueHDi 132
0–60 mph	8.36 s
0–100 km/h	8.92 s
0–100 mph	—
60 ft	2.57 s
1/8 mile	10.65 s
1/4 mile	16.53 s
Trap speed	83.7 mph

About the 2008 1.5 BlueHDi 132

The 2024 Peugeot 2008 1.5 BlueHDi 132 is a front-drive turbodiesel SUV of 1,270 kg with 129 bhp, which works out at 101 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.57 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 7,232nd quickest to 60 mph, and the 83rd quickest of the 456 Peugeots here. Its 83.7 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 2008 1.5 BlueHDi 132
Year	2024
Power	129 hp (96 kW)
Kerb mass	1,270 kg
Power to weight	101 bhp/t
Drivetrain	Front drive
Gears	8
Engine	Turbodiesel
Top speed	122 mph (196 km/h), quoted

Similar cars

Car	Year	0–60	1/4 mile	Trap	Power
Nissan X-Trail (T32) 1.6 DIG-T 163	2017	8.34 s	16.54 s	83.8 mph	161 bhp
Jeep Compass 2.2 CRD 163 (2011)	2011	8.36 s	16.47 s	81.8 mph	161 bhp
Renault Koleos 2.0 dCI 175 (2007)	2007	8.37 s	16.48 s	81.8 mph	170 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

Where these times sit

0-60 under 10 seconds10,136 cars 0-100 km/h under 10 seconds9,062 cars Slower in the wetevery car, re-run The cost of altitudeevery car, re-run The cost of a passengerevery car, re-run

Peugeot 0-60 timesevery model Fastest SUVs2,049 cars Fastest cars of the 2020s867 cars

Put this race on your own page

<iframe src="https://myautoracer.com/?a=peugeot-2008-1-5-bluehdi-132-96-2024&amp;b=nissan-x-trail-t32-1-6-dig-t-163-120-2017&amp;embed=1" width="100%" height="880" style="border:0;border-radius:6px" loading="lazy" allow="fullscreen; web-share" allowfullscreen title="Peugeot 2008 1.5 BlueHDi 132 versus Nissan X-Trail (T32) 1.6 DIG-T 163, simulated"></iframe>
<p><a href="https://myautoracer.com/">Race simulator by My Auto Racer</a></p>

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the Peugeot 2008 1.5 BlueHDi 132 0-60 time?: The Peugeot 2008 1.5 BlueHDi 132 reaches 60 mph in 8.36 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,232nd quickest of the 14,946 cars in the set.
What is the Peugeot 2008 1.5 BlueHDi 132 quarter mile time?: 16.53 s at 83.7 mph. It reaches the eighth mile in 10.65 s and clears the first 60 ft in 2.57 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 2008 1.5 BlueHDi 132 have?: 129 bhp and 1,270 kg, which is 101 bhp per tonne. It is front-drive, turbodiesel, with 8 gears and a quoted top speed of 196 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 2008 1.5 BlueHDi 132?: Closest here on pace: Nissan X-Trail (T32) 1.6 DIG-T 163 (8.34 s), Jeep Compass 2.2 CRD 163 (2011) (8.36 s), Renault Koleos 2.0 dCI 175 (2007) (8.37 s). Each one can be raced against the Peugeot 2008 1.5 BlueHDi 132 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 2008 1.5 BlueHDi 132 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.