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

Dacia Duster 1.5 dCi 110 (2010)

The Dacia Duster 1.5 dCi 110 (2010) reaches 60 mph in 11.27 s (100 km/h in 12.05 s) and covers a standing quarter mile in 18.14 s, tripping the lights at 74.2 mph. It clears the first 60 ft in 2.56 s and the eighth mile in 11.51 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 110 (2010) MG ZS 1.0T GDI 111

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 110 (2010)
0–60 mph11.27 s
0–100 km/h12.05 s
0–100 mph—
60 ft2.56 s
1/8 mile11.51 s
1/4 mile18.14 s
Trap speed74.2 mph

About the Duster 1.5 dCi 110

The 2010 Dacia Duster 1.5 dCi 110 (2010) is an all-wheel-drive turbodiesel SUV of 1,294 kg with 107 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.56 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,002nd quickest to 60 mph, and the 27th quickest of the 93 Dacias here. It leaves better than it pulls: 74.2 mph at the lights is only the 12,968th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Dacia Duster 1.5 dCi 110 (2010)
Year2010
Power107 hp (80 kW)
Kerb mass1,294 kg
Power to weight83 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed104 mph (167 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
MG ZS 1.0T GDI 111201711.29 s18.30 s75.7 mph110 bhp
Ssangyong Rexton 2.3 150200111.29 s18.46 s76.1 mph148 bhp
Daewoo Winstorm 2.0 D 152200611.30 s18.34 s75.8 mph150 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 110 (2010) 0-60 time?
The Dacia Duster 1.5 dCi 110 (2010) reaches 60 mph in 11.27 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 12,002nd quickest of the 14,946 cars in the set.
What is the Dacia Duster 1.5 dCi 110 (2010) quarter mile time?
18.14 s at 74.2 mph. It reaches the eighth mile in 11.51 s and clears the first 60 ft in 2.56 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Dacia Duster 1.5 dCi 110 (2010) have?
107 bhp and 1,294 kg, which is 83 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 167 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Dacia Duster 1.5 dCi 110 (2010)?
Closest here on pace: MG ZS 1.0T GDI 111 (11.29 s), Ssangyong Rexton 2.3 150 (11.29 s), Daewoo Winstorm 2.0 D 152 (11.30 s). Each one can be raced against the Dacia Duster 1.5 dCi 110 (2010) 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 110 (2010) 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.