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

Lotus Exige Cup 430 Mk III

The Lotus Exige Cup 430 Mk III reaches 60 mph in 3.04 s (100 km/h in 3.21 s) and covers a standing quarter mile in 11.41 s, tripping the lights at 119.4 mph. It clears the first 60 ft in 1.71 s and the eighth mile in 7.28 s, reaching 100 mph in 7.75 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 Cup 430 Mk III Lucra Cars LC 470 LS6 engine

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 Cup 430 Mk III
0–60 mph3.04 s
0–100 km/h3.21 s
0–100 mph7.75 s
60 ft1.71 s
1/8 mile7.28 s
1/4 mile11.41 s
Trap speed119.4 mph

About the Exige Cup 430 Mk III

The 2017 Lotus Exige Cup 430 Mk III is a rear-drive naturally aspirated supercar of 1,093 kg with 430 bhp, which works out at 394 bhp per tonne. Rear drive and 394 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.71 s. Against the 14,946 cars in the set it is the 300th quickest to 60 mph, inside the fastest five per cent, and the 4th quickest of the 66 Lotuss here. Its 119.4 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.

On paper

Specification Lotus Exige Cup 430 Mk III
Year2017
Power430 hp (321 kW)
Kerb mass1,093 kg
Power to weight394 bhp/t
DrivetrainRear drive
Gears7
EngineNaturally aspirated
Top speed180 mph (290 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lucra Cars LC 470 LS6 engine20103.15 s11.40 s122.5 mph400 bhp
Rossion Q120083.01 s11.27 s121.6 mph451 bhp
Ruf R-Turbo20153.06 s11.17 s125.1 mph582 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 110 mph1,380 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 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 Lotus Exige Cup 430 Mk III 0-60 time?
The Lotus Exige Cup 430 Mk III reaches 60 mph in 3.04 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 300th quickest of the 14,946 cars in the set.
What is the Lotus Exige Cup 430 Mk III quarter mile time?
11.41 s at 119.4 mph. It reaches the eighth mile in 7.28 s and clears the first 60 ft in 1.71 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Lotus Exige Cup 430 Mk III have?
430 bhp and 1,093 kg, which is 394 bhp per tonne. It is rear-drive, naturally aspirated, with 7 gears and a quoted top speed of 290 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Lotus Exige Cup 430 Mk III?
Closest here on pace: Lucra Cars LC 470 LS6 engine (3.15 s), Rossion Q1 (3.01 s), Ruf R-Turbo (3.06 s). Each one can be raced against the Lotus Exige Cup 430 Mk III 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 Cup 430 Mk III is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 5 of its 5 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-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.