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

Honda CR-V 2.0 i-VTEC 2WD 155

The Honda CR-V 2.0 i-VTEC 2WD 155 reaches 60 mph in 9.11 s (100 km/h in 9.63 s) and covers a standing quarter mile in 16.84 s, tripping the lights at 82.8 mph. It clears the first 60 ft in 2.62 s and the eighth mile in 10.89 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.0 i-VTEC 2WD 155 Mitsubishi Grandis 2.4 165

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.0 i-VTEC 2WD 155
0–60 mph9.11 s
0–100 km/h9.63 s
0–100 mph—
60 ft2.62 s
1/8 mile10.89 s
1/4 mile16.84 s
Trap speed82.8 mph

About the CR-V 2.0 i-VTEC 2WD 155

The 2011 Honda CR-V 2.0 i-VTEC 2WD 155 is a front-drive naturally aspirated SUV of 1,527 kg with 153 bhp, which works out at 100 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.62 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,619th quickest to 60 mph, and the 84th quickest of the 191 Hondas here. Its 82.8 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 Honda CR-V 2.0 i-VTEC 2WD 155
Year2011
Power153 hp (114 kW)
Kerb mass1,527 kg
Power to weight100 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed118 mph (190 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mitsubishi Grandis 2.4 16520059.12 s16.93 s83.8 mph162 bhp
Land Rover Discovery Sport 2.2 SD4 19020149.15 s16.74 s80.5 mph186 bhp
Renault Koleos 2.5 4x2 17020119.11 s16.89 s82.4 mph169 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 2.0 i-VTEC 2WD 155 0-60 time?
The Honda CR-V 2.0 i-VTEC 2WD 155 reaches 60 mph in 9.11 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,619th quickest of the 14,946 cars in the set.
What is the Honda CR-V 2.0 i-VTEC 2WD 155 quarter mile time?
16.84 s at 82.8 mph. It reaches the eighth mile in 10.89 s and clears the first 60 ft in 2.62 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda CR-V 2.0 i-VTEC 2WD 155 have?
153 bhp and 1,527 kg, which is 100 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 190 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda CR-V 2.0 i-VTEC 2WD 155?
Closest here on pace: Mitsubishi Grandis 2.4 165 (9.12 s), Land Rover Discovery Sport 2.2 SD4 190 (9.15 s), Renault Koleos 2.5 4x2 170 (9.11 s). Each one can be raced against the Honda CR-V 2.0 i-VTEC 2WD 155 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.0 i-VTEC 2WD 155 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.