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

Jaguar F-Pace 2.0 180

The Jaguar F-Pace 2.0 180 reaches 60 mph in 7.81 s (100 km/h in 8.33 s) and covers a standing quarter mile in 16.06 s, tripping the lights at 84.0 mph. It clears the first 60 ft in 2.30 s and the eighth mile in 10.24 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.

Jaguar F-Pace 2.0 180 Ford Focus Sedan 2.0 TDCi 150

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 Jaguar F-Pace 2.0 180
0–60 mph7.81 s
0–100 km/h8.33 s
0–100 mph—
60 ft2.30 s
1/8 mile10.24 s
1/4 mile16.06 s
Trap speed84.0 mph

About the F-Pace 2.0 180

The 2015 Jaguar F-Pace 2.0 180 is an all-wheel-drive turbodiesel saloon of 1,767 kg with 177 bhp, which works out at 100 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.30 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 6,155th quickest to 60 mph, and the 160th quickest of the 187 Jaguars here. It leaves better than it pulls: 84.0 mph at the lights is only the 7,799th 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 Jaguar F-Pace 2.0 180
Year2015
Power177 hp (132 kW)
Kerb mass1,767 kg
Power to weight100 bhp/t
DrivetrainAll-wheel drive
Gears6
EngineTurbodiesel
Top speed129 mph (208 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ford Focus Sedan 2.0 TDCi 15020147.81 s16.12 s85.5 mph148 bhp
Ford Focus Sedan 2.0 TDCi Start/Stop 150 Auto20147.81 s16.12 s85.5 mph148 bhp
BMW 5 Series 520d 16320037.82 s16.06 s86.3 mph161 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 8 seconds6,514 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
Jaguar 0-60 timesevery modelFastest 4x4s and all-wheel-drive cars2,981 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 Jaguar F-Pace 2.0 180 0-60 time?
The Jaguar F-Pace 2.0 180 reaches 60 mph in 7.81 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 6,155th quickest of the 14,946 cars in the set.
What is the Jaguar F-Pace 2.0 180 quarter mile time?
16.06 s at 84.0 mph. It reaches the eighth mile in 10.24 s and clears the first 60 ft in 2.30 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Jaguar F-Pace 2.0 180 have?
177 bhp and 1,767 kg, which is 100 bhp per tonne. It is all-wheel-drive, turbodiesel, with 6 gears and a quoted top speed of 208 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Jaguar F-Pace 2.0 180?
Closest here on pace: Ford Focus Sedan 2.0 TDCi 150 (7.81 s), Ford Focus Sedan 2.0 TDCi Start/Stop 150 Auto (7.81 s), BMW 5 Series 520d 163 (7.82 s). Each one can be raced against the Jaguar F-Pace 2.0 180 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 Jaguar F-Pace 2.0 180 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.