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+2 more notice

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

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

ᐊᖁᑦ 74: Limebank ⇄ Tunney's Pasture

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

ᑐᕌᖓᔪᖅLimebank1 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: 8 trips with qualifying later matching vehicle observations. Trips with any notice: 16.

Trips needing investigation

9 of 711 trips with a usable feed window (1.3%) had no matching position.

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

702 with position · 9 to investigate · 1 excluded · 712 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 702 / 712 (98.6%). 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:18 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

83.3%

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

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

The hours we have evidence for

00100% · 463 predictions · 14 days
0595% · 297 predictions · 11 days
0695% · 1,530 predictions · 13 days
0792% · 2,405 predictions · 14 days
0892% · 2,715 predictions · 14 days
0981% · 3,070 predictions · 14 days
1087% · 3,203 predictions · 14 days
1189% · 3,220 predictions · 14 days
1286% · 3,202 predictions · 14 days
1383% · 3,222 predictions · 14 days
1489% · 3,196 predictions · 14 days
1576% · 3,070 predictions · 14 days
1661% · 3,388 predictions · 14 days
1766% · 3,103 predictions · 14 days
1879% · 2,522 predictions · 14 days
1988% · 1,625 predictions · 14 days
2086% · 1,529 predictions · 14 days
2191% · 1,340 predictions · 14 days
2292% · 845 predictions · 14 days
2388% · 407 predictions · 13 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?

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

2% of back-to-back buses on this route arrived bunched together: 1,074 of 66,378 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

2% of pairs (998) 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.)	8,049	1% (118)	1% (108)
Midday (9 a.m. to 3 p.m.)	31,158	1% (339)	1% (264)
Afternoon rush (3 to 6 p.m.)	15,995	3% (529)	4% (582)
Evening (6 to 10 p.m.)	10,686	1% (88)	0% (44)
Night (10 p.m. to 4 a.m.)	490	0% (0)	0% (0)

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

Where this route is slowest

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

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
BASELINE 2B	QUEENSWAY 2A	1.5 km	13.1 km/h	11.6 km/h	1,068	6%
RICHMOND / GOLDEN	WESTBORO B	750 m	9 km/h	12.5 km/h	56	0%
QUEENSWAY 1A	BASELINE 1D	1.6 km	13.6 km/h	13.6 km/h	1,074	1%
RIVERVIEW B	NEPEAN WOODS B	1.8 km	14.8 km/h	16.1 km/h	1,188	3%
WESTBORO A	RICHMOND / GOLDEN	820 m	24.9 km/h	17.2 km/h	61	44%
LINCOLN FIELDS 3B	RICHMOND / GOLDEN	3.2 km	20.2 km/h	18.2 km/h	56	0%
LIMEBANK H	RIVERVIEW B	2.6 km	26 km/h	19.8 km/h	1,170	21%
RIVERVIEW A	LIMEBANK C	2.6 km	25.9 km/h	19.9 km/h	21	19%

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.

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

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

Hours with the most cancellations: 4 p.m. (5), 5 p.m. (5), 3 p.m. (4)

Latest cancelled trips

Thu, Oct 29, scheduled 15:43
Wed, Oct 28, scheduled 17:25
Wed, Oct 28, scheduled 16:11
Wed, Oct 28, scheduled 15:56
Wed, Oct 28, scheduled 15:39

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 711 trips we could check.

Open the dated prediction analysis

ᐃᓱᓕᑦᑎᓂᖅ

What this route needs

Median provider predictions are 3.3 min later than the timetable in 2 hours of the day.

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

16:00 has 61% of predictions within five minutes of the timetable, against 88% 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, 20 hours with samples

00:00: 100% of final predictions within five minutes of the timetable, 463 predictions, typically 0.3 min early
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 94.6% of final predictions within five minutes of the timetable, 297 predictions, typically 1.3 min late
06:00: 94.9% of final predictions within five minutes of the timetable, 1,530 predictions, typically 1.1 min late
07:00: 91.5% of final predictions within five minutes of the timetable, 2,405 predictions, typically 0.7 min late
08:00: 92.2% of final predictions within five minutes of the timetable, 2,715 predictions, typically 1 min late
09:00: 80.8% of final predictions within five minutes of the timetable, 3,070 predictions, typically 1.6 min late
10:00: 86.7% of final predictions within five minutes of the timetable, 3,203 predictions, typically 0.9 min late
11:00: 89.2% of final predictions within five minutes of the timetable, 3,220 predictions, typically 0.9 min late
12:00: 86.4% of final predictions within five minutes of the timetable, 3,202 predictions, typically 1.1 min late
13:00: 83.3% of final predictions within five minutes of the timetable, 3,222 predictions, typically 1.6 min late
14:00: 88.6% of final predictions within five minutes of the timetable, 3,196 predictions, typically 1.3 min late
15:00: 75.7% of final predictions within five minutes of the timetable, 3,070 predictions, typically 2.3 min late
16:00: 60.5% of final predictions within five minutes of the timetable, 3,388 predictions, typically 3.5 min late
17:00: 66% of final predictions within five minutes of the timetable, 3,103 predictions, typically 3.2 min late
18:00: 78.5% of final predictions within five minutes of the timetable, 2,522 predictions, typically 1.8 min late
19:00: 87.6% of final predictions within five minutes of the timetable, 1,625 predictions, typically 0.8 min late
20:00: 85.9% of final predictions within five minutes of the timetable, 1,529 predictions, typically 1.3 min late
21:00: 91.1% of final predictions within five minutes of the timetable, 1,340 predictions, typically 0.6 min late
22:00: 92.4% of final predictions within five minutes of the timetable, 845 predictions, typically 0.2 min late
23:00: 87.7% of final predictions within five minutes of the timetable, 407 predictions, typically 0.7 min late

90% or more of predictions within five minutes
80 to 90% of predictions within five minutes
under 80% of predictions within five minutes
not enough data

Findings
What	ᖃᖓ	ᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅ	Scenario or next investigation
ProblemPredictions later than timetable	16:00 to 18:00	3.3 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	16:00	61%	Operations, not the timetable
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 16:00 to 18:00: Measured arrivals 6,491; Hours affected 2; Spread 13.1 min; Median delay 3.3 min; Suggested running time change 3.3 min
One hour has a lower prediction match · 16:00: ᐃᑲᕐᕋᖅ 16:00; ᐱᕕᒃᓴᖓᓂ 60.5%; Measured arrivals 3,388; Shortfall 27.2 pts; Route median on time 87.7%
Coverage gap · All measured hours: ᑐᕌᒐᖅ 99.5%; Trips with a matching position 98.6%; ᐅᓪᓗᑦ ᐸᓯᑦ ᐊᐅᓚᑕᐅᓂᖏᑦ 6; Trips with a matching position 702; ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ 712

Open history, reliability and route analysis

Route check

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

83 in 100 eligible predictions were within 5 minutes of the timetable · 83,104 predictions checked

Prediction sample size: Larger sample

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

Updated Nov 3, 2026, 11: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: 40 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,388 predictions over 14 days).
17–18: 34 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,103 predictions over 14 days).

3 current notices affect this route

• Detour: Routes 57, 61, 62, 63, 74, 75, 87 during nightly Kichi Zībī Mīkan closures
• Limebank Station: Passenger pick-up and drop-off area relocation
• Detour: Routes entering and exiting Limebank Station

Prediction differences by stop

IRIS 2A
32 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,289 predictions over 29 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 1Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 9 of 711 checked trips need a closer look9 of 711 trips with enough public-feed evidence had no matching position over 7 days. 1 of 712 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 9.6 min (positive means later; negative means earlier)83 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: 7.4 min average predicted wait1.2 min beyond the scheduled wait, based on 2,226 eligible predictions at 36 high-frequency stops over 14 days.

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

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

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

Current published schedule began October 30, 2026

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

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

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

ᓯᕗᓂᐊᓂ

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

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

Operator calendar-date records: 0 added · 2 removed

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

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

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

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

Operator calendar-date records: 0 added · 2 removed

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

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

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

Still collecting: before has 44,155 arrivals over 14 days; after has 11,166 arrivals over 4 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: 83.3%
Eligible predictions checked: 83,104
Weekdays with data: 19
95th-percentile predicted delay: 9.6 min late

Patterns by hour (20)

Patterns by hour (20)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
00:00	100.0%	0.3 min early	2 min late	463 · 14 days
05:00	94.6%	1.3 min late	5.9 min late	297 · 11 days
06:00	94.9%	1.1 min late	5 min late	1,530 · 13 days
07:00	91.5%	0.7 min late	5.9 min late	2,405 · 14 days
08:00	92.2%	1 min late	5.7 min late	2,715 · 14 days
09:00	80.8%	1.6 min late	8.5 min late	3,070 · 14 days
10:00	86.7%	0.9 min late	6.9 min late	3,203 · 14 days
11:00	89.2%	0.9 min late	6.6 min late	3,220 · 14 days
12:00	86.4%	1.1 min late	9.2 min late	3,202 · 14 days
13:00	83.3%	1.6 min late	9.5 min late	3,222 · 14 days
14:00	88.6%	1.3 min late	6.8 min late	3,196 · 14 days
15:00	75.7%	2.3 min late	9.8 min late	3,070 · 14 days
16:00	60.5%	3.5 min late	15.8 min late	3,388 · 14 days
17:00	66.0%	3.2 min late	17.1 min late	3,103 · 14 days
18:00	78.5%	1.8 min late	11.9 min late	2,522 · 14 days
19:00	87.6%	0.8 min late	9.6 min late	1,625 · 14 days
20:00	85.9%	1.3 min late	8.2 min late	1,529 · 14 days
21:00	91.1%	0.6 min late	6.1 min late	1,340 · 14 days
22:00	92.4%	0.2 min late	5.9 min late	845 · 14 days
23:00	87.7%	0.7 min late	8.2 min late	407 · 13 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

702 / 712 scheduled trips published at least one position across 6 service days (98.6%).

15:003 / 48 trips without a position93.8%
09:002 / 48 trips without a position95.8%
08:001 / 47 trips without a position97.9%
11:001 / 48 trips without a position97.9%
12:001 / 48 trips without a position97.9%
14:001 / 48 trips without a position97.9%

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 · 119 trips in the retained timetable · retained notices; capture coverage unverified

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

05:45– 06:35
Trip 24265030Vehicle position matchedFirst / last feed position: 5:26 a.m. EST / 6:50 a.m. EST; not actual start or end times.
05:50– 06:08
Trip 20698030Vehicle position matchedFirst / last feed position: 5:04 a.m. EST / 6:22 a.m. EST; not actual start or end times.
06:05– 06:51
Trip 12024030Vehicle position matchedFirst / last feed position: 5:43 a.m. EST / 7:20 a.m. EST; not actual start or end times.
06:09– 06:59
Trip 16977030Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:59 a.m. EST; not actual start or end times.
06:23– 07:17
Trip 35549030Vehicle position matchedFirst / last feed position: 6:23 a.m. EST / 7:14 a.m. EST; not actual start or end times.
06:39– 07:36
Trip 3055030Vehicle position matchedFirst / last feed position: 6:18 a.m. EST / 7:44 a.m. EST; not actual start or end times.
06:40– 07:27
Trip 28502030Vehicle position matchedFirst / last feed position: 6:41 a.m. EST / 7:32 a.m. EST; not actual start or end times.
06:52– 07:49
Trip 22401030Vehicle position matchedFirst / last feed position: 6:38 a.m. EST / 7:49 a.m. EST; not actual start or end times.
07:07– 08:04
Trip 9947030Vehicle position matchedFirst / last feed position: 6:46 a.m. EST / 8:04 a.m. EST; not actual start or end times.
07:10– 08:03
Trip 32035030Vehicle position matchedFirst / last feed position: 7:14 a.m. EST / 8:10 a.m. EST; not actual start or end times.
07:17– 07:59
Trip 15301030Vehicle position matchedFirst / last feed position: 6:32 a.m. EST / 7:57 a.m. EST; not actual start or end times.
07:19– 08:16
Trip 20998030Vehicle position matchedFirst / last feed position: 7:21 a.m. EST / 8:20 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).