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

Lotus Elise S Club Racer

The Lotus Elise S Club Racer reaches 60 mph in 4.11 s (100 km/h in 4.35 s) and covers a standing quarter mile in 12.82 s, tripping the lights at 104.6 mph. It clears the first 60 ft in 1.88 s and the eighth mile in 8.14 s, reaching 100 mph in 11.52 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 S Club Racer 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 S Club Racer
0–60 mph4.11 s
0–100 km/h4.35 s
0–100 mph11.52 s
60 ft1.88 s
1/8 mile8.14 s
1/4 mile12.82 s
Trap speed104.6 mph

About the Elise S Club Racer

The 2015 Lotus Elise S Club Racer is a rear-drive turbocharged roadster of 905 kg with 217 bhp, which works out at 240 bhp per tonne. Rear drive and 240 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.88 s. Against the 14,946 cars in the set it is the 1,170th quickest to 60 mph, inside the fastest tenth, and the 23rd quickest of the 66 Lotuss here. Its 104.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 9 of 10 published acceleration figures for this car.

On paper

Specification Lotus Elise S Club Racer
Year2015
Power217 hp (162 kW)
Kerb mass905 kg
Power to weight240 bhp/t
DrivetrainRear drive
Gears7
EngineTurbocharged
Top speed145 mph (234 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Ferrari 360 Spider20004.14 s12.73 s111.6 mph394 bhp
Lexus LC 500 Convertible 5.0 V8 47120214.29 s12.86 s109.4 mph464 bhp
Alfa Romeo 4C Spyder20153.99 s12.64 s107.6 mph237 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 S Club Racer 0-60 time?
The Lotus Elise S Club Racer reaches 60 mph in 4.11 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 1,170th quickest of the 14,946 cars in the set.
What is the Lotus Elise S Club Racer quarter mile time?
12.82 s at 104.6 mph. It reaches the eighth mile in 8.14 s and clears the first 60 ft in 1.88 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Lotus Elise S Club Racer have?
217 bhp and 905 kg, which is 240 bhp per tonne. It is rear-drive, turbocharged, with 7 gears and a quoted top speed of 234 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Lotus Elise S Club Racer?
Closest here on pace: Ferrari 360 Spider (4.14 s), Lexus LC 500 Convertible 5.0 V8 471 (4.29 s), Alfa Romeo 4C Spyder (3.99 s). Each one can be raced against the Lotus Elise S Club Racer 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 S Club Racer 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.