← My Auto Racer All cars Daihatsu 0-60 Comparisons
The Daihatsu Charade GTti UK spec reaches 60 mph in 8.74 s and covers a standing quarter mile in 16.72 s, tripping the lights at 83.6 mph. It clears the first 60 ft in 2.77 s and the eighth mile in 10.83 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 | Daihatsu Charade GTti UK spec |
|---|---|
| 0–60 mph | 8.74 s |
| 0–100 mph | — |
| 60 ft | 2.77 s |
| 1/8 mile | 10.83 s |
| 1/4 mile | 16.72 s |
| Trap speed | 83.6 mph |
The 1987 Daihatsu Charade GTti UK spec is a front-drive naturally aspirated car of 810 kg with 99 bhp, which works out at 123 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.77 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,766th quickest to 60 mph. Its 83.6 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 | Daihatsu Charade GTti UK spec |
|---|---|
| Year | 1987 |
| Power | 99 bhp |
| Kerb mass | 810 kg |
| Power to weight | 123 bhp/t |
| Drivetrain | Front drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 189 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Lada Priora TMS | 2010 | 8.75 s | 16.91 s | 84.7 mph | 122 bhp |
| Dacia Bigster Hybrid 155 PS | 2024 | 8.71 s | 16.77 s | 85.1 mph | 153 bhp |
| Isuzu Piazza Turbo | 1985 | 8.57 s | 16.51 s | 86.0 mph | 148 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.