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

Ford EDGE 2.0 TDCi 210

The Ford EDGE 2.0 TDCi 210 reaches 60 mph in 8.40 s (100 km/h in 8.99 s) and covers a standing quarter mile in 16.48 s, tripping the lights at 83.1 mph. It clears the first 60 ft in 2.51 s and the eighth mile in 10.54 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 EDGE 2.0 TDCi 210 Mazda CX-5 2.2D 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 Ford EDGE 2.0 TDCi 210
0–60 mph8.40 s
0–100 km/h8.99 s
0–100 mph—
60 ft2.51 s
1/8 mile10.54 s
1/4 mile16.48 s
Trap speed83.1 mph

About the EDGE 2.0 TDCi 210

The 2015 Ford EDGE 2.0 TDCi 210 is an all-wheel-drive turbodiesel SUV of 1,949 kg with 207 bhp, which works out at 106 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.51 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 7,297th quickest to 60 mph, and the 239th quickest of the 789 Fords here. It leaves better than it pulls: 83.1 mph at the lights is only the 8,282nd highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Ford EDGE 2.0 TDCi 210
Year2015
Power207 hp (154 kW)
Kerb mass1,949 kg
Power to weight106 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed131 mph (211 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mazda CX-5 2.2D 17520128.39 s16.48 s82.7 mph173 bhp
Hyundai Santa Fe Sport 2.2 CRDI 20020168.38 s16.47 s82.3 mph197 bhp
Renault Koleos 2.0 dCI 175 (2007)20078.37 s16.48 s81.8 mph170 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 EDGE 2.0 TDCi 210 0-60 time?
The Ford EDGE 2.0 TDCi 210 reaches 60 mph in 8.40 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,297th quickest of the 14,946 cars in the set.
What is the Ford EDGE 2.0 TDCi 210 quarter mile time?
16.48 s at 83.1 mph. It reaches the eighth mile in 10.54 s and clears the first 60 ft in 2.51 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Ford EDGE 2.0 TDCi 210 have?
207 bhp and 1,949 kg, which is 106 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 211 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Ford EDGE 2.0 TDCi 210?
Closest here on pace: Mazda CX-5 2.2D 175 (8.39 s), Hyundai Santa Fe Sport 2.2 CRDI 200 (8.38 s), Renault Koleos 2.0 dCI 175 (2007) (8.37 s). Each one can be raced against the Ford EDGE 2.0 TDCi 210 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 EDGE 2.0 TDCi 210 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.