Recorded public evidence
Replay the network
Watch recorded bus positions across the day.
Selected replay context
October 24, 2026 at 08:04 EDT · 4× playback
- Dataset
- Archived public-feed vehicle positions
- Coverage for the loaded map window
- Checking the recorded archive for this period…
How to read the markers
Watch recorded bus positions across the day. Marker colours show archived predicted delay against the timetable, not measured stop arrivals.
Colour uses the median retained arrival prediction minus the timetable for the trip in that archived snapshot. It does not measure an actual stop arrival or prove that a pickup was on time. These are the latest recorded observations no more than 7 minutes old at the selected replay clock. Selecting one coordinates the map and historical detail. A cancelled trip has no recorded vehicle location to place on this map. The replay does not turn a missing marker or data gap into a cancellation.
Every time, route, trip and vehicle below belongs to the selected recorded period. Use Departures or Explore for current service.
Source sampling: at most one recorded position per vehicle per minute. Faint straight lines only connect observations within 2 minutes. Markers jump to recorded positions; no path or missing position is inferred.
The replay link includes the selected date, exact clock minute, playback speed, filters, selected vehicle and current map bounds.
Date, route and operator filters
Play through service date
Compare the same time yesterday or last week, or play through a range of days. The clock pauses while records load. Faster playback advances recorded time in smaller steps; an empty map may mean missing records, not absent service.
What the replay can prove
Where a bus reported itself and when. Not why, and not where a bus with no position was.
More about this evidence
Every bus marker is a recorded public-feed position. A faint straight line joins observations only when they are no more than 2 minutes apart. It is not a street path.
Purple is context, not an on-time grade. Express 200/500 routes need pickup-point evidence; community/shopper 300 routes and event 400 routes need purpose-specific checks. This trip-level replay cannot make those checks, so it does not grade them.
O-Train is not shown because the public OC Transpo feed does not publish live rail positions.
Movement without a published trip assignment
These are public-feed observations without a published trip assignment. They do not reveal whether a bus is in service, deadheading, travelling to a route or depot, or affected by an equipment or feed problem. Distance is a straight-line minimum between consecutive observations; gaps over 10 minutes and implausible jumps are excluded.
See this day’s movement report