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

Mercury Milan 2.5 DOHC 175

The Mercury Milan 2.5 DOHC 175 reaches 60 mph in 8.39 s (100 km/h in 8.92 s) and covers a standing quarter mile in 16.51 s, tripping the lights at 83.2 mph. It clears the first 60 ft in 2.58 s and the eighth mile in 10.60 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.

Mercury Milan 2.5 DOHC 175 Chrysler 200 2.4 173

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 Mercury Milan 2.5 DOHC 175
0–60 mph8.39 s
0–100 km/h8.92 s
0–100 mph—
60 ft2.58 s
1/8 mile10.60 s
1/4 mile16.51 s
Trap speed83.2 mph

About the Milan 2.5 DOHC 175

The 2009 Mercury Milan 2.5 DOHC 175 is a front-drive naturally aspirated saloon of 1,526 kg with 176 bhp, which works out at 115 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.58 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,282nd quickest to 60 mph, and the 6th quickest of the 10 Mercurys here. It leaves better than it pulls: 83.2 mph at the lights is only the 8,225th 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 Mercury Milan 2.5 DOHC 175
Year2009
Power176 hp (131 kW)
Kerb mass1,526 kg
Power to weight115 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed112 mph (180 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chrysler 200 2.4 17320118.39 s16.47 s83.9 mph173 bhp
Alfa Romeo 166 2.4 JTD 20V 17520038.35 s16.55 s85.0 mph173 bhp
Chevrolet Cruze 2.0TD 16320098.44 s16.54 s83.7 mph161 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
Mercury 0-60 timesevery modelFastest saloon cars3,808 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 Mercury Milan 2.5 DOHC 175 0-60 time?
The Mercury Milan 2.5 DOHC 175 reaches 60 mph in 8.39 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,282nd quickest of the 14,946 cars in the set.
What is the Mercury Milan 2.5 DOHC 175 quarter mile time?
16.51 s at 83.2 mph. It reaches the eighth mile in 10.60 s and clears the first 60 ft in 2.58 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Mercury Milan 2.5 DOHC 175 have?
176 bhp and 1,526 kg, which is 115 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 180 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Mercury Milan 2.5 DOHC 175?
Closest here on pace: Chrysler 200 2.4 173 (8.39 s), Alfa Romeo 166 2.4 JTD 20V 175 (8.35 s), Chevrolet Cruze 2.0TD 163 (8.44 s). Each one can be raced against the Mercury Milan 2.5 DOHC 175 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 Mercury Milan 2.5 DOHC 175 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.