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

Fiat Palio Weekend 1.6 16v 115

The Fiat Palio Weekend 1.6 16v 115 reaches 60 mph in 9.10 s (100 km/h in 9.62 s) and covers a standing quarter mile in 17.01 s, tripping the lights at 82.2 mph. It clears the first 60 ft in 2.80 s and the eighth mile in 11.00 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.

Fiat Palio Weekend 1.6 16v 115 Kia Pro cee'd 2.0 CRDi 140

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 Fiat Palio Weekend 1.6 16v 115
0–60 mph9.10 s
0–100 km/h9.62 s
0–100 mph—
60 ft2.80 s
1/8 mile11.00 s
1/4 mile17.01 s
Trap speed82.2 mph

About the Palio Weekend 1.6 16v 115

The 2012 Fiat Palio Weekend 1.6 16v 115 is a front-drive naturally aspirated car of 1,186 kg with 114 bhp, which works out at 96 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.80 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,583rd quickest to 60 mph, and the 89th quickest of the 455 Fiats 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 Fiat Palio Weekend 1.6 16v 115
Year2012
Power114 hp (85 kW)
Kerb mass1,186 kg
Power to weight96 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed113 mph (182 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Kia Pro cee'd 2.0 CRDi 14020079.10 s17.00 s82.0 mph138 bhp
Dacia Logan 1.6 MPI 10520049.10 s17.00 s82.3 mph103 bhp
MG Montego EFi19849.09 s16.96 s84.8 mph117 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
Fiat 0-60 timesevery modelFastest 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 Fiat Palio Weekend 1.6 16v 115 0-60 time?
The Fiat Palio Weekend 1.6 16v 115 reaches 60 mph in 9.10 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,583rd quickest of the 14,946 cars in the set.
What is the Fiat Palio Weekend 1.6 16v 115 quarter mile time?
17.01 s at 82.2 mph. It reaches the eighth mile in 11.00 s and clears the first 60 ft in 2.80 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Fiat Palio Weekend 1.6 16v 115 have?
114 bhp and 1,186 kg, which is 96 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 182 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Fiat Palio Weekend 1.6 16v 115?
Closest here on pace: Kia Pro cee'd 2.0 CRDi 140 (9.10 s), Dacia Logan 1.6 MPI 105 (9.10 s), MG Montego EFi (9.09 s). Each one can be raced against the Fiat Palio Weekend 1.6 16v 115 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 Fiat Palio Weekend 1.6 16v 115 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.