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

SEAT Arosa 1.4 16V 100 (1997)

The SEAT Arosa 1.4 16V 100 (1997) reaches 60 mph in 9.11 s (100 km/h in 9.62 s) and covers a standing quarter mile in 16.98 s, tripping the lights at 82.7 mph. It clears the first 60 ft in 2.83 s and the eighth mile in 11.02 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 Arosa 1.4 16V 100 (1997) Mitsubishi Colt 5dr 1.5 109 (2008)

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 Arosa 1.4 16V 100 (1997)
0–60 mph9.11 s
0–100 km/h9.62 s
0–100 mph—
60 ft2.83 s
1/8 mile11.02 s
1/4 mile16.98 s
Trap speed82.7 mph

About the Arosa 1.4 16V 100

The 1997 SEAT Arosa 1.4 16V 100 (1997) is a front-drive naturally aspirated car of 885 kg with 99 bhp, which works out at 112 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.83 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,610th quickest to 60 mph, and the 58th quickest of the 192 SEATs here. Its 82.7 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 Arosa 1.4 16V 100 (1997)
Year1997
Power99 hp (74 kW)
Kerb mass885 kg
Power to weight112 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed117 mph (188 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Mitsubishi Colt 5dr 1.5 109 (2008)20089.11 s16.98 s82.6 mph109 bhp
Peugeot 106 1.4 9519919.11 s16.98 s82.7 mph94 bhp
Mitsubishi Colt 5dr 1.5 109 (2004)20049.11 s16.97 s82.9 mph107 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 small cars1,681 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 Arosa 1.4 16V 100 (1997) 0-60 time?
The SEAT Arosa 1.4 16V 100 (1997) reaches 60 mph in 9.11 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,610th quickest of the 14,946 cars in the set.
What is the SEAT Arosa 1.4 16V 100 (1997) quarter mile time?
16.98 s at 82.7 mph. It reaches the eighth mile in 11.02 s and clears the first 60 ft in 2.83 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the SEAT Arosa 1.4 16V 100 (1997) have?
99 bhp and 885 kg, which is 112 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 188 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the SEAT Arosa 1.4 16V 100 (1997)?
Closest here on pace: Mitsubishi Colt 5dr 1.5 109 (2008) (9.11 s), Peugeot 106 1.4 95 (9.11 s), Mitsubishi Colt 5dr 1.5 109 (2004) (9.11 s). Each one can be raced against the SEAT Arosa 1.4 16V 100 (1997) 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 Arosa 1.4 16V 100 (1997) 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.