← My Auto Racer All cars SEAT 0-60 Comparisons Answers

SEAT Tarraco 1.5 TSI 150

The SEAT Tarraco 1.5 TSI 150 reaches 60 mph in 8.33 s (100 km/h in 9.33 s) and covers a standing quarter mile in 16.53 s, tripping the lights at 83.8 mph. It clears the first 60 ft in 2.53 s and the eighth mile in 10.67 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.

SEAT Tarraco 1.5 TSI 150 Mitsubishi ASX / RVR / Outlander Sport 1.8 DiD 2WD 150

Pick who it runs against, then watch it happen — and change the surface, the weather or the distance and run it again.

Down the strip

Standing start SEAT Tarraco 1.5 TSI 150
0–60 mph8.33 s
0–100 km/h9.33 s
0–100 mph—
60 ft2.53 s
1/8 mile10.67 s
1/4 mile16.53 s
Trap speed83.8 mph

About the Tarraco 1.5 TSI 150

The 2018 SEAT Tarraco 1.5 TSI 150 is a front-drive turbocharged SUV of 1,524 kg with 148 bhp, which works out at 97 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.53 s — so most of what it has to give arrives once it is already moving. Against the 14,946 cars in the set it is the 7,178th quickest to 60 mph, and the 44th quickest of the 192 SEATs here. Its 83.8 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 2 of 2 published acceleration figures for this car.

On paper

Specification SEAT Tarraco 1.5 TSI 150
Year2018
Power148 hp (110 kW)
Kerb mass1,524 kg
Power to weight97 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed125 mph (201 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mitsubishi ASX / RVR / Outlander Sport 1.8 DiD 2WD 15020108.34 s16.54 s83.8 mph148 bhp
Ford C-Max 2.0 TDCi 15020148.31 s16.50 s83.9 mph148 bhp
Cupra Terramar 1.5 eTSI MHEV 15020258.35 s16.49 s83.9 mph148 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.

Where these times sit

0-60 under 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
SEAT 0-60 timesevery modelFastest SUVs2,049 carsFastest cars of the 2010s4,541 cars
Put this race on your own page

Free to use anywhere, no attribution required beyond the credit line included above. How to embed →

Questions

What is the SEAT Tarraco 1.5 TSI 150 0-60 time?
The SEAT Tarraco 1.5 TSI 150 reaches 60 mph in 8.33 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,178th quickest of the 14,946 cars in the set.
What is the SEAT Tarraco 1.5 TSI 150 quarter mile time?
16.53 s at 83.8 mph. It reaches the eighth mile in 10.67 s and clears the first 60 ft in 2.53 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the SEAT Tarraco 1.5 TSI 150 have?
148 bhp and 1,524 kg, which is 97 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 201 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the SEAT Tarraco 1.5 TSI 150?
Closest here on pace: Mitsubishi ASX / RVR / Outlander Sport 1.8 DiD 2WD 150 (8.34 s), Ford C-Max 2.0 TDCi 150 (8.31 s), Cupra Terramar 1.5 eTSI MHEV 150 (8.35 s). Each one can be raced against the SEAT Tarraco 1.5 TSI 150 in the panel at the top of this page. These are theoretical times from a physics simulation, not measured runs.
Are these real measured times?
No. Every figure on this page is produced by a physics simulation, not by a stopwatch at a drag strip. The SEAT Tarraco 1.5 TSI 150 is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 2 of its 2 published acceleration figures. Conditions are the same for every car in the set: dry asphalt, 20 °C, sea level, 1 ft rollout.

Figures regenerated 2026-10-12. Every number on this page is computed by the simulator at build time, so the page and the app can never disagree.