← My Auto Racer All cars Wiesmann 0-60 Comparisons
The Wiesmann GT MF5 Mk II reaches 60 mph in 3.50 s and covers a standing quarter mile in 11.46 s, tripping the lights at 125.5 mph. It clears the first 60 ft in 1.86 s and the eighth mile in 7.54 s, reaching 100 mph in 7.65 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 | Wiesmann GT MF5 Mk II |
|---|---|
| 0–60 mph | 3.50 s |
| 0–100 mph | 7.65 s |
| 60 ft | 1.86 s |
| 1/8 mile | 7.54 s |
| 1/4 mile | 11.46 s |
| Trap speed | 125.5 mph |
The 2011 Wiesmann GT MF5 Mk II is a rear-drive turbocharged supercar of 1,405 kg with 547 bhp, which works out at 389 bhp per tonne. Rear drive and 389 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.86 s. Against the 2,929 cars in the set it is the 506th quickest to 60 mph, inside the fastest quarter, and the quickest of the 6 Wiesmanns here. Its 125.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 9 of 11 published acceleration figures for this car.
| Specification | Wiesmann GT MF5 Mk II |
|---|---|
| Year | 2011 |
| Power | 547 bhp |
| Kerb mass | 1,405 kg |
| Power to weight | 389 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 311 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Dodge Viper ACR Mk V | 2016 | 3.51 s | 11.48 s | 126.1 mph | 645 bhp |
| Lexus LFA Nurburgring Package | 2012 | 3.45 s | 11.43 s | 128.2 mph | 562 bhp |
| SRT Viper | 2013 | 3.49 s | 11.39 s | 129.2 mph | 640 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.