← My Auto Racer All cars Laraki 0-60 Comparisons
The Laraki Fulgura V8 reaches 60 mph in 3.26 s and covers a standing quarter mile in 11.25 s, tripping the lights at 126.1 mph. It clears the first 60 ft in 1.84 s and the eighth mile in 7.33 s, reaching 100 mph in 7.05 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 | Laraki Fulgura V8 |
|---|---|
| 0–60 mph | 3.26 s |
| 0–100 mph | 7.05 s |
| 60 ft | 1.84 s |
| 1/8 mile | 7.33 s |
| 1/4 mile | 11.25 s |
| Trap speed | 126.1 mph |
The 2015 Laraki Fulgura V8 is a rear-drive turbocharged supercar of 1,152 kg with 575 bhp, which works out at 499 bhp per tonne. Rear drive and 499 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.84 s. Against the 2,929 cars in the set it is the 356th quickest to 60 mph, inside the fastest quarter. Its 126.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 5 of 5 published acceleration figures for this car.
| Specification | Laraki Fulgura V8 |
|---|---|
| Year | 2015 |
| Power | 575 bhp |
| Kerb mass | 1,152 kg |
| Power to weight | 499 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 334 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Brooke Double R 320 | 2007 | 3.22 s | 11.27 s | 120.0 mph | 315 bhp |
| Pagani Zonda C12-S 7.3 Roadster | 2005 | 3.27 s | 11.26 s | 128.5 mph | 547 bhp |
| Mosler MT900S | 2015 | 3.11 s | 11.33 s | 122.1 mph | 429 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.