← My Auto Racer All cars Noble 0-60 Comparisons
The Noble M400 reaches 60 mph in 3.15 s and covers a standing quarter mile in 11.33 s, tripping the lights at 122.5 mph. It clears the first 60 ft in 1.74 s and the eighth mile in 7.35 s, reaching 100 mph in 7.48 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 M400 |
|---|---|
| 0–60 mph | 3.15 s |
| 0–100 mph | 7.48 s |
| 60 ft | 1.74 s |
| 1/8 mile | 7.35 s |
| 1/4 mile | 11.33 s |
| Trap speed | 122.5 mph |
The 2005 Noble M400 is a rear-drive turbocharged supercar of 960 kg with 420 bhp, which works out at 437 bhp per tonne. Rear drive and 437 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.74 s. Against the 2,929 cars in the set it is the 297th quickest to 60 mph, inside the fastest quarter, and the 2nd quickest of the 5 Nobles here. Its 122.5 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 | Noble M400 |
|---|---|
| Year | 2005 |
| Power | 420 bhp |
| Kerb mass | 960 kg |
| Power to weight | 437 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 300 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Mosler MT900S | 2015 | 3.11 s | 11.33 s | 122.1 mph | 429 bhp |
| Lucra Cars LC 470 LS6 engine | 2010 | 3.15 s | 11.40 s | 122.5 mph | 400 bhp |
| Chevrolet Corvette Z06 Z07 Package C7 | 2015 | 3.23 s | 11.28 s | 125.5 mph | 650 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.