No 97 trips cancelled now · 2 did not run in NovemberCancellations →

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

STO ᐊᖁᑎᖓ 97: Masson-Angers/Buckingham

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

STATION LORRAIN4 min sched.
LORRAIN/SAINT-RENÉ EST5 min sched.
LORRAIN/VINCENT-LEGRIS EST5 min sched.
LORRAIN/MARLENE-GOYET6 min sched.
LORRAIN/AUGUSTE-RENOIR7 min sched.
LORRAIN/des FLEURS7 min sched.
des LAURENTIDES/de NEUVILLE16 min sched.
des LAURENTIDES/de GRANDPRÉ17 min sched.
des LAURENTIDES/de CHERISY17 min sched.
ROUTE 148/des LAURENTIDES17 min sched.
ROUTE 148/du RUISSEAU18 min sched.
ROUTE 148/ de SAINT-MARIN18 min sched.
ROUTE 148/ des BALBUZARDS18 min sched.
ROUTE 148/de la PAPETIÈRE19 min sched.
ROUTE 148/de la FORTERESSE19 min sched.
ROUTE 148/des HAUTS-BOIS19 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant20 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant20 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant21 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant22 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant24 min sched.
ARRÊT DE COURTOISIE Montréal/Kendall25 min sched.
PARC-O-BUS GEORGES/ROUTE 14825 min sched.
GEORGES/JEAN-BAPTISTE-ROUTHIER26 min sched.
ENCAN de MASSON27 min sched.
GEORGES/des LIARDS28 min sched.
GEORGES/de l'ÉCORCE28 min sched.
GEORGES/de l'ÉCORCE29 min sched.
GEORGES/FOUCAULT30 min sched.
PARC-O-BUS GEORGES/FOUCAULT30 min sched.
GEORGES/DAMIEN-CHARRON31 min sched.
GEORGES/CARDINAL31 min sched.
BERTRAND/ARTHUR-GRATTON32 min sched.
BERTRAND/CHARETTE32 min sched.
CHARETTE/RACAN33 min sched.
CHARETTE/BOULADIER33 min sched.
PIERRE-LAPORTE/ALBERT-FILLION34 min sched.
PIERRE-LAPORTE/ARTHUR-GRATTON34 min sched.
CURÉ-ROY/ELZÉAR-LAFLEUR35 min sched.
CURÉ-ROY/L'ABBÉ36 min sched.
l'ABBÉ/BERGERON36 min sched.
BERGERON/GÉRARD-GAUTHIER37 min sched.
BERGERON/BRIDGE37 min sched.
KENNY/BRIDGE38 min sched.
KENNY/SPENCER39 min sched.
KENNY/MACLAREN39 min sched.
MACLAREN OUEST/GEORGES40 min sched.
Av. de BUCKINGHAM/JOSEPH41 min sched.
Av. de BUCKINGHAM/JEAN-XXIII42 min sched.
JEAN-XXIII/des PINS43 min sched.
BÉLANGER/ROSS43 min sched.
BÉLANGER/JOSEPH44 min sched.
BÉLANGER/MACLAREN EST44 min sched.
MACLAREN EST/JAMES45 min sched.
MACLAREN EST/PAUL46 min sched.
MACLAREN EST/LAFRAMBOISE47 min sched.
ÉCOLE HORMISDAS-GAMELIN47 min sched.
MACLAREN/SAUVÉ48 min sched.
MACLAREN/MOISE-GAUTHIER49 min sched.
MACLAREN/ELISABETH-CHAUVIN49 min sched.
MACLAREN/ALPHONSE-LABELLE50 min sched.
LÉPINE/MACLAREN EST51 min sched.
LÉPINE51 min sched.
LÉPINE/DOLLARD52 min sched.
121, AVENUE LÉPINE52 min sched.
LÉPINE/Av. de BUCKINGHAM53 min sched.
AV. DE BUCKINGHAM/ODILE-DAOUST56 min sched.
de MASSON/des CHUTES-RHÉAUME58 min sched.
de MASSON/SAINT-CHARLES58 min sched.
ROUTE 148/NAPOLÉON59 min sched.
ROUTE 148/GUY-DUBUC0 min sched.
ROUTE 148/DANIEL-KELLY0 min sched.
ROUTE 148/LOMBARD0 min sched.
de l'ARÉNA/LOMBARD arrivée1 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. Not counted: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 1.

Trips needing investigation

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

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

216 with position · 2 to investigate · 33 excluded · 251 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 216 / 251 (86.1%). 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:09 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

87.3%

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

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

The hours we have evidence for

0098% · 687 predictions · 10 days
01100% · 60 predictions · 9 days
0694% · 565 predictions · 7 days
0791% · 1,067 predictions · 9 days
0894% · 1,149 predictions · 10 days
0997% · 1,404 predictions · 11 days
1090% · 1,463 predictions · 11 days
1191% · 1,544 predictions · 12 days
1287% · 1,559 predictions · 12 days
1388% · 1,642 predictions · 12 days
1489% · 1,471 predictions · 13 days
1575% · 1,533 predictions · 12 days
1661% · 1,435 predictions · 13 days
1775% · 1,480 predictions · 12 days
1878% · 1,834 predictions · 11 days
1987% · 1,826 predictions · 11 days
2088% · 1,419 predictions · 10 days
2187% · 1,332 predictions · 10 days
2294% · 1,379 predictions · 10 days
2393% · 756 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

No bunched buses were measured on this route in the last 28 days (1,535 pairs checked at stops).

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

Buses arriving bunched
ᐅᓪᓗᒥ ᐃᑲᕐᕋᖅ	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	166	0% (0)	0% (0)
Evening (6 to 10 p.m.)	1,369	0% (0)	0% (0)

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

Where this route is slowest

Slowest: STATION LORRAIN to LORRAIN/des FLEURS, 7.9 km/h actual against 22.8 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
STATION LORRAIN	LORRAIN/des FLEURS	1.2 km	22.8 km/h	7.9 km/h	300	79%
KENNY/MACLAREN	Av. de BUCKINGHAM/JOSEPH	640 m	14.7 km/h	14.4 km/h	324	7%
Av. de BUCKINGHAM/MACLAREN	KENNY/MACLAREN	580 m	13.6 km/h	15 km/h	278	8%
de l'ARÉNA/LOMBARD	130, AVENUE LÉPINE	4.8 km	33.7 km/h	18.6 km/h	266	67%
QUAI LOCAL de la CITÉ #6	Station LABROSSE #04	3.2 km	32.1 km/h	19.1 km/h	36	56%
130, AVENUE LÉPINE	Av. de BUCKINGHAM/MACLAREN	4.1 km	22.3 km/h	21.7 km/h	271	0%
KENNY/MACLAREN	CURÉ-ROY/PIERRE-LAPORTE	1.6 km	23 km/h	22 km/h	275	2%
CURÉ-ROY/ELZÉAR-LAFLEUR	KENNY/MACLAREN	1.5 km	22.1 km/h	22 km/h	319	2%

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

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

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

No counted cancellations on this route in the last four weeks. Notices we could not check would be listed below.

Did not come (no bus seen, no notice), last 7 days: 2 of 218 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 seats0% of 15 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats27.4% of 164 trips	Usually seats0% of 28 trips	Usually seats0% of 21 trips
9 am to 3 pm	Usually seats7.8% of 477 trips	Usually seats6.6% of 106 trips	Usually seats1% of 98 trips
3 to 6 pm	Usually seats14% of 322 trips	Usually seats8.1% of 62 trips	Usually seats1.5% of 65 trips
6 to 10 pm	Usually seats3% of 401 trips	Usually seats0% of 74 trips	Usually seats0% of 71 trips
After 10 pm	Usually seats1.4% of 207 trips	Usually seats0% of 43 trips	Usually seats0% of 37 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 1 hours of the day.

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

16:00 has 61% of predictions within five minutes of the timetable, against 89% the rest of the day.

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: 98.4% of final predictions within five minutes of the timetable, 687 predictions, typically 0.2 min late
01:00: 100% of final predictions within five minutes of the timetable, 60 predictions, typically 0.4 min early
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: not enough data
06:00: 94.2% of final predictions within five minutes of the timetable, 565 predictions, typically 0.2 min late
07:00: 90.6% of final predictions within five minutes of the timetable, 1,067 predictions, typically 0.9 min late
08:00: 94.4% of final predictions within five minutes of the timetable, 1,149 predictions, typically 1.1 min late
09:00: 97.4% of final predictions within five minutes of the timetable, 1,404 predictions, typically 1.5 min late
10:00: 90% of final predictions within five minutes of the timetable, 1,463 predictions, typically 1.3 min late
11:00: 91.2% of final predictions within five minutes of the timetable, 1,544 predictions, typically 1 min late
12:00: 86.8% of final predictions within five minutes of the timetable, 1,559 predictions, typically 1.4 min late
13:00: 88.2% of final predictions within five minutes of the timetable, 1,642 predictions, typically 1.4 min late
14:00: 88.8% of final predictions within five minutes of the timetable, 1,471 predictions, typically 1.4 min late
15:00: 74.9% of final predictions within five minutes of the timetable, 1,533 predictions, typically 2.6 min late
16:00: 60.8% of final predictions within five minutes of the timetable, 1,435 predictions, typically 3.4 min late
17:00: 75.3% of final predictions within five minutes of the timetable, 1,480 predictions, typically 2.8 min late
18:00: 77.7% of final predictions within five minutes of the timetable, 1,834 predictions, typically 1.5 min late
19:00: 86.9% of final predictions within five minutes of the timetable, 1,826 predictions, typically 1.1 min late
20:00: 87.5% of final predictions within five minutes of the timetable, 1,419 predictions, typically 2.1 min late
21:00: 86.7% of final predictions within five minutes of the timetable, 1,332 predictions, typically 1.9 min late
22:00: 93.5% of final predictions within five minutes of the timetable, 1,379 predictions, typically 1.3 min late
23:00: 92.6% of final predictions within five minutes of the timetable, 756 predictions, typically 0.9 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	16:00	3.4 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	16:00	61%	Operations, not the timetable

Measurements

Predictions later than timetable · 16:00: Measured arrivals 1,435; Hours affected 1; Spread 8.9 min; Median delay 3.4 min; Suggested running time change 3.4 min
One hour has a lower prediction match · 16:00: ᐃᑲᕐᕋᖅ 16:00; ᐱᕕᒃᓴᖓᓂ 60.8%; Measured arrivals 1,435; Shortfall 28.6 pts; Route median on time 89.4%

Open history, reliability and route analysis

Route check

How route 97 has been running

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

Bottom line

Provider predictions were usually close to schedule, but check the problem times below.

87 in 100 eligible predictions were within 5 minutes of the timetable · 47,925 predictions checked

Prediction sample size: Larger sample

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

Updated Nov 4, 2026, 12: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: 39 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,435 predictions over 13 days).

No current official notice matches this route.

Prediction differences by stop

de l'ARÉNA/LOMBARD
59 in 100 eligible predictions differed from the timetable by more than 5 minutes (320 predictions over 24 days).
Open this stop
STATION LORRAIN
44 in 100 eligible predictions differed from the timetable by more than 5 minutes (366 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 9Checks 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 218 checked trips need a closer look2 of 218 trips with enough public-feed evidence had no matching position over 7 days. 33 of 251 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 7.7 min (positive means later; negative means earlier)87 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.

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

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

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

Current published schedule began November 2, 2026

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

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

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

ᓯᕗᓂᐊᓂ

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

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

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

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

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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 37
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 152
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 3
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 05:59–01:03 next day

Operator calendar-date records: 1 added · 0 removed

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

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

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

Still collecting: before has 27,203 arrivals over 13 days; after has 3,168 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: 87.3%
Eligible predictions checked: 47,925
Weekdays with data: 17
95th-percentile predicted delay: 7.7 min late

Patterns by hour (20)

Patterns by hour (20)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
00:00	98.4%	0.2 min late	2.8 min late	687 · 10 days
01:00	100.0%	0.4 min early	3.5 min late	60 · 9 days
06:00	94.2%	0.2 min late	5 min late	565 · 7 days
07:00	90.6%	0.9 min late	6.5 min late	1,067 · 9 days
08:00	94.4%	1.1 min late	4.8 min late	1,149 · 10 days
09:00	97.4%	1.5 min late	4.3 min late	1,404 · 11 days
10:00	90.0%	1.3 min late	6.7 min late	1,463 · 11 days
11:00	91.2%	1 min late	6 min late	1,544 · 12 days
12:00	86.8%	1.4 min late	6.7 min late	1,559 · 12 days
13:00	88.2%	1.4 min late	6.8 min late	1,642 · 12 days
14:00	88.8%	1.4 min late	6.7 min late	1,471 · 13 days
15:00	74.9%	2.6 min late	9.7 min late	1,533 · 12 days
16:00	60.8%	3.4 min late	12.3 min late	1,435 · 13 days
17:00	75.3%	2.8 min late	12.7 min late	1,480 · 12 days
18:00	77.7%	1.5 min late	12.7 min late	1,834 · 11 days
19:00	86.9%	1.1 min late	6.7 min late	1,826 · 11 days
20:00	87.5%	2.1 min late	6.5 min late	1,419 · 10 days
21:00	86.7%	1.9 min late	6.3 min late	1,332 · 10 days
22:00	93.5%	1.3 min late	4.9 min late	1,379 · 10 days
23:00	92.6%	0.9 min late	6.6 min late	756 · 10 days

1 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

216 / 251 scheduled trips published at least one position across 7 service days (86.1%).

06:004 / 10 trips without a position60.0%
21:005 / 14 trips without a position64.3%
22:005 / 14 trips without a position64.3%
00:002 / 7 trips without a position71.4%
07:002 / 7 trips without a position71.4%
19:004 / 14 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 · 37 trips in the retained timetable · retained notices; capture coverage unverified

In short: 29 with a matched position · 2 with no matching position (to investigate) · 6 with an unknown outcome.

05:59– 07:00
Trip sto:63296984Insufficient coverage or identity; outcome unknown
06:40– 07:39
Trip sto:63297001Insufficient coverage or identity; outcome unknown
06:57– 07:58
Trip sto:63296985Insufficient coverage or identity; outcome unknown
07:10– 08:13
Trip sto:63297002Insufficient coverage or identity; outcome unknown
08:08– 09:09
Trip sto:63296986Insufficient coverage or identity; outcome unknown
08:10– 09:07
Trip sto:63297003Insufficient coverage or identity; outcome unknown
09:10– 10:07
Trip sto:63297004Vehicle position matchedFirst / last feed position: 9:22 a.m. EST / 10:03 a.m. EST; not actual start or end times.
09:17– 10:18
Trip sto:63296987Vehicle position matchedFirst / last feed position: 9:22 a.m. EST / 10:15 a.m. EST; not actual start or end times.
10:10– 11:07
Trip sto:63297005Vehicle position matchedFirst / last feed position: 10:04 a.m. EST / 11:07 a.m. EST; not actual start or end times.
10:17– 11:17
Trip sto:63296988Vehicle position matchedFirst / last feed position: 10:04 a.m. EST / 11:18 a.m. EST; not actual start or end times.
11:10– 12:07
Trip sto:63297006Vehicle position matchedFirst / last feed position: 11:05 a.m. EST / 12:06 p.m. EST; not actual start or end times.
11:17– 12:17
Trip sto:63296989Vehicle position matchedFirst / last feed position: 11:20 a.m. EST / 12:18 p.m. EST; not actual start or end times.

· 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).