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

Peugeot 3008 2.0 HDi FAP 163

The Peugeot 3008 2.0 HDi FAP 163 reaches 60 mph in 9.15 s (100 km/h in 9.79 s) and covers a standing quarter mile in 17.02 s, tripping the lights at 81.4 mph. It clears the first 60 ft in 2.65 s and the eighth mile in 10.94 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 2.0 HDi FAP 163 Subaru Forester 2.0 147

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 2.0 HDi FAP 163
0–60 mph9.15 s
0–100 km/h9.79 s
0–100 mph—
60 ft2.65 s
1/8 mile10.94 s
1/4 mile17.02 s
Trap speed81.4 mph

About the 3008 2.0 HDi FAP 163

The 2013 Peugeot 3008 2.0 HDi FAP 163 is a front-drive turbodiesel SUV of 1,701 kg with 161 bhp, which works out at 95 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.65 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 8,694th quickest to 60 mph, and the 135th quickest of the 456 Peugeots here. Its 81.4 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 2.0 HDi FAP 163
Year2013
Power161 hp (120 kW)
Kerb mass1,701 kg
Power to weight95 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed127 mph (204 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Subaru Forester 2.0 14720139.16 s17.04 s80.3 mph145 bhp
Renault Avantime 2.0 Turbo 16320019.23 s17.01 s81.8 mph161 bhp
Jeep Wrangler Unlimited Rubicon JL 2.2 CRD 20020189.18 s16.94 s77.5 mph197 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 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 3008 2.0 HDi FAP 163 0-60 time?
The Peugeot 3008 2.0 HDi FAP 163 reaches 60 mph in 9.15 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,694th quickest of the 14,946 cars in the set.
What is the Peugeot 3008 2.0 HDi FAP 163 quarter mile time?
17.02 s at 81.4 mph. It reaches the eighth mile in 10.94 s and clears the first 60 ft in 2.65 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 3008 2.0 HDi FAP 163 have?
161 bhp and 1,701 kg, which is 95 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 204 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 3008 2.0 HDi FAP 163?
Closest here on pace: Subaru Forester 2.0 147 (9.16 s), Renault Avantime 2.0 Turbo 163 (9.23 s), Jeep Wrangler Unlimited Rubicon JL 2.2 CRD 200 (9.18 s). Each one can be raced against the Peugeot 3008 2.0 HDi FAP 163 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 2.0 HDi FAP 163 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.