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

Peugeot 5008 1.6 PureTech 180

The Peugeot 5008 1.6 PureTech 180 reaches 60 mph in 7.50 s (100 km/h in 7.93 s) and covers a standing quarter mile in 15.82 s, tripping the lights at 89.6 mph. It clears the first 60 ft in 2.54 s and the eighth mile in 10.29 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 5008 1.6 PureTech 180 Audi Q3 Sportback 40 TDI 190

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 5008 1.6 PureTech 180
0–60 mph7.50 s
0–100 km/h7.93 s
0–100 mph—
60 ft2.54 s
1/8 mile10.29 s
1/4 mile15.82 s
Trap speed89.6 mph

About the 5008 1.6 PureTech 180

The 2016 Peugeot 5008 1.6 PureTech 180 is a front-drive turbocharged SUV of 1,530 kg with 177 bhp, which works out at 116 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.54 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 5,568th quickest to 60 mph, and the 32nd quickest of the 456 Peugeots here. Its 89.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 5008 1.6 PureTech 180
Year2016
Power177 hp (132 kW)
Kerb mass1,530 kg
Power to weight116 bhp/t
DrivetrainFront drive
Gears8
EngineTurbocharged
Top speed137 mph (220 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Audi Q3 Sportback 40 TDI 19020197.50 s15.83 s89.4 mph188 bhp
Ford Explorer 2.0 Ecoboost 24020107.50 s15.88 s87.5 mph237 bhp
Jeep Renegade 2.0 MultiJet 17020147.47 s15.81 s84.4 mph168 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 8 seconds6,514 cars0-100 km/h under 8 seconds5,602 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 2010s4,541 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 5008 1.6 PureTech 180 0-60 time?
The Peugeot 5008 1.6 PureTech 180 reaches 60 mph in 7.50 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,568th quickest of the 14,946 cars in the set.
What is the Peugeot 5008 1.6 PureTech 180 quarter mile time?
15.82 s at 89.6 mph. It reaches the eighth mile in 10.29 s and clears the first 60 ft in 2.54 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 5008 1.6 PureTech 180 have?
177 bhp and 1,530 kg, which is 116 bhp per tonne. It is front-drive, turbocharged, with 8 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 5008 1.6 PureTech 180?
Closest here on pace: Audi Q3 Sportback 40 TDI 190 (7.50 s), Ford Explorer 2.0 Ecoboost 240 (7.50 s), Jeep Renegade 2.0 MultiJet 170 (7.47 s). Each one can be raced against the Peugeot 5008 1.6 PureTech 180 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 5008 1.6 PureTech 180 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.