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

Toyota Verso 2.0 D-4D 126 (2013)

The Toyota Verso 2.0 D-4D 126 (2013) reaches 60 mph in 10.27 s (100 km/h in 10.89 s) and covers a standing quarter mile in 17.55 s, tripping the lights at 78.2 mph. It clears the first 60 ft in 2.63 s and the eighth mile in 11.26 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 2.0 D-4D 126 (2013) Ford Galaxy 2.0 TDCi 150 (Mk3)

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 2.0 D-4D 126 (2013)
0–60 mph10.27 s
0–100 km/h10.89 s
0–100 mph—
60 ft2.63 s
1/8 mile11.26 s
1/4 mile17.55 s
Trap speed78.2 mph

About the Verso 2.0 D-4D 126

The 2013 Toyota Verso 2.0 D-4D 126 (2013) is a front-drive turbodiesel MPV of 1,515 kg with 123 bhp, which works out at 81 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.63 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 10,594th quickest to 60 mph, and the 165th quickest of the 311 Toyotas here. Its 78.2 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 2.0 D-4D 126 (2013)
Year2013
Power123 hp (92 kW)
Kerb mass1,515 kg
Power to weight81 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ford Galaxy 2.0 TDCi 150 (Mk3)201510.38 s17.56 s78.2 mph148 bhp
Citroen Berlingo BlueHDi 130 (Mk3)201810.20 s17.59 s78.8 mph129 bhp
Vauxhall Meriva 1.4 Turbo 120201410.25 s17.63 s78.2 mph118 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

Slower 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 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 Verso 2.0 D-4D 126 (2013) 0-60 time?
The Toyota Verso 2.0 D-4D 126 (2013) reaches 60 mph in 10.27 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,594th quickest of the 14,946 cars in the set.
What is the Toyota Verso 2.0 D-4D 126 (2013) quarter mile time?
17.55 s at 78.2 mph. It reaches the eighth mile in 11.26 s and clears the first 60 ft in 2.63 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Toyota Verso 2.0 D-4D 126 (2013) have?
123 bhp and 1,515 kg, which is 81 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 185 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Toyota Verso 2.0 D-4D 126 (2013)?
Closest here on pace: Ford Galaxy 2.0 TDCi 150 (Mk3) (10.38 s), Citroen Berlingo BlueHDi 130 (Mk3) (10.20 s), Vauxhall Meriva 1.4 Turbo 120 (10.25 s). Each one can be raced against the Toyota Verso 2.0 D-4D 126 (2013) 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 2.0 D-4D 126 (2013) 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.