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

Cadillac ATS-V Coupe

The Cadillac ATS-V Coupe reaches 60 mph in 3.66 s (100 km/h in 3.86 s) and covers a standing quarter mile in 12.07 s, tripping the lights at 115.7 mph. It clears the first 60 ft in 1.89 s and the eighth mile in 7.79 s, reaching 100 mph in 9.01 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.

Cadillac ATS-V Coupe Mercedes-AMG S 65 Coupe (C217) 6.0 V12 630

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 Cadillac ATS-V Coupe
0–60 mph3.66 s
0–100 km/h3.86 s
0–100 mph9.01 s
60 ft1.89 s
1/8 mile7.79 s
1/4 mile12.07 s
Trap speed115.7 mph

About the ATS-V Coupe

The 2016 Cadillac ATS-V Coupe is a rear-drive turbocharged coupe of 1,636 kg with 464 bhp, which works out at 284 bhp per tonne. Rear drive and 284 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.89 s. Against the 14,946 cars in the set it is the 775th quickest to 60 mph, inside the fastest tenth, and the 3rd quickest of the 65 Cadillacs here. Its 115.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 9 of 11 published acceleration figures for this car.

On paper

Specification Cadillac ATS-V Coupe
Year2016
Power464 hp (346 kW)
Kerb mass1,636 kg
Power to weight284 bhp/t
DrivetrainRear drive
Gears7
EngineTurbocharged
Top speed189 mph (304 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mercedes-AMG S 65 Coupe (C217) 6.0 V12 63020173.66 s11.94 s115.6 mph621 bhp
Aston Martin V8 Vantage LeMans19993.68 s12.10 s116.1 mph599 bhp
AC 378 GT Zagato20123.60 s12.06 s117.7 mph428 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 13 seconds1,638 cars0-100 under 12 seconds1,963 carsTraps over 110 mph1,380 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Cadillac 0-60 timesevery modelFastest coupes911 carsFastest cars of the 2010s4,541 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 Cadillac ATS-V Coupe 0-60 time?
The Cadillac ATS-V Coupe reaches 60 mph in 3.66 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 775th quickest of the 14,946 cars in the set.
What is the Cadillac ATS-V Coupe quarter mile time?
12.07 s at 115.7 mph. It reaches the eighth mile in 7.79 s and clears the first 60 ft in 1.89 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Cadillac ATS-V Coupe have?
464 bhp and 1,636 kg, which is 284 bhp per tonne. It is rear-drive, turbocharged, with 7 gears and a quoted top speed of 304 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Cadillac ATS-V Coupe?
Closest here on pace: Mercedes-AMG S 65 Coupe (C217) 6.0 V12 630 (3.66 s), Aston Martin V8 Vantage LeMans (3.68 s), AC 378 GT Zagato (3.60 s). Each one can be raced against the Cadillac ATS-V Coupe 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 Cadillac ATS-V Coupe is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 11 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.