← My Auto Racer All cars Suzuki 0-60 Comparisons Answers

Suzuki Baleno 1.2 DUALJET SHVS 90

The Suzuki Baleno 1.2 DUALJET SHVS 90 reaches 60 mph in 11.22 s (100 km/h in 11.88 s) and covers a standing quarter mile in 18.39 s, tripping the lights at 77.0 mph. It clears the first 60 ft in 3.15 s and the eighth mile in 11.99 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.

Suzuki Baleno 1.2 DUALJET SHVS 90 Subaru Impreza 5dr 1.6 114

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start Suzuki Baleno 1.2 DUALJET SHVS 90
0–60 mph11.22 s
0–100 km/h11.88 s
0–100 mph—
60 ft3.15 s
1/8 mile11.99 s
1/4 mile18.39 s
Trap speed77.0 mph

About the Baleno 1.2 DUALJET SHVS 90

The 2016 Suzuki Baleno 1.2 DUALJET SHVS 90 is a front-drive naturally aspirated car of 990 kg with 89 bhp, which works out at 89 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.15 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 11,925th quickest to 60 mph, and the 44th quickest of the 93 Suzukis here. Its 77.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 2 of 2 published acceleration figures for this car.

On paper

Specification Suzuki Baleno 1.2 DUALJET SHVS 90
Year2016
Power89 hp (66 kW)
Kerb mass990 kg
Power to weight89 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Subaru Impreza 5dr 1.6 114201211.23 s18.37 s77.4 mph113 bhp
Chevrolet Classic 1.4 99200211.21 s18.40 s76.6 mph98 bhp
Subaru Impreza 4dr 1.6 114201211.23 s18.37 s77.6 mph114 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.

Where these times sit

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Suzuki 0-60 timesevery modelFastest small cars1,681 carsFastest cars of the 2010s4,541 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the Suzuki Baleno 1.2 DUALJET SHVS 90 0-60 time?
The Suzuki Baleno 1.2 DUALJET SHVS 90 reaches 60 mph in 11.22 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,925th quickest of the 14,946 cars in the set.
What is the Suzuki Baleno 1.2 DUALJET SHVS 90 quarter mile time?
18.39 s at 77.0 mph. It reaches the eighth mile in 11.99 s and clears the first 60 ft in 3.15 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Suzuki Baleno 1.2 DUALJET SHVS 90 have?
89 bhp and 990 kg, which is 89 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Suzuki Baleno 1.2 DUALJET SHVS 90?
Closest here on pace: Subaru Impreza 5dr 1.6 114 (11.23 s), Chevrolet Classic 1.4 99 (11.21 s), Subaru Impreza 4dr 1.6 114 (11.23 s). Each one can be raced against the Suzuki Baleno 1.2 DUALJET SHVS 90 in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The Suzuki Baleno 1.2 DUALJET SHVS 90 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

Figures regenerated 2026-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.