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

Jaguar F-Type R Coupe

The Jaguar F-Type R Coupe reaches 60 mph in 3.44 s (100 km/h in 3.59 s) and covers a standing quarter mile in 11.69 s, tripping the lights at 121.5 mph. It clears the first 60 ft in 1.82 s and the eighth mile in 7.60 s, reaching 100 mph in 8.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.

Jaguar F-Type R Coupe TVR Tuscan S Mk II

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-Type R Coupe
0–60 mph3.44 s
0–100 km/h3.59 s
0–100 mph8.17 s
60 ft1.82 s
1/8 mile7.60 s
1/4 mile11.69 s
Trap speed121.5 mph

About the F-Type R Coupe

The 2014 Jaguar F-Type R Coupe is a rear-drive turbocharged supercar of 1,665 kg with 543 bhp, which works out at 326 bhp per tonne. Rear drive and 326 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.82 s. Against the 14,946 cars in the set it is the 587th quickest to 60 mph, inside the fastest five per cent, and the 9th quickest of the 187 Jaguars here. Its 121.5 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 10 of 10 published acceleration figures for this car.

On paper

Specification Jaguar F-Type R Coupe
Year2014
Power543 hp (405 kW)
Kerb mass1,665 kg
Power to weight326 bhp/t
DrivetrainRear drive
Gears6
EngineTurbocharged
Top speed186 mph (300 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
TVR Tuscan S Mk II20153.44 s11.69 s120.2 mph394 bhp
Lamborghini Diablo SV 5.7 V12 53019963.40 s11.70 s125.9 mph523 bhp
Lamborghini Gallardo Superleggera20073.44 s11.75 s121.2 mph523 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 4 seconds1,060 cars0-100 km/h under 4 seconds881 carsQuarter mile under 12 seconds780 cars0-100 under 9 seconds871 carsTraps over 120 mph651 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 supercars629 carsFastest cars of the 2010s4,541 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-Type R Coupe 0-60 time?
The Jaguar F-Type R Coupe reaches 60 mph in 3.44 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 587th quickest of the 14,946 cars in the set.
What is the Jaguar F-Type R Coupe quarter mile time?
11.69 s at 121.5 mph. It reaches the eighth mile in 7.60 s and clears the first 60 ft in 1.82 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Jaguar F-Type R Coupe have?
543 bhp and 1,665 kg, which is 326 bhp per tonne. It is rear-drive, turbocharged, with 6 gears and a quoted top speed of 300 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Jaguar F-Type R Coupe?
Closest here on pace: TVR Tuscan S Mk II (3.44 s), Lamborghini Diablo SV 5.7 V12 530 (3.40 s), Lamborghini Gallardo Superleggera (3.44 s). Each one can be raced against the Jaguar F-Type R Coupe 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-Type R Coupe is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 10 of its 10 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.