← My Auto Racer All cars Gumpert 0-60 Comparisons
The Gumpert Apollo Speed reaches 60 mph in 2.86 s and covers a standing quarter mile in 10.59 s, tripping the lights at 132.8 mph. It clears the first 60 ft in 1.66 s and the eighth mile in 6.92 s, reaching 100 mph in 5.92 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 | Gumpert Apollo Speed |
|---|---|
| 0–60 mph | 2.86 s |
| 0–100 mph | 5.92 s |
| 60 ft | 1.66 s |
| 1/8 mile | 6.92 s |
| 1/4 mile | 10.59 s |
| Trap speed | 132.8 mph |
The 2009 Gumpert Apollo Speed is a rear-drive turbocharged supercar of 1,448 kg with 691 bhp, which works out at 477 bhp per tonne. Rear drive and 477 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.66 s. Against the 2,929 cars in the set it is the 174th quickest to 60 mph, inside the fastest tenth, and the quickest of the 3 Gumperts here. Its 132.8 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 11 published acceleration figures for this car.
| Specification | Gumpert Apollo Speed |
|---|---|
| Year | 2009 |
| Power | 691 bhp |
| Kerb mass | 1,448 kg |
| Power to weight | 477 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 330 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Ruf RT 12 R AWD | 2011 | 2.77 s | 10.60 s | 133.0 mph | 720 bhp |
| Ruf CTR3 | 2008 | 2.95 s | 10.62 s | 135.3 mph | 691 bhp |
| Ruf Ultimate | 2016 | 2.88 s | 10.90 s | 127.7 mph | 582 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.