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

Honda HR-V 1.6 i-DTEC 120

The Honda HR-V 1.6 i-DTEC 120 reaches 60 mph in 9.56 s (100 km/h in 10.11 s) and covers a standing quarter mile in 17.10 s, tripping the lights at 80.6 mph. It clears the first 60 ft in 2.57 s and the eighth mile in 10.99 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 HR-V 1.6 i-DTEC 120 Fiat 500X 1.6 120

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 HR-V 1.6 i-DTEC 120
0–60 mph9.56 s
0–100 km/h10.11 s
0–100 mph—
60 ft2.57 s
1/8 mile10.99 s
1/4 mile17.10 s
Trap speed80.6 mph

About the HR-V 1.6 i-DTEC 120

The 2018 Honda HR-V 1.6 i-DTEC 120 is a front-drive turbodiesel SUV of 1,406 kg with 118 bhp, which works out at 84 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.57 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 9,373rd quickest to 60 mph, and the 102nd quickest of the 191 Hondas here. Its 80.6 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 HR-V 1.6 i-DTEC 120
Year2018
Power118 hp (88 kW)
Kerb mass1,406 kg
Power to weight84 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed117 mph (188 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Fiat 500X 1.6 12020159.56 s17.11 s80.6 mph118 bhp
Dodge Nitro 2.8 CRD 16320069.53 s17.11 s80.0 mph161 bhp
SEAT Ateca 1.6 TDI 11520169.55 s17.14 s80.4 mph114 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.

Head to head

Honda CR-V 2.0 i-VTEC 155 (2016) vs Honda HR-V 1.6 i-DTEC 120Full comparisonSEAT Ateca 1.4 TSI 150 vs Honda HR-V 1.6 i-DTEC 120Full comparison

Where these times sit

0-60 under 10 seconds10,136 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 HR-V 1.6 i-DTEC 120 0-60 time?
The Honda HR-V 1.6 i-DTEC 120 reaches 60 mph in 9.56 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,373rd quickest of the 14,946 cars in the set.
What is the Honda HR-V 1.6 i-DTEC 120 quarter mile time?
17.10 s at 80.6 mph. It reaches the eighth mile in 10.99 s and clears the first 60 ft in 2.57 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda HR-V 1.6 i-DTEC 120 have?
118 bhp and 1,406 kg, which is 84 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 188 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda HR-V 1.6 i-DTEC 120?
Closest here on pace: Fiat 500X 1.6 120 (9.56 s), Dodge Nitro 2.8 CRD 163 (9.53 s), SEAT Ateca 1.6 TDI 115 (9.55 s). Each one can be raced against the Honda HR-V 1.6 i-DTEC 120 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 HR-V 1.6 i-DTEC 120 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.