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

Aston Martin V8 Coupe

The Aston Martin V8 Coupe reaches 60 mph in 5.10 s (100 km/h in 5.83 s) and covers a standing quarter mile in 13.84 s, tripping the lights at 103.3 mph. It clears the first 60 ft in 2.23 s and the eighth mile in 8.98 s, reaching 100 mph in 13.05 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 Coupe Daewoo G2X 2.0 264

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 Coupe
0–60 mph5.10 s
0–100 km/h5.83 s
0–100 mph13.05 s
60 ft2.23 s
1/8 mile8.98 s
1/4 mile13.84 s
Trap speed103.3 mph

About the V8 Coupe

The 1996 Aston Martin V8 Coupe is a rear-drive naturally aspirated coupe of 1,954 kg with 350 bhp, which works out at 179 bhp per tonne. Rear drive and 179 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.23 s. Against the 14,946 cars in the set it is the 2,254th quickest to 60 mph, inside the fastest quarter, and the 67th quickest of the 84 Aston Martins here. Its 103.3 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 6 of 7 published acceleration figures for this car.

On paper

Specification Aston Martin V8 Coupe
Year1996
Power350 hp (261 kW)
Kerb mass1,954 kg
Power to weight179 bhp/t
DrivetrainRear drive
Gears6
EngineNaturally aspirated
Top speed170 mph (274 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Daewoo G2X 2.0 26420065.11 s13.89 s98.9 mph260 bhp
Rolls-Royce Phantom Coupe 6.75 V12 46020125.14 s13.66 s102.1 mph453 bhp
Nissan Altima Coupe20085.29 s13.84 s100.9 mph270 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 6 seconds3,249 cars0-100 km/h under 6 seconds2,894 carsQuarter mile under 14 seconds2,644 cars0-100 under 16 seconds2,740 carsTraps over 100 mph2,737 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 coupes911 carsFastest cars of the 1990s2,649 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 Coupe 0-60 time?
The Aston Martin V8 Coupe reaches 60 mph in 5.10 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 2,254th quickest of the 14,946 cars in the set.
What is the Aston Martin V8 Coupe quarter mile time?
13.84 s at 103.3 mph. It reaches the eighth mile in 8.98 s and clears the first 60 ft in 2.23 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Aston Martin V8 Coupe have?
350 bhp and 1,954 kg, which is 179 bhp per tonne. It is rear-drive, naturally aspirated, with 6 gears and a quoted top speed of 274 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Aston Martin V8 Coupe?
Closest here on pace: Daewoo G2X 2.0 264 (5.11 s), Rolls-Royce Phantom Coupe 6.75 V12 460 (5.14 s), Nissan Altima Coupe (5.29 s). Each one can be raced against the Aston Martin V8 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 Aston Martin V8 Coupe is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 6 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.