← My Auto Racer All cars Abarth 0-60 Comparisons
The Abarth 124 Spider reaches 60 mph in 6.18 s and covers a standing quarter mile in 14.80 s, tripping the lights at 91.7 mph. It clears the first 60 ft in 2.17 s and the eighth mile in 9.41 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 | Abarth 124 Spider |
|---|---|
| 0–60 mph | 6.18 s |
| 0–100 mph | — |
| 60 ft | 2.17 s |
| 1/8 mile | 9.41 s |
| 1/4 mile | 14.80 s |
| Trap speed | 91.7 mph |
The 2016 Abarth 124 Spider is a rear-drive turbocharged roadster of 1,060 kg with 168 bhp, which works out at 158 bhp per tonne. Rear drive and 158 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.17 s. Against the 2,929 cars in the set it is the 2,030th quickest to 60 mph, and the 2nd quickest of the 6 Abarths here. It leaves better than it pulls: 91.7 mph at the lights is only the 2,408th 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 | Abarth 124 Spider |
|---|---|
| Year | 2016 |
| Power | 168 bhp |
| Kerb mass | 1,060 kg |
| Power to weight | 158 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 232 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| MINI Roadster JCW | 2012 | 6.06 s | 14.64 s | 95.1 mph | 208 bhp |
| Mazda MX-5 2.0 (ND2) | 2019 | 6.00 s | 14.49 s | 95.1 mph | 181 bhp |
| Kia Stinger 2.0T 256 PS | 2017 | 6.13 s | 14.66 s | 96.0 mph | 255 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.