← My Auto Racer All cars Koenigsegg 0-60 Comparisons Answers

Koenigsegg CC8S 4.7 V8 655

The Koenigsegg CC8S 4.7 V8 655 reaches 60 mph in 2.83 s (100 km/h in 2.93 s) and covers a standing quarter mile in 10.16 s, tripping the lights at 144.8 mph. It clears the first 60 ft in 1.65 s and the eighth mile in 6.67 s, reaching 100 mph in 5.49 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.

Koenigsegg CC8S 4.7 V8 655 Ifr Aspid Super Sport

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start Koenigsegg CC8S 4.7 V8 655
0–60 mph2.83 s
0–100 km/h2.93 s
0–100 mph5.49 s
60 ft1.65 s
1/8 mile6.67 s
1/4 mile10.16 s
Trap speed144.8 mph

About the CC8S 4.7 V8 655

The 2002 Koenigsegg CC8S 4.7 V8 655 is a rear-drive turbocharged supercar of 1,175 kg with 646 bhp, which works out at 550 bhp per tonne. Rear drive and 550 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.65 s. Against the 14,946 cars in the set it is the 206th quickest to 60 mph, inside the fastest five per cent, and the 13th quickest of the 17 Koenigseggs here. Its 144.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 2 of 2 published acceleration figures for this car.

On paper

Specification Koenigsegg CC8S 4.7 V8 655
Year2002
Power646 hp (482 kW)
Kerb mass1,175 kg
Power to weight550 bhp/t
DrivetrainRear drive
Gears6
EngineTurbocharged
Top speed240 mph (386 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ifr Aspid Super Sport20082.90 s10.34 s138.9 mph402 bhp
Fahlke Larea GT1 S720112.72 s10.22 s141.1 mph553 bhp
Mclaren 675LT20152.69 s10.14 s141.0 mph665 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.

Where these times sit

0-60 under 3 seconds271 cars0-100 km/h under 3 seconds213 carsQuarter mile under 11 seconds272 cars0-100 under 7 seconds311 carsTraps over 140 mph108 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Koenigsegg 0-60 timesevery modelFastest supercars629 carsFastest cars of the 2000s5,138 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the Koenigsegg CC8S 4.7 V8 655 0-60 time?
The Koenigsegg CC8S 4.7 V8 655 reaches 60 mph in 2.83 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 206th quickest of the 14,946 cars in the set.
What is the Koenigsegg CC8S 4.7 V8 655 quarter mile time?
10.16 s at 144.8 mph. It reaches the eighth mile in 6.67 s and clears the first 60 ft in 1.65 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Koenigsegg CC8S 4.7 V8 655 have?
646 bhp and 1,175 kg, which is 550 bhp per tonne. It is rear-drive, turbocharged, with 6 gears and a quoted top speed of 386 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Koenigsegg CC8S 4.7 V8 655?
Closest here on pace: Ifr Aspid Super Sport (2.90 s), Fahlke Larea GT1 S7 (2.72 s), Mclaren 675LT (2.69 s). Each one can be raced against the Koenigsegg CC8S 4.7 V8 655 in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The Koenigsegg CC8S 4.7 V8 655 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

Figures regenerated 2026-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.