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

Citroen Xsara Coupe VTS 1.8i 110

The Citroen Xsara Coupe VTS 1.8i 110 reaches 60 mph in 9.67 s (100 km/h in 10.22 s) and covers a standing quarter mile in 17.32 s, tripping the lights at 82.1 mph. It clears the first 60 ft in 2.98 s and the eighth mile in 11.33 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 Xsara Coupe VTS 1.8i 110 Hyundai i20 Coupe 1.0 100

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 Xsara Coupe VTS 1.8i 110
0–60 mph9.67 s
0–100 km/h10.22 s
0–100 mph—
60 ft2.98 s
1/8 mile11.33 s
1/4 mile17.32 s
Trap speed82.1 mph

About the Xsara Coupe VTS 1.8i 110

The 1998 Citroen Xsara Coupe VTS 1.8i 110 is a front-drive naturally aspirated coupe of 1,090 kg with 109 bhp, which works out at 100 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.98 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,591st quickest to 60 mph, and the 88th quickest of the 387 Citroens here. Its 82.1 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 Xsara Coupe VTS 1.8i 110
Year1998
Power109 hp (81 kW)
Kerb mass1,090 kg
Power to weight100 bhp/t
DrivetrainFront drive
Gears5
EngineNaturally aspirated
Top speed123 mph (198 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Hyundai i20 Coupe 1.0 10020159.70 s17.28 s79.6 mph99 bhp
Fiat 124 Sport Coupe BC 1.6 11019699.65 s17.39 s80.5 mph109 bhp
Mazda MX-5 / Miata 1.6i 9019899.64 s17.41 s80.1 mph89 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 coupes911 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 Xsara Coupe VTS 1.8i 110 0-60 time?
The Citroen Xsara Coupe VTS 1.8i 110 reaches 60 mph in 9.67 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 9,591st quickest of the 14,946 cars in the set.
What is the Citroen Xsara Coupe VTS 1.8i 110 quarter mile time?
17.32 s at 82.1 mph. It reaches the eighth mile in 11.33 s and clears the first 60 ft in 2.98 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Citroen Xsara Coupe VTS 1.8i 110 have?
109 bhp and 1,090 kg, which is 100 bhp per tonne. It is front-drive, naturally aspirated, with 5 gears and a quoted top speed of 198 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Citroen Xsara Coupe VTS 1.8i 110?
Closest here on pace: Hyundai i20 Coupe 1.0 100 (9.70 s), Fiat 124 Sport Coupe BC 1.6 110 (9.65 s), Mazda MX-5 / Miata 1.6i 90 (9.64 s). Each one can be raced against the Citroen Xsara Coupe VTS 1.8i 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 Citroen Xsara Coupe VTS 1.8i 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.