← My Auto Racer All cars Donkervoort 0-60 Comparisons
The Donkervoort F22 reaches 60 mph in 2.17 s and covers a standing quarter mile in 9.70 s, tripping the lights at 140.7 mph. It clears the first 60 ft in 1.53 s and the eighth mile in 6.23 s, reaching 100 mph in 4.66 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 F22 |
|---|---|
| 0–60 mph | 2.17 s |
| 0–100 mph | 4.66 s |
| 60 ft | 1.53 s |
| 1/8 mile | 6.23 s |
| 1/4 mile | 9.70 s |
| Trap speed | 140.7 mph |
The 2023 Donkervoort F22 is a rear-drive turbocharged car of 750 kg with 492 bhp, which works out at 656 bhp per tonne. Rear drive and 656 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.53 s. Against the 2,929 cars in the set it is the 30th quickest to 60 mph, inside the fastest five per cent, and the quickest of the 4 Donkervoorts here. Its 140.7 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 F22 |
|---|---|
| Year | 2023 |
| Power | 492 bhp |
| Kerb mass | 750 kg |
| Power to weight | 656 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 290 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 |
| Ariel Atom 500 V8 | 2010 | 2.00 s | 9.68 s | 142.0 mph | 475 bhp |
| Dauer Porsche 962 LeMans | 1994 | 2.32 s | 9.61 s | 153.8 mph | 720 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.