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

VW Passat CC 2.0 TDI 170 PS

The VW Passat CC 2.0 TDI 170 PS reaches 60 mph in 8.19 s (100 km/h in 8.66 s) and covers a standing quarter mile in 16.39 s, tripping the lights at 87.3 mph. It clears the first 60 ft in 2.71 s and the eighth mile in 10.70 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 Passat CC 2.0 TDI 170 PS Holden Vectra Liftback 2.0 Turbo 175

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 Passat CC 2.0 TDI 170 PS
0–60 mph8.19 s
0–100 km/h8.66 s
0–100 mph—
60 ft2.71 s
1/8 mile10.70 s
1/4 mile16.39 s
Trap speed87.3 mph

About the Passat CC 2.0 TDI 170 PS

The 2008 VW Passat CC 2.0 TDI 170 PS is a front-drive turbodiesel car of 1,630 kg with 168 bhp, which works out at 103 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.71 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 6,895th quickest to 60 mph, and the 397th quickest of the 1124 VWs here. Its 87.3 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 9 of 9 published acceleration figures for this car.

On paper

Specification VW Passat CC 2.0 TDI 170 PS
Year2008
Power168 hp (125 kW)
Kerb mass1,630 kg
Power to weight103 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed137 mph (221 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Holden Vectra Liftback 2.0 Turbo 17520028.25 s16.32 s86.4 mph173 bhp
Peugeot 206 CC20018.20 s16.47 s85.6 mph135 bhp
Holden Vectra Liftback 3.0 CDTi V6 17720028.43 s16.46 s85.5 mph174 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
VW 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 VW Passat CC 2.0 TDI 170 PS 0-60 time?
The VW Passat CC 2.0 TDI 170 PS reaches 60 mph in 8.19 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,895th quickest of the 14,946 cars in the set.
What is the VW Passat CC 2.0 TDI 170 PS quarter mile time?
16.39 s at 87.3 mph. It reaches the eighth mile in 10.70 s and clears the first 60 ft in 2.71 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the VW Passat CC 2.0 TDI 170 PS have?
168 bhp and 1,630 kg, which is 103 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 221 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the VW Passat CC 2.0 TDI 170 PS?
Closest here on pace: Holden Vectra Liftback 2.0 Turbo 175 (8.25 s), Peugeot 206 CC (8.20 s), Holden Vectra Liftback 3.0 CDTi V6 177 (8.43 s). Each one can be raced against the VW Passat CC 2.0 TDI 170 PS 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 Passat CC 2.0 TDI 170 PS is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 9 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.