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

Renault Mégane Hatch 1.5 dCi 110

The Renault Mégane Hatch 1.5 dCi 110 reaches 60 mph in 9.55 s (100 km/h in 10.10 s) and covers a standing quarter mile in 17.06 s, tripping the lights at 80.4 mph. It clears the first 60 ft in 2.54 s and the eighth mile in 10.94 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.

Renault Mégane Hatch 1.5 dCi 110 Fiat Bravo 1.9 Multijet 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 Renault Mégane Hatch 1.5 dCi 110
0–60 mph9.55 s
0–100 km/h10.10 s
0–100 mph—
60 ft2.54 s
1/8 mile10.94 s
1/4 mile17.06 s
Trap speed80.4 mph

About the Mégane Hatch 1.5 dCi 110

The 2008 Renault Mégane Hatch 1.5 dCi 110 is a front-drive turbodiesel car of 1,215 kg with 109 bhp, which works out at 89 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.54 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 9,350th quickest to 60 mph, and the 166th quickest of the 499 Renaults here. Its 80.4 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 Renault Mégane Hatch 1.5 dCi 110
Year2008
Power109 hp (81 kW)
Kerb mass1,215 kg
Power to weight89 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed118 mph (190 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Fiat Bravo 1.9 Multijet 12020079.53 s17.14 s80.4 mph118 bhp
Vauxhall Corsa 3dr 1.7 CDTi 10020019.55 s17.08 s80.3 mph99 bhp
Fiat Bravo 1.6 Multijet 12020079.48 s17.08 s80.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 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Renault 0-60 timesevery modelFastest diesel cars4,019 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 Renault Mégane Hatch 1.5 dCi 110 0-60 time?
The Renault Mégane Hatch 1.5 dCi 110 reaches 60 mph in 9.55 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,350th quickest of the 14,946 cars in the set.
What is the Renault Mégane Hatch 1.5 dCi 110 quarter mile time?
17.06 s at 80.4 mph. It reaches the eighth mile in 10.94 s and clears the first 60 ft in 2.54 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Renault Mégane Hatch 1.5 dCi 110 have?
109 bhp and 1,215 kg, which is 89 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 190 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Renault Mégane Hatch 1.5 dCi 110?
Closest here on pace: Fiat Bravo 1.9 Multijet 120 (9.53 s), Vauxhall Corsa 3dr 1.7 CDTi 100 (9.55 s), Fiat Bravo 1.6 Multijet 120 (9.48 s). Each one can be raced against the Renault Mégane Hatch 1.5 dCi 110 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 Renault Mégane Hatch 1.5 dCi 110 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.