Detour: Routes 57, 61, 62, 63, 74, 75, 87 during nightly Kichi Zībī Mīkan closures: May 07 2026 - Until further notice, routes 57, 61, 62, 63, 74, 75, and 87 will detour on weeknights and weekends between 11:30 pm and 6 am in both directions around the Kichi Zībī Mīkan parkway, between Lincoln Fields station and Churchill Avenue. Please allow extra time for your travels. Affected stops Bus Stop (560#) not in use · Routes · Alternate Stop #3013 -- Dominion 2A · · 57 Tunney's Pasture · 61 Tunney's Pasture · 62 Tunney's Pasture · 63 Tunney's Pasture · 74 Tunney's Pasture · 75 Tunney's Pasture & N Rideau · 87 Tunney's Pasture · #4941 -- Richmond (south side) / Golden #3013 -- Dominion 1A · · 57 Crystal Bay · 61 Stittsville · 62 Stittsville · 63 Innovation · 74 Nepean Woods · 75 Barrhaven · #4922 -- Richmond (north side) / Golden #3014 -- Lincoln Fields 1A · · 61 Stittsville · 62 Stittsville · 63 Innovation · 74 Nepean Woods · 75 Barrhaven · 87 Baseline · #3014 -- Lincoln Fields 3B OR #3014 -- Lincoln Fields 5A #4944 -- Woodroffe (west side) / Saunders* · · 87 Baseline · #6244 -- Woodroffe (west side) / Knightsbridge #1832 -- Woodroffe (west side) / Richmond* · · 87 Baseline · #6244 -- Woodroffe (west side) / Knightsbridge #4942 -- Woodroffe (east side) / Saunders* · · 87 Tunney's Pasture · #6472 -- Woodroffe (east side) / Knightsbridge #2783 -- Woodroffe (east side) / Richmond* · · 87 Tunney's Pasture · #6472 -- Woodroffe (east side) / Knightsbridge *These stops are already not in use due to the closure of Woodroffe Avenue (Byron/Richmond to Kichi Zībī Mīkan) Detour routing 57 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 57 Bayshore: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe, right onto Carling, left onto J-Ramp, continue regular routing. 61 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 61 Stittsville / Terry Fox: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 62 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 62 Stittsville: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 63 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 63 Innovation/ Briarbrook: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 74 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 74 Limebank: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 75 Tunney's Pasture & N Rideau: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 75 Barrhaven Centre / Cambrian: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 87 Baseline: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe, right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 87 Tunney's Pasture: From Woodroffe and Byron, turn right onto Byron, continue on Richmond, left onto Churchill, right onto Scott to regular route. Detour Map

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

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

ᐊᖁᑦ 75: Tunney's Pasture & N Rideau ⇄ Barrhaven Centre / Cambrian

5 ᐊᒻᒪ 16 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ

ᑐᕌᖓᔪᖅTunney's Pasture2 buses · boards at · under each stop: the next bus (live dot = live, grey = 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: 20 trips with qualifying later matching vehicle observations. Trips with any notice: 24.

Trips needing investigation

5 of 1,275 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.

1,270 with position · 5 to investigate · 8 excluded · 1,283 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 1,270 / 1,283 (99%). 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, 1:08 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

88.1%

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

Predictions in the source: 147,463
Weekdays with evidence: 19
Evidence window: Oct 5, 2026 – Nov 2, 2026

The hours we have evidence for

0096% · 1,147 predictions · 14 days
0192% · 1,715 predictions · 14 days
0282% · 1,725 predictions · 14 days
0390% · 1,866 predictions · 15 days
0494% · 2,033 predictions · 15 days
0596% · 1,960 predictions · 15 days
0694% · 3,247 predictions · 15 days
0790% · 4,587 predictions · 14 days
0878% · 4,261 predictions · 14 days
0987% · 3,807 predictions · 14 days
1087% · 4,165 predictions · 14 days
1193% · 4,140 predictions · 14 days
1295% · 4,094 predictions · 14 days
1387% · 3,369 predictions · 14 days
1492% · 3,406 predictions · 14 days
1582% · 4,464 predictions · 14 days
1680% · 5,184 predictions · 14 days
1785% · 4,769 predictions · 14 days
1882% · 4,547 predictions · 14 days
1987% · 3,403 predictions · 14 days
2087% · 2,999 predictions · 14 days
2193% · 3,049 predictions · 14 days
2287% · 2,688 predictions · 14 days
2391% · 1,846 predictions · 14 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

2 partial-capture days not counted.

What about time of day?

24 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: 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

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

2% of pairs (2,140) 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.)	3,889	0% (0)	0% (9)
Morning rush (6 to 9 a.m.)	17,250	5% (882)	5% (789)
Midday (9 a.m. to 3 p.m.)	38,806	1% (449)	0% (192)
Afternoon rush (3 to 6 p.m.)	22,740	6% (1,286)	3% (682)
Evening (6 to 10 p.m.)	22,014	2% (512)	2% (431)
Night (10 p.m. to 4 a.m.)	14,091	0% (34)	0% (37)

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

Where this route is slowest

Slowest: BASELINE 2B to QUEENSWAY 2A, 12.5 km/h actual against 14.1 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
BASELINE 2B	QUEENSWAY 2A	1.5 km	14.1 km/h	12.5 km/h	2,136	7%
RIDEAU A	PARLIAMENT B	940 m	13.2 km/h	13.7 km/h	217	3%
QUEENSWAY 1A	BASELINE 1D	1.6 km	14.3 km/h	14.3 km/h	2,201	1%
PARLIAMENT B	LYON A	490 m	11.7 km/h	14.8 km/h	223	1%
BARRHAVEN CENTRE B	MARKETPLACE B	310 m	11.2 km/h	14.9 km/h	1,982	7%
LYON B	PARLIAMENT A	540 m	11.3 km/h	16.3 km/h	240	0%
RICHMOND / GOLDEN	WESTBORO B	750 m	11.9 km/h	16.5 km/h	534	4%
TUNNEY'S PASTURE C	PIMISI D	2.1 km	24.4 km/h	17.4 km/h	240	44%

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.

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

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

Hours with the most cancellations: 7 a.m. (13), 4 p.m. (5), 8 a.m. (3)

Latest cancelled trips

Mon, Nov 2, scheduled 07:51
Sat, Oct 31, scheduled 24:05
Fri, Oct 30, scheduled 22:52
Fri, Oct 30, scheduled 03:28
Tue, Oct 27, scheduled 05:40

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

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

Open the dated prediction analysis

ᐃᓱᓕᑦᑎᓂᖅ

What this route needs

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

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

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

00:00: 95.5% of final predictions within five minutes of the timetable, 1,147 predictions, typically 0.2 min late
01:00: 91.7% of final predictions within five minutes of the timetable, 1,715 predictions, typically 0.9 min late
02:00: 81.5% of final predictions within five minutes of the timetable, 1,725 predictions, typically 0.7 min late
03:00: 90.2% of final predictions within five minutes of the timetable, 1,866 predictions, typically 0.4 min late
04:00: 94.3% of final predictions within five minutes of the timetable, 2,033 predictions, typically 0.3 min late
05:00: 95.8% of final predictions within five minutes of the timetable, 1,960 predictions, typically 0.1 min early
06:00: 94.2% of final predictions within five minutes of the timetable, 3,247 predictions, typically 0 min late
07:00: 90.2% of final predictions within five minutes of the timetable, 4,587 predictions, typically 0.2 min late
08:00: 77.7% of final predictions within five minutes of the timetable, 4,261 predictions, typically 1.1 min late
09:00: 87.2% of final predictions within five minutes of the timetable, 3,807 predictions, typically 0.4 min late
10:00: 86.9% of final predictions within five minutes of the timetable, 4,165 predictions, typically 0 min late
11:00: 92.6% of final predictions within five minutes of the timetable, 4,140 predictions, typically 0.2 min late
12:00: 95.1% of final predictions within five minutes of the timetable, 4,094 predictions, typically 0.3 min late
13:00: 86.7% of final predictions within five minutes of the timetable, 3,369 predictions, typically 1 min late
14:00: 92% of final predictions within five minutes of the timetable, 3,406 predictions, typically 0.9 min late
15:00: 82.2% of final predictions within five minutes of the timetable, 4,464 predictions, typically 1.5 min late
16:00: 79.7% of final predictions within five minutes of the timetable, 5,184 predictions, typically 1.6 min late
17:00: 84.5% of final predictions within five minutes of the timetable, 4,769 predictions, typically 1.5 min late
18:00: 82.2% of final predictions within five minutes of the timetable, 4,547 predictions, typically 1 min late
19:00: 87.1% of final predictions within five minutes of the timetable, 3,403 predictions, typically 0.8 min late
20:00: 87.4% of final predictions within five minutes of the timetable, 2,999 predictions, typically 1 min late
21:00: 92.9% of final predictions within five minutes of the timetable, 3,049 predictions, typically 0.6 min late
22:00: 86.8% of final predictions within five minutes of the timetable, 2,688 predictions, typically 0.6 min late
23:00: 91.2% of final predictions within five minutes of the timetable, 1,846 predictions, typically 0.2 min early

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
ProblemPredicted spacing varies	All measured hours	1.2 min extra wait	Manage the headway
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predicted spacing varies · All measured hours: ᓄᖃᕐᕕᐃᑦ 82; Extra wait share 26.2%; Matched arrivals 15,543; ᐅᑕᖅᑭᓂᖅ ᐃᓚᔭᐅᔪᖅ 1.2 min; Scheduled wait 4.8 min
Coverage gap · All measured hours: ᑐᕌᒐᖅ 99.5%; Trips with a matching position 99.2%; ᐅᓪᓗᑦ ᐸᓯᑦ ᐊᐅᓚᑕᐅᓂᖏᑦ 7; Trips with a matching position 1,273; ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ 1,283

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.

88 in 100 eligible predictions were within 5 minutes of the timetable · 147,463 predictions checked

Prediction sample size: Larger sample

Based on 147,463 eligible provider predictions over 27 measured days, from Oct 5, 2026 to Nov 2, 2026.

Updated Nov 4, 2026, 1:43 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.

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

1 current notice affects this route

• Detour: Routes 57, 61, 62, 63, 74, 75, 87 during nightly Kichi Zībī Mīkan closures

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 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?: 5 of 1,275 checked trips need a closer look5 of 1,275 trips with enough public-feed evidence had no matching position over 7 days. 8 of 1,283 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.6 min (positive means later; negative means earlier)88 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: 6.0 min average predicted wait1.2 min beyond the scheduled wait, based on 15,543 eligible predictions at 82 high-frequency stops over 17 days.

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

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

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

Current published schedule began October 30, 2026

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

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

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

ᓯᕗᓂᐊᓂ

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

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

Operator calendar-date records: 0 added · 2 removed

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

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

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

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

Operator calendar-date records: 0 added · 2 removed

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

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

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

Still collecting: before has 77,515 arrivals over 14 days; after has 27,125 arrivals over 5 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 5, 2026 to November 2, 2026

Within 5 minutes of schedule: 88.1%
Eligible predictions checked: 147,463
Weekdays with data: 19
95th-percentile predicted delay: 7.6 min late

Patterns by hour (24)

Patterns by hour (24)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
00:00	95.5%	0.2 min late	4.3 min late	1,147 · 14 days
01:00	91.7%	0.9 min late	5.6 min late	1,715 · 14 days
02:00	81.5%	0.7 min late	7.3 min late	1,725 · 14 days
03:00	90.2%	0.4 min late	5.8 min late	1,866 · 15 days
04:00	94.3%	0.3 min late	4.9 min late	2,033 · 15 days
05:00	95.8%	0.1 min early	4.7 min late	1,960 · 15 days
06:00	94.2%	0 min late	5.3 min late	3,247 · 15 days
07:00	90.2%	0.2 min late	7.1 min late	4,587 · 14 days
08:00	77.7%	1.1 min late	19.8 min late	4,261 · 14 days
09:00	87.2%	0.4 min late	10 min late	3,807 · 14 days
10:00	86.9%	0 min late	6.6 min late	4,165 · 14 days
11:00	92.6%	0.2 min late	5.4 min late	4,140 · 14 days
12:00	95.1%	0.3 min late	4.6 min late	4,094 · 14 days
13:00	86.7%	1 min late	7.8 min late	3,369 · 14 days
14:00	92.0%	0.9 min late	6.4 min late	3,406 · 14 days
15:00	82.2%	1.5 min late	9.5 min late	4,464 · 14 days
16:00	79.7%	1.6 min late	9.7 min late	5,184 · 14 days
17:00	84.5%	1.5 min late	7.5 min late	4,769 · 14 days
18:00	82.2%	1 min late	8.8 min late	4,547 · 14 days
19:00	87.1%	0.8 min late	8 min late	3,403 · 14 days
20:00	87.4%	1 min late	7.7 min late	2,999 · 14 days
21:00	92.9%	0.6 min late	6.3 min late	3,049 · 14 days
22:00	86.8%	0.6 min late	6.9 min late	2,688 · 14 days
23:00	91.2%	0.2 min early	5.5 min late	1,846 · 14 days

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

Scheduled bus, but not observed in realtime

1,273 / 1,283 scheduled trips published at least one position across 7 service days (99.2%).

02:004 / 28 trips without a position85.7%
01:002 / 28 trips without a position92.9%
00:001 / 28 trips without a position96.4%
21:002 / 55 trips without a position96.4%
15:001 / 92 trips without a position98.9%
03:000 / 31 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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

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

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

03:02– 03:59
Trip 27833030Vehicle position matchedFirst / last feed position: 4:00 a.m. EST / 4:18 a.m. EST; not actual start or end times.
03:28– 04:25
Trip 11444030Vehicle position matchedFirst / last feed position: 4:00 a.m. EST / 4:21 a.m. EST; not actual start or end times.
03:32– 04:29
Trip 12424030Vehicle position matchedFirst / last feed position: 4:00 a.m. EST / 4:56 a.m. EST; not actual start or end times.
03:54– 04:51
Trip 25465030Vehicle position matchedFirst / last feed position: 4:01 a.m. EST / 4:53 a.m. EST; not actual start or end times.
04:04– 05:01
Trip 13127030Vehicle position matchedFirst / last feed position: 4:00 a.m. EST / 5:23 a.m. EST; not actual start or end times.
04:24– 05:05
Trip 21129030Vehicle position matchedFirst / last feed position: 4:19 a.m. EST / 6:16 a.m. EST; not actual start or end times.
04:29– 05:39
Trip 31560030Vehicle position matchedFirst / last feed position: 4:24 a.m. EST / 5:38 a.m. EST; not actual start or end times.
04:56– 05:40
Trip 7488030Vehicle position matchedFirst / last feed position: 4:58 a.m. EST / 6:16 a.m. EST; not actual start or end times.
05:24– 06:08
Trip 10854030Vehicle position matchedFirst / last feed position: 4:56 a.m. EST / 6:05 a.m. EST; not actual start or end times.
05:24– 06:20
Trip 34233030Vehicle position matchedFirst / last feed position: 5:04 a.m. EST / 6:32 a.m. EST; not actual start or end times.
05:39– 06:20
Trip 22908030Vehicle position matchedFirst / last feed position: 5:11 a.m. EST / 6:23 a.m. EST; not actual start or end times.
05:40– 06:39
Trip 24328030Vehicle position matchedFirst / last feed position: 5:16 a.m. EST / 6:41 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).