← My Auto Racer All cars Aston Martin 0-60 Comparisons Answers

Aston Martin V8 Zagato

The Aston Martin V8 Zagato reaches 60 mph in 4.61 s (100 km/h in 4.81 s) and covers a standing quarter mile in 12.74 s, tripping the lights at 116.1 mph. It clears the first 60 ft in 2.24 s and the eighth mile in 8.40 s, reaching 100 mph in 9.89 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.

Aston Martin V8 Zagato Dodge Viper RT/10 405 PS

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 Aston Martin V8 Zagato
0–60 mph4.61 s
0–100 km/h4.81 s
0–100 mph9.89 s
60 ft2.24 s
1/8 mile8.40 s
1/4 mile12.74 s
Trap speed116.1 mph

About the V8 Zagato

The 1986 Aston Martin V8 Zagato is a rear-drive naturally aspirated car of 1,590 kg with 432 bhp, which works out at 272 bhp per tonne. Rear drive and 272 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.24 s. Against the 14,946 cars in the set it is the 1,754th quickest to 60 mph, inside the fastest quarter, and the 58th quickest of the 84 Aston Martins here. Its 116.1 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 7 published acceleration figures for this car.

On paper

Specification Aston Martin V8 Zagato
Year1986
Power432 hp (322 kW)
Kerb mass1,590 kg
Power to weight272 bhp/t
DrivetrainRear drive
Gears5
EngineNaturally aspirated
Top speed186 mph (300 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dodge Viper RT/10 405 PS19924.69 s12.94 s110.5 mph400 bhp
Melkus RS 200020094.62 s13.05 s104.7 mph266 bhp
Cadillac CTS-V MK I20054.59 s12.83 s108.7 mph400 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 5 seconds2,158 cars0-100 km/h under 5 seconds1,845 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
Aston Martin 0-60 timesevery modelFastest hatchbacks4,513 carsFastest cars of the 1980s1,057 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 Aston Martin V8 Zagato 0-60 time?
The Aston Martin V8 Zagato reaches 60 mph in 4.61 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 1,754th quickest of the 14,946 cars in the set.
What is the Aston Martin V8 Zagato quarter mile time?
12.74 s at 116.1 mph. It reaches the eighth mile in 8.40 s and clears the first 60 ft in 2.24 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Aston Martin V8 Zagato have?
432 bhp and 1,590 kg, which is 272 bhp per tonne. It is rear-drive, naturally aspirated, with 5 gears and a quoted top speed of 300 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Aston Martin V8 Zagato?
Closest here on pace: Dodge Viper RT/10 405 PS (4.69 s), Melkus RS 2000 (4.62 s), Cadillac CTS-V MK I (4.59 s). Each one can be raced against the Aston Martin V8 Zagato 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 Aston Martin V8 Zagato is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 5 of its 7 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.