← My Auto Racer All cars VW 0-60 Comparisons Answers
The VW Passat CC 2.0 TDI 170 PS reaches 60 mph in 8.19 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | VW Passat CC 2.0 TDI 170 PS |
|---|---|
| 0–60 mph | 8.19 s |
| 0–100 mph | — |
| 60 ft | 2.71 s |
| 1/8 mile | 10.70 s |
| 1/4 mile | 16.39 s |
| Trap speed | 87.3 mph |
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 2,939 cars in the set it is the 2,674th quickest to 60 mph, and the 75th quickest of the 97 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.
| Specification | VW Passat CC 2.0 TDI 170 PS |
|---|---|
| Year | 2008 |
| Power | 168 bhp |
| Kerb mass | 1,630 kg |
| Power to weight | 103 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbodiesel |
| Top speed | 221 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Peugeot 206 CC | 2001 | 8.20 s | 16.47 s | 85.6 mph | 135 bhp |
| Alfa Romeo GTV 2.0 TS | 1995 | 8.20 s | 16.35 s | 87.4 mph | 148 bhp |
| MG MGF 1.8i | 1995 | 8.20 s | 16.44 s | 84.1 mph | 118 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.
Figures regenerated 2026-09-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.