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

SEAT Alhambra 2.0 TDI 170

The SEAT Alhambra 2.0 TDI 170 reaches 60 mph in 8.79 s (100 km/h in 9.40 s) and covers a standing quarter mile in 16.80 s, tripping the lights at 82.6 mph. It clears the first 60 ft in 2.62 s and the eighth mile in 10.81 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 Alhambra 2.0 TDI 170 Renault Espace 2.0 16V Turbo 170

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 Alhambra 2.0 TDI 170
0–60 mph8.79 s
0–100 km/h9.40 s
0–100 mph—
60 ft2.62 s
1/8 mile10.81 s
1/4 mile16.80 s
Trap speed82.6 mph

About the Alhambra 2.0 TDI 170

The 2010 SEAT Alhambra 2.0 TDI 170 is a front-drive turbodiesel MPV of 1,776 kg with 168 bhp, which works out at 94 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.62 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 8,038th quickest to 60 mph, and the 51st quickest of the 192 SEATs here. Its 82.6 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 Alhambra 2.0 TDI 170
Year2010
Power168 hp (125 kW)
Kerb mass1,776 kg
Power to weight94 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed127 mph (204 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Renault Espace 2.0 16V Turbo 17020068.76 s16.79 s83.1 mph168 bhp
Chevrolet Orlando 2.0D 16320108.95 s16.77 s82.0 mph161 bhp
Renault Grand Espace 3.0 dCi V6 24V 18020068.68 s16.65 s83.5 mph178 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 MPVs and people carriers478 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 Alhambra 2.0 TDI 170 0-60 time?
The SEAT Alhambra 2.0 TDI 170 reaches 60 mph in 8.79 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,038th quickest of the 14,946 cars in the set.
What is the SEAT Alhambra 2.0 TDI 170 quarter mile time?
16.80 s at 82.6 mph. It reaches the eighth mile in 10.81 s and clears the first 60 ft in 2.62 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the SEAT Alhambra 2.0 TDI 170 have?
168 bhp and 1,776 kg, which is 94 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 204 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the SEAT Alhambra 2.0 TDI 170?
Closest here on pace: Renault Espace 2.0 16V Turbo 170 (8.76 s), Chevrolet Orlando 2.0D 163 (8.95 s), Renault Grand Espace 3.0 dCi V6 24V 180 (8.68 s). Each one can be raced against the SEAT Alhambra 2.0 TDI 170 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 Alhambra 2.0 TDI 170 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.