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

VW Touareg 5.0 V10 TDI 310

The VW Touareg 5.0 V10 TDI 310 reaches 60 mph in 6.63 s (100 km/h in 7.05 s) and covers a standing quarter mile in 15.13 s, tripping the lights at 90.7 mph. It clears the first 60 ft in 2.26 s and the eighth mile in 9.66 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.

VW Touareg 5.0 V10 TDI 310 BMW X3 3.0d 218 (2007)

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 VW Touareg 5.0 V10 TDI 310
0–60 mph6.63 s
0–100 km/h7.05 s
0–100 mph—
60 ft2.26 s
1/8 mile9.66 s
1/4 mile15.13 s
Trap speed90.7 mph

About the Touareg 5.0 V10 TDI 310

The 2007 VW Touareg 5.0 V10 TDI 310 is an all-wheel-drive turbodiesel SUV of 2,577 kg with 308 bhp, which works out at 120 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.26 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 4,054th quickest to 60 mph, and the 116th quickest of the 1124 VWs here. Its 90.7 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 VW Touareg 5.0 V10 TDI 310
Year2007
Power308 hp (230 kW)
Kerb mass2,577 kg
Power to weight120 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed144 mph (231 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
BMW X3 3.0d 218 (2007)20076.65 s15.14 s88.9 mph215 bhp
Mercedes-Benz ML-Class (W166) 350 BlueTEC 4MATIC 25820116.62 s15.08 s89.9 mph255 bhp
BMW X1 xDrive20i 19220166.62 s15.08 s89.9 mph189 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 7 seconds4,651 cars0-100 km/h under 8 seconds5,602 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
VW 0-60 timesevery modelFastest SUVs2,049 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 VW Touareg 5.0 V10 TDI 310 0-60 time?
The VW Touareg 5.0 V10 TDI 310 reaches 60 mph in 6.63 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,054th quickest of the 14,946 cars in the set.
What is the VW Touareg 5.0 V10 TDI 310 quarter mile time?
15.13 s at 90.7 mph. It reaches the eighth mile in 9.66 s and clears the first 60 ft in 2.26 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the VW Touareg 5.0 V10 TDI 310 have?
308 bhp and 2,577 kg, which is 120 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 231 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the VW Touareg 5.0 V10 TDI 310?
Closest here on pace: BMW X3 3.0d 218 (2007) (6.65 s), Mercedes-Benz ML-Class (W166) 350 BlueTEC 4MATIC 258 (6.62 s), BMW X1 xDrive20i 192 (6.62 s). Each one can be raced against the VW Touareg 5.0 V10 TDI 310 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 VW Touareg 5.0 V10 TDI 310 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.