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

SEAT Altea Freetrack 1.6 TDI 105

The SEAT Altea Freetrack 1.6 TDI 105 reaches 60 mph in 11.43 s (100 km/h in 12.16 s) and covers a standing quarter mile in 18.24 s, tripping the lights at 74.8 mph. It clears the first 60 ft in 2.70 s and the eighth mile in 11.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 Altea Freetrack 1.6 TDI 105 Toyota Land Cruiser 150 2.8 D-4D 177

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 Altea Freetrack 1.6 TDI 105
0–60 mph11.43 s
0–100 km/h12.16 s
0–100 mph—
60 ft2.70 s
1/8 mile11.67 s
1/4 mile18.24 s
Trap speed74.8 mph

About the Altea Freetrack 1.6 TDI 105

The 2009 SEAT Altea Freetrack 1.6 TDI 105 is a front-drive turbodiesel SUV of 1,405 kg with 103 bhp, which works out at 73 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.70 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 12,210th quickest to 60 mph, and the 113th quickest of the 192 SEATs here. Its 74.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 Altea Freetrack 1.6 TDI 105
Year2009
Power103 hp (77 kW)
Kerb mass1,405 kg
Power to weight73 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed110 mph (177 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Toyota Land Cruiser 150 2.8 D-4D 177201711.42 s18.23 s74.1 mph174 bhp
Dacia Jogger 1.0 TCe EGO-G 101202311.33 s18.21 s75.0 mph90 bhp
Chrysler Town and Country 2.5 CRD 145200011.43 s18.34 s75.2 mph139 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 SUVs2,049 carsFastest cars of the 2000s5,138 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 Altea Freetrack 1.6 TDI 105 0-60 time?
The SEAT Altea Freetrack 1.6 TDI 105 reaches 60 mph in 11.43 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 12,210th quickest of the 14,946 cars in the set.
What is the SEAT Altea Freetrack 1.6 TDI 105 quarter mile time?
18.24 s at 74.8 mph. It reaches the eighth mile in 11.67 s and clears the first 60 ft in 2.70 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the SEAT Altea Freetrack 1.6 TDI 105 have?
103 bhp and 1,405 kg, which is 73 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 177 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the SEAT Altea Freetrack 1.6 TDI 105?
Closest here on pace: Toyota Land Cruiser 150 2.8 D-4D 177 (11.42 s), Dacia Jogger 1.0 TCe EGO-G 101 (11.33 s), Chrysler Town and Country 2.5 CRD 145 (11.43 s). Each one can be raced against the SEAT Altea Freetrack 1.6 TDI 105 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 Altea Freetrack 1.6 TDI 105 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.