Detour Route 59 South: Route 59 diverted from Laval to Station Lyon.

No 59 trips cancelled now · 1 did not run in NovemberCancellations →

Previous measure: 74.2% of arrivals were within five minutes of the timetable (73,007 arrivals over 22 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.

STO ᐊᖁᑎᖓ 59: Ottawa

ᑐᕌᖓᔪᖅPob Allum2 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

CENTRE RIDEAU6 min sched.
ALBERT/METCALFE9 min sched.
ALBERT/BANK10 min sched.
KENT / SPARKS12 min sched.
WELLINGTON/LYON13 min sched.
du PORTAGE/AUBRY2 min sched.
du PORTAGE/LAVAL3 min sched.
LAURIER/EDDY5 min sched.
ALEXANDRE-TACHÉ/MILLAR7 min sched.
ALEXANDRE-TACHÉ/SAINT-JOSEPH8 min sched.
ALEXANDRE-TACHÉ/CHÂTEAUBRIAND9 min sched.
ALEXANDRE-TACHÉ/HORMIDAS-DUPUIS10 min sched.
ALEXANDRE-TACHÉ/BÉGIN10 min sched.
ALEXANDRE-TACHÉ/BOUDRIA11 min sched.
ALEXANDRE-TACHÉ/SAINTE-THÉRÈSE11 min sched.
ALEXANDRE-TACHÉ/SAINT-DOMINIQUE12 min sched.
ALEXANDRE-TACHÉ/SAINT-RAYMOND13 min sched.
chemin d'AYLMER/ROYALE13 min sched.
chemin d'AYLMER/SAMUEL-DE-CHAMPLAIN0 min sched.
chemin d'AYLMER/d'AUGUSTA1 min sched.
chemin d'AYLMER/CHAUDIÈRE2 min sched.
chemin d'AYLMER/ALLEN3 min sched.
chemin d'AYLMER/ATHOLL DOUNE4 min sched.
chemin d'AYLMER/d'AMOUR4 min sched.
PARC-O-BUS RIVERMEAD5 min sched.
chemin d'AYLMER/de l'HIPPODROME7 min sched.
chemin d'AYLMER/MORLEY-WALTERS8 min sched.
chemin d'AYLMER/VANIER9 min sched.
chemin d'AYLMER/VANIER9 min sched.
chemin d'AYLMER/GARDEN10 min sched.
chemin d'AYLMER/du GOLF11 min sched.
chemin d'AYLMER/GRIMES12 min sched.
chemin d'AYLMER/FRASER13 min sched.
chemin d'AYLMER/SAMUEL-EDEY14 min sched.
chemin d'AYLMER/BELMONT15 min sched.
chemin d'AYLMER/de la COLLINE15 min sched.
PRINCIPALE/du BORDEAUX16 min sched.
PRINCIPALE/ WILFRID-LAVIGNE16 min sched.
PRINCIPALE/FRANK-ROBINSON17 min sched.
PARK/SYMMES18 min sched.
EARDLEY/PARKER19 min sched.
EARDLEY/ROMÉO-GENDRON19 min sched.
EARDLEY/GOULET19 min sched.
EARDLEY/FRONT20 min sched.
EARDLEY/ÉDOUARD-GAGNON21 min sched.
147, EARDLEY21 min sched.
EARDLEY/RILEY22 min sched.
PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée23 min sched.

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 28, 2026 – Nov 3, 2026

Scheduled trips with cancellation notices

Trips in the published timetable marked cancelled without qualifying later matching vehicle observations in our archive. This does not prove the trip did not operate. Trips with any notice: 3.

Trips needing investigation

2 of 518 trips with a usable feed window (0.4%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

516 with position · 2 to investigate · 89 excluded · 607 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 2:20 p.m..

Coverage, exclusions and sources

0 of 12 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

89 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 516 / 607 (85%). This is not a delivered-service rate. 7 service days in this source.

Timetables retained before the service day: 7 / 7 requested days · 0 missing days.

Historical calculation: Nov 4, 2026, 12:48 p.m.

Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.

What does the evidence show?

Predictions against the timetable

74.2%

of eligible provider predictions were within five minutes of the timetable.

Predictions in the source: 73,007
Weekdays with evidence: 17
Evidence window: Oct 6, 2026 – Nov 3, 2026

The hours we have evidence for

0097% · 768 predictions · 10 days
0589% · 1,008 predictions · 7 days
0689% · 1,326 predictions · 7 days
0781% · 1,764 predictions · 9 days
0873% · 2,111 predictions · 10 days
0981% · 1,929 predictions · 11 days
1087% · 1,850 predictions · 11 days
1183% · 1,903 predictions · 12 days
1281% · 2,072 predictions · 12 days
1383% · 2,111 predictions · 12 days
1478% · 2,263 predictions · 13 days
1566% · 2,098 predictions · 12 days
1663% · 2,622 predictions · 13 days
1765% · 2,948 predictions · 12 days
1874% · 2,571 predictions · 11 days
1973% · 1,747 predictions · 11 days
2084% · 1,793 predictions · 10 days
2183% · 1,735 predictions · 10 days
2286% · 1,705 predictions · 10 days
2390% · 1,661 predictions · 10 days

Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.

These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.

Calculated: Nov 4, 2026

6 partial-capture days not counted.

What about time of day?

20 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.

Improvement or decline requires comparable periods. This single result cannot establish a trend.

Explore the dated evidence Source of this result

Buses arriving bunched

Last 28 days, October 7, 2026 to November 3, 2026: 21 days counted.

2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: October 8, 2026, October 12, 2026.

Values and interpretation

2% of back-to-back buses on this route arrived bunched together: 1,048 of 53,307 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

2% of pairs (883) had a long gap: more than 1.75 times the planned wait between them.

Buses arriving bunched
ᐅᓪᓗᒥ ᐃᑲᕐᕋᖅ	Pairs checked	Bunched	Long gap
Early morning (4 to 6 a.m.)	1,116	0% (0)	0% (5)
Morning rush (6 to 9 a.m.)	7,440	3% (219)	2% (173)
Midday (9 a.m. to 3 p.m.)	17,164	0% (40)	0% (32)
Afternoon rush (3 to 6 p.m.)	10,222	6% (635)	6% (589)
Evening (6 to 10 p.m.)	10,945	1% (153)	1% (84)
Night (10 p.m. to 4 a.m.)	6,420	0% (1)	0% (0)

ᖃᓄᖅ ᐅᒃᑐᖅᑕᐅᒻᒪᖔᑦ →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: CENTRE RIDEAU to KENT / SPARKS, 7.7 km/h actual against 11.7 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
CENTRE RIDEAU	KENT / SPARKS	1.2 km	11.7 km/h	7.7 km/h	646	38%
PARC-O-BUS ALLUMETTIÈRES	chemin d'AYLMER/du BORDEAUX	2.9 km	22.5 km/h	9 km/h	592	78%
KENT / SPARKS	du PORTAGE/AUBRY	1.2 km	12.9 km/h	9 km/h	691	46%
du PORTAGE/AUBRY	LAURIER/EDDY	470 m	8.8 km/h	11.6 km/h	705	2%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	16 km/h	12.1 km/h	692	33%
PARC-O-BUS RIVERMEAD	chemin d'AYLMER/MORLEY-WALTERS	790 m	16.2 km/h	14.9 km/h	732	9%
de l'HÔTEL-de-VILLE/LAURIER	CENTRE RIDEAU	2.5 km	12.1 km/h	15.8 km/h	569	0%
PRINCIPALE/du BORDEAUX	PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée	2.8 km	22.9 km/h	20.4 km/h	698	4%

A slow trip took at least 1.5 times the planned time.

ᖃᓄᖅ ᐅᒃᑐᖅᑕᐅᒻᒪᖔᑦ →

ᓄᓇᓕᐅᑉ ᐊᖅᑯᑎᓂᒃ ᐱᓕᕆᓂᖓ ᐅᓇ ᐊᖅᑯᑎ ᖃᓂᒋᔮᓂ

ᐋᑐᕚ ᓄᓇᓕᖓᑕ ᑐᓴᖅᑎᑦᑎᓂᖏᑦ ᐊᖁᑏᑦ ᓴᓇᔭᐅᔪᑦ ᒪᑐᑦᑕᐅᔪᓪᓗ ᑲᑐᔾᔨᖃᑎᒌᓐᓂᖏᓐᓄᑦ, ᑕᒪᑐᒪ ᐊᖁᑎᐅᑉ ᖃᓂᒋᔮᓂ. ᖃᓂᒋᔭᐅᓂᖓ ᓴᖅᑭᑦᑎᙱᑦᑐᖅ ᐸᔅ ᐊᓯᐊᒍᑦ ᐃᖏᕐᕋᓂᖓᓂᒃ. ᑕᒪᑐᒥᖓ ᖃᐅᔨᔪᒪᒍᕕᑦ, ᐊᐅᓚᑦᑎᔨᐅᑉ ᑐᓴᒐᒃᓴᖏᑦ ᕿᒥᕐᕈᒋᑦ.

ᐊᖁᑎᒥᒃ ᓴᓇᔪᑦ
ALBERT between ELGIN and METCALFE
Oct 29, 2026, 12:00 a.m. to Jan 26, 2027, 5:00 p.m.
ALBERT lane reduction between ELGIN and METCALFE due to construction, from October 29th to January 26th.
ᓄᓇᓕᐅᑉ ᑎᑎᕋᖅᓯᒪᔭᖓ ᐅᓇ ᐊᑦᑐᐃᓂᖃᖅᑐᖅ ᐃᖏᕐᕋᔾᔪᑎᓄᑦ.
about 0 m from the route
City record updated Nov 2, 2026, 12:44 p.m..
ᐊᖁᑎᒥᒃ ᓴᓇᔪᑦ
Slater between Bay and Lyon
Oct 30, 2026, 12:00 a.m. to Nov 6, 2026, 5:00 p.m.
Slater lane reduction between Bay and Lyon due to construction, from November 2nd to 6th.
about 0 m from the route
City record updated Oct 30, 2026, 1:28 p.m..
ᐊᖁᑎᒥᒃ ᓴᓇᔪᑦ
ALBERT at LYON
ᐅᓪᓗᖏᑦ ᑐᓴᖅᑎᑕᐅᓯᒪᙱᑦᑐᑦ
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 2 m from the route
City record updated Sep 9, 2026, 6:32 p.m..

A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.

ᐱᕝᕕᖓ: ᐋᑐᕚ ᓄᓇᓕᐊ, ᐊᖅᑯᑎᓂ ᐱᓇᓱᐊᕐᓂᐅᔪᑦ ᒪᑐᓯᒪᔪᓪᓗ. ᑐᓴᒐᒃᓴᐃᑦ ᐊᑐᖅᑕᐅᔪᑦ Open Government Licence ᑯᑦ, ᐋᑐᕚ ᓄᓇᓕᐊ. ᓄᓇᓕᐊ ᐅᖃᖅᑐᖅ ᑎᑎᕋᖅᓯᒪᔪᑦ ᐱᐅᓂᖅᐹᒥ ᐱᓇᓱᐊᕈᓯᐅᓂᖏᓐᓂᒃ. ᐃᓘᓐᓇᖏᓐᓂᒃ ᐃᓗᓕᖃᙱᓐᓇᔭᖅᑐᑦ. ᐋᑐᕚ ᓄᓈᓖᑦ ᐊᖅᑯᑏᑦ ᓄᓇᙳᐊᖓ ↗

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

8 scheduled trips with counted cancellation notices from Wed, Oct 7 to Tue, Nov 3.

Not counted: 1 trips with qualifying later matching vehicle observations and 1 for trips not in that day’s timetable.

Hours with the most cancellations: 7 a.m. (3), 4 p.m. (2), 6 a.m. (1)

Latest cancelled trips

Fri, Oct 30, scheduled 16:37
Thu, Oct 29, scheduled 19:11
Wed, Oct 28, scheduled 07:12
Fri, Oct 23, scheduled 06:06
Thu, Oct 22, scheduled 16:08

A cause is shown only when STO’s own alert for that trip gives one.

Did not come (no bus seen, no notice), last 7 days: 1 of 518 trips we could check.

When this route is usually busy

From the load level STO’s buses report, over the last eight weeks. A time is marked usually busy when at least half of the trips with a reading reached standing room or fuller.

No time of day was usually busy in the last eight weeks.

When this route is usually busy	ᐱᓇᓱᐊᕈᓰᑦ	ᓈᑦᓰᓈᕐᕕᒃᑯᑦ	ᓈᑦᑏᖑᔭᕐᓂ
Before 6 am	Usually seats2.4% of 164 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats27.4% of 712 trips	Usually seats1.8% of 55 trips	Usually seats0% of 55 trips
9 am to 3 pm	Usually seats12.5% of 1,002 trips	Usually seats6.4% of 202 trips	Usually seats2.7% of 185 trips
3 to 6 pm	Usually seats37.7% of 804 trips	Usually seats8.1% of 123 trips	Usually seats2.7% of 112 trips
6 to 10 pm	Usually seats10.4% of 709 trips	Usually seats2.6% of 151 trips	Usually seats1.4% of 145 trips
After 10 pm	Usually seats2.5% of 359 trips	Usually seats3.3% of 61 trips	Usually seats0% of 51 trips

Based on 56 computed days.

Source: the occupancy status in STO’s public real-time vehicle feed, which STO sets from each bus’s load sensor (seats available under 60% full, standing room under 90%, full above 90%).
Each trip counts once per time of day, at the highest load it reported.
Reports of an empty bus are left out, because older records could not tell an empty bus from one with no sensor.
A time of day needs at least 12 trips on at least 4 different days before anything is shown. Holidays are counted with their day of the week.

Open the dated prediction analysis

ᐃᓱᓕᑦᑎᓂᖅ

What this route needs

Median provider predictions are 3.4 min later than the timetable in 3 hours of the day.

Predictions near the start are about 2.3 min later than the timetable, with a similar difference near the end. This does not establish the cause.

Predicted waits All measured hours are 1.4 min longer than scheduled waits.

Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 20 hours with samples

00:00: 97% of final predictions within five minutes of the timetable, 768 predictions, typically 0.7 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 89.4% of final predictions within five minutes of the timetable, 1,008 predictions, typically 1.8 min late
06:00: 89.1% of final predictions within five minutes of the timetable, 1,326 predictions, typically 2.2 min late
07:00: 81.2% of final predictions within five minutes of the timetable, 1,764 predictions, typically 1.8 min late
08:00: 72.8% of final predictions within five minutes of the timetable, 2,111 predictions, typically 2.8 min late
09:00: 81.3% of final predictions within five minutes of the timetable, 1,929 predictions, typically 2.6 min late
10:00: 87% of final predictions within five minutes of the timetable, 1,850 predictions, typically 1.5 min late
11:00: 83.1% of final predictions within five minutes of the timetable, 1,903 predictions, typically 1.7 min late
12:00: 81.3% of final predictions within five minutes of the timetable, 2,072 predictions, typically 2.2 min late
13:00: 83% of final predictions within five minutes of the timetable, 2,111 predictions, typically 1.9 min late
14:00: 77.6% of final predictions within five minutes of the timetable, 2,263 predictions, typically 2.7 min late
15:00: 66% of final predictions within five minutes of the timetable, 2,098 predictions, typically 3.6 min late
16:00: 62.6% of final predictions within five minutes of the timetable, 2,622 predictions, typically 3.3 min late
17:00: 64.5% of final predictions within five minutes of the timetable, 2,948 predictions, typically 3.4 min late
18:00: 74.2% of final predictions within five minutes of the timetable, 2,571 predictions, typically 2.3 min late
19:00: 72.5% of final predictions within five minutes of the timetable, 1,747 predictions, typically 2.9 min late
20:00: 83.6% of final predictions within five minutes of the timetable, 1,793 predictions, typically 1.8 min late
21:00: 82.9% of final predictions within five minutes of the timetable, 1,735 predictions, typically 1.5 min late
22:00: 85.5% of final predictions within five minutes of the timetable, 1,705 predictions, typically 2.4 min late
23:00: 90.2% of final predictions within five minutes of the timetable, 1,661 predictions, typically 1.3 min late

90% or more of predictions within five minutes
80 to 90% of predictions within five minutes
under 80% of predictions within five minutes
not enough data

Findings
What	ᖃᖓ	ᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅ	Scenario or next investigation
ProblemPredictions later than timetable	15:00 to 18:00	3.4 min late	Recovery time at the terminal
ProblemPredicted spacing varies	All measured hours	1.4 min extra wait	Manage the headway

Measurements

Predictions later than timetable · 15:00 to 18:00: Measured arrivals 7,668; Hours affected 3; Spread 10 min; Median delay 3.4 min; Suggested running time change 3.4 min
Predicted spacing varies · All measured hours: ᓄᖃᕐᕕᐃᑦ 74; Extra wait share 25.3%; Matched arrivals 5,502; ᐅᑕᖅᑭᓂᖅ ᐃᓚᔭᐅᔪᖅ 1.4 min; Scheduled wait 5.6 min

Open history, reliability and route analysis

Route check

How route 59 has been running

A short summary of what we know. We say so when we cannot answer a question.

Bottom line

Provider predictions often differed from the timetable; actual arrivals were not independently measured.

74 in 100 eligible predictions were within 5 minutes of the timetable · 73,007 predictions checked

Prediction sample size: Larger sample

Based on 73,007 eligible provider predictions over 22 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 4, 2026, 1:32 p.m.

Where and when did predictions differ repeatedly?

These are repeated prediction-to-timetable differences, not independently measured service failures. They use the same eligible predictions as the result above, but group by stop rather than hour, so the lists need not match line for line.

16–17: 37 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,622 predictions over 13 days).
17–18: 36 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,948 predictions over 12 days).
15–16: 34 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,098 predictions over 12 days).

1 current notice affects this route

• Detour Route 59 South

Prediction differences by stop

PARC-O-BUS ALLUMETTIÈRES
64 in 100 eligible predictions differed from the timetable by more than 5 minutes (755 predictions over 24 days).
Open this stop
EARDLEY/GOULET
41 in 100 eligible predictions differed from the timetable by more than 5 minutes (858 predictions over 24 days).
Open this stop
PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée
40 in 100 eligible predictions differed from the timetable by more than 5 minutes (830 predictions over 24 days).
Open this stop
EARDLEY/FRONT
40 in 100 eligible predictions differed from the timetable by more than 5 minutes (855 predictions over 24 days).
Open this stop

These are route-specific provider predictions compared with the timetable. They identify repeated prediction differences at a place and time, not measured arrivals or their cause.

Check every trip and date

Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.

What riders want to know

Is any trip cancelled right now?: 0 of 12Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 2 of 518 checked trips need a closer look2 of 518 trips with enough public-feed evidence had no matching position over 7 days. 89 of 607 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
How did provider predictions differ from the timetable?: At the 95th percentile, the predicted difference was 10.7 min (positive means later; negative means earlier)74 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: 7.0 min average predicted wait1.4 min beyond the scheduled wait, based on 5,502 eligible predictions at 74 high-frequency stops over 12 days.

ᐊᐅᓪᓚᖅᑕᕐᕕᐅᓂᖏᑦ ᐊᓯᔾᔨᕐᓂᖏᓐᓂᒃ ᕿᒥᕐᕈᓂᖅ

ᓴᖅᑭᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᖏᑦ ᐅᓪᓗᖏᑦ: ᓯᕗᓂᐊᓂ ᑭᖑᓂᐊᓂᓗ

ᐅᓇ ᒫᓐᓇ ᐊᐅᓚᓂᕐᒧᑦ ᐸᕐᓇᐅᑎ ᓇᓪᓕᐅᓇᐃᓪᓗᒍ ᓯᕗᓪᓕᐅᔪᒧᑦ ᐸᕐᓇᐅᑎᒧᑦ. ᐸᕐᓇᐅᑎᒥ ᐊᓯᔾᔨᕐᓂᑦ ᐸᕐᓇᓯᒪᔪᓂᒃ ᓇᓗᓇᐃᖅᓯᔪᑦ. ᐃᖏᕐᕋᓂᖅ ᐊᐅᓚᓚᐅᕐᓂᖓᓂᒃ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ.

Current published schedule began November 2, 2026

ᐅᓪᓗᖅ ᓂᕈᐊᖅᑕᐅᓯᒪᔪᖅ ᐊᑐᓂ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐅᓪᓗᓂ ᐃᑲᕐᕋᓂᓪᓗ ᓴᖅᑭᑕᐅᓯᒪᔪᓂᑦ

ᑕᑯᓐᓇᕈᑦᑕᖅᐳᒍᑦ ᓯᕗᓪᓕᖅᐹᖅ ᓇᒡᒐᔾᔭᐅ ᓄᑖᑦ ᐊᐅᓚᓂᕐᒧᑦ ᐸᕐᓇᐅᑎᑦ ᐱᒋᐊᓚᐅᖅᑎᓪᓗᒋᑦ. ᐊᒻᒪ ᓇᒡᒐᔾᔭᐅ ᐱᓇᓱᐊᕈᓯᕐᒥᒃ ᓯᕗᓂᐊᒍᑦ. ᓈᓴᐅᑎᑦ ᑕᒪᕐᒥᒃ ᐱᔭᐅᔪᑦ ᐱᑕᖃᕐᓂᐊᖅᑐᓂᑦ ᒐᕙᒪᐅᑉ GTFS ᑐᓴᒐᒃᓴᖏᓐᓂᑦ. ᐊᑎᖏᑦ ᐊᑖᓂ ᐃᓗᓕᖃᖅᑐᑦ.

ᐅᓪᓗᑦ ᓂᕈᐊᖅᓯᒪᔭᑎᑦ ᐊᑕᐅᓯᖅ ᐅᖓᑖᓄᓪᓗ ᐊᐅᓚᓂᖓ ᐊᓯᔾᔨᖅᑕᐅᓯᒪᔪᖅ. ᐅᓇ ᖁᕕᐊᓱᐊᕐᕕᐅᓂᖓᓄᑦ ᐅᕝᕙᓘᓐᓃᑦ ᐊᔾᔨᐅᙱᑦᑐᒥᒃ ᐊᐅᓚᓂᖃᕐᓂᖓᓄᑦ ᐱᔾᔪᑎᖃᖅᑐᖅ. ᐱᓇᓱᐊᕐᕕᐅᔪᓂ ᐅᓪᓗᓂ ᐊᐅᓚᓂᖓ ᐅᒃᓱᓂᖓᓂᒃ ᑐᑭᖃᙱᑦᑐᖅ.

ᓯᕗᓂᐊᓂ

ᐱᔨᑦᑎᕋᐅᑎᐅᑉ ᐅᓪᓗᖓ ᕿᒥᕐᕈᐊᖅᑕᐅᔪᖅ: October 26, 2026

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 0
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 0
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 0
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: —–—

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

ᓄᑖᖅ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐸᕐᓇᐅᑎ

ᐱᔨᑦᑎᕋᐅᑎᐅᑉ ᐅᓪᓗᖓ ᕿᒥᕐᕈᐊᖅᑕᐅᔪᖅ: November 2, 2026

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 95
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 97
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 5
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 05:06–00:47 next day

Operator calendar-date records: 1 added · 0 removed

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

ᐱᔨᑦᑎᕋᐅᑎᑦ ᐱᐅᓯᕚᓕᓚᐅᖅᐸᑦ ᐊᓯᔾᔨᕐᓂᐅᑉ ᑭᖑᓂᐊᒍᑦ?

ᑎᑭᓐᓂᖏᑦ ᓇᓗᓇᐃᖅᓯᒪᔪᑦ ᐊᔾᔨᒌᙱᓐᓂᖏᑦ ᖃᐅᔨᓴᕐᓂᐊᖅᐸᕗᑦ. 14 ᐅᓪᓗᓂ ᐊᓯᔾᔨᕐᓂᖓᑕ ᓯᕗᓂᖓᓂ ᑭᖑᓂᖓᓂᓗ. ᓴᖅᑭᑎᑦᑎᓂᐊᖅᐳᒍᑦ ᒪᕐᕉᒃ ᐱᑕᖃᓕᕋᐃᒐᒃ ᐱᔨᑦᑎᕐᕕᐅᔪᓂᒃ ᐅᓪᓗᓂᒃ 7 ᐅᖓᑖᓄᓪᓗ, ᑎᑭᓐᓂᕐᓂᓪᓗ 200 ᐅᖓᑖᓄᓪᓗ.

Still collecting: before has 40,268 arrivals over 13 days; after has 5,224 arrivals over 2 days. No improvement or decline is claimed yet.

Checksums let anyone verify which retained timetable produced the counts. A changed count does not identify a cause, cancellation, operator decision, or passenger impact.

How this route is judged: Regular all-stop route

We compare the last eligible provider prediction for each scheduled arrival with the official schedule. These are not independently measured arrivals. A result needs at least 200 eligible predictions. Within 5 minutes is the rider-facing target used here.

What this data cannot prove

The public feed does not provide dependable passenger counts or passed-up-rider events. A missing position does not by itself prove a cancellation, no-show, short turn or cause.

See the definitions, thresholds and evidence order

Official current feed: explicit cancellations, skipped stops and active notices.
Matched observations: vehicle positions and settled predictions tied to the official schedule.
Official timetable: what was planned, kept separate from what was observed.
Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.

Provisional results, published evidence

How did predictions compare with the timetable?

Each hour compares the last eligible provider prediction for a scheduled arrival with the timetable. “Within 5 minutes” describes that prediction difference, not a measured arrival or proof that a bus ran.

Evidence window: October 6, 2026 to November 3, 2026

Within 5 minutes of schedule: 74.2%
Eligible predictions checked: 73,007
Weekdays with data: 17
95th-percentile predicted delay: 10.7 min late

Patterns by hour (20)

Patterns by hour (20)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
00:00	97.0%	0.7 min late	4 min late	768 · 10 days
05:00	89.4%	1.8 min late	5.7 min late	1,008 · 7 days
06:00	89.1%	2.2 min late	5.7 min late	1,326 · 7 days
07:00	81.2%	1.8 min late	8.4 min late	1,764 · 9 days
08:00	72.8%	2.8 min late	9.3 min late	2,111 · 10 days
09:00	81.3%	2.6 min late	7.2 min late	1,929 · 11 days
10:00	87.0%	1.5 min late	6.3 min late	1,850 · 11 days
11:00	83.1%	1.7 min late	7.4 min late	1,903 · 12 days
12:00	81.3%	2.2 min late	8.1 min late	2,072 · 12 days
13:00	83.0%	1.9 min late	7.3 min late	2,111 · 12 days
14:00	77.6%	2.7 min late	8.4 min late	2,263 · 13 days
15:00	66.0%	3.6 min late	10.2 min late	2,098 · 12 days
16:00	62.6%	3.3 min late	13.3 min late	2,622 · 13 days
17:00	64.5%	3.4 min late	17.2 min late	2,948 · 12 days
18:00	74.2%	2.3 min late	8.9 min late	2,571 · 11 days
19:00	72.5%	2.9 min late	10.2 min late	1,747 · 11 days
20:00	83.6%	1.8 min late	7.4 min late	1,793 · 10 days
21:00	82.9%	1.5 min late	7.7 min late	1,735 · 10 days
22:00	85.5%	2.4 min late	6.3 min late	1,705 · 10 days
23:00	90.2%	1.3 min late	6.3 min late	1,661 · 10 days

3 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

Scheduled bus, but not observed in realtime

516 / 607 scheduled trips published at least one position across 5 service days (85.0%).

00:002 / 5 trips without a position60.0%
07:0018 / 48 trips without a position62.5%
06:009 / 25 trips without a position64.0%
19:009 / 28 trips without a position67.9%
21:009 / 28 trips without a position67.9%
20:008 / 28 trips without a position71.4%

This is not a confirmed no-show. A missing position can mean a cancelled or missed bus, but it can also mean an unassigned trip ID or an operator-feed gap. Otranspo publishes the gap because it matters to riders while keeping the conclusion honest.

Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position check: the timetable kept before each service day, matched to recorded positions. Exact IDs are preferred; an OC timetable suffix is matched only to one trip on the same route and date with an overlapping time window. Missing timetables, ambiguous matches and feed gaps stay labelled; they are not confirmed no-shows. Sources and limitations.

Dated service

Trips scheduled that day

The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.

Service day

November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 95 trips in the retained timetable · retained notices; capture coverage unverified

In short: 72 with a matched position · 0 with no matching position (to investigate) · 23 with an unknown outcome.

05:06– 05:45
Trip sto:63294704Insufficient coverage or identity; outcome unknown
05:21– 06:00
Trip sto:63295736Insufficient coverage or identity; outcome unknown
05:36– 06:15
Trip sto:63294932Insufficient coverage or identity; outcome unknown
05:45– 06:26
Trip sto:63294853Insufficient coverage or identity; outcome unknown
05:51– 06:30
Trip sto:63295527Insufficient coverage or identity; outcome unknown
06:06– 06:49
Trip sto:63294933Insufficient coverage or identity; outcome unknown
06:20– 07:03
Trip sto:63294690Insufficient coverage or identity; outcome unknown
06:33– 07:16
Trip sto:63294707Insufficient coverage or identity; outcome unknown
06:40– 07:24
Trip sto:63295781Insufficient coverage or identity; outcome unknown
06:45– 07:34
Trip sto:63294805Insufficient coverage or identity; outcome unknown
07:02– 07:53
Trip sto:63294920Insufficient coverage or identity; outcome unknown
07:12– 07:49
Trip sto:63296103Insufficient coverage or identity; outcome unknown

· Open all evidence for this day

ᑐᕌᕝᑦ

ᑖᓐᓇ ᐅᖃᐅᓯᒧᑦ ᐊᓯᔾᔨᖅᓯᒪᔪᖅ ᑐᕌᕝᑦᐅᕗᖅ.

Help improve it

About 48% of this site is translated so far. The rest is shown in English.

Read this page in English

This translation is a draft.

This page is a machine draft in Inuktitut (ᐃᓄᒃᑎᑐᑦ), the language of the Inuit. It was prepared without review by its speakers, and is waiting for one. Speakers and the community are invited to correct it. We will replace it with their words. Ottawa is on the unceded territory of the Anishinabe Algonquin Nation.

Cette page est une ébauche automatique en inuktitut (ᐃᓄᒃᑎᑐᑦ), la langue des Inuits. Elle a été préparée sans révision par ses locuteurs, et attend l’un d’eux. Les locuteurs et la communauté sont invités à la corriger. Nous la remplacerons par leurs mots. Ottawa se trouve sur le territoire non cédé de la Nation algonquine anishinabe (Anishinabe Algonquin Nation).