← My Auto Racer All cars Jaguar 0-60 Comparisons
The Jaguar F-Type Coupe reaches 60 mph in 5.14 s and covers a standing quarter mile in 13.46 s, tripping the lights at 105.0 mph. It clears the first 60 ft in 2.07 s and the eighth mile in 8.71 s, reaching 100 mph in 12.17 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 Coupe |
|---|---|
| 0–60 mph | 5.14 s |
| 0–100 mph | 12.17 s |
| 60 ft | 2.07 s |
| 1/8 mile | 8.71 s |
| 1/4 mile | 13.46 s |
| Trap speed | 105.0 mph |
The 2014 Jaguar F-Type Coupe is a rear-drive turbocharged coupe of 1,577 kg with 335 bhp, which works out at 213 bhp per tonne. Rear drive and 213 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.07 s. Against the 2,929 cars in the set it is the 1,471st quickest to 60 mph, and the 32nd quickest of the 68 Jaguars here. Its 105.0 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 Coupe |
|---|---|
| Year | 2014 |
| Power | 335 bhp |
| Kerb mass | 1,577 kg |
| Power to weight | 213 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 260 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Toyota Supra Turbo Mk IV Europe | 1993 | 5.03 s | 13.64 s | 101.0 mph | 326 bhp |
| Infiniti G35 Coupe Mk III 302 PS | 2005 | 4.98 s | 13.52 s | 103.1 mph | 298 bhp |
| Nissan Skyline GT-R R34 | 1998 | 5.09 s | 13.51 s | 102.5 mph | 276 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.