← My Auto Racer All cars Alpine 0-60 Comparisons
The Alpine A110 Mk II reaches 60 mph in 3.96 s and covers a standing quarter mile in 12.52 s, tripping the lights at 110.5 mph. It clears the first 60 ft in 1.96 s and the eighth mile in 8.06 s, reaching 100 mph in 9.95 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 | Alpine A110 Mk II |
|---|---|
| 0–60 mph | 3.96 s |
| 0–100 mph | 9.95 s |
| 60 ft | 1.96 s |
| 1/8 mile | 8.06 s |
| 1/4 mile | 12.52 s |
| Trap speed | 110.5 mph |
The 2017 Alpine A110 Mk II is a rear-drive turbocharged car of 1,080 kg with 248 bhp, which works out at 230 bhp per tonne. Rear drive and 230 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.96 s. Against the 2,929 cars in the set it is the 774th quickest to 60 mph, and the 4th quickest of the 4 Alpines here. It leaves better than it pulls: 110.5 mph at the lights is only the 1,000th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 9 of 10 published acceleration figures for this car.
| Specification | Alpine A110 Mk II |
|---|---|
| Year | 2017 |
| Power | 248 bhp |
| Kerb mass | 1,080 kg |
| Power to weight | 230 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 255 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| VW Golf R MK VIII facelift | 2025 | 3.98 s | 12.55 s | 110.2 mph | 329 bhp |
| BMW M140i | 2016 | 3.90 s | 12.38 s | 111.0 mph | 335 bhp |
| Shelby Series 1 | 1998 | 4.00 s | 12.67 s | 111.0 mph | 321 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.