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

Toyota Corolla 1.6 VVT-i 132

The Toyota Corolla 1.6 VVT-i 132 reaches 60 mph in 8.34 s (100 km/h in 9.33 s) and covers a standing quarter mile in 16.58 s, tripping the lights at 84.0 mph. It clears the first 60 ft in 2.60 s and the eighth mile in 10.74 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 Corolla 1.6 VVT-i 132 Volvo S60 2.0 T 180 (2008)

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 Corolla 1.6 VVT-i 132
0–60 mph8.34 s
0–100 km/h9.33 s
0–100 mph—
60 ft2.60 s
1/8 mile10.74 s
1/4 mile16.58 s
Trap speed84.0 mph

About the Corolla 1.6 VVT-i 132

The 2020 Toyota Corolla 1.6 VVT-i 132 is a front-drive naturally aspirated saloon of 1,185 kg with 130 bhp, which works out at 110 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.60 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 7,198th quickest to 60 mph, and the 87th quickest of the 311 Toyotas here. Its 84.0 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 Toyota Corolla 1.6 VVT-i 132
Year2020
Power130 hp (97 kW)
Kerb mass1,185 kg
Power to weight110 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Volvo S60 2.0 T 180 (2008)20088.35 s16.54 s84.9 mph177 bhp
Renault Safrane 2.5 16819968.30 s16.59 s86.6 mph162 bhp
Alfa Romeo 166 2.4 JTD 20V 17520038.35 s16.55 s85.0 mph173 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 cars0-100 km/h under 10 seconds9,062 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 saloon cars3,808 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 Corolla 1.6 VVT-i 132 0-60 time?
The Toyota Corolla 1.6 VVT-i 132 reaches 60 mph in 8.34 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,198th quickest of the 14,946 cars in the set.
What is the Toyota Corolla 1.6 VVT-i 132 quarter mile time?
16.58 s at 84.0 mph. It reaches the eighth mile in 10.74 s and clears the first 60 ft in 2.60 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Toyota Corolla 1.6 VVT-i 132 have?
130 bhp and 1,185 kg, which is 110 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 200 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Toyota Corolla 1.6 VVT-i 132?
Closest here on pace: Volvo S60 2.0 T 180 (2008) (8.35 s), Renault Safrane 2.5 168 (8.30 s), Alfa Romeo 166 2.4 JTD 20V 175 (8.35 s). Each one can be raced against the Toyota Corolla 1.6 VVT-i 132 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 Corolla 1.6 VVT-i 132 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.