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

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

STO ᐊᖁᑎᖓ 76: La Vérendrye

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

QUAI LOCAL de la CITÉ #829 min sched.
de la GAPPE/de ROUVILLE1 min sched.
de l'HÔPITAL/de ROUVILLE2 min sched.
de l'HÔPITAL/de la CITÉ-JARDIN2 min sched.
de la FUTAIE3 min sched.
de l'HÔPITAL/SAINT-RENÉ OUEST3 min sched.
HÔPITAL DE GATINEAU4 min sched.
de l'OASIS/du DÉSERT5 min sched.
de la CITÉ/la VÉRENDRYE OUEST6 min sched.
la VÉRENDRYE OUEST/de la CITÉ6 min sched.
la VÉRENDRYE OUEST/MONTÉE PAIEMENT7 min sched.
la VÉRENDRYE OUEST/GÉNÉREUX7 min sched.
la VÉRENDRYE OUEST/LAFRANCE8 min sched.
la VÉRENDRYE OUEST/GUINDON8 min sched.
la VÉRENDRYE OUEST/PAQUETTE10 min sched.
la VÉRENDRYE EST/MAIN10 min sched.
la VÉRENDRYE EST/R.H-LALONDE11 min sched.
la VÉRENDRYE EST/MAIN11 min sched.
la VÉRENDRYE EST/LABROSSE11 min sched.
LABROSSE/de CANDIAC12 min sched.
LABROSSE/MARQUETTE14 min sched.
LABROSSE/SAINT-RENÉ EST14 min sched.
Terminus Labrosse15 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 341 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.

335 with position · 6 to investigate · 73 excluded · 414 scheduled trips

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

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

Published position coverage: 335 / 414 (80.9%). 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

89.2%

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

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

The hours we have evidence for

0599% · 130 predictions · 7 days
0695% · 567 predictions · 7 days
0792% · 643 predictions · 9 days
0892% · 696 predictions · 10 days
0990% · 855 predictions · 11 days
1092% · 704 predictions · 11 days
1191% · 736 predictions · 12 days
1294% · 801 predictions · 12 days
1388% · 849 predictions · 12 days
1489% · 773 predictions · 13 days
1577% · 814 predictions · 12 days
1667% · 845 predictions · 13 days
1787% · 864 predictions · 12 days
1889% · 673 predictions · 11 days
1996% · 511 predictions · 10 days
2096% · 445 predictions · 10 days
2194% · 403 predictions · 10 days
2296% · 443 predictions · 10 days
2399% · 161 predictions · 8 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?

19 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: 38 of 12,244 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (39) 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,955	0% (4)	0% (3)
Midday (9 a.m. to 3 p.m.)	5,553	0% (17)	0% (11)
Afternoon rush (3 to 6 p.m.)	2,678	1% (17)	1% (25)
Evening (6 to 10 p.m.)	1,058	0% (0)	0% (0)

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

Where this route is slowest

Slowest: QUAI LOCAL de la CITÉ #8 to HÔPITAL DE GATINEAU, 6.7 km/h actual against 17.2 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
QUAI LOCAL de la CITÉ #8	HÔPITAL DE GATINEAU	1.4 km	17.2 km/h	6.7 km/h	466	80%
Quai local LABROSSE #5	la VÉRENDRYE EST/MAIN	1.7 km	19.2 km/h	7.5 km/h	388	76%
HÔPITAL DE GATINEAU	la VÉRENDRYE OUEST/de la CITÉ	690 m	15.1 km/h	15.9 km/h	528	5%
HÔPITAL DE GATINEAU	QUAI LOCAL de la CITÉ arrivée	1.5 km	18.9 km/h	18.1 km/h	415	3%
de l'OASIS/de la CITÉ	HÔPITAL DE GATINEAU	590 m	17 km/h	20.2 km/h	443	3%
la VÉRENDRYE EST/MAIN	Terminus Labrosse	1.3 km	21.6 km/h	22.3 km/h	490	2%
la VÉRENDRYE EST/MAIN	de l'OASIS/de la CITÉ	2.8 km	28.7 km/h	28.6 km/h	439	3%
la VÉRENDRYE OUEST/de la CITÉ	la VÉRENDRYE EST/MAIN	3 km	32.7 km/h	31.1 km/h	518	3%

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: 0 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.

Hours with the most cancellations: 10 a.m. (1)

Latest cancelled trips

Tue, Nov 3, scheduled 10:18

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 341 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 36 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats1.1% of 464 trips	Usually seats0% of 37 trips	Usually seats0% of 31 trips
9 am to 3 pm	Usually seats1.8% of 795 trips	Usually seats0% of 96 trips	Usually seats0% of 88 trips
3 to 6 pm	Usually seats4.7% of 553 trips	Usually seats0% of 46 trips	Usually seats0% of 49 trips
6 to 10 pm	Usually seats0% of 342 trips	Usually seats0% of 62 trips	Usually seats0% of 54 trips
After 10 pm	Usually seats0% of 112 trips	Usually seats0% of 15 trips	Not enough readings

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

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

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

00:00: not enough data
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 99.2% of final predictions within five minutes of the timetable, 130 predictions, typically 0.3 min late
06:00: 94.7% of final predictions within five minutes of the timetable, 567 predictions, typically 1 min late
07:00: 91.9% of final predictions within five minutes of the timetable, 643 predictions, typically 1.6 min late
08:00: 91.5% of final predictions within five minutes of the timetable, 696 predictions, typically 1.2 min late
09:00: 89.8% of final predictions within five minutes of the timetable, 855 predictions, typically 1.4 min late
10:00: 92.3% of final predictions within five minutes of the timetable, 704 predictions, typically 1.8 min late
11:00: 91.3% of final predictions within five minutes of the timetable, 736 predictions, typically 1.4 min late
12:00: 93.8% of final predictions within five minutes of the timetable, 801 predictions, typically 0.9 min late
13:00: 88.2% of final predictions within five minutes of the timetable, 849 predictions, typically 1.9 min late
14:00: 89.3% of final predictions within five minutes of the timetable, 773 predictions, typically 1.8 min late
15:00: 76.5% of final predictions within five minutes of the timetable, 814 predictions, typically 2.2 min late
16:00: 66.9% of final predictions within five minutes of the timetable, 845 predictions, typically 2.9 min late
17:00: 86.7% of final predictions within five minutes of the timetable, 864 predictions, typically 2.3 min late
18:00: 88.9% of final predictions within five minutes of the timetable, 673 predictions, typically 1.3 min late
19:00: 95.7% of final predictions within five minutes of the timetable, 511 predictions, typically 1 min late
20:00: 96.4% of final predictions within five minutes of the timetable, 445 predictions, typically 0.9 min late
21:00: 94.3% of final predictions within five minutes of the timetable, 403 predictions, typically 0.7 min late
22:00: 96.4% of final predictions within five minutes of the timetable, 443 predictions, typically 0.5 min late
23:00: 99.4% of final predictions within five minutes of the timetable, 161 predictions, typically 0.6 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
ProblemOne hour has a lower prediction match	16:00	67%	Operations, not the timetable

Measurements

One hour has a lower prediction match · 16:00: ᐃᑲᕐᕋᖅ 16:00; ᐱᕕᒃᓴᖓᓂ 66.9%; Measured arrivals 845; Shortfall 25 pts; Route median on time 91.9%

Open history, reliability and route analysis

Route check

How route 76 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.

89 in 100 eligible predictions were within 5 minutes of the timetable · 23,476 predictions checked

Prediction sample size: Larger sample

Based on 23,476 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: 33 in 100 eligible predictions differed from the timetable by more than 5 minutes (845 predictions over 13 days).

No current official notice matches this route.

Prediction differences by stop

Quai local LABROSSE #5
59 in 100 eligible predictions differed from the timetable by more than 5 minutes (505 predictions over 24 days).
Open this stop
QUAI LOCAL de la CITÉ #8
54 in 100 eligible predictions differed from the timetable by more than 5 minutes (602 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 341 checked trips need a closer look6 of 341 trips with enough public-feed evidence had no matching position over 7 days. 73 of 414 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.9 min (positive means later; negative means earlier)89 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

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

Operator calendar-date records: 1 added · 0 removed

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

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

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

Still collecting: before has 12,777 arrivals over 13 days; after has 1,726 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: 89.2%
Eligible predictions checked: 23,476
Weekdays with data: 17
95th-percentile predicted delay: 5.9 min late

Patterns by hour (19)

Patterns by hour (19)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
05:00	99.2%	0.3 min late	2.4 min late	130 · 7 days
06:00	94.7%	1 min late	3.2 min late	567 · 7 days
07:00	91.9%	1.6 min late	5.5 min late	643 · 9 days
08:00	91.5%	1.2 min late	5.7 min late	696 · 10 days
09:00	89.8%	1.4 min late	5.4 min late	855 · 11 days
10:00	92.3%	1.8 min late	5.4 min late	704 · 11 days
11:00	91.3%	1.4 min late	5.2 min late	736 · 12 days
12:00	93.8%	0.9 min late	4.7 min late	801 · 12 days
13:00	88.2%	1.9 min late	5.5 min late	849 · 12 days
14:00	89.3%	1.8 min late	5.7 min late	773 · 13 days
15:00	76.5%	2.2 min late	7.7 min late	814 · 12 days
16:00	66.9%	2.9 min late	12.3 min late	845 · 13 days
17:00	86.7%	2.3 min late	6 min late	864 · 12 days
18:00	88.9%	1.3 min late	6 min late	673 · 11 days
19:00	95.7%	1 min late	4.3 min late	511 · 10 days
20:00	96.4%	0.9 min late	3.3 min late	445 · 10 days
21:00	94.3%	0.7 min late	3.1 min late	403 · 10 days
22:00	96.4%	0.5 min late	2.4 min late	443 · 10 days
23:00	99.4%	0.6 min late	2.5 min late	161 · 8 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

335 / 414 scheduled trips published at least one position across 5 service days (80.9%).

06:0012 / 30 trips without a position60.0%
07:0013 / 34 trips without a position61.8%
21:005 / 14 trips without a position64.3%
08:0010 / 29 trips without a position65.5%
19:006 / 19 trips without a position68.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 · 70 trips in the retained timetable · retained notices; capture coverage unverified

In short: 47 with a matched position · 3 with no matching position (to investigate) · 20 with an unknown outcome.

05:38– 05:56
Trip sto:63296800Insufficient coverage or identity; outcome unknown
06:08– 06:26
Trip sto:63296793Insufficient coverage or identity; outcome unknown
06:20– 06:37
Trip sto:63296765Insufficient coverage or identity; outcome unknown
06:30– 06:48
Trip sto:63296801Insufficient coverage or identity; outcome unknown
06:38– 06:55
Trip sto:63296769Insufficient coverage or identity; outcome unknown
06:48– 07:06
Trip sto:63296794Insufficient coverage or identity; outcome unknown
06:57– 07:14
Trip sto:63296766Insufficient coverage or identity; outcome unknown
07:07– 07:25
Trip sto:63296796Insufficient coverage or identity; outcome unknown
07:16– 07:37
Trip sto:63296767Insufficient coverage or identity; outcome unknown
07:31– 07:49
Trip sto:63296802Insufficient coverage or identity; outcome unknown
07:32– 07:53
Trip sto:63296768Insufficient coverage or identity; outcome unknown
07:53– 08:14
Trip sto:63296770Insufficient 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).