← My Auto Racer All cars Lotec 0-60 Comparisons
The Lotec Sirius reaches 60 mph in 3.37 s and covers a standing quarter mile in 10.41 s, tripping the lights at 160.2 mph. It clears the first 60 ft in 1.91 s and the eighth mile in 7.18 s, reaching 100 mph in 6.04 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 | Lotec Sirius |
|---|---|
| 0–60 mph | 3.37 s |
| 0–100 mph | 6.04 s |
| 60 ft | 1.91 s |
| 1/8 mile | 7.18 s |
| 1/4 mile | 10.41 s |
| Trap speed | 160.2 mph |
The 2015 Lotec Sirius is a rear-drive turbocharged supercar of 1,282 kg with 1,183 bhp, which works out at 923 bhp per tonne. Rear drive and 923 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.91 s. Against the 2,929 cars in the set it is the 419th quickest to 60 mph, inside the fastest quarter, and the quickest of the 3 Lotecs here. It traps higher than its 0-60 suggests — 160.2 mph, the 19th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 10 of 11 published acceleration figures for this car.
| Specification | Lotec Sirius |
|---|---|
| Year | 2015 |
| Power | 1,183 bhp |
| Kerb mass | 1,282 kg |
| Power to weight | 923 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Turbocharged |
| Top speed | 402 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Toyota GT-One TS020 | 1999 | 3.37 s | 10.56 s | 147.7 mph | 591 bhp |
| Praga Bohema | 2023 | 3.06 s | 10.25 s | 147.4 mph | 700 bhp |
| Lotec C1000 | 1991 | 3.43 s | 10.86 s | 146.9 mph | 838 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.