← My Auto Racer All cars Alfa Romeo 0-60 Comparisons
The Alfa Romeo Giulia QV reaches 60 mph in 3.65 s and covers a standing quarter mile in 11.83 s, tripping the lights at 120.8 mph. It clears the first 60 ft in 1.94 s and the eighth mile in 7.72 s, reaching 100 mph in 8.27 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 | Alfa Romeo Giulia QV |
|---|---|
| 0–60 mph | 3.65 s |
| 0–100 mph | 8.27 s |
| 60 ft | 1.94 s |
| 1/8 mile | 7.72 s |
| 1/4 mile | 11.83 s |
| Trap speed | 120.8 mph |
The 2015 Alfa Romeo Giulia QV is a rear-drive turbocharged car of 1,733 kg with 503 bhp, which works out at 290 bhp per tonne. Rear drive and 290 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.94 s. Against the 2,929 cars in the set it is the 595th quickest to 60 mph, inside the fastest quarter, and the 3rd quickest of the 43 Alfa Romeos here. Its 120.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 | Alfa Romeo Giulia QV |
|---|---|
| Year | 2015 |
| Power | 503 bhp |
| Kerb mass | 1,733 kg |
| Power to weight | 290 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 309 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Alpine A110R | 2023 | 3.59 s | 12.00 s | 116.1 mph | 296 bhp |
| Lotus Emira Turbo SE | 2025 | 3.46 s | 11.87 s | 116.8 mph | 400 bhp |
| Morgan SuperSport | 2026 | 3.45 s | 11.96 s | 114.0 mph | 335 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.