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

Peugeot 3008 1.6 THP 156

The Peugeot 3008 1.6 THP 156 reaches 60 mph in 8.33 s (100 km/h in 9.11 s) and covers a standing quarter mile in 16.50 s, tripping the lights at 83.6 mph. It clears the first 60 ft in 2.57 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 3008 1.6 THP 156 Renault Koleos 2.5 CVT 170 (2007)

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 3008 1.6 THP 156
0–60 mph8.33 s
0–100 km/h9.11 s
0–100 mph—
60 ft2.57 s
1/8 mile10.62 s
1/4 mile16.50 s
Trap speed83.6 mph

About the 3008 1.6 THP 156

The 2009 Peugeot 3008 1.6 THP 156 is a front-drive turbocharged SUV of 1,480 kg with 154 bhp, which works out at 104 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,188th quickest to 60 mph, and the 81st quickest of the 456 Peugeots here. Its 83.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 3008 1.6 THP 156
Year2009
Power154 hp (115 kW)
Kerb mass1,480 kg
Power to weight104 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed126 mph (203 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Koleos 2.5 CVT 170 (2007)20078.34 s16.48 s82.7 mph169 bhp
Mitsubishi ASX / RVR / Outlander Sport 1.8 DI-D 2WD 15020128.34 s16.54 s83.8 mph148 bhp
Nissan X-Trail (T32) 1.6 DIG-T 16320178.34 s16.54 s83.8 mph161 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 3008 1.6 THP 156 0-60 time?
The Peugeot 3008 1.6 THP 156 reaches 60 mph in 8.33 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,188th quickest of the 14,946 cars in the set.
What is the Peugeot 3008 1.6 THP 156 quarter mile time?
16.50 s at 83.6 mph. It reaches the eighth mile in 10.62 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 3008 1.6 THP 156 have?
154 bhp and 1,480 kg, which is 104 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 203 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 3008 1.6 THP 156?
Closest here on pace: Renault Koleos 2.5 CVT 170 (2007) (8.34 s), Mitsubishi ASX / RVR / Outlander Sport 1.8 DI-D 2WD 150 (8.34 s), Nissan X-Trail (T32) 1.6 DIG-T 163 (8.34 s). Each one can be raced against the Peugeot 3008 1.6 THP 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 3008 1.6 THP 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.