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

Ford Grand C-Max 2.0 TDCi 163

The Ford Grand C-Max 2.0 TDCi 163 reaches 60 mph in 8.31 s (100 km/h in 8.83 s) and covers a standing quarter mile in 16.50 s, tripping the lights at 83.9 mph. It clears the first 60 ft in 2.53 s and the eighth mile in 10.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.

Ford Grand C-Max 2.0 TDCi 163 Peugeot 2008 1.2 PureTech 130 (2020)

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 Ford Grand C-Max 2.0 TDCi 163
0–60 mph8.31 s
0–100 km/h8.83 s
0–100 mph—
60 ft2.53 s
1/8 mile10.66 s
1/4 mile16.50 s
Trap speed83.9 mph

About the Grand C-Max 2.0 TDCi 163

The 2011 Ford Grand C-Max 2.0 TDCi 163 is a front-drive turbodiesel SUV of 1,488 kg with 161 bhp, which works out at 108 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 7,140th quickest to 60 mph, and the 231st quickest of the 789 Fords here. Its 83.9 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 Ford Grand C-Max 2.0 TDCi 163
Year2011
Power161 hp (120 kW)
Kerb mass1,488 kg
Power to weight108 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed127 mph (204 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Peugeot 2008 1.2 PureTech 130 (2020)20208.32 s16.51 s83.9 mph129 bhp
Suzuki Vitara 1.4 Boosterjet 14020188.35 s16.51 s83.5 mph138 bhp
Peugeot 3008 1.6 THP 15620098.33 s16.50 s83.6 mph154 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
Ford 0-60 timesevery modelFastest SUVs2,049 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 Ford Grand C-Max 2.0 TDCi 163 0-60 time?
The Ford Grand C-Max 2.0 TDCi 163 reaches 60 mph in 8.31 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,140th quickest of the 14,946 cars in the set.
What is the Ford Grand C-Max 2.0 TDCi 163 quarter mile time?
16.50 s at 83.9 mph. It reaches the eighth mile in 10.66 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 Ford Grand C-Max 2.0 TDCi 163 have?
161 bhp and 1,488 kg, which is 108 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 204 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ford Grand C-Max 2.0 TDCi 163?
Closest here on pace: Peugeot 2008 1.2 PureTech 130 (2020) (8.32 s), Suzuki Vitara 1.4 Boosterjet 140 (8.35 s), Peugeot 3008 1.6 THP 156 (8.33 s). Each one can be raced against the Ford Grand C-Max 2.0 TDCi 163 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 Ford Grand C-Max 2.0 TDCi 163 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.