← My Auto Racer All cars Opel 0-60 Comparisons
The Opel Speedster Turbo reaches 60 mph in 4.69 s and covers a standing quarter mile in 13.31 s, tripping the lights at 103.0 mph. It clears the first 60 ft in 2.06 s and the eighth mile in 8.54 s, reaching 100 mph in 12.45 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 Speedster Turbo |
|---|---|
| 0–60 mph | 4.69 s |
| 0–100 mph | 12.45 s |
| 60 ft | 2.06 s |
| 1/8 mile | 8.54 s |
| 1/4 mile | 13.31 s |
| Trap speed | 103.0 mph |
The 2015 Opel Speedster Turbo is a rear-drive naturally aspirated roadster of 928 kg with 197 bhp, which works out at 212 bhp per tonne. Rear drive and 212 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.06 s. Against the 2,929 cars in the set it is the 1,213th quickest to 60 mph, and the quickest of the 34 Opels here. It leaves better than it pulls: 103.0 mph at the lights is only the 1,488th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 9 of 10 published acceleration figures for this car.
| Specification | Opel Speedster Turbo |
|---|---|
| Year | 2015 |
| Power | 197 bhp |
| Kerb mass | 928 kg |
| Power to weight | 212 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 243 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| BMW M3 E46 | 2000 | 4.66 s | 13.35 s | 107.0 mph | 338 bhp |
| Chrysler Crossfire SRT-6 Roadster | 2015 | 4.66 s | 13.26 s | 105.3 mph | 330 bhp |
| K1 Roadster | 2008 | 4.64 s | 13.24 s | 103.8 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-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.