← My Auto Racer All cars Jaguar 0-60 Comparisons Answers
The Jaguar XF 2.7D Mk I reaches 60 mph in 8.02 s and covers a standing quarter mile in 16.25 s, tripping the lights at 87.6 mph. It clears the first 60 ft in 2.67 s and the eighth mile in 10.58 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Jaguar XF 2.7D Mk I |
|---|---|
| 0–60 mph | 8.02 s |
| 0–100 mph | — |
| 60 ft | 2.67 s |
| 1/8 mile | 10.58 s |
| 1/4 mile | 16.25 s |
| Trap speed | 87.6 mph |
The 2008 Jaguar XF 2.7D Mk I is a rear-drive turbocharged car of 1,755 kg with 204 bhp, which works out at 116 bhp per tonne. Rear drive and 116 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.67 s. Against the 2,939 cars in the set it is the 2,643rd quickest to 60 mph, and the 65th quickest of the 68 Jaguars here. Its 87.6 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 9 of 9 published acceleration figures for this car.
| Specification | Jaguar XF 2.7D Mk I |
|---|---|
| Year | 2008 |
| Power | 204 bhp |
| Kerb mass | 1,755 kg |
| Power to weight | 116 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 229 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Renault Twingo Gordini RS Mk II | 2010 | 8.02 s | 16.35 s | 84.4 mph | 131 bhp |
| Vauxhall Cavalier SRi | 1988 | 8.02 s | 16.11 s | 87.8 mph | 129 bhp |
| Peugeot 106 GTi/S16 | 1996 | 8.09 s | 16.35 s | 85.5 mph | 118 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.
Figures regenerated 2026-09-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.