← My Auto Racer All cars W Motors 0-60 Comparisons
The W Motors Lykan Hypersport reaches 60 mph in 2.65 s and covers a standing quarter mile in 10.39 s, tripping the lights at 134.6 mph. It clears the first 60 ft in 1.59 s and the eighth mile in 6.69 s, reaching 100 mph in 5.91 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 | W Motors Lykan Hypersport |
|---|---|
| 0–60 mph | 2.65 s |
| 0–100 mph | 5.91 s |
| 60 ft | 1.59 s |
| 1/8 mile | 6.69 s |
| 1/4 mile | 10.39 s |
| Trap speed | 134.6 mph |
The 2013 W Motors Lykan Hypersport is a rear-drive turbocharged supercar of 1,510 kg with 780 bhp, which works out at 517 bhp per tonne. Rear drive and 517 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.59 s. Against the 2,929 cars in the set it is the 111th quickest to 60 mph, inside the fastest five per cent. Its 134.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 11 published acceleration figures for this car.
| Specification | W Motors Lykan Hypersport |
|---|---|
| Year | 2013 |
| Power | 780 bhp |
| Kerb mass | 1,510 kg |
| Power to weight | 517 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 390 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Pagani Zonda C12-F Clubsport Roadster | 2015 | 2.69 s | 10.61 s | 133.3 mph | 641 bhp |
| Pagani Zonda Cinque | 2009 | 2.75 s | 10.45 s | 137.7 mph | 671 bhp |
| Lotus 3-Eleven Race | 2016 | 2.73 s | 10.35 s | 136.9 mph | 460 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.