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

SEAT Alhambra 1.8 Turbo 150

The SEAT Alhambra 1.8 Turbo 150 reaches 60 mph in 10.90 s (100 km/h in 11.57 s) and covers a standing quarter mile in 17.99 s, tripping the lights at 76.8 mph. It clears the first 60 ft in 2.94 s and the eighth mile in 11.62 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 1.8 Turbo 150 Peugeot Tepee Partner 1.6 VTi 120 BVM5

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 1.8 Turbo 150
0–60 mph10.90 s
0–100 km/h11.57 s
0–100 mph—
60 ft2.94 s
1/8 mile11.62 s
1/4 mile17.99 s
Trap speed76.8 mph

About the Alhambra 1.8 Turbo 150

The 1996 SEAT Alhambra 1.8 Turbo 150 is a front-drive turbocharged MPV of 1,589 kg with 148 bhp, which works out at 93 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.94 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 11,520th quickest to 60 mph, and the 93rd quickest of the 192 SEATs here. Its 76.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 Alhambra 1.8 Turbo 150
Year1996
Power148 hp (110 kW)
Kerb mass1,589 kg
Power to weight93 bhp/t
DrivetrainFront drive
Gears5
EngineTurbocharged
Top speed121 mph (194 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Peugeot Tepee Partner 1.6 VTi 120 BVM5200810.93 s18.22 s77.3 mph118 bhp
Vauxhall Meriva 1.4 ecoFLEX bi-fuel 120201410.71 s17.90 s77.0 mph118 bhp
Chevrolet Orlando 1.8 141201010.65 s17.82 s76.6 mph138 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

Slower 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 1990s2,649 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 1.8 Turbo 150 0-60 time?
The SEAT Alhambra 1.8 Turbo 150 reaches 60 mph in 10.90 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,520th quickest of the 14,946 cars in the set.
What is the SEAT Alhambra 1.8 Turbo 150 quarter mile time?
17.99 s at 76.8 mph. It reaches the eighth mile in 11.62 s and clears the first 60 ft in 2.94 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the SEAT Alhambra 1.8 Turbo 150 have?
148 bhp and 1,589 kg, which is 93 bhp per tonne. It is front-drive, turbocharged, with 5 gears and a quoted top speed of 194 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the SEAT Alhambra 1.8 Turbo 150?
Closest here on pace: Peugeot Tepee Partner 1.6 VTi 120 BVM5 (10.93 s), Vauxhall Meriva 1.4 ecoFLEX bi-fuel 120 (10.71 s), Chevrolet Orlando 1.8 141 (10.65 s). Each one can be raced against the SEAT Alhambra 1.8 Turbo 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 Alhambra 1.8 Turbo 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.