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

Dacia Duster 1.5 dCi 90 (2017)

The Dacia Duster 1.5 dCi 90 (2017) reaches 60 mph in 12.43 s (100 km/h in 13.34 s) and covers a standing quarter mile in 18.86 s, tripping the lights at 72.0 mph. It clears the first 60 ft in 2.75 s and the eighth mile in 12.01 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 Duster 1.5 dCi 90 (2017) Holden Captiva MaXX 2.0 CDTI 126

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 Duster 1.5 dCi 90 (2017)
0–60 mph12.43 s
0–100 km/h13.34 s
0–100 mph—
60 ft2.75 s
1/8 mile12.01 s
1/4 mile18.86 s
Trap speed72.0 mph

About the Duster 1.5 dCi 90

The 2017 Dacia Duster 1.5 dCi 90 (2017) is a front-drive turbodiesel SUV of 1,280 kg with 89 bhp, which works out at 69 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.75 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,189th quickest to 60 mph, and the 51st quickest of the 93 Dacias here. Its 72.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 Dacia Duster 1.5 dCi 90 (2017)
Year2017
Power89 hp (66 kW)
Kerb mass1,280 kg
Power to weight69 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed98 mph (158 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Holden Captiva MaXX 2.0 CDTI 126200612.44 s18.94 s72.4 mph125 bhp
Land Rover Range Rover 2.9 TD V6 177200512.28 s18.90 s73.5 mph174 bhp
Land Rover Range Rover 2.9 V6 TD 177200212.28 s18.90 s73.5 mph174 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 SUVs2,049 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 Dacia Duster 1.5 dCi 90 (2017) 0-60 time?
The Dacia Duster 1.5 dCi 90 (2017) reaches 60 mph in 12.43 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 13,189th quickest of the 14,946 cars in the set.
What is the Dacia Duster 1.5 dCi 90 (2017) quarter mile time?
18.86 s at 72.0 mph. It reaches the eighth mile in 12.01 s and clears the first 60 ft in 2.75 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Dacia Duster 1.5 dCi 90 (2017) have?
89 bhp and 1,280 kg, which is 69 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 158 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Dacia Duster 1.5 dCi 90 (2017)?
Closest here on pace: Holden Captiva MaXX 2.0 CDTI 126 (12.44 s), Land Rover Range Rover 2.9 TD V6 177 (12.28 s), Land Rover Range Rover 2.9 V6 TD 177 (12.28 s). Each one can be raced against the Dacia Duster 1.5 dCi 90 (2017) 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 Duster 1.5 dCi 90 (2017) 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.