← My Auto Racer All cars Comparisons Answers
The Rossion Q1 reaches 60 mph in 3.01 s (100 km/h in 3.14 s) and covers a standing quarter mile in 11.27 s, tripping the lights at 121.6 mph. It clears the first 60 ft in 1.68 s and the eighth mile in 7.27 s, reaching 100 mph in 7.45 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 | Rossion Q1 |
|---|---|
| 0–60 mph | 3.01 s |
| 0–100 km/h | 3.14 s |
| 0–100 mph | 7.45 s |
| 60 ft | 1.68 s |
| 1/8 mile | 7.27 s |
| 1/4 mile | 11.27 s |
| Trap speed | 121.6 mph |
The 2008 Rossion Q1 is a rear-drive turbocharged supercar of 1,083 kg with 451 bhp, which works out at 416 bhp per tonne. Rear drive and 416 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.68 s. Against the 14,946 cars in the set it is the 278th quickest to 60 mph, inside the fastest five per cent. Its 121.6 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 | Rossion Q1 |
|---|---|
| Year | 2008 |
| Power | 451 hp (336 kW) |
| Kerb mass | 1,083 kg |
| Power to weight | 416 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 185 mph (298 km/h), quoted |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Ruf R-Turbo | 2015 | 3.06 s | 11.17 s | 125.1 mph | 582 bhp |
| Bugatti EB110 SS | 1992 | 3.05 s | 11.10 s | 131.3 mph | 603 bhp |
| Lotus Exige Cup 430 Mk III | 2017 | 3.04 s | 11.41 s | 119.4 mph | 430 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-10-16. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.