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

Renault Fluence 1.6 dCI 130

The Renault Fluence 1.6 dCI 130 reaches 60 mph in 8.41 s (100 km/h in 9.42 s) and covers a standing quarter mile in 16.57 s, tripping the lights at 83.0 mph. It clears the first 60 ft in 2.50 s and the eighth mile in 10.67 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 Fluence 1.6 dCI 130 Volvo V70 2.4 D4 181

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 Fluence 1.6 dCI 130
0–60 mph8.41 s
0–100 km/h9.42 s
0–100 mph—
60 ft2.50 s
1/8 mile10.67 s
1/4 mile16.57 s
Trap speed83.0 mph

About the Fluence 1.6 dCI 130

The 2013 Renault Fluence 1.6 dCI 130 is a front-drive turbodiesel saloon of 1,349 kg with 129 bhp, which works out at 95 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.50 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,327th quickest to 60 mph, and the 91st quickest of the 499 Renaults here. It leaves better than it pulls: 83.0 mph at the lights is only the 8,335th highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Renault Fluence 1.6 dCI 130
Year2013
Power129 hp (96 kW)
Kerb mass1,349 kg
Power to weight95 bhp/t
DrivetrainFront drive
Gears6
EngineTurbodiesel
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Volvo V70 2.4 D4 18120078.43 s16.50 s83.6 mph178 bhp
Volvo V60 2.0 D4 163 (2014)20148.45 s16.54 s84.1 mph161 bhp
Alfa Romeo 159 1.9 JTDm 16V 15020058.49 s16.57 s84.5 mph148 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
Renault 0-60 timesevery modelFastest saloon cars3,808 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 Renault Fluence 1.6 dCI 130 0-60 time?
The Renault Fluence 1.6 dCI 130 reaches 60 mph in 8.41 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,327th quickest of the 14,946 cars in the set.
What is the Renault Fluence 1.6 dCI 130 quarter mile time?
16.57 s at 83.0 mph. It reaches the eighth mile in 10.67 s and clears the first 60 ft in 2.50 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Renault Fluence 1.6 dCI 130 have?
129 bhp and 1,349 kg, which is 95 bhp per tonne. It is front-drive, turbodiesel, with 6 gears and a quoted top speed of 200 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Renault Fluence 1.6 dCI 130?
Closest here on pace: Volvo V70 2.4 D4 181 (8.43 s), Volvo V60 2.0 D4 163 (2014) (8.45 s), Alfa Romeo 159 1.9 JTDm 16V 150 (8.49 s). Each one can be raced against the Renault Fluence 1.6 dCI 130 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 Fluence 1.6 dCI 130 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.