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

Jaguar F-Pace 3.0 340

The Jaguar F-Pace 3.0 340 reaches 60 mph in 5.19 s (100 km/h in 5.50 s) and covers a standing quarter mile in 13.78 s, tripping the lights at 98.9 mph. It clears the first 60 ft in 1.98 s and the eighth mile in 8.78 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 3.0 340 Land Rover Defender 90 3.0 400

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 3.0 340
0–60 mph5.19 s
0–100 km/h5.50 s
0–100 mph—
60 ft1.98 s
1/8 mile8.78 s
1/4 mile13.78 s
Trap speed98.9 mph

About the F-Pace 3.0 340

The 2020 Jaguar F-Pace 3.0 340 is an all-wheel-drive turbocharged SUV of 1,951 kg with 335 bhp, which works out at 172 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 1.98 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 2,359th quickest to 60 mph, inside the fastest quarter, and the 68th quickest of the 187 Jaguars here. Its 98.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 Jaguar F-Pace 3.0 340
Year2020
Power335 hp (250 kW)
Kerb mass1,951 kg
Power to weight172 bhp/t
DrivetrainAll-wheel drive
Gears8
EngineTurbocharged
Top speed149 mph (240 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Land Rover Defender 90 3.0 40020195.17 s14.00 s95.8 mph394 bhp
Range Rover Sport V8 SC20105.12 s13.71 s101.7 mph503 bhp
Audi Q8 55 TSFI V6 34020195.28 s13.83 s99.0 mph335 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 6 seconds3,249 cars0-100 km/h under 6 seconds2,894 carsQuarter mile under 14 seconds2,644 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 SUVs2,049 carsFastest cars of the 2020s867 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 3.0 340 0-60 time?
The Jaguar F-Pace 3.0 340 reaches 60 mph in 5.19 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 2,359th quickest of the 14,946 cars in the set.
What is the Jaguar F-Pace 3.0 340 quarter mile time?
13.78 s at 98.9 mph. It reaches the eighth mile in 8.78 s and clears the first 60 ft in 1.98 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Jaguar F-Pace 3.0 340 have?
335 bhp and 1,951 kg, which is 172 bhp per tonne. It is all-wheel-drive, turbocharged, with 8 gears and a quoted top speed of 240 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Jaguar F-Pace 3.0 340?
Closest here on pace: Land Rover Defender 90 3.0 400 (5.17 s), Range Rover Sport V8 SC (5.12 s), Audi Q8 55 TSFI V6 340 (5.28 s). Each one can be raced against the Jaguar F-Pace 3.0 340 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 3.0 340 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.