← My Auto Racer All cars Koenigsegg 0-60 Comparisons
The Koenigsegg CCXR reaches 60 mph in 2.50 s and covers a standing quarter mile in 10.15 s, tripping the lights at 145.2 mph. It clears the first 60 ft in 1.68 s and the eighth mile in 6.69 s, reaching 100 mph in 5.51 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 | Koenigsegg CCXR |
|---|---|
| 0–60 mph | 2.50 s |
| 0–100 mph | 5.51 s |
| 60 ft | 1.68 s |
| 1/8 mile | 6.69 s |
| 1/4 mile | 10.15 s |
| Trap speed | 145.2 mph |
The 2007 Koenigsegg CCXR is a rear-drive turbocharged supercar of 1,180 kg with 1,004 bhp, which works out at 851 bhp per tonne. Rear drive and 851 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.68 s. Against the 2,929 cars in the set it is the 63rd quickest to 60 mph, inside the fastest five per cent, and the 2nd quickest of the 10 Koenigseggs here. Its 145.2 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 10 of 11 published acceleration figures for this car.
| Specification | Koenigsegg CCXR |
|---|---|
| Year | 2007 |
| Power | 1,004 bhp |
| Kerb mass | 1,180 kg |
| Power to weight | 851 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 403 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| 9ff GT9-R | 2009 | 2.46 s | 10.05 s | 146.7 mph | 1,105 bhp |
| Caparo T1 | 2007 | 2.36 s | 9.94 s | 139.0 mph | 575 bhp |
| Hennessey Venom GT | 2010 | 2.54 s | 9.71 s | 164.6 mph | 1,200 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.