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

Peugeot 308 GTi 270 T9

The Peugeot 308 GTi 270 T9 reaches 60 mph in 5.29 s (100 km/h in 5.54 s) and covers a standing quarter mile in 13.75 s, tripping the lights at 103.2 mph. It clears the first 60 ft in 2.29 s and the eighth mile in 8.99 s, reaching 100 mph in 12.69 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 GTi 270 T9 Nissan 370Z Nismo

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 GTi 270 T9
0–60 mph5.29 s
0–100 km/h5.54 s
0–100 mph12.69 s
60 ft2.29 s
1/8 mile8.99 s
1/4 mile13.75 s
Trap speed103.2 mph

About the 308 GTi 270 T9

The 2015 Peugeot 308 GTi 270 T9 is a front-drive turbocharged car of 1,205 kg with 267 bhp, which works out at 221 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.29 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 2,460th quickest to 60 mph, inside the fastest quarter, and the 2nd quickest of the 456 Peugeots here. Its 103.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 9 of 10 published acceleration figures for this car.

On paper

Specification Peugeot 308 GTi 270 T9
Year2015
Power267 hp (199 kW)
Kerb mass1,205 kg
Power to weight221 bhp/t
DrivetrainFront drive
Gears7
EngineTurbocharged
Top speed155 mph (250 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Nissan 370Z Nismo20135.29 s13.63 s102.9 mph339 bhp
AC Ace 5.0 V819995.28 s13.57 s103.9 mph350 bhp
SEAT Leon Cupra 280 Mk III20145.32 s13.68 s105.1 mph276 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 6 seconds3,249 cars0-100 km/h under 6 seconds2,894 carsQuarter mile under 14 seconds2,644 cars0-100 under 16 seconds2,740 carsTraps over 100 mph2,737 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 hot hatches298 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 GTi 270 T9 0-60 time?
The Peugeot 308 GTi 270 T9 reaches 60 mph in 5.29 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 2,460th quickest of the 14,946 cars in the set.
What is the Peugeot 308 GTi 270 T9 quarter mile time?
13.75 s at 103.2 mph. It reaches the eighth mile in 8.99 s and clears the first 60 ft in 2.29 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 308 GTi 270 T9 have?
267 bhp and 1,205 kg, which is 221 bhp per tonne. It is front-drive, turbocharged, with 7 gears and a quoted top speed of 250 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 308 GTi 270 T9?
Closest here on pace: Nissan 370Z Nismo (5.29 s), AC Ace 5.0 V8 (5.28 s), SEAT Leon Cupra 280 Mk III (5.32 s). Each one can be raced against the Peugeot 308 GTi 270 T9 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 GTi 270 T9 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 10 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.