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

Citroen XM Break 2.0 Turbo 146

The Citroen XM Break 2.0 Turbo 146 reaches 60 mph in 10.00 s (100 km/h in 10.59 s) and covers a standing quarter mile in 17.39 s, tripping the lights at 79.4 mph. It clears the first 60 ft in 2.83 s and the eighth mile in 11.23 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 XM Break 2.0 Turbo 146 Skoda Octavia I Combi 2.0 115

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 XM Break 2.0 Turbo 146
0–60 mph10.00 s
0–100 km/h10.59 s
0–100 mph—
60 ft2.83 s
1/8 mile11.23 s
1/4 mile17.39 s
Trap speed79.4 mph

About the XM Break 2.0 Turbo 146

The 1992 Citroen XM Break 2.0 Turbo 146 is a front-drive turbocharged estate of 1,500 kg with 143 bhp, which works out at 96 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.83 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 10,141st quickest to 60 mph, and the 104th quickest of the 387 Citroens here. Its 79.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 XM Break 2.0 Turbo 146
Year1992
Power143 hp (107 kW)
Kerb mass1,500 kg
Power to weight96 bhp/t
DrivetrainFront drive
Gears5
EngineTurbocharged
Top speed126 mph (202 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Skoda Octavia I Combi 2.0 11519979.95 s17.51 s81.4 mph114 bhp
Mazda 6/Atenza Wagon 2.0 CD 12020029.99 s17.41 s79.1 mph118 bhp
Honda Accord Tourer 2.4 160200310.00 s17.67 s81.6 mph158 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
Citroen 0-60 timesevery modelFastest estate cars1,484 carsFastest cars of the 1990s2,649 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 XM Break 2.0 Turbo 146 0-60 time?
The Citroen XM Break 2.0 Turbo 146 reaches 60 mph in 10.00 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 10,141st quickest of the 14,946 cars in the set.
What is the Citroen XM Break 2.0 Turbo 146 quarter mile time?
17.39 s at 79.4 mph. It reaches the eighth mile in 11.23 s and clears the first 60 ft in 2.83 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Citroen XM Break 2.0 Turbo 146 have?
143 bhp and 1,500 kg, which is 96 bhp per tonne. It is front-drive, turbocharged, with 5 gears and a quoted top speed of 202 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Citroen XM Break 2.0 Turbo 146?
Closest here on pace: Skoda Octavia I Combi 2.0 115 (9.95 s), Mazda 6/Atenza Wagon 2.0 CD 120 (9.99 s), Honda Accord Tourer 2.4 160 (10.00 s). Each one can be raced against the Citroen XM Break 2.0 Turbo 146 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 XM Break 2.0 Turbo 146 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.