← My Auto Racer All cars Cadillac 0-60 Comparisons
The Cadillac ATS-V reaches 60 mph in 3.77 s and covers a standing quarter mile in 12.16 s, tripping the lights at 115.8 mph. It clears the first 60 ft in 1.93 s and the eighth mile in 7.87 s, reaching 100 mph in 9.11 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 | Cadillac ATS-V |
|---|---|
| 0–60 mph | 3.77 s |
| 0–100 mph | 9.11 s |
| 60 ft | 1.93 s |
| 1/8 mile | 7.87 s |
| 1/4 mile | 12.16 s |
| Trap speed | 115.8 mph |
The 2015 Cadillac ATS-V is a rear-drive turbocharged saloon of 1,722 kg with 464 bhp, which works out at 269 bhp per tonne. Rear drive and 269 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.93 s. Against the 2,929 cars in the set it is the 664th quickest to 60 mph, inside the fastest quarter, and the 5th quickest of the 24 Cadillacs here. Its 115.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 9 of 11 published acceleration figures for this car.
| Specification | Cadillac ATS-V |
|---|---|
| Year | 2015 |
| Power | 464 bhp |
| Kerb mass | 1,722 kg |
| Power to weight | 269 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 304 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Polestar 4 Dual Motor Performance | 2024 | 3.66 s | 12.12 s | 114.9 mph | 536 bhp |
| Polestar 1 | 2020 | 3.88 s | 12.30 s | 113.2 mph | 620 bhp |
| Lister Le Mans V12 | 2015 | 3.87 s | 12.39 s | 111.8 mph | 488 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.