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

Honda CR-V 2.2 CDTi 140

The Honda CR-V 2.2 CDTi 140 reaches 60 mph in 9.33 s (100 km/h in 9.90 s) and covers a standing quarter mile in 16.87 s, tripping the lights at 79.9 mph. It clears the first 60 ft in 2.37 s and the eighth mile in 10.72 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 2.2 CDTi 140 Skoda Kamiq 1.6 TDI 115

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 2.2 CDTi 140
0–60 mph9.33 s
0–100 km/h9.90 s
0–100 mph—
60 ft2.37 s
1/8 mile10.72 s
1/4 mile16.87 s
Trap speed79.9 mph

About the CR-V 2.2 CDTi 140

The 2007 Honda CR-V 2.2 CDTi 140 is an all-wheel-drive turbodiesel SUV of 1,617 kg with 138 bhp, which works out at 85 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.37 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 8,996th quickest to 60 mph, and the 95th quickest of the 191 Hondas here. It leaves better than it pulls: 79.9 mph at the lights is only the 10,073rd 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 2.2 CDTi 140
Year2007
Power138 hp (103 kW)
Kerb mass1,617 kg
Power to weight85 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed116 mph (187 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Skoda Kamiq 1.6 TDI 11520209.28 s16.85 s81.3 mph114 bhp
Jeep Compass 1.3 4x2 13020199.38 s16.95 s81.4 mph129 bhp
Land Rover Defender 110 2.0 SD4 20020209.23 s16.89 s78.6 mph197 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 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 Honda CR-V 2.2 CDTi 140 0-60 time?
The Honda CR-V 2.2 CDTi 140 reaches 60 mph in 9.33 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,996th quickest of the 14,946 cars in the set.
What is the Honda CR-V 2.2 CDTi 140 quarter mile time?
16.87 s at 79.9 mph. It reaches the eighth mile in 10.72 s and clears the first 60 ft in 2.37 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda CR-V 2.2 CDTi 140 have?
138 bhp and 1,617 kg, which is 85 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 187 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda CR-V 2.2 CDTi 140?
Closest here on pace: Skoda Kamiq 1.6 TDI 115 (9.28 s), Jeep Compass 1.3 4x2 130 (9.38 s), Land Rover Defender 110 2.0 SD4 200 (9.23 s). Each one can be raced against the Honda CR-V 2.2 CDTi 140 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 2.2 CDTi 140 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.