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

Opel Tigra Twin Top 1.8 16V 125

The Opel Tigra Twin Top 1.8 16V 125 reaches 60 mph in 8.56 s (100 km/h in 9.04 s) and covers a standing quarter mile in 16.51 s, tripping the lights at 85.8 mph. It clears the first 60 ft in 2.81 s and the eighth mile in 10.78 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 Tigra Twin Top 1.8 16V 125 Lancia Delta 1.8 130

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 Tigra Twin Top 1.8 16V 125
0–60 mph8.56 s
0–100 km/h9.04 s
0–100 mph—
60 ft2.81 s
1/8 mile10.78 s
1/4 mile16.51 s
Trap speed85.8 mph

About the Tigra Twin Top 1.8 16V 125

The 2005 Opel Tigra Twin Top 1.8 16V 125 is a front-drive naturally aspirated car of 1,165 kg with 123 bhp, which works out at 106 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.81 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,601st quickest to 60 mph, and the 174th quickest of the 721 Opels here. Its 85.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 Opel Tigra Twin Top 1.8 16V 125
Year2005
Power123 hp (92 kW)
Kerb mass1,165 kg
Power to weight106 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed127 mph (204 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Lancia Delta 1.8 13019938.56 s16.53 s85.5 mph129 bhp
Lancia Delta HPE 1.8 13019958.56 s16.53 s85.5 mph129 bhp
Holden Tigra 1.8 12620058.56 s16.51 s85.8 mph123 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 small cars1,681 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 Opel Tigra Twin Top 1.8 16V 125 0-60 time?
The Opel Tigra Twin Top 1.8 16V 125 reaches 60 mph in 8.56 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,601st quickest of the 14,946 cars in the set.
What is the Opel Tigra Twin Top 1.8 16V 125 quarter mile time?
16.51 s at 85.8 mph. It reaches the eighth mile in 10.78 s and clears the first 60 ft in 2.81 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Opel Tigra Twin Top 1.8 16V 125 have?
123 bhp and 1,165 kg, which is 106 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 204 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Opel Tigra Twin Top 1.8 16V 125?
Closest here on pace: Lancia Delta 1.8 130 (8.56 s), Lancia Delta HPE 1.8 130 (8.56 s), Holden Tigra 1.8 126 (8.56 s). Each one can be raced against the Opel Tigra Twin Top 1.8 16V 125 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 Tigra Twin Top 1.8 16V 125 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.