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

Peugeot 307 5dr 2.0 16V 138

The Peugeot 307 5dr 2.0 16V 138 reaches 60 mph in 9.27 s (100 km/h in 9.74 s) and covers a standing quarter mile in 17.26 s, tripping the lights at 86.1 mph. It clears the first 60 ft in 3.06 s and the eighth mile in 11.51 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 307 5dr 2.0 16V 138 Lada Vesta Sport

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 307 5dr 2.0 16V 138
0–60 mph9.27 s
0–100 km/h9.74 s
0–100 mph—
60 ft3.06 s
1/8 mile11.51 s
1/4 mile17.26 s
Trap speed86.1 mph

About the 307 5dr 2.0 16V 138

The 2001 Peugeot 307 5dr 2.0 16V 138 is a front-drive naturally aspirated car of 1,213 kg with 134 bhp, which works out at 111 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.06 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,887th quickest to 60 mph, and the 142nd quickest of the 456 Peugeots here. It traps higher than its 0-60 suggests — 86.1 mph, the 6,796th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Peugeot 307 5dr 2.0 16V 138
Year2001
Power134 hp (100 kW)
Kerb mass1,213 kg
Power to weight111 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lada Vesta Sport20199.25 s17.26 s86.2 mph145 bhp
Toyota RAV4 5dr 2.0 VVTi 15820089.29 s17.12 s81.9 mph156 bhp
Lancia Delta 1.6 10519799.28 s17.14 s81.5 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 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 307 5dr 2.0 16V 138 0-60 time?
The Peugeot 307 5dr 2.0 16V 138 reaches 60 mph in 9.27 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,887th quickest of the 14,946 cars in the set.
What is the Peugeot 307 5dr 2.0 16V 138 quarter mile time?
17.26 s at 86.1 mph. It reaches the eighth mile in 11.51 s and clears the first 60 ft in 3.06 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Peugeot 307 5dr 2.0 16V 138 have?
134 bhp and 1,213 kg, which is 111 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 200 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Peugeot 307 5dr 2.0 16V 138?
Closest here on pace: Lada Vesta Sport (9.25 s), Toyota RAV4 5dr 2.0 VVTi 158 (9.29 s), Lancia Delta 1.6 105 (9.28 s). Each one can be raced against the Peugeot 307 5dr 2.0 16V 138 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 307 5dr 2.0 16V 138 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.