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

Suzuki SX4 S-Cross 1.6 120

The Suzuki SX4 S-Cross 1.6 120 reaches 60 mph in 11.69 s (100 km/h in 12.53 s) and covers a standing quarter mile in 18.38 s, tripping the lights at 73.6 mph. It clears the first 60 ft in 2.73 s and the eighth mile in 11.70 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 SX4 S-Cross 1.6 120 Chevrolet Matiz / Spark (M150) 1.0 64

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 SX4 S-Cross 1.6 120
0–60 mph11.69 s
0–100 km/h12.53 s
0–100 mph—
60 ft2.73 s
1/8 mile11.70 s
1/4 mile18.38 s
Trap speed73.6 mph

About the SX4 S-Cross 1.6 120

The 2016 Suzuki SX4 S-Cross 1.6 120 is an all-wheel-drive turbodiesel car of 1,430 kg with 118 bhp, which works out at 83 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.73 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 12,477th quickest to 60 mph, and the 54th quickest of the 93 Suzukis here. Its 73.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 2 of 2 published acceleration figures for this car.

On paper

Specification Suzuki SX4 S-Cross 1.6 120
Year2016
Power118 hp (88 kW)
Kerb mass1,430 kg
Power to weight83 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed109 mph (175 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chevrolet Matiz / Spark (M150) 1.0 64200011.67 s18.40 s74.6 mph63 bhp
Lada Kalina Hatchback 1.6 TDCi 90200711.71 s18.54 s73.7 mph89 bhp
Subaru Trezia 1.4D 90201011.70 s18.40 s73.7 mph89 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 4x4s and all-wheel-drive cars2,981 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 SX4 S-Cross 1.6 120 0-60 time?
The Suzuki SX4 S-Cross 1.6 120 reaches 60 mph in 11.69 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 12,477th quickest of the 14,946 cars in the set.
What is the Suzuki SX4 S-Cross 1.6 120 quarter mile time?
18.38 s at 73.6 mph. It reaches the eighth mile in 11.70 s and clears the first 60 ft in 2.73 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Suzuki SX4 S-Cross 1.6 120 have?
118 bhp and 1,430 kg, which is 83 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 175 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Suzuki SX4 S-Cross 1.6 120?
Closest here on pace: Chevrolet Matiz / Spark (M150) 1.0 64 (11.67 s), Lada Kalina Hatchback 1.6 TDCi 90 (11.71 s), Subaru Trezia 1.4D 90 (11.70 s). Each one can be raced against the Suzuki SX4 S-Cross 1.6 120 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 SX4 S-Cross 1.6 120 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.