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

Jaguar XK 5.0 V8 379

The Jaguar XK 5.0 V8 379 reaches 60 mph in 4.94 s (100 km/h in 5.21 s) and covers a standing quarter mile in 13.50 s, tripping the lights at 102.7 mph. It clears the first 60 ft in 2.14 s and the eighth mile in 8.71 s, reaching 100 mph in 12.47 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 XK 5.0 V8 379 Maserati Quattroporte S

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 XK 5.0 V8 379
0–60 mph4.94 s
0–100 km/h5.21 s
0–100 mph12.47 s
60 ft2.14 s
1/8 mile8.71 s
1/4 mile13.50 s
Trap speed102.7 mph

About the XK 5.0 V8 379

The 2006 Jaguar XK 5.0 V8 379 is a rear-drive naturally aspirated saloon of 1,660 kg with 380 bhp, which works out at 229 bhp per tonne. Rear drive and 229 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.14 s. Against the 14,946 cars in the set it is the 2,108th quickest to 60 mph, inside the fastest quarter, and the 51st quickest of the 187 Jaguars here. Its 102.7 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 XK 5.0 V8 379
Year2006
Power380 hp (283 kW)
Kerb mass1,660 kg
Power to weight229 bhp/t
DrivetrainRear drive
Gears6
EngineNaturally aspirated
Top speed155 mph (249 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Maserati Quattroporte S20084.94 s13.61 s105.6 mph425 bhp
Maserati Quattroporte Sport GT S 440 PS20094.83 s13.48 s106.6 mph433 bhp
Brabus GLK 6.120095.07 s13.41 s105.4 mph456 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 5 seconds2,158 cars0-100 km/h under 6 seconds2,894 carsQuarter mile under 14 seconds2,644 cars0-100 under 16 seconds2,740 carsTraps over 100 mph2,737 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 saloon cars3,808 carsFastest cars of the 2000s5,138 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 XK 5.0 V8 379 0-60 time?
The Jaguar XK 5.0 V8 379 reaches 60 mph in 4.94 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 2,108th quickest of the 14,946 cars in the set.
What is the Jaguar XK 5.0 V8 379 quarter mile time?
13.50 s at 102.7 mph. It reaches the eighth mile in 8.71 s and clears the first 60 ft in 2.14 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Jaguar XK 5.0 V8 379 have?
380 bhp and 1,660 kg, which is 229 bhp per tonne. It is rear-drive, naturally aspirated, with 6 gears and a quoted top speed of 249 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Jaguar XK 5.0 V8 379?
Closest here on pace: Maserati Quattroporte S (4.94 s), Maserati Quattroporte Sport GT S 440 PS (4.83 s), Brabus GLK 6.1 (5.07 s). Each one can be raced against the Jaguar XK 5.0 V8 379 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 XK 5.0 V8 379 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.