← My Auto Racer All cars Ford 0-60 Comparisons
The Ford Fiesta ST (Mk8) reaches 60 mph in 6.14 s and covers a standing quarter mile in 14.58 s, tripping the lights at 96.2 mph. It clears the first 60 ft in 2.29 s and the eighth mile in 9.49 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 | Ford Fiesta ST (Mk8) |
|---|---|
| 0–60 mph | 6.14 s |
| 0–100 mph | — |
| 60 ft | 2.29 s |
| 1/8 mile | 9.49 s |
| 1/4 mile | 14.58 s |
| Trap speed | 96.2 mph |
The 2019 Ford Fiesta ST (Mk8) is a front-drive turbocharged car of 1,262 kg with 197 bhp, which works out at 156 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.29 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,011th quickest to 60 mph, and the 50th quickest of the 109 Fords here. Its 96.2 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 10 published acceleration figures for this car.
| Specification | Ford Fiesta ST (Mk8) |
|---|---|
| Year | 2019 |
| Power | 197 bhp |
| Kerb mass | 1,262 kg |
| Power to weight | 156 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 232 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| MINI Clubman JCW Mk I | 2008 | 6.09 s | 14.66 s | 94.8 mph | 208 bhp |
| Citroen DS3 Racing | 2010 | 5.99 s | 14.57 s | 95.4 mph | 204 bhp |
| Abarth 500 EsseEsse | 2008 | 6.11 s | 14.81 s | 91.7 mph | 158 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.