← My Auto Racer All cars Noble 0-60 Comparisons
The Noble M12 GTO reaches 60 mph in 3.92 s and covers a standing quarter mile in 12.18 s, tripping the lights at 111.2 mph. It clears the first 60 ft in 1.73 s and the eighth mile in 7.79 s, reaching 100 mph in 9.30 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 | Noble M12 GTO |
|---|---|
| 0–60 mph | 3.92 s |
| 0–100 mph | 9.30 s |
| 60 ft | 1.73 s |
| 1/8 mile | 7.79 s |
| 1/4 mile | 12.18 s |
| Trap speed | 111.2 mph |
The 2000 Noble M12 GTO is a rear-drive turbocharged muscle car of 980 kg with 306 bhp, which works out at 312 bhp per tonne. Rear drive and 312 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.73 s. Against the 2,929 cars in the set it is the 748th quickest to 60 mph, and the 4th quickest of the 5 Nobles here. It leaves better than it pulls: 111.2 mph at the lights is only the 947th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 5 of 5 published acceleration figures for this car.
| Specification | Noble M12 GTO |
|---|---|
| Year | 2000 |
| Power | 306 bhp |
| Kerb mass | 980 kg |
| Power to weight | 312 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 266 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Ford Mustang GT Mk VI facelift | 2017 | 3.93 s | 12.40 s | 112.5 mph | 460 bhp |
| Dodge Charger SRT Hellcat | 2021 | 3.88 s | 11.75 s | 125.3 mph | 707 bhp |
| Aston Martin V12 Vantage Mk I | 2009 | 3.94 s | 12.18 s | 120.2 mph | 510 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.