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

Opel Corsa 3dr 1.8 GSi 125

The Opel Corsa 3dr 1.8 GSi 125 reaches 60 mph in 8.19 s (100 km/h in 8.64 s) and covers a standing quarter mile in 16.24 s, tripping the lights at 87.2 mph. It clears the first 60 ft in 2.74 s and the eighth mile in 10.59 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.

Opel Corsa 3dr 1.8 GSi 125 Mazda 3/Axela Hatchback 2.0 150

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 Opel Corsa 3dr 1.8 GSi 125
0–60 mph8.19 s
0–100 km/h8.64 s
0–100 mph—
60 ft2.74 s
1/8 mile10.59 s
1/4 mile16.24 s
Trap speed87.2 mph

About the Corsa 3dr 1.8 GSi 125

The 2000 Opel Corsa 3dr 1.8 GSi 125 is a front-drive naturally aspirated car of 1,085 kg with 123 bhp, which works out at 114 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.74 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 6,881st quickest to 60 mph, and the 137th quickest of the 721 Opels here. Its 87.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 Opel Corsa 3dr 1.8 GSi 125
Year2000
Power123 hp (92 kW)
Kerb mass1,085 kg
Power to weight114 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed126 mph (203 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda 3/Axela Hatchback 2.0 15020048.19 s16.25 s87.0 mph148 bhp
Dodge Neon 2.0 SMPI 13320038.19 s16.25 s87.0 mph131 bhp
Toyota Yaris 3dr 1.5 16V VVT-i 106 (2003)20038.17 s16.26 s84.9 mph105 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
Opel 0-60 timesevery modelFastest small cars1,681 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 Opel Corsa 3dr 1.8 GSi 125 0-60 time?
The Opel Corsa 3dr 1.8 GSi 125 reaches 60 mph in 8.19 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,881st quickest of the 14,946 cars in the set.
What is the Opel Corsa 3dr 1.8 GSi 125 quarter mile time?
16.24 s at 87.2 mph. It reaches the eighth mile in 10.59 s and clears the first 60 ft in 2.74 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Opel Corsa 3dr 1.8 GSi 125 have?
123 bhp and 1,085 kg, which is 114 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 203 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Opel Corsa 3dr 1.8 GSi 125?
Closest here on pace: Mazda 3/Axela Hatchback 2.0 150 (8.19 s), Dodge Neon 2.0 SMPI 133 (8.19 s), Toyota Yaris 3dr 1.5 16V VVT-i 106 (2003) (8.17 s). Each one can be raced against the Opel Corsa 3dr 1.8 GSi 125 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 Opel Corsa 3dr 1.8 GSi 125 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.