← My Auto Racer All cars Carlsson 0-60 Comparisons
The Carlsson C25 reaches 60 mph in 3.33 s and covers a standing quarter mile in 11.19 s, tripping the lights at 129.9 mph. It clears the first 60 ft in 1.81 s and the eighth mile in 7.32 s, reaching 100 mph in 6.93 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 | Carlsson C25 |
|---|---|
| 0–60 mph | 3.33 s |
| 0–100 mph | 6.93 s |
| 60 ft | 1.81 s |
| 1/8 mile | 7.32 s |
| 1/4 mile | 11.19 s |
| Trap speed | 129.9 mph |
The 2010 Carlsson C25 is a rear-drive turbocharged supercar of 1,950 kg with 743 bhp, which works out at 381 bhp per tonne. Rear drive and 381 bhp per tonne make the launch the hard part of the run: 60 ft takes 1.81 s. Against the 2,929 cars in the set it is the 396th quickest to 60 mph, inside the fastest quarter. It traps higher than its 0-60 suggests — 129.9 mph, the 216th highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 9 of 11 published acceleration figures for this car.
| Specification | Carlsson C25 |
|---|---|
| Year | 2010 |
| Power | 743 bhp |
| Kerb mass | 1,950 kg |
| Power to weight | 381 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Turbocharged |
| Top speed | 352 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Palmer Jaguar JP1 | 2005 | 3.29 s | 11.26 s | 128.9 mph | 249 bhp |
| Superformance Le Mans Coupe V8 | 2007 | 3.37 s | 11.42 s | 126.6 mph | 510 bhp |
| Pagani Zonda C12-S 7.3 Roadster | 2005 | 3.27 s | 11.26 s | 128.5 mph | 547 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.