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

Renault Koleos 2.0 dCI 4x2 150

The Renault Koleos 2.0 dCI 4x2 150 reaches 60 mph in 9.11 s (100 km/h in 9.62 s) and covers a standing quarter mile in 16.87 s, tripping the lights at 82.1 mph. It clears the first 60 ft in 2.54 s and the eighth mile in 10.85 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.

Renault Koleos 2.0 dCI 4x2 150 Skoda Yeti 1.4 TSI 125

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 Renault Koleos 2.0 dCI 4x2 150
0–60 mph9.11 s
0–100 km/h9.62 s
0–100 mph—
60 ft2.54 s
1/8 mile10.85 s
1/4 mile16.87 s
Trap speed82.1 mph

About the Koleos 2.0 dCI 4x2 150

The 2011 Renault Koleos 2.0 dCI 4x2 150 is a front-drive turbodiesel SUV of 1,649 kg with 148 bhp, which works out at 89 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.54 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 8,615th quickest to 60 mph, and the 137th quickest of the 499 Renaults here. Its 82.1 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 Renault Koleos 2.0 dCI 4x2 150
Year2011
Power148 hp (110 kW)
Kerb mass1,649 kg
Power to weight89 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed114 mph (183 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Skoda Yeti 1.4 TSI 12520139.10 s16.92 s80.8 mph123 bhp
Land Rover Defender 90 2.0 SD4 20020199.14 s16.83 s78.9 mph197 bhp
Honda HR-V 5dr 1.6 i-DTEC 12020149.12 s16.78 s82.4 mph118 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

0-60 under 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Renault 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 Renault Koleos 2.0 dCI 4x2 150 0-60 time?
The Renault Koleos 2.0 dCI 4x2 150 reaches 60 mph in 9.11 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,615th quickest of the 14,946 cars in the set.
What is the Renault Koleos 2.0 dCI 4x2 150 quarter mile time?
16.87 s at 82.1 mph. It reaches the eighth mile in 10.85 s and clears the first 60 ft in 2.54 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Renault Koleos 2.0 dCI 4x2 150 have?
148 bhp and 1,649 kg, which is 89 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 183 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Renault Koleos 2.0 dCI 4x2 150?
Closest here on pace: Skoda Yeti 1.4 TSI 125 (9.10 s), Land Rover Defender 90 2.0 SD4 200 (9.14 s), Honda HR-V 5dr 1.6 i-DTEC 120 (9.12 s). Each one can be raced against the Renault Koleos 2.0 dCI 4x2 150 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 Renault Koleos 2.0 dCI 4x2 150 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.