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

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

ᐊᖁᑦ 58: Carling Campus/Abbott POC ~ Complexe Carling/Abbott POC ⇄ Bayshore / Tunney's Pasture

30 ᐊᒻᒪ 31 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 29, 2026 – Nov 4, 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: 2 trips with qualifying later matching vehicle observations. Trips with any notice: 5.

Trips needing investigation

4 of 443 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.

439 with position · 4 to investigate · 0 excluded · 443 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 5, 2026, 3:02 a.m..

Coverage, exclusions and sources

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

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

Published position coverage: 439 / 443 (99.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 5, 2026, 2:09 a.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

85.9%

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

Predictions in the source: 48,775
Weekdays with evidence: 19
Evidence window: Oct 6, 2026 – Nov 3, 2026

The hours we have evidence for

0697% · 809 predictions · 11 days
0791% · 1,243 predictions · 11 days
0873% · 1,654 predictions · 13 days
0987% · 2,149 predictions · 15 days
1090% · 2,076 predictions · 15 days
1191% · 2,115 predictions · 15 days
1292% · 2,097 predictions · 15 days
1392% · 2,046 predictions · 15 days
1487% · 2,099 predictions · 15 days
1586% · 1,845 predictions · 15 days
1686% · 1,862 predictions · 15 days
1768% · 1,686 predictions · 15 days
1862% · 1,545 predictions · 15 days
1986% · 1,328 predictions · 15 days
2095% · 1,139 predictions · 13 days
2193% · 1,092 predictions · 13 days
22100% · 668 predictions · 13 days
2399% · 469 predictions · 12 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 5, 2026

2 partial-capture days not counted.

What about time of day?

18 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 8, 2026 to November 4, 2026: 25 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 15, 2026.

Values and interpretation

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

0% of pairs (45) 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.)	1,082	0% (0)	0% (0)
Midday (9 a.m. to 3 p.m.)	14,527	0% (14)	0% (11)
Afternoon rush (3 to 6 p.m.)	4,744	0% (0)	0% (11)
Evening (6 to 10 p.m.)	6,189	1% (61)	0% (23)
Night (10 p.m. to 4 a.m.)	796	0% (0)	0% (0)

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

Where this route is slowest

Slowest: LINCOLN FIELDS 4A to BAYSHORE C, 14.1 km/h actual against 15.3 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
LINCOLN FIELDS 4A	BAYSHORE C	3.8 km	15.3 km/h	14.1 km/h	398	2%
BAYSHORE A	LINCOLN FIELDS 3A	3.4 km	13.5 km/h	14.5 km/h	339	1%
BAYSHORE A	LINCOLN FIELDS 2A	3.3 km	16.4 km/h	15.4 km/h	32	0%
ABBOTT POINT OF CARE / MOODIE	DISCOVERY / NETWORK ACCESS	1.7 km	16.9 km/h	16.5 km/h	96	7%
TUNNEY'S PASTURE B	RICHMOND / GOLDEN	2.4 km	16.6 km/h	17.3 km/h	33	3%
LINCOLN FIELDS 3A	RICHMOND / GOLDEN	3.2 km	21.5 km/h	18 km/h	33	3%
BAYSHORE C	DISCOVERY / NETWORK ACCESS	5.8 km	20.1 km/h	19.4 km/h	121	1%
RICHMOND / GOLDEN	LINCOLN FIELDS 4A	3.2 km	31.6 km/h	22 km/h	33	36%

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

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

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

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

ᓄᓇᓕᐅᑉ ᐊᖁᑎᓂ ᓴᓇᓂᖏᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ ᐅᖃᓕᒫᕋᔅᓴᐅᙱᑦᑐᑦ ᒫᓐᓇ.

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 →

2 partial-capture days not counted.

12 scheduled trips with counted cancellation notices from Thu, Oct 8 to Wed, Nov 4.

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

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

Latest cancelled trips

Tue, Nov 3, scheduled 18:19
Fri, Oct 30, scheduled 18:19
Wed, Oct 28, scheduled 20:16
Sat, Oct 24, scheduled 17:49
Sat, Oct 24, scheduled 13:34

OC Transpo gives no reason for single trips, so none is shown.

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

Open the dated prediction analysis

ᐃᓱᓕᑦᑎᓂᖅ

What this route needs

Median provider predictions are 3.8 min later than the timetable in 1 hours of the day.

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

18:00 has 62% of predictions within five minutes of the timetable, against 91% the rest of the day.

Only 99% of scheduled trips were seen; the rest are not counted as missed.

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, 18 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: not enough data
06:00: 96.8% of final predictions within five minutes of the timetable, 809 predictions, typically 1.1 min late
07:00: 91.4% of final predictions within five minutes of the timetable, 1,243 predictions, typically 1.1 min late
08:00: 72.9% of final predictions within five minutes of the timetable, 1,654 predictions, typically 1.9 min late
09:00: 87.1% of final predictions within five minutes of the timetable, 2,149 predictions, typically 0.8 min late
10:00: 90.2% of final predictions within five minutes of the timetable, 2,076 predictions, typically 1.3 min late
11:00: 91.1% of final predictions within five minutes of the timetable, 2,115 predictions, typically 0.8 min late
12:00: 92.3% of final predictions within five minutes of the timetable, 2,097 predictions, typically 0.7 min late
13:00: 91.6% of final predictions within five minutes of the timetable, 2,046 predictions, typically 0.8 min late
14:00: 86.6% of final predictions within five minutes of the timetable, 2,099 predictions, typically 0.3 min late
15:00: 85.7% of final predictions within five minutes of the timetable, 1,845 predictions, typically 0.8 min late
16:00: 86.4% of final predictions within five minutes of the timetable, 1,862 predictions, typically 2 min late
17:00: 68.1% of final predictions within five minutes of the timetable, 1,686 predictions, typically 2.6 min late
18:00: 61.9% of final predictions within five minutes of the timetable, 1,545 predictions, typically 3.8 min late
19:00: 86.4% of final predictions within five minutes of the timetable, 1,328 predictions, typically 1.9 min late
20:00: 94.9% of final predictions within five minutes of the timetable, 1,139 predictions, typically 0.5 min late
21:00: 92.5% of final predictions within five minutes of the timetable, 1,092 predictions, typically 0.7 min late
22:00: 100% of final predictions within five minutes of the timetable, 668 predictions, typically 0.2 min late
23:00: 99.1% of final predictions within five minutes of the timetable, 469 predictions, typically 0.1 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	18:00	3.8 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	18:00	62%	Operations, not the timetable
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 18:00: Measured arrivals 1,545; Hours affected 1; Spread 12.2 min; Median delay 3.8 min; Suggested running time change 3.8 min
One hour has a lower prediction match · 18:00: ᐃᑲᕐᕋᖅ 18:00; ᐱᕕᒃᓴᖓᓂ 61.9%; Measured arrivals 1,545; Shortfall 28.8 pts; Route median on time 90.7%
Coverage gap · All measured hours: ᑐᕌᒐᖅ 99.5%; Trips with a matching position 99.1%; ᐅᓪᓗᑦ ᐸᓯᑦ ᐊᐅᓚᑕᐅᓂᖏᑦ 5; Trips with a matching position 439; ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ 443

Open history, reliability and route analysis

Route check

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

86 in 100 eligible predictions were within 5 minutes of the timetable · 48,775 predictions checked

Prediction sample size: Larger sample

Based on 48,775 eligible provider predictions over 27 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 5, 2026, 2:32 a.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.

18–19: 38 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,545 predictions over 15 days).
17–18: 32 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,686 predictions over 15 days).

No current official notice matches this route.

Prediction differences by stop

We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.

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 3Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 4 of 443 checked trips need a closer look4 of 443 trips with enough public-feed evidence had no matching position over 7 days. 0 of 443 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 8.9 min (positive means later; negative means earlier)86 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: Average predicted extra wait was under 30 seconds at the sampled stop0.1 min less than the scheduled wait, based on 75 eligible predictions at 1 stop hours across 15 service days.

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

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

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

Current published schedule began October 30, 2026

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

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

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

ᓯᕗᓂᐊᓂ

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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 69
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 79
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 8
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 06:09–23:33

Operator calendar-date records: 0 added · 2 removed

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

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

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

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 69
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 79
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 8
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 06:09–23:33

Operator calendar-date records: 0 added · 2 removed

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

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

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

Still collecting: before has 25,900 arrivals over 14 days; after has 10,965 arrivals over 6 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: 85.9%
Eligible predictions checked: 48,775
Weekdays with data: 19
95th-percentile predicted delay: 8.9 min late

Patterns by hour (18)

Patterns by hour (18)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
06:00	96.8%	1.1 min late	4.6 min late	809 · 11 days
07:00	91.4%	1.1 min late	5.6 min late	1,243 · 11 days
08:00	72.9%	1.9 min late	13.7 min late	1,654 · 13 days
09:00	87.1%	0.8 min late	11 min late	2,149 · 15 days
10:00	90.2%	1.3 min late	7 min late	2,076 · 15 days
11:00	91.1%	0.8 min late	5.9 min late	2,115 · 15 days
12:00	92.3%	0.7 min late	6.2 min late	2,097 · 15 days
13:00	91.6%	0.8 min late	5.8 min late	2,046 · 15 days
14:00	86.6%	0.3 min late	14.6 min late	2,099 · 15 days
15:00	85.7%	0.8 min late	6.8 min late	1,845 · 15 days
16:00	86.4%	2 min late	7.6 min late	1,862 · 15 days
17:00	68.1%	2.6 min late	16 min late	1,686 · 15 days
18:00	61.9%	3.8 min late	16 min late	1,545 · 15 days
19:00	86.4%	1.9 min late	7.9 min late	1,328 · 15 days
20:00	94.9%	0.5 min late	5 min late	1,139 · 13 days
21:00	92.5%	0.7 min late	5.7 min late	1,092 · 13 days
22:00	100.0%	0.2 min late	2.2 min late	668 · 13 days
23:00	99.1%	0.1 min late	2.9 min late	469 · 12 days

2 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

439 / 443 scheduled trips published at least one position across 5 service days (99.1%).

18:002 / 28 trips without a position92.9%
06:001 / 15 trips without a position93.3%
17:001 / 28 trips without a position96.4%
07:000 / 20 trips without a position100.0%
08:000 / 28 trips without a position100.0%
09:000 / 27 trips without a position100.0%

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 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

November 4, 2026 · 69 trips in the retained timetable · retained notices; capture coverage unverified

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

06:09– 06:23
Trip 18817040No matching position; investigate, not a confirmed cancellation
06:24– 07:00
Trip 22929040Vehicle position matchedFirst / last feed position: 5:57 a.m. EST / 6:49 a.m. EST; not actual start or end times.
06:46– 07:06
Trip 31904040Vehicle position matchedFirst / last feed position: 6:42 a.m. EST / 7:06 a.m. EST; not actual start or end times.
07:08– 07:54
Trip 6864040Vehicle position matchedFirst / last feed position: 6:34 a.m. EST / 8:06 a.m. EST; not actual start or end times.
07:17– 07:37
Trip 27631040Vehicle position matchedFirst / last feed position: 7:04 a.m. EST / 7:36 a.m. EST; not actual start or end times.
07:39– 08:27
Trip 23957040Vehicle position matchedFirst / last feed position: 7:37 a.m. EST / 8:45 a.m. EST; not actual start or end times.
07:47– 08:07
Trip 30322040Vehicle position matchedFirst / last feed position: 7:35 a.m. EST / 8:06 a.m. EST; not actual start or end times.
08:09– 09:00
Trip 31039040Vehicle position matchedFirst / last feed position: 8:04 a.m. EST / 9:58 a.m. EST; not actual start or end times.
08:17– 08:37
Trip 10570040Vehicle position matchedFirst / last feed position: 8:21 a.m. EST / 8:39 a.m. EST; not actual start or end times.
08:32– 09:18
Trip 28774040Vehicle position matchedFirst / last feed position: 8:46 a.m. EST / 9:30 a.m. EST; not actual start or end times.
08:39– 09:30
Trip 31021040Vehicle position matchedFirst / last feed position: 8:08 a.m. EST / 9:44 a.m. EST; not actual start or end times.
08:47– 09:05
Trip 30943040Vehicle position matchedFirst / last feed position: 8:43 a.m. EST / 9:00 a.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).