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

Lotus Elise Cup 250 Mk III

The Lotus Elise Cup 250 Mk III reaches 60 mph in 4.16 s (100 km/h in 4.41 s) and covers a standing quarter mile in 12.84 s, tripping the lights at 104.1 mph. It clears the first 60 ft in 1.87 s and the eighth mile in 8.15 s, reaching 100 mph in 11.46 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 Elise Cup 250 Mk III Ferrari 360 Spider

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 Elise Cup 250 Mk III
0–60 mph4.16 s
0–100 km/h4.41 s
0–100 mph11.46 s
60 ft1.87 s
1/8 mile8.15 s
1/4 mile12.84 s
Trap speed104.1 mph

About the Elise Cup 250 Mk III

The 2016 Lotus Elise Cup 250 Mk III is a rear-drive turbocharged roadster of 931 kg with 243 bhp, which works out at 261 bhp per tonne. Rear drive and 261 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.87 s. Against the 14,946 cars in the set it is the 1,254th quickest to 60 mph, inside the fastest tenth, and the 24th quickest of the 66 Lotuss here. Its 104.1 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 9 of 10 published acceleration figures for this car.

On paper

Specification Lotus Elise Cup 250 Mk III
Year2016
Power243 hp (181 kW)
Kerb mass931 kg
Power to weight261 bhp/t
DrivetrainRear drive
Gears7
EngineTurbocharged
Top speed154 mph (248 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ferrari 360 Spider20004.14 s12.73 s111.6 mph394 bhp
Jaguar XKR 510 PS20094.14 s12.49 s115.4 mph503 bhp
Panoz AIV Roadster20004.41 s12.79 s107.5 mph304 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 13 seconds1,638 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 roadsters682 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 Elise Cup 250 Mk III 0-60 time?
The Lotus Elise Cup 250 Mk III reaches 60 mph in 4.16 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 1,254th quickest of the 14,946 cars in the set.
What is the Lotus Elise Cup 250 Mk III quarter mile time?
12.84 s at 104.1 mph. It reaches the eighth mile in 8.15 s and clears the first 60 ft in 1.87 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Lotus Elise Cup 250 Mk III have?
243 bhp and 931 kg, which is 261 bhp per tonne. It is rear-drive, turbocharged, with 7 gears and a quoted top speed of 248 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Lotus Elise Cup 250 Mk III?
Closest here on pace: Ferrari 360 Spider (4.14 s), Jaguar XKR 510 PS (4.14 s), Panoz AIV Roadster (4.41 s). Each one can be raced against the Lotus Elise Cup 250 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 Elise Cup 250 Mk III is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 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.