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

Jaguar E-type 4.2 Mk I facelift

The Jaguar E-type 4.2 Mk I facelift reaches 60 mph in 6.67 s (100 km/h in 6.98 s) and covers a standing quarter mile in 15.11 s, tripping the lights at 95.3 mph. It clears the first 60 ft in 2.65 s and the eighth mile in 9.97 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 E-type 4.2 Mk I facelift Maserati Ghibli Mk I

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 E-type 4.2 Mk I facelift
0–60 mph6.67 s
0–100 km/h6.98 s
0–100 mph—
60 ft2.65 s
1/8 mile9.97 s
1/4 mile15.11 s
Trap speed95.3 mph

About the E-type 4.2 Mk I facelift

The 1964 Jaguar E-type 4.2 Mk I facelift is a rear-drive naturally aspirated car of 1,350 kg with 264 bhp, which works out at 196 bhp per tonne. Rear drive and 196 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.65 s. Against the 14,946 cars in the set it is the 4,133rd quickest to 60 mph, and the 119th quickest of the 187 Jaguars here. Its 95.3 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 7 of 9 published acceleration figures for this car.

On paper

Specification Jaguar E-type 4.2 Mk I facelift
Year1964
Power264 hp (197 kW)
Kerb mass1,350 kg
Power to weight196 bhp/t
DrivetrainRear drive
Gears5
EngineNaturally aspirated
Top speed150 mph (242 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Maserati Ghibli Mk I19676.59 s14.85 s100.8 mph326 bhp
Renault Clio 19720066.65 s15.21 s92.0 mph194 bhp
Citroen DS4 THP 20020126.58 s15.09 s93.3 mph197 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.

Head to head

Jaguar F-Type Coupe 2.0 300 vs Jaguar E-type 4.2 Mk I faceliftFull comparison

Where these times sit

0-60 under 7 seconds4,651 cars0-100 km/h under 7 seconds4,031 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 hatchbacks4,513 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 E-type 4.2 Mk I facelift 0-60 time?
The Jaguar E-type 4.2 Mk I facelift reaches 60 mph in 6.67 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 4,133rd quickest of the 14,946 cars in the set.
What is the Jaguar E-type 4.2 Mk I facelift quarter mile time?
15.11 s at 95.3 mph. It reaches the eighth mile in 9.97 s and clears the first 60 ft in 2.65 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Jaguar E-type 4.2 Mk I facelift have?
264 bhp and 1,350 kg, which is 196 bhp per tonne. It is rear-drive, naturally aspirated, with 5 gears and a quoted top speed of 242 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Jaguar E-type 4.2 Mk I facelift?
Closest here on pace: Maserati Ghibli Mk I (6.59 s), Renault Clio 197 (6.65 s), Citroen DS4 THP 200 (6.58 s). Each one can be raced against the Jaguar E-type 4.2 Mk I facelift 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 E-type 4.2 Mk I facelift is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 7 of its 9 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.