← My Auto Racer All cars Comparisons Answers

Qoros 3 Hatchbach 1.6 Turbo 156

The Qoros 3 Hatchbach 1.6 Turbo 156 reaches 60 mph in 8.71 s (100 km/h in 9.30 s) and covers a standing quarter mile in 16.72 s, tripping the lights at 82.9 mph. It clears the first 60 ft in 2.60 s and the eighth mile in 10.74 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.

Qoros 3 Hatchbach 1.6 Turbo 156 Alfa Romeo 147 (5dr) 1.9 JTD 120

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 Qoros 3 Hatchbach 1.6 Turbo 156
0–60 mph8.71 s
0–100 km/h9.30 s
0–100 mph—
60 ft2.60 s
1/8 mile10.74 s
1/4 mile16.72 s
Trap speed82.9 mph

About the 3 Hatchbach 1.6 Turbo 156

The 2014 Qoros 3 Hatchbach 1.6 Turbo 156 is a front-drive turbocharged car of 1,410 kg with 125 bhp, which works out at 88 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.60 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,878th quickest to 60 mph, and the quickest of the 4 Qoross here. Its 82.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 Qoros 3 Hatchbach 1.6 Turbo 156
Year2014
Power125 hp (93 kW)
Kerb mass1,410 kg
Power to weight88 bhp/t
DrivetrainFront drive
Gears6
EngineTurbocharged
Top speed130 mph (209 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Alfa Romeo 147 (5dr) 1.9 JTD 12020058.71 s16.61 s83.0 mph118 bhp
MG ZR 5dr 2.0 D 10320048.79 s16.71 s82.4 mph102 bhp
Mazda CX-3 2.0 12020158.64 s16.62 s83.0 mph118 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
Fastest hatchbacks4,513 carsFastest cars of the 2010s4,541 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 Qoros 3 Hatchbach 1.6 Turbo 156 0-60 time?
The Qoros 3 Hatchbach 1.6 Turbo 156 reaches 60 mph in 8.71 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,878th quickest of the 14,946 cars in the set.
What is the Qoros 3 Hatchbach 1.6 Turbo 156 quarter mile time?
16.72 s at 82.9 mph. It reaches the eighth mile in 10.74 s and clears the first 60 ft in 2.60 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Qoros 3 Hatchbach 1.6 Turbo 156 have?
125 bhp and 1,410 kg, which is 88 bhp per tonne. It is front-drive, turbocharged, with 6 gears and a quoted top speed of 209 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Qoros 3 Hatchbach 1.6 Turbo 156?
Closest here on pace: Alfa Romeo 147 (5dr) 1.9 JTD 120 (8.71 s), MG ZR 5dr 2.0 D 103 (8.79 s), Mazda CX-3 2.0 120 (8.64 s). Each one can be raced against the Qoros 3 Hatchbach 1.6 Turbo 156 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 Qoros 3 Hatchbach 1.6 Turbo 156 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.