← My Auto Racer All cars Mosler 0-60 Comparisons
The Mosler MT900S reaches 60 mph in 3.11 s and covers a standing quarter mile in 11.33 s, tripping the lights at 122.1 mph. It clears the first 60 ft in 1.78 s and the eighth mile in 7.29 s, reaching 100 mph in 7.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 | Mosler MT900S |
|---|---|
| 0–60 mph | 3.11 s |
| 0–100 mph | 7.44 s |
| 60 ft | 1.78 s |
| 1/8 mile | 7.29 s |
| 1/4 mile | 11.33 s |
| Trap speed | 122.1 mph |
The 2015 Mosler MT900S is a rear-drive naturally aspirated supercar of 900 kg with 429 bhp, which works out at 477 bhp per tonne. Rear drive and 477 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.78 s. Against the 2,929 cars in the set it is the 278th quickest to 60 mph, inside the fastest tenth, and the 3rd quickest of the 5 Moslers here. Its 122.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 | Mosler MT900S |
|---|---|
| Year | 2015 |
| Power | 429 bhp |
| Kerb mass | 900 kg |
| Power to weight | 477 bhp/t |
| Drivetrain | Rear drive |
| Gears | 7 |
| Engine | Naturally aspirated |
| Top speed | 306 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Noble M400 | 2005 | 3.15 s | 11.33 s | 122.5 mph | 420 bhp |
| Laraki Fulgura V8 | 2015 | 3.26 s | 11.25 s | 126.1 mph | 575 bhp |
| Lucra Cars LC 470 LS6 engine | 2010 | 3.15 s | 11.40 s | 122.5 mph | 400 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.