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

Dacia Logan MCV 1.5 dCi 70 (2008)

The Dacia Logan MCV 1.5 dCi 70 (2008) reaches 60 mph in 16.04 s (100 km/h in 17.18 s) and covers a standing quarter mile in 20.33 s, tripping the lights at 67.3 mph. It clears the first 60 ft in 3.19 s and the eighth mile in 13.00 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 Logan MCV 1.5 dCi 70 (2008) Land Rover Discovery 2.5 113

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 Logan MCV 1.5 dCi 70 (2008)
0–60 mph16.04 s
0–100 km/h17.18 s
0–100 mph—
60 ft3.19 s
1/8 mile13.00 s
1/4 mile20.33 s
Trap speed67.3 mph

About the Logan MCV 1.5 dCi 70

The 2008 Dacia Logan MCV 1.5 dCi 70 (2008) is a front-drive turbodiesel SUV of 1,318 kg with 67 bhp, which works out at 51 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.19 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 14,624th quickest to 60 mph, and the 82nd quickest of the 93 Dacias here. Its 67.3 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 Logan MCV 1.5 dCi 70 (2008)
Year2008
Power67 hp (50 kW)
Kerb mass1,318 kg
Power to weight51 bhp/t
DrivetrainFront drive
Gears5
EngineTurbodiesel
Top speed93 mph (150 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Land Rover Discovery 2.5 113199016.12 s20.36 s67.1 mph111 bhp
Land Rover Discovery 3dr 2.5 TDI 113199016.12 s20.36 s67.1 mph111 bhp
Dacia Logan MCV 1.5 dCi 70 (2006)200616.04 s20.33 s67.3 mph67 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 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 Logan MCV 1.5 dCi 70 (2008) 0-60 time?
The Dacia Logan MCV 1.5 dCi 70 (2008) reaches 60 mph in 16.04 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 14,624th quickest of the 14,946 cars in the set.
What is the Dacia Logan MCV 1.5 dCi 70 (2008) quarter mile time?
20.33 s at 67.3 mph. It reaches the eighth mile in 13.00 s and clears the first 60 ft in 3.19 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Dacia Logan MCV 1.5 dCi 70 (2008) have?
67 bhp and 1,318 kg, which is 51 bhp per tonne. It is front-drive, turbodiesel, with 5 gears and a quoted top speed of 150 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Dacia Logan MCV 1.5 dCi 70 (2008)?
Closest here on pace: Land Rover Discovery 2.5 113 (16.12 s), Land Rover Discovery 3dr 2.5 TDI 113 (16.12 s), Dacia Logan MCV 1.5 dCi 70 (2006) (16.04 s). Each one can be raced against the Dacia Logan MCV 1.5 dCi 70 (2008) 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 Logan MCV 1.5 dCi 70 (2008) 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.