← My Auto Racer All cars Donkervoort 0-60 Comparisons
The Donkervoort GTO RS reaches 60 mph in 2.34 s and covers a standing quarter mile in 9.92 s, tripping the lights at 139.3 mph. It clears the first 60 ft in 1.59 s and the eighth mile in 6.40 s, reaching 100 mph in 4.95 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 | Donkervoort GTO RS |
|---|---|
| 0–60 mph | 2.34 s |
| 0–100 mph | 4.95 s |
| 60 ft | 1.59 s |
| 1/8 mile | 6.40 s |
| 1/4 mile | 9.92 s |
| Trap speed | 139.3 mph |
The 2016 Donkervoort GTO RS is a rear-drive turbocharged car of 695 kg with 380 bhp, which works out at 546 bhp per tonne. Rear drive and 546 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.59 s. Against the 2,929 cars in the set it is the 43rd quickest to 60 mph, inside the fastest five per cent, and the 2nd quickest of the 4 Donkervoorts here. Its 139.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 5 of 6 published acceleration figures for this car.
| Specification | Donkervoort GTO RS |
|---|---|
| Year | 2016 |
| Power | 380 bhp |
| Kerb mass | 695 kg |
| Power to weight | 546 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 280 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Ariel Atom 4R | 2023 | 2.22 s | 9.83 s | 139.9 mph | 400 bhp |
| Lamborghini Sesto Elemento | 2012 | 2.37 s | 10.07 s | 138.5 mph | 562 bhp |
| Lamborghini Temerario | 2024 | 2.36 s | 9.74 s | 144.8 mph | 908 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.