← My Auto Racer All cars Lotus 0-60 Comparisons
The Lotus Evora 400 reaches 60 mph in 3.96 s and covers a standing quarter mile in 12.33 s, tripping the lights at 115.0 mph. It clears the first 60 ft in 2.00 s and the eighth mile in 8.01 s, reaching 100 mph in 9.36 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.
Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.
| Standing start | Lotus Evora 400 |
|---|---|
| 0–60 mph | 3.96 s |
| 0–100 mph | 9.36 s |
| 60 ft | 2.00 s |
| 1/8 mile | 8.01 s |
| 1/4 mile | 12.33 s |
| Trap speed | 115.0 mph |
The 2016 Lotus Evora 400 is a rear-drive naturally aspirated car of 1,415 kg with 400 bhp, which works out at 282 bhp per tonne. Rear drive and 282 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.00 s. Against the 2,929 cars in the set it is the 773rd quickest to 60 mph, and the 10th quickest of the 49 Lotuss here. Its 115.0 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.
| Specification | Lotus Evora 400 |
|---|---|
| Year | 2016 |
| Power | 400 bhp |
| Kerb mass | 1,415 kg |
| Power to weight | 282 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Naturally aspirated |
| Top speed | 300 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Vector M12 | 1996 | 3.95 s | 12.25 s | 118.7 mph | 485 bhp |
| Panoz Esperante GTLM | 2006 | 3.81 s | 12.38 s | 114.4 mph | 414 bhp |
| Shelby Series 1 | 1998 | 4.00 s | 12.67 s | 111.0 mph | 321 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.
Figures regenerated 2026-09-01. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.