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

Kia Rio Hatchback 1.6 16V 112

The Kia Rio Hatchback 1.6 16V 112 reaches 60 mph in 9.29 s (100 km/h in 9.82 s) and covers a standing quarter mile in 17.10 s, tripping the lights at 82.2 mph. It clears the first 60 ft in 2.87 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.

Kia Rio Hatchback 1.6 16V 112 Citroen ZX 3dr 1.8i 103 (1992)

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 Kia Rio Hatchback 1.6 16V 112
0–60 mph9.29 s
0–100 km/h9.82 s
0–100 mph—
60 ft2.87 s
1/8 mile11.11 s
1/4 mile17.10 s
Trap speed82.2 mph

About the Rio Hatchback 1.6 16V 112

The 2005 Kia Rio Hatchback 1.6 16V 112 is a front-drive naturally aspirated car of 1,079 kg with 110 bhp, which works out at 102 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.87 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,934th quickest to 60 mph, and the 56th quickest of the 205 Kias here. Its 82.2 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 Kia Rio Hatchback 1.6 16V 112
Year2005
Power110 hp (82 kW)
Kerb mass1,079 kg
Power to weight102 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed117 mph (188 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Citroen ZX 3dr 1.8i 103 (1992)19929.29 s17.10 s82.2 mph102 bhp
Alfa Romeo 145 1.6 TS 12019949.30 s17.07 s82.8 mph118 bhp
Honda Civic 5dr 1.6i 13319959.30 s17.08 s82.6 mph111 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
Kia 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 Kia Rio Hatchback 1.6 16V 112 0-60 time?
The Kia Rio Hatchback 1.6 16V 112 reaches 60 mph in 9.29 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,934th quickest of the 14,946 cars in the set.
What is the Kia Rio Hatchback 1.6 16V 112 quarter mile time?
17.10 s at 82.2 mph. It reaches the eighth mile in 11.11 s and clears the first 60 ft in 2.87 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Kia Rio Hatchback 1.6 16V 112 have?
110 bhp and 1,079 kg, which is 102 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 Kia Rio Hatchback 1.6 16V 112?
Closest here on pace: Citroen ZX 3dr 1.8i 103 (1992) (9.29 s), Alfa Romeo 145 1.6 TS 120 (9.30 s), Honda Civic 5dr 1.6i 133 (9.30 s). Each one can be raced against the Kia Rio Hatchback 1.6 16V 112 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 Kia Rio Hatchback 1.6 16V 112 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.