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

Pontiac Trans Sport 2.3i 16V 137

The Pontiac Trans Sport 2.3i 16V 137 reaches 60 mph in 11.23 s (100 km/h in 11.88 s) and covers a standing quarter mile in 18.37 s, tripping the lights at 77.4 mph. It clears the first 60 ft in 3.17 s and the eighth mile in 12.01 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.

Pontiac Trans Sport 2.3i 16V 137 Lancia Musa 1.3 Multijet 95

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 Pontiac Trans Sport 2.3i 16V 137
0–60 mph11.23 s
0–100 km/h11.88 s
0–100 mph—
60 ft3.17 s
1/8 mile12.01 s
1/4 mile18.37 s
Trap speed77.4 mph

About the Trans Sport 2.3i 16V 137

The 1990 Pontiac Trans Sport 2.3i 16V 137 is a front-drive naturally aspirated SUV of 1,735 kg with 135 bhp, which works out at 78 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.17 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,941st quickest to 60 mph, and the 26th quickest of the 26 Pontiacs here. Its 77.4 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 Pontiac Trans Sport 2.3i 16V 137
Year1990
Power135 hp (101 kW)
Kerb mass1,735 kg
Power to weight78 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed115 mph (185 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lancia Musa 1.3 Multijet 95200311.24 s18.31 s75.0 mph91 bhp
Lancia Musa 1.3 Multijet 90200311.24 s18.31 s75.0 mph89 bhp
Ssangyong Rexton 2.3 150200111.29 s18.46 s76.1 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Pontiac 0-60 timesevery modelFastest SUVs2,049 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 Pontiac Trans Sport 2.3i 16V 137 0-60 time?
The Pontiac Trans Sport 2.3i 16V 137 reaches 60 mph in 11.23 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,941st quickest of the 14,946 cars in the set.
What is the Pontiac Trans Sport 2.3i 16V 137 quarter mile time?
18.37 s at 77.4 mph. It reaches the eighth mile in 12.01 s and clears the first 60 ft in 3.17 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Pontiac Trans Sport 2.3i 16V 137 have?
135 bhp and 1,735 kg, which is 78 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 185 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Pontiac Trans Sport 2.3i 16V 137?
Closest here on pace: Lancia Musa 1.3 Multijet 95 (11.24 s), Lancia Musa 1.3 Multijet 90 (11.24 s), Ssangyong Rexton 2.3 150 (11.29 s). Each one can be raced against the Pontiac Trans Sport 2.3i 16V 137 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 Pontiac Trans Sport 2.3i 16V 137 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.