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

Toyota Prius Hybrid Mk II

The Toyota Prius Hybrid Mk II reaches 60 mph in 11.06 s (100 km/h in 11.74 s) and covers a standing quarter mile in 18.17 s, tripping the lights at 76.1 mph. It clears the first 60 ft in 2.80 s and the eighth mile in 11.69 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.

Toyota Prius Hybrid Mk II Nissan Note 1.2 DIG-S CVT 98

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 Toyota Prius Hybrid Mk II
0–60 mph11.06 s
0–100 km/h11.74 s
0–100 mph—
60 ft2.80 s
1/8 mile11.69 s
1/4 mile18.17 s
Trap speed76.1 mph

About the Prius Hybrid Mk II

The 2004 Toyota Prius Hybrid Mk II is a front-drive naturally aspirated car of 1,300 kg with 110 bhp, which works out at 85 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.80 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 11,756th quickest to 60 mph, and the 222nd quickest of the 311 Toyotas here. Its 76.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 9 of 9 published acceleration figures for this car.

On paper

Specification Toyota Prius Hybrid Mk II
Year2004
Power110 hp (82 kW)
Kerb mass1,300 kg
Power to weight85 bhp/t
DrivetrainFront drive
Gears6
EngineNaturally aspirated
Top speed106 mph (170 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Nissan Note 1.2 DIG-S CVT 98201310.97 s18.15 s75.5 mph97 bhp
Lancia Ypsilon 0.9 Twinair 85201110.98 s18.16 s75.7 mph84 bhp
Nissan Almera / Pulsar 3dr 2.2 Di 110200011.15 s18.18 s75.8 mph109 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.

Head to head

Toyota GR Corolla vs Toyota Prius Hybrid Mk IIFull comparison

Where these times sit

Slower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Toyota 0-60 timesevery modelFastest hatchbacks4,513 carsFastest cars of the 2000s5,138 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 Toyota Prius Hybrid Mk II 0-60 time?
The Toyota Prius Hybrid Mk II reaches 60 mph in 11.06 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 11,756th quickest of the 14,946 cars in the set.
What is the Toyota Prius Hybrid Mk II quarter mile time?
18.17 s at 76.1 mph. It reaches the eighth mile in 11.69 s and clears the first 60 ft in 2.80 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Toyota Prius Hybrid Mk II have?
110 bhp and 1,300 kg, which is 85 bhp per tonne. It is front-drive, naturally aspirated, with 6 gears and a quoted top speed of 170 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Toyota Prius Hybrid Mk II?
Closest here on pace: Nissan Note 1.2 DIG-S CVT 98 (10.97 s), Lancia Ypsilon 0.9 Twinair 85 (10.98 s), Nissan Almera / Pulsar 3dr 2.2 Di 110 (11.15 s). Each one can be raced against the Toyota Prius Hybrid Mk II 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 Toyota Prius Hybrid Mk II is modelled from its published kerb mass, rated power, drivetrain and gearing, then trimmed until it reproduces 9 of its 9 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.