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

Citroen Nemo Combi 1.4 73

The Citroen Nemo Combi 1.4 73 reaches 60 mph in 14.46 s (100 km/h in 16.11 s) and covers a standing quarter mile in 20.22 s, tripping the lights at 69.4 mph. It clears the first 60 ft in 3.43 s and the eighth mile in 13.12 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.

Citroen Nemo Combi 1.4 73 Opel Astra Sedan 1.4 60

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 Citroen Nemo Combi 1.4 73
0–60 mph14.46 s
0–100 km/h16.11 s
0–100 mph—
60 ft3.43 s
1/8 mile13.12 s
1/4 mile20.22 s
Trap speed69.4 mph

About the Nemo Combi 1.4 73

The 2008 Citroen Nemo Combi 1.4 73 is a front-drive naturally aspirated estate of 1,165 kg with 72 bhp, which works out at 62 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 3.43 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 14,272nd quickest to 60 mph, and the 339th quickest of the 387 Citroens here. Its 69.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 Citroen Nemo Combi 1.4 73
Year2008
Power72 hp (54 kW)
Kerb mass1,165 kg
Power to weight62 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed96 mph (154 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Opel Astra Sedan 1.4 60199414.55 s20.28 s69.7 mph59 bhp
Land Rover Range Rover 2.5 D 136199414.40 s20.42 s71.8 mph134 bhp
VW Cross Up! 1.0 75201614.45 s20.28 s70.6 mph74 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.

Head to head

Citroen Berlingo BlueHDi 130 (Mk3) vs Citroen Nemo Combi 1.4 73Full comparison

Where these times sit

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Citroen 0-60 timesevery modelFastest estate cars1,484 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 Citroen Nemo Combi 1.4 73 0-60 time?
The Citroen Nemo Combi 1.4 73 reaches 60 mph in 14.46 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 14,272nd quickest of the 14,946 cars in the set.
What is the Citroen Nemo Combi 1.4 73 quarter mile time?
20.22 s at 69.4 mph. It reaches the eighth mile in 13.12 s and clears the first 60 ft in 3.43 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Citroen Nemo Combi 1.4 73 have?
72 bhp and 1,165 kg, which is 62 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 154 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Citroen Nemo Combi 1.4 73?
Closest here on pace: Opel Astra Sedan 1.4 60 (14.55 s), Land Rover Range Rover 2.5 D 136 (14.40 s), VW Cross Up! 1.0 75 (14.45 s). Each one can be raced against the Citroen Nemo Combi 1.4 73 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 Citroen Nemo Combi 1.4 73 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.