← My Auto Racer All cars Jaguar 0-60 Comparisons
The Jaguar XJ220S TWR reaches 60 mph in 2.79 s and covers a standing quarter mile in 10.49 s, tripping the lights at 136.8 mph. It clears the first 60 ft in 1.74 s and the eighth mile in 6.86 s, reaching 100 mph in 5.81 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 XJ220S TWR |
|---|---|
| 0–60 mph | 2.79 s |
| 0–100 mph | 5.81 s |
| 60 ft | 1.74 s |
| 1/8 mile | 6.86 s |
| 1/4 mile | 10.49 s |
| Trap speed | 136.8 mph |
The 2015 Jaguar XJ220S TWR is a rear-drive turbocharged supercar of 1,052 kg with 671 bhp, which works out at 637 bhp per tonne. Rear drive and 637 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.74 s. Against the 2,929 cars in the set it is the 157th quickest to 60 mph, inside the fastest tenth, and the quickest of the 68 Jaguars here. Its 136.8 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 5 of 5 published acceleration figures for this car.
| Specification | Jaguar XJ220S TWR |
|---|---|
| Year | 2015 |
| Power | 671 bhp |
| Kerb mass | 1,052 kg |
| Power to weight | 637 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 369 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Mosler MT900 GTR | 2008 | 2.75 s | 10.31 s | 137.7 mph | 591 bhp |
| 9ff BT-2 | 2009 | 2.76 s | 10.31 s | 138.8 mph | 850 bhp |
| Pagani Zonda Cinque | 2009 | 2.75 s | 10.45 s | 137.7 mph | 671 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.