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

Honda HR-V 1.5 i-MMD e-CVT 131

The Honda HR-V 1.5 i-MMD e-CVT 131 reaches 60 mph in 9.51 s (100 km/h in 10.21 s) and covers a standing quarter mile in 17.28 s, tripping the lights at 78.3 mph. It clears the first 60 ft in 2.67 s and the eighth mile in 11.02 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.5 i-MMD e-CVT 131 Dacia Duster Blue dCi 115 (Mk2)

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.5 i-MMD e-CVT 131
0–60 mph9.51 s
0–100 km/h10.21 s
0–100 mph—
60 ft2.67 s
1/8 mile11.02 s
1/4 mile17.28 s
Trap speed78.3 mph

About the HR-V 1.5 i-MMD e-CVT 131

The 2022 Honda HR-V 1.5 i-MMD e-CVT 131 is a front-drive naturally aspirated SUV of 1,453 kg with 106 bhp, which works out at 73 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.67 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,289th quickest to 60 mph, and the 99th quickest of the 191 Hondas here. It leaves better than it pulls: 78.3 mph at the lights is only the 10,950th 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 HR-V 1.5 i-MMD e-CVT 131
Year2022
Power106 hp (79 kW)
Kerb mass1,453 kg
Power to weight73 bhp/t
DrivetrainFront drive
Gears1
EngineNaturally aspirated
Top speed106 mph (171 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dacia Duster Blue dCi 115 (Mk2)20189.47 s17.15 s80.9 mph113 bhp
SEAT Ateca 1.6 TDI 11520169.55 s17.14 s80.4 mph114 bhp
Dodge Nitro 2.8 CRD 16320069.53 s17.11 s80.0 mph161 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 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 2020s867 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.5 i-MMD e-CVT 131 0-60 time?
The Honda HR-V 1.5 i-MMD e-CVT 131 reaches 60 mph in 9.51 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,289th quickest of the 14,946 cars in the set.
What is the Honda HR-V 1.5 i-MMD e-CVT 131 quarter mile time?
17.28 s at 78.3 mph. It reaches the eighth mile in 11.02 s and clears the first 60 ft in 2.67 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda HR-V 1.5 i-MMD e-CVT 131 have?
106 bhp and 1,453 kg, which is 73 bhp per tonne. It is front-drive, naturally aspirated, with 1 gears and a quoted top speed of 171 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda HR-V 1.5 i-MMD e-CVT 131?
Closest here on pace: Dacia Duster Blue dCi 115 (Mk2) (9.47 s), SEAT Ateca 1.6 TDI 115 (9.55 s), Dodge Nitro 2.8 CRD 163 (9.53 s). Each one can be raced against the Honda HR-V 1.5 i-MMD e-CVT 131 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.5 i-MMD e-CVT 131 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.