← My Auto Racer All cars Honda 0-60 Comparisons
The Honda S2000 Type S reaches 60 mph in 5.47 s and covers a standing quarter mile in 14.03 s, tripping the lights at 100.2 mph. It clears the first 60 ft in 2.26 s and the eighth mile in 9.07 s, reaching 100 mph in 13.98 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 | Honda S2000 Type S |
|---|---|
| 0–60 mph | 5.47 s |
| 0–100 mph | 13.98 s |
| 60 ft | 2.26 s |
| 1/8 mile | 9.07 s |
| 1/4 mile | 14.03 s |
| Trap speed | 100.2 mph |
The 2007 Honda S2000 Type S is a rear-drive naturally aspirated roadster of 1,270 kg with 239 bhp, which works out at 188 bhp per tonne. Rear drive and 188 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.26 s. Against the 2,929 cars in the set it is the 1,658th quickest to 60 mph, and the 10th quickest of the 41 Hondas here. Its 100.2 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 10 published acceleration figures for this car.
| Specification | Honda S2000 Type S |
|---|---|
| Year | 2007 |
| Power | 239 bhp |
| Kerb mass | 1,270 kg |
| Power to weight | 188 bhp/t |
| Drivetrain | Rear drive |
| Gears | 6 |
| Engine | Naturally aspirated |
| Top speed | 251 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Nissan 350Z 313 PS | 2007 | 5.51 s | 13.91 s | 103.0 mph | 308 bhp |
| Lotus Exige | 2004 | 5.32 s | 13.85 s | 98.9 mph | 189 bhp |
| Renault Megane RS 265 Trophy | 2011 | 5.51 s | 14.01 s | 100.9 mph | 261 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.