Skip to main content
Otranspo
FR

Service reports

Every figure here is a count of arrivals this site observed and settled, added up over the service dates in the period. Routes are named for running well on the same evidence they are named for running badly.

Across the network

Sep 6, 2026 to Sep 12, 2026 · 7 service days

Arrivals on time
75.6%
Arrivals observed
1,915,563
Routes measured
142

Previous week: 80.4% on time.

Met the 99.5% on-time standard

OC Transpo argues for 99.5%. That target is written for service delivery, meaning trips operated against trips scheduled, and this site does not observe enough trips to speak to it. These routes cleared the same bar on the measure this site does hold to a large sample: settled arrivals within five minutes of the timetable.

No route held 99.5% of its arrivals on time for this whole period. Routes reach it on a single service day; none has yet held it for a week.

Most reliable this period

The routes with the highest share of on-time arrivals, whether or not any of them met the standard above. A ranking, not a claim about a target.

Most improved

Measured against the week immediately before this one.

Biggest decline

Measured against the week immediately before this one.

Furthest from the timetable

The routes with the lowest share of on-time arrivals. A low figure does not say whose fault it is: a route can be late because its timetable is wrong, because the service is failing, or because of the traffic it runs in. Each route page separates those.

Routes this report does not rank

These routes are measured, and their arrivals are left out of every ranking and out of the network figure above. They are not all-day conventional service, so an on-time percentage would be compared against routes that are. A school journey exists to reach a bell, a community route is built around pickups, and an event shuttle is released when a venue empties. Each route page carries what this site does hold it to.

Monthly service reports

One page per calendar month. A month is published once, when every day in it is accounted for, and is not recomputed afterwards.

What this report does not cover

This site observes about half the trips that run: median observed coverage across the network is 53%. That is enough to measure whether the trips it sees arrived on time, and not enough to say how many trips ran at all. Nothing here should be read as a count of cancellations.

These figures are buses. Lines 1, 2 and 4 are published in the timetable but this site has recorded no settled train arrivals, so the O-Train is absent from every figure above rather than being counted as running well.

How these figures are produced →