← My Auto Racer All cars Opel 0-60 Comparisons Answers
The Opel Corsa GSi D reaches 60 mph in 7.44 s and covers a standing quarter mile in 15.86 s, tripping the lights at 88.3 mph. It clears the first 60 ft in 2.55 s and the eighth mile in 10.29 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Opel Corsa GSi D |
|---|---|
| 0–60 mph | 7.44 s |
| 0–100 mph | — |
| 60 ft | 2.55 s |
| 1/8 mile | 10.29 s |
| 1/4 mile | 15.86 s |
| Trap speed | 88.3 mph |
The 2008 Opel Corsa GSi D is a front-drive turbocharged car of 1,244 kg with 148 bhp, which works out at 119 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 2,939 cars in the set it is the 2,507th quickest to 60 mph, and the 24th quickest of the 34 Opels here. Its 88.3 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 9 published acceleration figures for this car.
| Specification | Opel Corsa GSi D |
|---|---|
| Year | 2008 |
| Power | 148 bhp |
| Kerb mass | 1,244 kg |
| Power to weight | 119 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 210 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Abarth Grande Punto | 2007 | 7.45 s | 15.88 s | 88.1 mph | 153 bhp |
| Abarth 500 | 2008 | 7.49 s | 15.91 s | 86.8 mph | 133 bhp |
| VW Phaeton 3.0 TDI | 2008 | 7.51 s | 15.80 s | 87.6 mph | 237 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.
Figures regenerated 2026-09-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.