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

Cadillac Seville 4.6 V8 300

The Cadillac Seville 4.6 V8 300 reaches 60 mph in 6.35 s (100 km/h in 6.64 s) and covers a standing quarter mile in 14.74 s, tripping the lights at 99.6 mph. It clears the first 60 ft in 2.64 s and the eighth mile in 9.77 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.

Cadillac Seville 4.6 V8 300 Bentley Continental R

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 Cadillac Seville 4.6 V8 300
0–60 mph6.35 s
0–100 km/h6.64 s
0–100 mph—
60 ft2.64 s
1/8 mile9.77 s
1/4 mile14.74 s
Trap speed99.6 mph

About the Seville 4.6 V8 300

The 1998 Cadillac Seville 4.6 V8 300 is a front-drive naturally aspirated saloon of 1,827 kg with 300 bhp, which works out at 164 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.64 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 3,699th quickest to 60 mph, inside the fastest quarter, and the 26th quickest of the 65 Cadillacs here. Its 99.6 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 Cadillac Seville 4.6 V8 300
Year1998
Power300 hp (224 kW)
Kerb mass1,827 kg
Power to weight164 bhp/t
DrivetrainFront drive
Gears4
EngineNaturally aspirated
Top speed130 mph (209 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Bentley Continental R19916.33 s14.74 s99.7 mph385 bhp
Mercury Marauder 4.6 V8 30020036.35 s14.78 s99.4 mph295 bhp
Lexus LS 40019976.42 s14.77 s97.0 mph290 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 7 seconds4,651 cars0-100 km/h under 7 seconds4,031 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Cadillac 0-60 timesevery modelFastest 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 Cadillac Seville 4.6 V8 300 0-60 time?
The Cadillac Seville 4.6 V8 300 reaches 60 mph in 6.35 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 3,699th quickest of the 14,946 cars in the set.
What is the Cadillac Seville 4.6 V8 300 quarter mile time?
14.74 s at 99.6 mph. It reaches the eighth mile in 9.77 s and clears the first 60 ft in 2.64 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Cadillac Seville 4.6 V8 300 have?
300 bhp and 1,827 kg, which is 164 bhp per tonne. It is front-drive, naturally aspirated, with 4 gears and a quoted top speed of 209 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Cadillac Seville 4.6 V8 300?
Closest here on pace: Bentley Continental R (6.33 s), Mercury Marauder 4.6 V8 300 (6.35 s), Lexus LS 400 (6.42 s). Each one can be raced against the Cadillac Seville 4.6 V8 300 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 Cadillac Seville 4.6 V8 300 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.