Skip to main content
Otranspo

Recorded public evidence

Replay the network

Watch recorded bus positions build across the day, like a weather map. Green is within 5 minutes; yellow, orange and red show increasing measured lateness.

Historical replay. This is not live service.

Selected replay context

September 14, 2026 at 04:00 EDT · 4 min per step

Dataset
Archived public-feed vehicle positions
Coverage for the loaded map window
Checking the recorded archive for this period…

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. Lines stop at gaps longer than 7 minutes. The replay never interpolates a missing position.

Compare the same time yesterday or last week, or play through a range of days. The clock pauses while records load. Faster playback skips minutes, never invents positions; an empty map may mean missing records, not absent service.

04:00 EDTOpen replay data (JSON)

The replay link includes the selected date, exact clock minute, playback speed, filters, selected vehicle and current map bounds.

Loading recorded positions…

Vehicles observed at the selected 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.

No vehicle has a recent recorded position at this replay minute.

Measured schedule difference

Colour uses the median published delay estimate for the trip in that recorded snapshot. It does not prove that a particular pickup was on time.

  • More than 5 min early
  • Within 5 min of schedule
  • 5–10 min late
  • 10–20 min late
  • More than 20 min late
  • Purpose-aware context
  • No trip assignment

What the replay can prove

Every marker is a recorded public-feed position. A line joins consecutive recorded positions only when they are no more than 7 minutes apart. The replay does not create a location inside a data gap.

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

This is the closest defensible public measure of “out of service.” It does not reveal whether a bus is deadheading, travelling to a route, at a depot, blocked by an operator, affected by onboard equipment, or experiencing a feed problem. Distance is a straight-line minimum between consecutive observations; gaps over 10 minutes and implausible jumps are excluded.

Movement without a published trip assignment

HourVehicles seenWithout trip assignmentPosition observationsMeasured vehicle-hoursMinimum observed km

Loading the daily movement summary…