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

Opel Vectra Sedan 2.0i 16V 135

The Opel Vectra Sedan 2.0i 16V 135 reaches 60 mph in 8.67 s (100 km/h in 9.63 s) and covers a standing quarter mile in 16.89 s, tripping the lights at 84.9 mph. It clears the first 60 ft in 2.94 s and the eighth mile in 11.11 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.

Opel Vectra Sedan 2.0i 16V 135 Holden Vectra Sedan 2.2 147

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 Opel Vectra Sedan 2.0i 16V 135
0–60 mph8.67 s
0–100 km/h9.63 s
0–100 mph—
60 ft2.94 s
1/8 mile11.11 s
1/4 mile16.89 s
Trap speed84.9 mph

About the Vectra Sedan 2.0i 16V 135

The 1995 Opel Vectra Sedan 2.0i 16V 135 is a front-drive naturally aspirated saloon of 1,252 kg with 134 bhp, which works out at 107 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 7,823rd quickest to 60 mph, and the 191st quickest of the 721 Opels here. Its 84.9 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 Opel Vectra Sedan 2.0i 16V 135
Year1995
Power134 hp (100 kW)
Kerb mass1,252 kg
Power to weight107 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed134 mph (215 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Holden Vectra Sedan 2.2 14719958.67 s16.88 s85.7 mph145 bhp
Alfa Romeo GT 1.9 JTD 15020038.67 s16.70 s83.7 mph148 bhp
Lexus ES 250 18420128.62 s16.77 s82.9 mph181 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
Opel 0-60 timesevery modelFastest saloon cars3,808 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 Opel Vectra Sedan 2.0i 16V 135 0-60 time?
The Opel Vectra Sedan 2.0i 16V 135 reaches 60 mph in 8.67 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,823rd quickest of the 14,946 cars in the set.
What is the Opel Vectra Sedan 2.0i 16V 135 quarter mile time?
16.89 s at 84.9 mph. It reaches the eighth mile in 11.11 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 Opel Vectra Sedan 2.0i 16V 135 have?
134 bhp and 1,252 kg, which is 107 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 215 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Opel Vectra Sedan 2.0i 16V 135?
Closest here on pace: Holden Vectra Sedan 2.2 147 (8.67 s), Alfa Romeo GT 1.9 JTD 150 (8.67 s), Lexus ES 250 184 (8.62 s). Each one can be raced against the Opel Vectra Sedan 2.0i 16V 135 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 Opel Vectra Sedan 2.0i 16V 135 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.