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

Dacia Duster 1.2 TCe 125 (2013)

The Dacia Duster 1.2 TCe 125 (2013) reaches 60 mph in 10.57 s (100 km/h in 11.28 s) and covers a standing quarter mile in 17.90 s, tripping the lights at 76.3 mph. It clears the first 60 ft in 2.64 s and the eighth mile in 11.43 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.2 TCe 125 (2013) Mitsubishi ASX 2.0 MIVEC CVT

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.2 TCe 125 (2013)
0–60 mph10.57 s
0–100 km/h11.28 s
0–100 mph—
60 ft2.64 s
1/8 mile11.43 s
1/4 mile17.90 s
Trap speed76.3 mph

About the Duster 1.2 TCe 125

The 2013 Dacia Duster 1.2 TCe 125 (2013) is a front-drive turbocharged SUV of 1,277 kg with 123 bhp, which works out at 97 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.64 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,085th quickest to 60 mph, and the 16th quickest of the 93 Dacias here. It leaves better than it pulls: 76.3 mph at the lights is only the 12,020th 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.2 TCe 125 (2013)
Year2013
Power123 hp (92 kW)
Kerb mass1,277 kg
Power to weight97 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed101 mph (163 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mitsubishi ASX 2.0 MIVEC CVT202010.56 s17.87 s77.9 mph148 bhp
Jeep Wrangler JK Unlimited 2.8 CRD 177200710.54 s17.90 s77.0 mph174 bhp
Daewoo Winstorm 2.4 141200610.47 s17.94 s78.1 mph139 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.2 TCe 125 (2013) 0-60 time?
The Dacia Duster 1.2 TCe 125 (2013) reaches 60 mph in 10.57 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,085th quickest of the 14,946 cars in the set.
What is the Dacia Duster 1.2 TCe 125 (2013) quarter mile time?
17.90 s at 76.3 mph. It reaches the eighth mile in 11.43 s and clears the first 60 ft in 2.64 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Dacia Duster 1.2 TCe 125 (2013) have?
123 bhp and 1,277 kg, which is 97 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 163 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Dacia Duster 1.2 TCe 125 (2013)?
Closest here on pace: Mitsubishi ASX 2.0 MIVEC CVT (10.56 s), Jeep Wrangler JK Unlimited 2.8 CRD 177 (10.54 s), Daewoo Winstorm 2.4 141 (10.47 s). Each one can be raced against the Dacia Duster 1.2 TCe 125 (2013) 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.2 TCe 125 (2013) 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.