← My Auto Racer All cars SEAT 0-60 Comparisons Answers
The SEAT Exeo ST 2.0 TDI reaches 60 mph in 9.64 s and covers a standing quarter mile in 17.44 s, tripping the lights at 81.5 mph. It clears the first 60 ft in 2.86 s and the eighth mile in 11.35 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 | SEAT Exeo ST 2.0 TDI |
|---|---|
| 0–60 mph | 9.64 s |
| 0–100 mph | — |
| 60 ft | 2.86 s |
| 1/8 mile | 11.35 s |
| 1/4 mile | 17.44 s |
| Trap speed | 81.5 mph |
The 2009 SEAT Exeo ST 2.0 TDI is a front-drive turbodiesel car of 1,490 kg with 141 bhp, which works out at 95 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.86 s — so most of what it has to give arrives once it is already moving. Against the 2,939 cars in the set it is the 2,850th quickest to 60 mph, and the 19th quickest of the 19 SEATs here. Its 81.5 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 9 published acceleration figures for this car.
| Specification | SEAT Exeo ST 2.0 TDI |
|---|---|
| Year | 2009 |
| Power | 141 bhp |
| Kerb mass | 1,490 kg |
| Power to weight | 95 bhp/t |
| Drivetrain | Front drive |
| Gears | 6 |
| Engine | Turbodiesel |
| Top speed | 207 km/h |
| Car | Year | 0–60 | 1/4 mile | Trap | Power |
|---|---|---|---|---|---|
| Honda Fit Sport | 2009 | 9.63 s | 17.35 s | 80.3 mph | 117 bhp |
| Honda Civic 1.0 VTEC Turbo (FK) | 2017 | 9.82 s | 17.45 s | 79.9 mph | 127 bhp |
| Alfa Romeo 145 1.7 16V | 1994 | 9.76 s | 17.38 s | 81.9 mph | 127 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-02. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.