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

Toyota C-HR 1.8 CVT 122 (2016)

The Toyota C-HR 1.8 CVT 122 (2016) reaches 60 mph in 9.87 s (100 km/h in 10.60 s) and covers a standing quarter mile in 17.50 s, tripping the lights at 77.5 mph. It clears the first 60 ft in 2.72 s and the eighth mile in 11.18 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 1.8 CVT 122 (2016) Toyota C-HR 1.8 CVT 122 (2020)

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 1.8 CVT 122 (2016)
0–60 mph9.87 s
0–100 km/h10.60 s
0–100 mph—
60 ft2.72 s
1/8 mile11.18 s
1/4 mile17.50 s
Trap speed77.5 mph

About the C-HR 1.8 CVT 122

The 2016 Toyota C-HR 1.8 CVT 122 (2016) is a front-drive naturally aspirated SUV of 1,420 kg with 97 bhp, which works out at 68 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.72 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,911th quickest to 60 mph, and the 144th quickest of the 311 Toyotas here. It leaves better than it pulls: 77.5 mph at the lights is only the 11,378th 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 1.8 CVT 122 (2016)
Year2016
Power97 hp (72 kW)
Kerb mass1,420 kg
Power to weight68 bhp/t
DrivetrainFront drive
Gears1
EngineNaturally aspirated
Top speed106 mph (171 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Toyota C-HR 1.8 CVT 122 (2020)20209.87 s17.50 s77.5 mph97 bhp
Skoda Roomster 1.2 TSI 10520109.88 s17.43 s78.9 mph103 bhp
Skoda Yeti 1.2 TSI 11020139.90 s17.39 s79.1 mph109 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
Toyota 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 Toyota C-HR 1.8 CVT 122 (2016) 0-60 time?
The Toyota C-HR 1.8 CVT 122 (2016) reaches 60 mph in 9.87 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,911th quickest of the 14,946 cars in the set.
What is the Toyota C-HR 1.8 CVT 122 (2016) quarter mile time?
17.50 s at 77.5 mph. It reaches the eighth mile in 11.18 s and clears the first 60 ft in 2.72 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Toyota C-HR 1.8 CVT 122 (2016) have?
97 bhp and 1,420 kg, which is 68 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 Toyota C-HR 1.8 CVT 122 (2016)?
Closest here on pace: Toyota C-HR 1.8 CVT 122 (2020) (9.87 s), Skoda Roomster 1.2 TSI 105 (9.88 s), Skoda Yeti 1.2 TSI 110 (9.90 s). Each one can be raced against the Toyota C-HR 1.8 CVT 122 (2016) 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 1.8 CVT 122 (2016) 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.