← My Auto Racer All cars Callaway 0-60 Comparisons
The Callaway C12 reaches 60 mph in 4.70 s and covers a standing quarter mile in 13.07 s, tripping the lights at 113.1 mph. It clears the first 60 ft in 2.19 s and the eighth mile in 8.61 s, reaching 100 mph in 10.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 | Callaway C12 |
|---|---|
| 0–60 mph | 4.70 s |
| 0–100 mph | 10.66 s |
| 60 ft | 2.19 s |
| 1/8 mile | 8.61 s |
| 1/4 mile | 13.07 s |
| Trap speed | 113.1 mph |
The 1999 Callaway C12 is a rear-drive naturally aspirated saloon of 1,565 kg with 394 bhp, which works out at 252 bhp per tonne. Rear drive and 252 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.19 s. Against the 2,929 cars in the set it is the 1,219th quickest to 60 mph, and the 2nd quickest of the 3 Callaways here. It traps higher than its 0-60 suggests — 113.1 mph, the 850th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 9 of 10 published acceleration figures for this car.
| Specification | Callaway C12 |
|---|---|
| Year | 1999 |
| Power | 394 bhp |
| Kerb mass | 1,565 kg |
| Power to weight | 252 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 295 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Fpv FG F6 | 2008 | 4.66 s | 13.02 s | 107.0 mph | 416 bhp |
| Pontiac G8 GXP | 2008 | 4.68 s | 12.99 s | 110.8 mph | 414 bhp |
| Rolls-Royce Ghost Mk I facelift | 2014 | 4.78 s | 12.98 s | 111.0 mph | 563 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.