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

Honda CR-V 1.6 i-DTEC 160

The Honda CR-V 1.6 i-DTEC 160 reaches 60 mph in 8.18 s (100 km/h in 9.22 s) and covers a standing quarter mile in 16.35 s, tripping the lights at 82.4 mph. It clears the first 60 ft in 2.32 s and the eighth mile in 10.42 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.

Honda CR-V 1.6 i-DTEC 160 Mazda CX-5 2.2 Skyactiv-D 150

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 Honda CR-V 1.6 i-DTEC 160
0–60 mph8.18 s
0–100 km/h9.22 s
0–100 mph—
60 ft2.32 s
1/8 mile10.42 s
1/4 mile16.35 s
Trap speed82.4 mph

About the CR-V 1.6 i-DTEC 160

The 2015 Honda CR-V 1.6 i-DTEC 160 is an all-wheel-drive turbodiesel SUV of 1,630 kg with 158 bhp, which works out at 97 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.32 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 6,864th quickest to 60 mph, and the 58th quickest of the 191 Hondas here. It leaves better than it pulls: 82.4 mph at the lights is only the 8,693rd 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 Honda CR-V 1.6 i-DTEC 160
Year2015
Power158 hp (118 kW)
Kerb mass1,630 kg
Power to weight97 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed125 mph (201 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda CX-5 2.2 Skyactiv-D 15020168.19 s16.36 s82.4 mph148 bhp
Skoda Karoq 2.0 TDI 14320178.17 s16.37 s84.2 mph141 bhp
Holden Captiva 2.2 DSL 18420118.19 s16.36 s82.4 mph181 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
Honda 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 Honda CR-V 1.6 i-DTEC 160 0-60 time?
The Honda CR-V 1.6 i-DTEC 160 reaches 60 mph in 8.18 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,864th quickest of the 14,946 cars in the set.
What is the Honda CR-V 1.6 i-DTEC 160 quarter mile time?
16.35 s at 82.4 mph. It reaches the eighth mile in 10.42 s and clears the first 60 ft in 2.32 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda CR-V 1.6 i-DTEC 160 have?
158 bhp and 1,630 kg, which is 97 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 201 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda CR-V 1.6 i-DTEC 160?
Closest here on pace: Mazda CX-5 2.2 Skyactiv-D 150 (8.19 s), Skoda Karoq 2.0 TDI 143 (8.17 s), Holden Captiva 2.2 DSL 184 (8.19 s). Each one can be raced against the Honda CR-V 1.6 i-DTEC 160 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 Honda CR-V 1.6 i-DTEC 160 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.