average vehicles visible
A day in the life of a route
A day on Route 32.
See when this monitored bus route appeared busiest, quieter, or less consistently visible during the last 24 hours.
The last 24 hours
Visible service through the day
Each dot is a stored observation. Breaks show periods when the platform did not collect enough data to join the record.
Reading stored route observations...
waiting for data
waiting for data
stored observations
Four parts of one day
The route does not look the same all day.
These cards summarize what the platform could see, making the daily rhythm easier to compare without turning a single observation into a service grade.
Reported bus occupancy
How busy were reported buses?
These are reported vehicle conditions, not passenger totals. The daily pattern appears only when enough buses report occupancy.
Checking stored bus occupancy reports...
Moments worth noticing
What changed during this 24-hour window?
These are descriptive observations, not explanations. Weather, disruptions, dispatching, feed quality, and ordinary daily schedules can all affect what appears.
Why the full day matters
A route supports different parts of city life at different hours.
Morning work and school trips, midday appointments, afternoon transfers, evening shifts, and late trips all depend on service being present beyond one live snapshot. The 24-hour view makes those changes visible without claiming who travelled or why.
Check the label
What the 24-hour record can and cannot tell us.
The record uses Toronto local time and refreshes as new observations are stored.
- Observed
- Vehicle records visible to the platform for this route at each sample time.
- Missing
- A blank period means the platform did not store enough observations. It does not mean no service operated.
- Compared
- A recent hourly comparison appears only when at least three earlier days are available.
- Not measured
- Passenger totals, boardings, exact crowding, schedule adherence, exact passenger waits, or every vehicle in service.