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

Toyota C-HR 2.0 CVT 184

The Toyota C-HR 2.0 CVT 184 reaches 60 mph in 7.33 s (100 km/h in 7.84 s) and covers a standing quarter mile in 15.85 s, tripping the lights at 85.2 mph. It clears the first 60 ft in 2.47 s and the eighth mile in 10.12 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.

Toyota C-HR 2.0 CVT 184 Gwm Ora 03 (Funky Cat) 03 GT 63kWh

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 Toyota C-HR 2.0 CVT 184
0–60 mph7.33 s
0–100 km/h7.84 s
0–100 mph—
60 ft2.47 s
1/8 mile10.12 s
1/4 mile15.85 s
Trap speed85.2 mph

About the C-HR 2.0 CVT 184

The 2020 Toyota C-HR 2.0 CVT 184 is a front-drive naturally aspirated SUV of 1,485 kg with 150 bhp, which works out at 101 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.47 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 5,223rd quickest to 60 mph, and the 44th quickest of the 311 Toyotas here. It leaves better than it pulls: 85.2 mph at the lights is only the 7,151st 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 Toyota C-HR 2.0 CVT 184
Year2020
Power150 hp (112 kW)
Kerb mass1,485 kg
Power to weight101 bhp/t
DrivetrainFront drive
Gears1
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Gwm Ora 03 (Funky Cat) 03 GT 63kWh20247.31 s15.93 s83.3 mph169 bhp
Gwm Ora 03 (Funky Cat) 03 Pro / Pro+ 63kWh20237.31 s15.94 s83.2 mph169 bhp
Volvo XC60 2.4 D5 18520087.39 s15.78 s85.4 mph182 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 8 seconds6,514 cars0-100 km/h under 8 seconds5,602 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Toyota 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 Toyota C-HR 2.0 CVT 184 0-60 time?
The Toyota C-HR 2.0 CVT 184 reaches 60 mph in 7.33 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 5,223rd quickest of the 14,946 cars in the set.
What is the Toyota C-HR 2.0 CVT 184 quarter mile time?
15.85 s at 85.2 mph. It reaches the eighth mile in 10.12 s and clears the first 60 ft in 2.47 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Toyota C-HR 2.0 CVT 184 have?
150 bhp and 1,485 kg, which is 101 bhp per tonne. It is front-drive, naturally aspirated, with 1 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Toyota C-HR 2.0 CVT 184?
Closest here on pace: Gwm Ora 03 (Funky Cat) 03 GT 63kWh (7.31 s), Gwm Ora 03 (Funky Cat) 03 Pro / Pro+ 63kWh (7.31 s), Volvo XC60 2.4 D5 185 (7.39 s). Each one can be raced against the Toyota C-HR 2.0 CVT 184 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 Toyota C-HR 2.0 CVT 184 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.