← My Auto Racer All cars Htt Locus 0-60 Comparisons
The Htt Locus Plethore lc750 reaches 60 mph in 2.70 s and covers a standing quarter mile in 10.13 s, tripping the lights at 142.2 mph. It clears the first 60 ft in 1.61 s and the eighth mile in 6.60 s, reaching 100 mph in 5.44 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 | Htt Locus Plethore lc750 |
|---|---|
| 0–60 mph | 2.70 s |
| 0–100 mph | 5.44 s |
| 60 ft | 1.61 s |
| 1/8 mile | 6.60 s |
| 1/4 mile | 10.13 s |
| Trap speed | 142.2 mph |
The 2011 Htt Locus Plethore lc750 is a rear-drive turbocharged supercar of 1,150 kg with 750 bhp, which works out at 652 bhp per tonne. Rear drive and 652 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.61 s. Against the 2,929 cars in the set it is the 125th quickest to 60 mph, inside the fastest five per cent. Its 142.2 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 10 of 11 published acceleration figures for this car.
| Specification | Htt Locus Plethore lc750 |
|---|---|
| Year | 2011 |
| Power | 750 bhp |
| Kerb mass | 1,150 kg |
| Power to weight | 652 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 385 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Koenigsegg Agera | 2010 | 2.60 s | 10.17 s | 146.7 mph | 940 bhp |
| Fahlke Larea GT1 S7 | 2011 | 2.72 s | 10.22 s | 141.1 mph | 553 bhp |
| Mosler MT900 GTR | 2008 | 2.75 s | 10.31 s | 137.7 mph | 591 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.