← My Auto Racer All cars Mosler 0-60 Comparisons
The Mosler MT900 GTR reaches 60 mph in 2.75 s and covers a standing quarter mile in 10.31 s, tripping the lights at 137.7 mph. It clears the first 60 ft in 1.64 s and the eighth mile in 6.74 s, reaching 100 mph in 5.52 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 MT900 GTR |
|---|---|
| 0–60 mph | 2.75 s |
| 0–100 mph | 5.52 s |
| 60 ft | 1.64 s |
| 1/8 mile | 6.74 s |
| 1/4 mile | 10.31 s |
| Trap speed | 137.7 mph |
The 2008 Mosler MT900 GTR is a rear-drive naturally aspirated supercar of 950 kg with 591 bhp, which works out at 623 bhp per tonne. Rear drive and 623 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.64 s. Against the 2,929 cars in the set it is the 143rd quickest to 60 mph, inside the fastest five per cent, and the quickest of the 5 Moslers here. Its 137.7 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 | Mosler MT900 GTR |
|---|---|
| Year | 2008 |
| Power | 591 bhp |
| Kerb mass | 950 kg |
| Power to weight | 623 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 342 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| 9ff BT-2 | 2009 | 2.76 s | 10.31 s | 138.8 mph | 850 bhp |
| Fahlke Larea GT1 S7 | 2011 | 2.72 s | 10.22 s | 141.1 mph | 553 bhp |
| Jaguar XJ220S TWR | 2015 | 2.79 s | 10.49 s | 136.8 mph | 671 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.