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

Peugeot 308 PureTech 130 (Mk2)

The Peugeot 308 PureTech 130 (Mk2) reaches 60 mph in 8.75 s (100 km/h in 9.31 s) and covers a standing quarter mile in 16.77 s, tripping the lights at 83.2 mph. It clears the first 60 ft in 2.55 s and the eighth mile in 10.80 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 308 PureTech 130 (Mk2) Hyundai Getz 3dr 1.6i 106

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 308 PureTech 130 (Mk2)
0–60 mph8.75 s
0–100 km/h9.31 s
0–100 mph—
60 ft2.55 s
1/8 mile10.80 s
1/4 mile16.77 s
Trap speed83.2 mph

About the 308 PureTech 130 (Mk2)

The 2017 Peugeot 308 PureTech 130 (Mk2) is a front-drive turbocharged car of 1,205 kg with 129 bhp, which works out at 107 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.55 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,964th quickest to 60 mph, and the 102nd quickest of the 456 Peugeots here. Its 83.2 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 308 PureTech 130 (Mk2)
Year2017
Power129 hp (96 kW)
Kerb mass1,205 kg
Power to weight107 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed127 mph (205 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Hyundai Getz 3dr 1.6i 10620058.74 s16.77 s83.2 mph105 bhp
Hyundai Getz 5dr 1.6i 10620058.74 s16.77 s83.2 mph105 bhp
Hyundai Getz 5dr 1.6i 10520028.73 s16.79 s82.8 mph103 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 hatchbacks4,513 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 308 PureTech 130 (Mk2) 0-60 time?
The Peugeot 308 PureTech 130 (Mk2) reaches 60 mph in 8.75 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,964th quickest of the 14,946 cars in the set.
What is the Peugeot 308 PureTech 130 (Mk2) quarter mile time?
16.77 s at 83.2 mph. It reaches the eighth mile in 10.80 s and clears the first 60 ft in 2.55 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 308 PureTech 130 (Mk2) have?
129 bhp and 1,205 kg, which is 107 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 205 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 308 PureTech 130 (Mk2)?
Closest here on pace: Hyundai Getz 3dr 1.6i 106 (8.74 s), Hyundai Getz 5dr 1.6i 106 (8.74 s), Hyundai Getz 5dr 1.6i 105 (8.73 s). Each one can be raced against the Peugeot 308 PureTech 130 (Mk2) 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 308 PureTech 130 (Mk2) 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.