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

Honda Stream 2.0 CVT 150

The Honda Stream 2.0 CVT 150 reaches 60 mph in 8.35 s (100 km/h in 8.93 s) and covers a standing quarter mile in 16.47 s, tripping the lights at 83.1 mph. It clears the first 60 ft in 2.54 s and the eighth mile in 10.54 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 CVT 150 Citroen Grand C4 Picasso 1.6 THP 156

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 CVT 150
0–60 mph8.35 s
0–100 km/h8.93 s
0–100 mph—
60 ft2.54 s
1/8 mile10.54 s
1/4 mile16.47 s
Trap speed83.1 mph

About the Stream 2.0 CVT 150

The 2006 Honda Stream 2.0 CVT 150 is a front-drive naturally aspirated MPV of 1,380 kg with 148 bhp, which works out at 107 bhp per tonne. Front drive caps what it can put down off the line — 60 ft takes 2.54 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 7,211th quickest to 60 mph, and the 62nd quickest of the 191 Hondas here. It leaves better than it pulls: 83.1 mph at the lights is only the 8,251st highest here, so its 0-60 flatters what it does further out. The simulation is trimmed to 2 of 2 published acceleration figures for this car.

On paper

Specification Honda Stream 2.0 CVT 150
Year2006
Power148 hp (110 kW)
Kerb mass1,380 kg
Power to weight107 bhp/t
DrivetrainFront drive
Gears1
EngineNaturally aspirated
Top speed127 mph (204 km/h), quoted

Similar cars

CarYear 0–601/4 mileTrapPower
Citroen Grand C4 Picasso 1.6 THP 15620138.33 s16.48 s84.6 mph154 bhp
Renault Scenic 2.0 dCi 16020098.22 s16.45 s84.5 mph158 bhp
Volkswagen Touran 2.0 TDI 150 (Mk3)20158.42 s16.56 s84.0 mph148 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 CVT 150 0-60 time?
The Honda Stream 2.0 CVT 150 reaches 60 mph in 8.35 s, simulated on dry asphalt at 20 °C with a 1 ft rollout. That makes it the 7,211th quickest of the 14,946 cars in the set.
What is the Honda Stream 2.0 CVT 150 quarter mile time?
16.47 s at 83.1 mph. It reaches the eighth mile in 10.54 s and clears the first 60 ft in 2.54 s. These are theoretical times from a physics simulation, not measured runs.
How much power does the Honda Stream 2.0 CVT 150 have?
148 bhp and 1,380 kg, which is 107 bhp per tonne. It is front-drive, naturally aspirated, with 1 gears and a quoted top speed of 204 km/h. These are theoretical times from a physics simulation, not measured runs.
What cars are comparable to the Honda Stream 2.0 CVT 150?
Closest here on pace: Citroen Grand C4 Picasso 1.6 THP 156 (8.33 s), Renault Scenic 2.0 dCi 160 (8.22 s), Volkswagen Touran 2.0 TDI 150 (Mk3) (8.42 s). Each one can be raced against the Honda Stream 2.0 CVT 150 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 CVT 150 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.