← My Auto Racer All cars Jaguar 0-60 Comparisons
The Jaguar F-type R AWD reaches 60 mph in 3.43 s and covers a standing quarter mile in 11.63 s, tripping the lights at 121.4 mph. It clears the first 60 ft in 1.88 s and the eighth mile in 7.56 s, reaching 100 mph in 7.91 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 F-type R AWD |
|---|---|
| 0–60 mph | 3.43 s |
| 0–100 mph | 7.91 s |
| 60 ft | 1.88 s |
| 1/8 mile | 7.56 s |
| 1/4 mile | 11.63 s |
| Trap speed | 121.4 mph |
The 2015 Jaguar F-type R AWD is a rear-drive turbocharged supercar of 1,730 kg with 543 bhp, which works out at 314 bhp per tonne. Rear drive and 314 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.88 s. Against the 2,929 cars in the set it is the 453rd quickest to 60 mph, inside the fastest quarter, and the 5th quickest of the 68 Jaguars here. Its 121.4 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 10 published acceleration figures for this car.
| Specification | Jaguar F-type R AWD |
|---|---|
| Year | 2015 |
| Power | 543 bhp |
| Kerb mass | 1,730 kg |
| Power to weight | 314 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 300 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| TVR Tuscan S Mk II | 2015 | 3.44 s | 11.69 s | 120.2 mph | 394 bhp |
| Brabham BT64 | 2009 | 3.51 s | 11.54 s | 126.4 mph | 605 bhp |
| TVR Sagaris | 2003 | 3.36 s | 11.67 s | 120.3 mph | 394 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-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.