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

Dacia Sandero Stepway 1.5 dCi 70

The Dacia Sandero Stepway 1.5 dCi 70 reaches 60 mph in 13.57 s (100 km/h in 15.21 s) and covers a standing quarter mile in 19.49 s, tripping the lights at 70.2 mph. It clears the first 60 ft in 3.04 s and the eighth mile in 12.45 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.

Dacia Sandero Stepway 1.5 dCi 70 Holden Astra 5dr 1.7 CDTI 80

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 Dacia Sandero Stepway 1.5 dCi 70
0–60 mph13.57 s
0–100 km/h15.21 s
0–100 mph—
60 ft3.04 s
1/8 mile12.45 s
1/4 mile19.49 s
Trap speed70.2 mph

About the Sandero Stepway 1.5 dCi 70

The 2009 Dacia Sandero Stepway 1.5 dCi 70 is a front-drive turbodiesel car of 1,141 kg with 67 bhp, which works out at 59 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.04 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 13,921st quickest to 60 mph, and the 67th quickest of the 93 Dacias here. Its 70.2 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 Dacia Sandero Stepway 1.5 dCi 70
Year2009
Power67 hp (50 kW)
Kerb mass1,141 kg
Power to weight59 bhp/t
DrivetrainFront drive
Gears5
EngineTurbodiesel
Top speed98 mph (157 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Holden Astra 5dr 1.7 CDTI 80200513.55 s19.52 s70.6 mph79 bhp
Tata Motors Indica 1.4 60199813.58 s19.43 s71.3 mph59 bhp
Chevrolet Matiz / Spark (M300) 1.0 62200913.43 s19.40 s70.2 mph62 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
Dacia 0-60 timesevery modelFastest small cars1,681 carsFastest cars of the 2000s5,138 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 Dacia Sandero Stepway 1.5 dCi 70 0-60 time?
The Dacia Sandero Stepway 1.5 dCi 70 reaches 60 mph in 13.57 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 13,921st quickest of the 14,946 cars in the set.
What is the Dacia Sandero Stepway 1.5 dCi 70 quarter mile time?
19.49 s at 70.2 mph. It reaches the eighth mile in 12.45 s and clears the first 60 ft in 3.04 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Dacia Sandero Stepway 1.5 dCi 70 have?
67 bhp and 1,141 kg, which is 59 bhp per tonne. It is front-drive, turbodiesel, with 5 gears and a quoted top speed of 157 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Dacia Sandero Stepway 1.5 dCi 70?
Closest here on pace: Holden Astra 5dr 1.7 CDTI 80 (13.55 s), Tata Motors Indica 1.4 60 (13.58 s), Chevrolet Matiz / Spark (M300) 1.0 62 (13.43 s). Each one can be raced against the Dacia Sandero Stepway 1.5 dCi 70 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 Dacia Sandero Stepway 1.5 dCi 70 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.