← My Auto Racer All cars Suzuki 0-60 Comparisons
The Suzuki Swift 1.2 Dualjet reaches 60 mph in 10.85 s and covers a standing quarter mile in 18.16 s, tripping the lights at 77.7 mph. It clears the first 60 ft in 3.09 s and the eighth mile in 11.82 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 | Suzuki Swift 1.2 Dualjet |
|---|---|
| 0–60 mph | 10.85 s |
| 0–100 mph | — |
| 60 ft | 3.09 s |
| 1/8 mile | 11.82 s |
| 1/4 mile | 18.16 s |
| Trap speed | 77.7 mph |
The 2017 Suzuki Swift 1.2 Dualjet is a front-drive naturally aspirated car of 890 kg with 89 bhp, which works out at 99 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.09 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,906th quickest to 60 mph. Its 77.7 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 2 of 2 published acceleration figures for this car.
| Specification | Suzuki Swift 1.2 Dualjet |
|---|---|
| Year | 2017 |
| Power | 89 bhp |
| Kerb mass | 890 kg |
| Power to weight | 99 bhp/t |
| Drivetrain | Front drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 180 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Dacia Sandero 1.0 TCe 90 | 2021 | 10.78 s | 17.92 s | 76.4 mph | 90 bhp |
| De Lorean DMC-12 USA spec | 1978 | 9.84 s | 17.75 s | 82.3 mph | 129 bhp |
| Volkswagen Polo 1.0 TSI 95 | 2022 | 9.92 s | 17.45 s | 78.8 mph | 94 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.