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

Bristol 405 Drophead Coupe 2.0 107

The Bristol 405 Drophead Coupe 2.0 107 reaches 60 mph in 12.86 s (100 km/h in 13.56 s) and covers a standing quarter mile in 19.73 s, tripping the lights at 75.2 mph. It clears the first 60 ft in 3.50 s and the eighth mile in 13.14 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.

Bristol 405 Drophead Coupe 2.0 107 Dodge Aries Coupe 2.6 92

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 Bristol 405 Drophead Coupe 2.0 107
0–60 mph12.86 s
0–100 km/h13.56 s
0–100 mph—
60 ft3.50 s
1/8 mile13.14 s
1/4 mile19.73 s
Trap speed75.2 mph

About the 405 Drophead Coupe 2.0 107

The 1954 Bristol 405 Drophead Coupe 2.0 107 is a rear-drive naturally aspirated coupe of 1,262 kg with 106 bhp, which works out at 84 bhp per tonne. Rear drive and 84 bhp per tonne make the launch the hard part of the run: 60 ft takes 3.50 s. Against the 14,946 cars in the set it is the 13,513th quickest to 60 mph, and the 18th quickest of the 21 Bristols here. It traps higher than its 0-60 suggests — 75.2 mph, the 12,532nd highest here — so it is a car that keeps going rather than one that simply leaves well. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Bristol 405 Drophead Coupe 2.0 107
Year1954
Power106 hp (79 kW)
Kerb mass1,262 kg
Power to weight84 bhp/t
DrivetrainRear drive
Gears4
EngineNaturally aspirated
Top speed110 mph (177 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Dodge Aries Coupe 2.6 92198112.88 s19.76 s76.7 mph91 bhp
BMW 3 Series Coupe (E30) 316 90198313.00 s19.82 s74.8 mph89 bhp
Citroen C4 Coupe 1.4 88200412.98 s19.43 s73.8 mph87 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

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Bristol 0-60 timesevery modelFastest coupes911 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 Bristol 405 Drophead Coupe 2.0 107 0-60 time?
The Bristol 405 Drophead Coupe 2.0 107 reaches 60 mph in 12.86 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 13,513th quickest of the 14,946 cars in the set.
What is the Bristol 405 Drophead Coupe 2.0 107 quarter mile time?
19.73 s at 75.2 mph. It reaches the eighth mile in 13.14 s and clears the first 60 ft in 3.50 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Bristol 405 Drophead Coupe 2.0 107 have?
106 bhp and 1,262 kg, which is 84 bhp per tonne. It is rear-drive, naturally aspirated, with 4 gears and a quoted top speed of 177 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Bristol 405 Drophead Coupe 2.0 107?
Closest here on pace: Dodge Aries Coupe 2.6 92 (12.88 s), BMW 3 Series Coupe (E30) 316 90 (13.00 s), Citroen C4 Coupe 1.4 88 (12.98 s). Each one can be raced against the Bristol 405 Drophead Coupe 2.0 107 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 Bristol 405 Drophead Coupe 2.0 107 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.