Detour Route 75 South: Route 75 diverted from Dupuis to Chamberland.+2 more notice

No 75 trips cancelled now · 5 did not run in NovemberCancellations →

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

STO ᐊᖁᑎᖓ 75: Notre-Dame

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

QUAI LOCAL de la CITÉ #98 min sched.
MALONEY OUEST/de la CITÉ10 min sched.
MALONEY OUEST/MONTÉE PAIEMENT11 min sched.
MALONEY OUEST/MONTÉE PAIEMENT11 min sched.
MALONEY OUEST/ANDRÉ-MÉNARD13 min sched.
MALONEY OUEST/SAINT-LOUIS14 min sched.
MALONEY OUEST/OAK17 min sched.
MALONEY EST/MAIN17 min sched.
NOTRE-DAME/JEAN-RENÉ-MONETTE18 min sched.
NOTRE-DAME/FERNAND-ARVISAIS19 min sched.
NOTRE-DAME/SAINT-ANDRÉ19 min sched.
NOTRE-DAME/LABROSSE20 min sched.
NOTRE-DAME/PLOUFFE21 min sched.
NOTRE-DAME/de CÔTÉVILLE22 min sched.
NOTRE-DAME/de VERSAILLES23 min sched.
NOTRE-DAME/MONSEIGNEUR-LEMIEUX24 min sched.
NOTRE-DAME/du LAC24 min sched.
NOTRE-DAME/LUCIENNE-BOURGEOIS25 min sched.
NOTRE-DAME/de CHAMBERLAND25 min sched.
NOTRE-DAME/DORÉ26 min sched.
MALONEY EST/DORÉ27 min sched.
MALONEY EST/DUPUIS27 min sched.
MALONEY EST/LORRAIN28 min sched.
MALONEY EST/MITCHELL28 min sched.
MALONEY EST/JOSEPH-ROY29 min sched.
MALONEY EST/JOSEPH-ROY30 min sched.
des SABLES/BEL-AIR30 min sched.
des SABLES/du SAGUENAY31 min sched.
SAINTE-ROSE/ROBERT-CORBETT32 min sched.
SAINTE-ROSE/JEAN-LÉPINE0 min sched.
SAINTE-ROSE/MITCHELL0 min sched.
LORRAIN/SAINTE-ROSE1 min sched.
STATION LORRAIN arrêt d'arrivée2 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: 1.

Trips needing investigation

6 of 338 trips with a usable feed window (1.8%) had no matching position.

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

332 with position · 6 to investigate · 54 excluded · 392 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 2:35 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.

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

Published position coverage: 332 / 392 (84.7%). 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:49 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

92.8%

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

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

The hours we have evidence for

0098% · 274 predictions · 10 days
0596% · 183 predictions · 7 days
0696% · 765 predictions · 10 days
0789% · 805 predictions · 9 days
0886% · 843 predictions · 10 days
0994% · 1,014 predictions · 11 days
1097% · 985 predictions · 11 days
1195% · 1,146 predictions · 12 days
1294% · 1,210 predictions · 12 days
1395% · 1,176 predictions · 12 days
1496% · 1,092 predictions · 13 days
1589% · 1,238 predictions · 12 days
1685% · 938 predictions · 13 days
1781% · 1,194 predictions · 12 days
1890% · 827 predictions · 11 days
1995% · 764 predictions · 10 days
2097% · 567 predictions · 10 days
2195% · 548 predictions · 10 days
2298% · 582 predictions · 10 days
2397% · 544 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

0% of back-to-back buses on this route arrived bunched together: 17 of 13,697 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (41) 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.)	2,731	0% (5)	0% (1)
Midday (9 a.m. to 3 p.m.)	7,164	0% (5)	0% (8)
Afternoon rush (3 to 6 p.m.)	3,179	0% (7)	1% (20)
Evening (6 to 10 p.m.)	623	0% (0)	2% (12)

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

Where this route is slowest

Slowest: STATION LORRAIN to SAINTE-ROSE/ROBERT-CORBETT, 7.9 km/h actual against 17.8 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
STATION LORRAIN	SAINTE-ROSE/ROBERT-CORBETT	1.1 km	17.8 km/h	7.9 km/h	436	75%
QUAI LOCAL de la CITÉ #9	NOTRE-DAME/JEAN-RENÉ-MONETTE	2.8 km	21.1 km/h	12.5 km/h	399	55%
NOTRE-DAME/de VERSAILLES	MALONEY EST/BROADWAY	1.9 km	19.2 km/h	19.3 km/h	454	0%
MALONEY EST/LORRAIN	SAINTE-ROSE/ROBERT-CORBETT	1.4 km	21.9 km/h	20 km/h	437	8%
SAINTE-ROSE/ROBERT-CORBETT	Stop name not found	1.3 km	20.6 km/h	21.8 km/h	285	1%
SAINTE-ROSE/ROBERT-CORBETT	STATION LORRAIN arrêt d'arrivée	1.1 km	21.5 km/h	22 km/h	426	1%
NOTRE-DAME/JEAN-RENÉ-MONETTE	NOTRE-DAME/de VERSAILLES	1.8 km	23.1 km/h	23.2 km/h	448	1%
SAINTE-ROSE/ROBERT-CORBETT	NOTRE-DAME/de VERSAILLES	3.5 km	23.1 km/h	23.7 km/h	172	1%

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.

1 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 0 for trips not in that day’s timetable.

Hours with the most cancellations: 5 p.m. (1)

Latest cancelled trips

Thu, Oct 29, scheduled 17:55

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: 5 of 338 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 45 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats4.3% of 439 trips	Usually seats0% of 45 trips	Usually seats0% of 41 trips
9 am to 3 pm	Usually seats0.2% of 825 trips	Usually seats2.1% of 97 trips	Usually seats0% of 93 trips
3 to 6 pm	Usually seats5.3% of 471 trips	Usually seats2% of 50 trips	Usually seats0% of 54 trips
6 to 10 pm	Usually seats0.3% of 329 trips	Usually seats0% of 66 trips	Usually seats0% of 61 trips
After 10 pm	Usually seats0% of 175 trips	Usually seats0% of 34 trips	Usually seats0% of 30 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

95% of predictions are within five minutes of the timetable in a typical sampled hour; the lowest sampled hour is 81%.

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

00:00: 97.8% of final predictions within five minutes of the timetable, 274 predictions, typically 1 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 96.2% of final predictions within five minutes of the timetable, 183 predictions, typically 0.2 min early
06:00: 96.2% of final predictions within five minutes of the timetable, 765 predictions, typically 0.2 min early
07:00: 89.3% of final predictions within five minutes of the timetable, 805 predictions, typically 0.7 min late
08:00: 85.6% of final predictions within five minutes of the timetable, 843 predictions, typically 0.8 min late
09:00: 93.8% of final predictions within five minutes of the timetable, 1,014 predictions, typically 0.4 min late
10:00: 97.3% of final predictions within five minutes of the timetable, 985 predictions, typically 0.3 min late
11:00: 94.9% of final predictions within five minutes of the timetable, 1,146 predictions, typically 0.4 min late
12:00: 93.9% of final predictions within five minutes of the timetable, 1,210 predictions, typically 0.9 min late
13:00: 94.7% of final predictions within five minutes of the timetable, 1,176 predictions, typically 0.9 min late
14:00: 96.2% of final predictions within five minutes of the timetable, 1,092 predictions, typically 0.9 min late
15:00: 89.1% of final predictions within five minutes of the timetable, 1,238 predictions, typically 0.8 min late
16:00: 85.2% of final predictions within five minutes of the timetable, 938 predictions, typically 1.3 min late
17:00: 81.1% of final predictions within five minutes of the timetable, 1,194 predictions, typically 0.9 min late
18:00: 89.5% of final predictions within five minutes of the timetable, 827 predictions, typically 1.4 min late
19:00: 94.9% of final predictions within five minutes of the timetable, 764 predictions, typically 1.2 min late
20:00: 96.8% of final predictions within five minutes of the timetable, 567 predictions, typically 1.3 min late
21:00: 94.9% of final predictions within five minutes of the timetable, 548 predictions, typically 1.5 min late
22:00: 98.1% of final predictions within five minutes of the timetable, 582 predictions, typically 1.2 min late
23:00: 97.4% of final predictions within five minutes of the timetable, 544 predictions, typically 0.8 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
StrengthPredictions consistently close to timetable	00:00, 05:00, 06:00, 07:00, 08:00, 09:00, 10:00, 11:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00, 20:00, 21:00, 22:00, 23:00	95%	Keep what works

Measurements

Predictions consistently close to timetable · 00:00, 05:00, 06:00, 07:00, 08:00, 09:00, 10:00, 11:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00, 20:00, 21:00, 22:00, 23:00: Measured arrivals 16,695; Hours measured 20; Worst hour on time 81.1%; Median hour on time 94.9%

Open history, reliability and route analysis

Route check

How route 75 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 in this dated sample.

93 in 100 eligible predictions were within 5 minutes of the timetable · 32,392 predictions checked

Prediction sample size: Larger sample

Based on 32,392 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.

No repeated prediction-difference period has cleared the evidence threshold yet.

2 current notices affect this route

• Detour Route 75 South
• Detour Route 75 North

Prediction differences by stop

STATION LORRAIN
42 in 100 eligible predictions differed from the timetable by more than 5 minutes (530 predictions over 24 days).
Open this stop
QUAI LOCAL de la CITÉ #9
41 in 100 eligible predictions differed from the timetable by more than 5 minutes (508 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?: 6 of 338 checked trips need a closer look6 of 338 trips with enough public-feed evidence had no matching position over 7 days. 54 of 392 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 5.5 min (positive means later; negative means earlier)93 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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 64
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 63
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 2
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 05:36–00:23 next day

Operator calendar-date records: 1 added · 0 removed

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

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

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

Still collecting: before has 17,675 arrivals over 13 days; after has 2,438 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: 92.8%
Eligible predictions checked: 32,392
Weekdays with data: 17
95th-percentile predicted delay: 5.5 min late

Patterns by hour (20)

Patterns by hour (20)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
00:00	97.8%	1 min late	3.6 min late	274 · 10 days
05:00	96.2%	0.2 min early	4.8 min late	183 · 7 days
06:00	96.2%	0.2 min early	2.1 min late	765 · 10 days
07:00	89.3%	0.7 min late	6.3 min late	805 · 9 days
08:00	85.6%	0.8 min late	8.5 min late	843 · 10 days
09:00	93.8%	0.4 min late	4.8 min late	1,014 · 11 days
10:00	97.3%	0.3 min late	2.8 min late	985 · 11 days
11:00	94.9%	0.4 min late	4.7 min late	1,146 · 12 days
12:00	93.9%	0.9 min late	5 min late	1,210 · 12 days
13:00	94.7%	0.9 min late	4.9 min late	1,176 · 12 days
14:00	96.2%	0.9 min late	4.4 min late	1,092 · 13 days
15:00	89.1%	0.8 min late	5.8 min late	1,238 · 12 days
16:00	85.2%	1.3 min late	9 min late	938 · 13 days
17:00	81.1%	0.9 min late	9.9 min late	1,194 · 12 days
18:00	89.5%	1.4 min late	6.8 min late	827 · 11 days
19:00	94.9%	1.2 min late	4.3 min late	764 · 10 days
20:00	96.8%	1.3 min late	4.3 min late	567 · 10 days
21:00	94.9%	1.5 min late	4.1 min late	548 · 10 days
22:00	98.1%	1.2 min late	3.8 min late	582 · 10 days
23:00	97.4%	0.8 min late	3.2 min late	544 · 10 days

No repeated pattern below 70% is yet established across at least three service days.

Scheduled bus, but not observed in realtime

332 / 392 scheduled trips published at least one position across 7 service days (84.7%).

07:009 / 24 trips without a position62.5%
06:008 / 27 trips without a position70.4%
08:007 / 24 trips without a position70.8%
00:002 / 7 trips without a position71.4%
19:004 / 14 trips without a position71.4%
20: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 · 64 trips in the retained timetable · retained notices; capture coverage unverified

In short: 46 with a matched position · 4 with no matching position (to investigate) · 14 with an unknown outcome.

05:36– 06:02
Trip sto:63296721Insufficient coverage or identity; outcome unknown
06:06– 06:32
Trip sto:63296672Insufficient coverage or identity; outcome unknown
06:15– 06:39
Trip sto:63296710Insufficient coverage or identity; outcome unknown
06:26– 06:52
Trip sto:63296668Insufficient coverage or identity; outcome unknown
06:39– 07:07
Trip sto:63296670Insufficient coverage or identity; outcome unknown
06:55– 07:23
Trip sto:63296715Insufficient coverage or identity; outcome unknown
07:10– 07:38
Trip sto:63296671Insufficient coverage or identity; outcome unknown
07:15– 07:39
Trip sto:63296676Insufficient coverage or identity; outcome unknown
07:26– 07:54
Trip sto:63296662Insufficient coverage or identity; outcome unknown
07:43– 08:11
Trip sto:63296706Insufficient coverage or identity; outcome unknown
08:00– 08:24
Trip sto:63296734Insufficient coverage or identity; outcome unknown
08:05– 08:33
Trip sto:63296731Insufficient 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).