← My Auto Racer All cars AC 0-60 Comparisons
The AC 378 GT Zagato reaches 60 mph in 3.60 s and covers a standing quarter mile in 12.06 s, tripping the lights at 117.7 mph. It clears the first 60 ft in 1.87 s and the eighth mile in 7.79 s, reaching 100 mph in 9.03 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 | AC 378 GT Zagato |
|---|---|
| 0–60 mph | 3.60 s |
| 0–100 mph | 9.03 s |
| 60 ft | 1.87 s |
| 1/8 mile | 7.79 s |
| 1/4 mile | 12.06 s |
| Trap speed | 117.7 mph |
The 2012 AC 378 GT Zagato is a rear-drive naturally aspirated coupe of 1,465 kg with 428 bhp, which works out at 292 bhp per tonne. Rear drive and 292 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.87 s. Against the 2,929 cars in the set it is the 557th quickest to 60 mph, inside the fastest quarter, and the quickest of the 3 ACs here. Its 117.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 5 published acceleration figures for this car.
| Specification | AC 378 GT Zagato |
|---|---|
| Year | 2012 |
| Power | 428 bhp |
| Kerb mass | 1,465 kg |
| Power to weight | 292 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 298 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Cadillac ATS-V Coupe | 2016 | 3.66 s | 12.07 s | 115.7 mph | 464 bhp |
| Toyota Supra Final Edition A90 | 2024 | 3.65 s | 11.97 s | 117.5 mph | 429 bhp |
| BMW M2 (G87) | 2023 | 3.63 s | 11.89 s | 118.3 mph | 453 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.