← My Auto Racer All cars Abarth 0-60 Comparisons
The Abarth Grande Punto reaches 60 mph in 7.45 s and covers a standing quarter mile in 15.88 s, tripping the lights at 88.1 mph. It clears the first 60 ft in 2.55 s and the eighth mile in 10.29 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 Grande Punto |
|---|---|
| 0–60 mph | 7.45 s |
| 0–100 mph | — |
| 60 ft | 2.55 s |
| 1/8 mile | 10.29 s |
| 1/4 mile | 15.88 s |
| Trap speed | 88.1 mph |
The 2007 Abarth Grande Punto is a front-drive turbocharged car of 1,258 kg with 153 bhp, which works out at 122 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.55 s — so most of what it has to give arrives once it is already moving. Against the 2,929 cars in the set it is the 2,511th quickest to 60 mph, and the 4th quickest of the 6 Abarths here. Its 88.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 9 of 9 published acceleration figures for this car.
| Specification | Abarth Grande Punto |
|---|---|
| Year | 2007 |
| Power | 153 bhp |
| Kerb mass | 1,258 kg |
| Power to weight | 122 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 208 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Seat Leon 1.5 TSI 150 (Mk4) | 2020 | 7.61 s | 15.89 s | 89.3 mph | 148 bhp |
| Seat Leon 2.0 TDI 150 (Mk3) | 2013 | 7.61 s | 15.93 s | 87.4 mph | 148 bhp |
| Merkur XR4Ti | 1984 | 7.53 s | 15.69 s | 90.2 mph | 170 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.