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

Toyota C-HR 2.0 CVT 198

The Toyota C-HR 2.0 CVT 198 reaches 60 mph in 7.05 s (100 km/h in 7.56 s) and covers a standing quarter mile in 15.62 s, tripping the lights at 85.2 mph. It clears the first 60 ft in 2.32 s and the eighth mile in 9.88 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 198 Deepal S07 79.97kWh

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 198
0–60 mph7.05 s
0–100 km/h7.56 s
0–100 mph—
60 ft2.32 s
1/8 mile9.88 s
1/4 mile15.62 s
Trap speed85.2 mph

About the C-HR 2.0 CVT 198

The 2024 Toyota C-HR 2.0 CVT 198 is an all-wheel-drive naturally aspirated SUV of 1,560 kg with 150 bhp, which works out at 96 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.32 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 4,761st quickest to 60 mph, and the 40th quickest of the 311 Toyotas here. It leaves better than it pulls: 85.2 mph at the lights is only the 7,179th 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 198
Year2024
Power150 hp (112 kW)
Kerb mass1,560 kg
Power to weight96 bhp/t
DrivetrainAll-wheel drive
Gears1
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Deepal S07 79.97kWh20257.05 s15.62 s85.2 mph215 bhp
BMW X4 xDrive20d 48V 19020217.06 s15.46 s87.3 mph188 bhp
Mercedes-Benz ML-Class (W163) 270 CDI 16320017.08 s15.61 s88.4 mph247 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 198 0-60 time?
The Toyota C-HR 2.0 CVT 198 reaches 60 mph in 7.05 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,761st quickest of the 14,946 cars in the set.
What is the Toyota C-HR 2.0 CVT 198 quarter mile time?
15.62 s at 85.2 mph. It reaches the eighth mile in 9.88 s and clears the first 60 ft in 2.32 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Toyota C-HR 2.0 CVT 198 have?
150 bhp and 1,560 kg, which is 96 bhp per tonne. It is all-wheel-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 198?
Closest here on pace: Deepal S07 79.97kWh (7.05 s), BMW X4 xDrive20d 48V 190 (7.06 s), Mercedes-Benz ML-Class (W163) 270 CDI 163 (7.08 s). Each one can be raced against the Toyota C-HR 2.0 CVT 198 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 198 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.