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

Pagani Zonda C12 S (2000)

The Pagani Zonda C12 S (2000) reaches 60 mph in 3.53 s (100 km/h in 3.67 s) and covers a standing quarter mile in 11.45 s, tripping the lights at 127.4 mph. It clears the first 60 ft in 1.90 s and the eighth mile in 7.51 s, reaching 100 mph in 7.32 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.

Pagani Zonda C12 S (2000) Dodge Viper ACR Mk V

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 Pagani Zonda C12 S (2000)
0–60 mph3.53 s
0–100 km/h3.67 s
0–100 mph7.32 s
60 ft1.90 s
1/8 mile7.51 s
1/4 mile11.45 s
Trap speed127.4 mph

About the Zonda C12 S

The 2000 Pagani Zonda C12 S (2000) is a rear-drive naturally aspirated supercar of 1,350 kg with 550 bhp, which works out at 407 bhp per tonne. Rear drive and 407 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.90 s. Against the 14,946 cars in the set it is the 673rd quickest to 60 mph, inside the fastest five per cent, and the 10th quickest of the 11 Paganis here. Its 127.4 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 5 published acceleration figures for this car.

On paper

Specification Pagani Zonda C12 S (2000)
Year2000
Power550 hp (410 kW)
Kerb mass1,350 kg
Power to weight407 bhp/t
DrivetrainRear drive
Gears6
EngineNaturally aspirated
Top speed217 mph (350 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dodge Viper ACR Mk V20163.51 s11.48 s126.1 mph645 bhp
Wiesmann GT MF5 Mk II20113.50 s11.46 s125.5 mph547 bhp
Ferrari F5019953.50 s11.53 s126.2 mph512 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 4 seconds1,060 cars0-100 km/h under 4 seconds881 carsQuarter mile under 12 seconds780 cars0-100 under 9 seconds871 carsTraps over 120 mph651 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Pagani 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 Pagani Zonda C12 S (2000) 0-60 time?
The Pagani Zonda C12 S (2000) reaches 60 mph in 3.53 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 673rd quickest of the 14,946 cars in the set.
What is the Pagani Zonda C12 S (2000) quarter mile time?
11.45 s at 127.4 mph. It reaches the eighth mile in 7.51 s and clears the first 60 ft in 1.90 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Pagani Zonda C12 S (2000) have?
550 bhp and 1,350 kg, which is 407 bhp per tonne. It is rear-drive, naturally aspirated, with 6 gears and a quoted top speed of 350 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Pagani Zonda C12 S (2000)?
Closest here on pace: Dodge Viper ACR Mk V (3.51 s), Wiesmann GT MF5 Mk II (3.50 s), Ferrari F50 (3.50 s). Each one can be raced against the Pagani Zonda C12 S (2000) 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 Pagani Zonda C12 S (2000) is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 5 of its 5 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.