← My Auto Racer All cars Marcos 0-60 Comparisons
The Marcos TSO GT2 reaches 60 mph in 3.63 s and covers a standing quarter mile in 11.79 s, tripping the lights at 120.8 mph. It clears the first 60 ft in 1.91 s and the eighth mile in 7.73 s, reaching 100 mph in 8.24 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 | Marcos TSO GT2 |
|---|---|
| 0–60 mph | 3.63 s |
| 0–100 mph | 8.24 s |
| 60 ft | 1.91 s |
| 1/8 mile | 7.73 s |
| 1/4 mile | 11.79 s |
| Trap speed | 120.8 mph |
The 2006 Marcos TSO GT2 is a rear-drive naturally aspirated supercar of 1,172 kg with 468 bhp, which works out at 399 bhp per tonne. Rear drive and 399 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.91 s. Against the 2,929 cars in the set it is the 572nd quickest to 60 mph, inside the fastest quarter, and the 2nd quickest of the 4 Marcoss here. Its 120.8 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 | Marcos TSO GT2 |
|---|---|
| Year | 2006 |
| Power | 468 bhp |
| Kerb mass | 1,172 kg |
| Power to weight | 399 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 300 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Dodge Viper SRT-10 612 PS | 2008 | 3.70 s | 11.76 s | 124.4 mph | 603 bhp |
| Wiesmann GT MF5 | 2008 | 3.62 s | 11.68 s | 125.8 mph | 500 bhp |
| Ford GT Mk I | 2004 | 3.64 s | 11.62 s | 126.1 mph | 543 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.