← My Auto Racer All cars Oldsmobile 0-60 Comparisons
The Oldsmobile Toronado reaches 60 mph in 8.30 s and covers a standing quarter mile in 16.37 s, tripping the lights at 94.1 mph. It clears the first 60 ft in 2.93 s and the eighth mile in 11.05 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 | Oldsmobile Toronado |
|---|---|
| 0–60 mph | 8.30 s |
| 0–100 mph | — |
| 60 ft | 2.93 s |
| 1/8 mile | 11.05 s |
| 1/4 mile | 16.37 s |
| Trap speed | 94.1 mph |
The 1966 Oldsmobile Toronado is a front-drive naturally aspirated saloon of 2,111 kg with 385 bhp, which works out at 182 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.93 s — so most of what it has to give arrives once it is already moving. Against the 2,929 cars in the set it is the 2,694th quickest to 60 mph. It traps higher than its 0-60 suggests — 94.1 mph, the 2,221st highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 8 of 9 published acceleration figures for this car.
| Specification | Oldsmobile Toronado |
|---|---|
| Year | 1966 |
| Power | 385 bhp |
| Kerb mass | 2,111 kg |
| Power to weight | 182 bhp/t |
| Drivetrain | Front drive |
| Gears | 5 |
| Engine | Naturally aspirated |
| Top speed | 217 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Rover 3500 Vitesse SD1 | 1984 | 8.08 s | 16.44 s | 87.5 mph | 186 bhp |
| Jensen Healey MK I | 1972 | 8.40 s | 16.47 s | 85.4 mph | 139 bhp |
| Rover 827i Fastback | 1988 | 8.24 s | 16.48 s | 88.9 mph | 177 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.