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

Honda Stream 2.0 5TM 156

The Honda Stream 2.0 5TM 156 reaches 60 mph in 8.93 s (100 km/h in 9.43 s) and covers a standing quarter mile in 16.79 s, tripping the lights at 84.3 mph. It clears the first 60 ft in 2.86 s and the eighth mile in 10.96 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.

Honda Stream 2.0 5TM 156 Chevrolet Orlando 2.0D 163

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 Honda Stream 2.0 5TM 156
0–60 mph8.93 s
0–100 km/h9.43 s
0–100 mph—
60 ft2.86 s
1/8 mile10.96 s
1/4 mile16.79 s
Trap speed84.3 mph

About the Stream 2.0 5TM 156

The 2003 Honda Stream 2.0 5TM 156 is an all-wheel-drive naturally aspirated MPV of 1,460 kg with 154 bhp, which works out at 106 bhp per tonne. All-wheel drive is worth most in the first car length: it covers 60 ft in 2.86 s, which is where a four-wheel-drive car takes its margin out of a rear-drive one with the same power. Against the 14,946 cars in the set it is the 8,302nd quickest to 60 mph, and the 78th quickest of the 191 Hondas here. Its 84.3 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 Honda Stream 2.0 5TM 156
Year2003
Power154 hp (115 kW)
Kerb mass1,460 kg
Power to weight106 bhp/t
DrivetrainAll-wheel drive
Gears5
EngineNaturally aspirated
Top speed124 mph (200 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Chevrolet Orlando 2.0D 16320108.95 s16.77 s82.0 mph161 bhp
Renault Espace 2.0 16V Turbo 17020068.76 s16.79 s83.1 mph168 bhp
SEAT Alhambra 2.0 TDI 17020108.79 s16.80 s82.6 mph168 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 10 seconds10,136 cars0-100 km/h under 10 seconds9,062 carsSlower in the wetevery car, re-runThe cost of altitudeevery car, re-runThe cost of a passengerevery car, re-run
Honda 0-60 timesevery modelFastest MPVs and people carriers478 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 Honda Stream 2.0 5TM 156 0-60 time?
The Honda Stream 2.0 5TM 156 reaches 60 mph in 8.93 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 8,302nd quickest of the 14,946 cars in the set.
What is the Honda Stream 2.0 5TM 156 quarter mile time?
16.79 s at 84.3 mph. It reaches the eighth mile in 10.96 s and clears the first 60 ft in 2.86 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda Stream 2.0 5TM 156 have?
154 bhp and 1,460 kg, which is 106 bhp per tonne. It is all-wheel-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 Honda Stream 2.0 5TM 156?
Closest here on pace: Chevrolet Orlando 2.0D 163 (8.95 s), Renault Espace 2.0 16V Turbo 170 (8.76 s), SEAT Alhambra 2.0 TDI 170 (8.79 s). Each one can be raced against the Honda Stream 2.0 5TM 156 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 Honda Stream 2.0 5TM 156 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.