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

Toyota Verso 1.8 Valvematic 147

The Toyota Verso 1.8 Valvematic 147 reaches 60 mph in 9.47 s (100 km/h in 10.02 s) and covers a standing quarter mile in 17.08 s, tripping the lights at 81.6 mph. It clears the first 60 ft in 2.67 s and the eighth mile in 11.05 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 Verso 1.8 Valvematic 147 Renault Scenic 1.4 TCe 130

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 Verso 1.8 Valvematic 147
0–60 mph9.47 s
0–100 km/h10.02 s
0–100 mph—
60 ft2.67 s
1/8 mile11.05 s
1/4 mile17.08 s
Trap speed81.6 mph

About the Verso 1.8 Valvematic 147

The 2009 Toyota Verso 1.8 Valvematic 147 is a front-drive naturally aspirated MPV of 1,505 kg with 145 bhp, which works out at 96 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,212th quickest to 60 mph, and the 123rd quickest of the 311 Toyotas here. Its 81.6 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 Verso 1.8 Valvematic 147
Year2009
Power145 hp (108 kW)
Kerb mass1,505 kg
Power to weight96 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed118 mph (190 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Scenic 1.4 TCe 13020099.56 s17.08 s80.7 mph129 bhp
Vauxhall Zafira 1.9 CDTi 15020059.44 s17.20 s80.3 mph148 bhp
Renault Espace 2.9 V6 15219919.39 s17.14 s82.6 mph150 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 MPVs and people carriers478 carsFastest cars of the 2000s5,138 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 Verso 1.8 Valvematic 147 0-60 time?
The Toyota Verso 1.8 Valvematic 147 reaches 60 mph in 9.47 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,212th quickest of the 14,946 cars in the set.
What is the Toyota Verso 1.8 Valvematic 147 quarter mile time?
17.08 s at 81.6 mph. It reaches the eighth mile in 11.05 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 Toyota Verso 1.8 Valvematic 147 have?
145 bhp and 1,505 kg, which is 96 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 190 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Toyota Verso 1.8 Valvematic 147?
Closest here on pace: Renault Scenic 1.4 TCe 130 (9.56 s), Vauxhall Zafira 1.9 CDTi 150 (9.44 s), Renault Espace 2.9 V6 152 (9.39 s). Each one can be raced against the Toyota Verso 1.8 Valvematic 147 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 Verso 1.8 Valvematic 147 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.