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

SEAT Tarraco 2.0 TDI 150

The SEAT Tarraco 2.0 TDI 150 reaches 60 mph in 8.72 s (100 km/h in 9.38 s) and covers a standing quarter mile in 16.61 s, tripping the lights at 80.7 mph. It clears the first 60 ft in 2.33 s and the eighth mile in 10.50 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 2.0 TDI 150 Skoda Kodiaq 1.4 TSI 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 2.0 TDI 150
0–60 mph8.72 s
0–100 km/h9.38 s
0–100 mph—
60 ft2.33 s
1/8 mile10.50 s
1/4 mile16.61 s
Trap speed80.7 mph

About the Tarraco 2.0 TDI 150

The 2018 SEAT Tarraco 2.0 TDI 150 is an all-wheel-drive turbodiesel SUV of 1,728 kg with 148 bhp, which works out at 85 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.33 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 7,897th quickest to 60 mph, and the 50th quickest of the 192 SEATs here. It leaves better than it pulls: 80.7 mph at the lights is only the 9,652nd highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification SEAT Tarraco 2.0 TDI 150
Year2018
Power148 hp (110 kW)
Kerb mass1,728 kg
Power to weight85 bhp/t
DrivetrainAll-wheel drive
Gears7
EngineTurbodiesel
Top speed123 mph (198 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Skoda Kodiaq 1.4 TSI 15020168.72 s16.56 s81.5 mph148 bhp
Volvo V60 Cross Country 2.0 D3 15020188.63 s16.57 s80.5 mph148 bhp
Subaru Outback 2.0D CVT 15020148.71 s16.73 s81.7 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 2.0 TDI 150 0-60 time?
The SEAT Tarraco 2.0 TDI 150 reaches 60 mph in 8.72 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,897th quickest of the 14,946 cars in the set.
What is the SEAT Tarraco 2.0 TDI 150 quarter mile time?
16.61 s at 80.7 mph. It reaches the eighth mile in 10.50 s and clears the first 60 ft in 2.33 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the SEAT Tarraco 2.0 TDI 150 have?
148 bhp and 1,728 kg, which is 85 bhp per tonne. It is all-wheel-drive, turbodiesel, with 7 gears and a quoted top speed of 198 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the SEAT Tarraco 2.0 TDI 150?
Closest here on pace: Skoda Kodiaq 1.4 TSI 150 (8.72 s), Volvo V60 Cross Country 2.0 D3 150 (8.63 s), Subaru Outback 2.0D CVT 150 (8.71 s). Each one can be raced against the SEAT Tarraco 2.0 TDI 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 2.0 TDI 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.