← My Auto Racer All cars Comparisons Answers

AC Aceca 3.5 V8 32V Turbo 354

The AC Aceca 3.5 V8 32V Turbo 354 reaches 60 mph in 5.06 s (100 km/h in 5.30 s) and covers a standing quarter mile in 13.46 s, tripping the lights at 102.7 mph. It clears the first 60 ft in 2.04 s and the eighth mile in 8.70 s, reaching 100 mph in 12.21 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.

AC Aceca 3.5 V8 32V Turbo 354 Dodge Ram SRT-10

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 AC Aceca 3.5 V8 32V Turbo 354
0–60 mph5.06 s
0–100 km/h5.30 s
0–100 mph12.21 s
60 ft2.04 s
1/8 mile8.70 s
1/4 mile13.46 s
Trap speed102.7 mph

About the Aceca 3.5 V8 32V Turbo 354

The 1998 AC Aceca 3.5 V8 32V Turbo 354 is a rear-drive turbocharged saloon of 1,615 kg with 345 bhp, which works out at 213 bhp per tonne. Rear drive and 213 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.04 s. Against the 14,946 cars in the set it is the 2,219th quickest to 60 mph, inside the fastest quarter, and the 4th quickest of the 5 ACs here. Its 102.7 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 AC Aceca 3.5 V8 32V Turbo 354
Year1998
Power345 hp (257 kW)
Kerb mass1,615 kg
Power to weight213 bhp/t
DrivetrainRear drive
Gears6
EngineTurbocharged
Top speed155 mph (249 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dodge Ram SRT-1020045.07 s13.45 s103.7 mph500 bhp
Brabus GLK 6.120095.07 s13.41 s105.4 mph456 bhp
Audi S6 C620065.06 s13.36 s105.9 mph429 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 6 seconds3,249 cars0-100 km/h under 6 seconds2,894 carsQuarter mile under 14 seconds2,644 cars0-100 under 16 seconds2,740 carsTraps over 100 mph2,737 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Fastest saloon cars3,808 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 AC Aceca 3.5 V8 32V Turbo 354 0-60 time?
The AC Aceca 3.5 V8 32V Turbo 354 reaches 60 mph in 5.06 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 2,219th quickest of the 14,946 cars in the set.
What is the AC Aceca 3.5 V8 32V Turbo 354 quarter mile time?
13.46 s at 102.7 mph. It reaches the eighth mile in 8.70 s and clears the first 60 ft in 2.04 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the AC Aceca 3.5 V8 32V Turbo 354 have?
345 bhp and 1,615 kg, which is 213 bhp per tonne. It is rear-drive, turbocharged, with 6 gears and a quoted top speed of 249 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the AC Aceca 3.5 V8 32V Turbo 354?
Closest here on pace: Dodge Ram SRT-10 (5.07 s), Brabus GLK 6.1 (5.07 s), Audi S6 C6 (5.06 s). Each one can be raced against the AC Aceca 3.5 V8 32V Turbo 354 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 AC Aceca 3.5 V8 32V Turbo 354 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.