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

Donkervoort D8 1.8 Zetec 140

The Donkervoort D8 1.8 Zetec 140 reaches 60 mph in 5.43 s (100 km/h in 5.70 s) and covers a standing quarter mile in 13.92 s, tripping the lights at 99.2 mph. It clears the first 60 ft in 2.17 s and the eighth mile in 8.93 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.

Donkervoort D8 1.8 Zetec 140 Aston Martin DB7

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 Donkervoort D8 1.8 Zetec 140
0–60 mph5.43 s
0–100 km/h5.70 s
0–100 mph—
60 ft2.17 s
1/8 mile8.93 s
1/4 mile13.92 s
Trap speed99.2 mph

About the D8 1.8 Zetec 140

The 1993 Donkervoort D8 1.8 Zetec 140 is a rear-drive naturally aspirated coupe of 630 kg with 138 bhp, which works out at 219 bhp per tonne. Rear drive and 219 bhp per tonne make the launch the hard part of the run: 60 ft takes 2.17 s. Against the 14,946 cars in the set it is the 2,595th quickest to 60 mph, inside the fastest quarter, and the 10th quickest of the 10 Donkervoorts here. Its 99.2 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 Donkervoort D8 1.8 Zetec 140
Year1993
Power138 hp (103 kW)
Kerb mass630 kg
Power to weight219 bhp/t
DrivetrainRear drive
Gears5
EngineNaturally aspirated
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Aston Martin DB719945.44 s13.98 s100.9 mph335 bhp
Caterham Roadsport 1.6 12720075.34 s14.08 s93.9 mph125 bhp
Ferrari 250 GT 3.0 V12 28019545.50 s13.87 s108.0 mph276 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 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Donkervoort 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 Donkervoort D8 1.8 Zetec 140 0-60 time?
The Donkervoort D8 1.8 Zetec 140 reaches 60 mph in 5.43 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 2,595th quickest of the 14,946 cars in the set.
What is the Donkervoort D8 1.8 Zetec 140 quarter mile time?
13.92 s at 99.2 mph. It reaches the eighth mile in 8.93 s and clears the first 60 ft in 2.17 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Donkervoort D8 1.8 Zetec 140 have?
138 bhp and 630 kg, which is 219 bhp per tonne. It is rear-drive, naturally aspirated, with 5 gears and a quoted top speed of 200 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Donkervoort D8 1.8 Zetec 140?
Closest here on pace: Aston Martin DB7 (5.44 s), Caterham Roadsport 1.6 127 (5.34 s), Ferrari 250 GT 3.0 V12 280 (5.50 s). Each one can be raced against the Donkervoort D8 1.8 Zetec 140 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 Donkervoort D8 1.8 Zetec 140 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.