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

Toyota Auris 3dr 2.0 D-4D 126

The Toyota Auris 3dr 2.0 D-4D 126 reaches 60 mph in 9.38 s (100 km/h in 9.91 s) and covers a standing quarter mile in 16.90 s, tripping the lights at 81.2 mph. It clears the first 60 ft in 2.53 s and the eighth mile in 10.86 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 Auris 3dr 2.0 D-4D 126 SEAT Altea 1.4 TSI 125

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 Auris 3dr 2.0 D-4D 126
0–60 mph9.38 s
0–100 km/h9.91 s
0–100 mph—
60 ft2.53 s
1/8 mile10.86 s
1/4 mile16.90 s
Trap speed81.2 mph

About the Auris 3dr 2.0 D-4D 126

The 2006 Toyota Auris 3dr 2.0 D-4D 126 is a front-drive turbodiesel car of 1,360 kg with 125 bhp, which works out at 92 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.53 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,066th quickest to 60 mph, and the 117th quickest of the 311 Toyotas here. Its 81.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 Auris 3dr 2.0 D-4D 126
Year2006
Power125 hp (93 kW)
Kerb mass1,360 kg
Power to weight92 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed121 mph (195 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
SEAT Altea 1.4 TSI 12520099.37 s16.92 s81.1 mph123 bhp
Vauxhall Corsa 3dr 1.0 Turbo 11520149.38 s16.90 s81.2 mph114 bhp
Vauxhall Corsa 5dr 1.0 Turbo 11520149.38 s16.90 s81.2 mph114 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 diesel cars4,019 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 Auris 3dr 2.0 D-4D 126 0-60 time?
The Toyota Auris 3dr 2.0 D-4D 126 reaches 60 mph in 9.38 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,066th quickest of the 14,946 cars in the set.
What is the Toyota Auris 3dr 2.0 D-4D 126 quarter mile time?
16.90 s at 81.2 mph. It reaches the eighth mile in 10.86 s and clears the first 60 ft in 2.53 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Toyota Auris 3dr 2.0 D-4D 126 have?
125 bhp and 1,360 kg, which is 92 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 195 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Toyota Auris 3dr 2.0 D-4D 126?
Closest here on pace: SEAT Altea 1.4 TSI 125 (9.37 s), Vauxhall Corsa 3dr 1.0 Turbo 115 (9.38 s), Vauxhall Corsa 5dr 1.0 Turbo 115 (9.38 s). Each one can be raced against the Toyota Auris 3dr 2.0 D-4D 126 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 Auris 3dr 2.0 D-4D 126 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.