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

Lotus Exige 1.8 179

The Lotus Exige 1.8 179 reaches 60 mph in 4.41 s (100 km/h in 4.60 s) and covers a standing quarter mile in 13.08 s, tripping the lights at 107.6 mph. It clears the first 60 ft in 2.10 s and the eighth mile in 8.47 s, reaching 100 mph in 11.21 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.

Lotus Exige 1.8 179 Venturi Atlantique 300 GT 310 PS

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 Lotus Exige 1.8 179
0–60 mph4.41 s
0–100 km/h4.60 s
0–100 mph11.21 s
60 ft2.10 s
1/8 mile8.47 s
1/4 mile13.08 s
Trap speed107.6 mph

About the Exige 1.8 179

The 2000 Lotus Exige 1.8 179 is a rear-drive naturally aspirated coupe of 780 kg with 178 bhp, which works out at 229 bhp per tonne. Rear drive and 229 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.10 s. Against the 14,946 cars in the set it is the 1,562nd quickest to 60 mph, inside the fastest quarter, and the 30th quickest of the 66 Lotuss here. Its 107.6 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 2 of 2 published acceleration figures for this car.

On paper

Specification Lotus Exige 1.8 179
Year2000
Power178 hp (133 kW)
Kerb mass780 kg
Power to weight229 bhp/t
DrivetrainRear drive
Gears5
EngineNaturally aspirated
Top speed136 mph (219 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Venturi Atlantique 300 GT 310 PS19994.37 s13.03 s108.8 mph306 bhp
Maserati GranTurismo S20084.49 s12.99 s111.5 mph433 bhp
Jaguar F-Type S Coupe20144.47 s13.21 s105.9 mph374 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 5 seconds2,158 cars0-100 km/h under 5 seconds1,845 carsQuarter mile under 14 seconds2,644 cars0-100 under 12 seconds1,963 carsTraps over 100 mph2,737 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Lotus 0-60 timesevery modelFastest coupes911 carsFastest cars of the 2000s5,138 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 Lotus Exige 1.8 179 0-60 time?
The Lotus Exige 1.8 179 reaches 60 mph in 4.41 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 1,562nd quickest of the 14,946 cars in the set.
What is the Lotus Exige 1.8 179 quarter mile time?
13.08 s at 107.6 mph. It reaches the eighth mile in 8.47 s and clears the first 60 ft in 2.10 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Lotus Exige 1.8 179 have?
178 bhp and 780 kg, which is 229 bhp per tonne. It is rear-drive, naturally aspirated, with 5 gears and a quoted top speed of 219 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Lotus Exige 1.8 179?
Closest here on pace: Venturi Atlantique 300 GT 310 PS (4.37 s), Maserati GranTurismo S (4.49 s), Jaguar F-Type S Coupe (4.47 s). Each one can be raced against the Lotus Exige 1.8 179 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 Lotus Exige 1.8 179 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 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.