← My Auto Racer All cars Fiat 0-60 Comparisons Answers
The Fiat Uno Turbo Mk I reaches 60 mph in 8.66 s and covers a standing quarter mile in 16.59 s, tripping the lights at 88.0 mph. It clears the first 60 ft in 2.86 s and the eighth mile in 10.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 | Fiat Uno Turbo Mk I |
|---|---|
| 0–60 mph | 8.66 s |
| 0–100 mph | — |
| 60 ft | 2.86 s |
| 1/8 mile | 10.95 s |
| 1/4 mile | 16.59 s |
| Trap speed | 88.0 mph |
The 1985 Fiat Uno Turbo Mk I is a front-drive naturally aspirated car of 845 kg with 103 bhp, which works out at 122 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.86 s — so most of what it has to give arrives once it is already moving. Against the 2,939 cars in the set it is the 2,760th quickest to 60 mph, and the 12th quickest of the 14 Fiats here. Its 88.0 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 7 of 9 published acceleration figures for this car.
| Specification | Fiat Uno Turbo Mk I |
|---|---|
| Year | 1985 |
| Power | 103 bhp |
| Kerb mass | 845 kg |
| Power to weight | 122 bhp/t |
| Drivetrain | Front drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 199 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Daihatsu Charade GTti UK spec | 1987 | 8.74 s | 16.72 s | 83.6 mph | 99 bhp |
| Isuzu Piazza Turbo | 1985 | 8.57 s | 16.51 s | 86.0 mph | 148 bhp |
| Ford Focus 2.0 16v | 2005 | 8.56 s | 16.72 s | 84.4 mph | 143 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-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.