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+1 more notice
No 87 trips cancelled now · 4 did not run in novembreCancellations →
Previous measure: 86,9% of arrivals were within five minutes of the timetable (42.022 arrivals over 27 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
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: 6.
Trips needing investigation
5
5 of 615 trips with a usable feed window (0,8%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
610 with position · 5 to investigate · 0 excluded · 615 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 4 nov 2026, 02:48.
Coverage, exclusions and sources
0 of 5 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: 610 / 615 (99,2%). 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: 4 nov 2026, 01:47
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
86,9%
of eligible provider predictions were within five minutes of the timetable.
Within five minutesOutside
Predictions in the source
42.022
Weekdays with evidence
19
Evidence window
5 ott 2026 – 2 nov 2026
The hours we have evidence for
697% · 408 predictions · 11 days
796% · 907 predictions · 12 days
892% · 1520 predictions · 12 days
990% · 1714 predictions · 12 days
1090% · 1752 predictions · 14 days
1193% · 1861 predictions · 14 days
1293% · 1868 predictions · 14 days
1388% · 1868 predictions · 14 days
1487% · 1896 predictions · 14 days
1580% · 1802 predictions · 14 days
1661% · 1819 predictions · 14 days
1772% · 1437 predictions · 14 days
1892% · 1304 predictions · 14 days
1991% · 884 predictions · 14 days
2084% · 760 predictions · 10 days
2183% · 763 predictions · 10 days
2296% · 129 predictions · 10 days
Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
Calculated: 4 nov 2026
2 partial-capture days not counted.
What about time of day?
17 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.
Last 28 days, 7 ottobre 2026 to 3 novembre 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: 8 ottobre 2026, 15 ottobre 2026.
Ora di punta del mattino (dalle 6 alle 9)0%
Metà giornata (dalle 9 del mattino alle 3 del pomeriggio)1%
Ora di punta pomeridiana (dalle 3 alle 6 del pomeriggio)2%
Sera (dalle 6 alle 10 di sera)0%
Notte (dalle 10 di sera alle 4 del mattino)0%
Valori e interpretazione
1% of back-to-back buses on this route arrived bunched together: 275 of 35.644 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
1% of pairs (259) had a long gap: more than 1.75 times the planned wait between them.
Autobus che arrivano ravvicinati
Ora del giorno
Coppie verificate
Corse ravvicinate
Lungo intervallo
Ora di punta del mattino (dalle 6 alle 9)
3725
0% (14)
0% (17)
Metà giornata (dalle 9 del mattino alle 3 del pomeriggio)
18.093
1% (93)
0% (83)
Ora di punta pomeridiana (dalle 3 alle 6 del pomeriggio)
Lavori stradali e chiusure di strade per eventi pubblicati dalla Città di Ottawa, misurati come vicini al percorso di questa linea. Vicino non prova che l'autobus sia deviato. Per questo, controlli gli avvisi dell'esercente.
Al momento non è possibile leggere l'elenco dei lavori stradali della Città.
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.
Fonte: eventi di traffico della Città di Ottawa (lavori stradali e chiusure). Contiene informazioni concesse in licenza ai sensi della Open Government Licence, City of Ottawa. La Città precisa che questo elenco è fornito al meglio delle sue possibilità e può essere incompleto. Mappa del traffico della Città di Ottawa ↗
7 scheduled trips with counted cancellation notices from mer 7 ott to mar 3 nov.
Not counted: 14 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Ore con più cancellazioni: 16 (3), 14 (2), 8 (1)
Ultime corse cancellate
lun 2 nov, scheduled 16:28
lun 2 nov, scheduled 14:27
mer 28 ott, scheduled 08:40
mar 27 ott, scheduled 16:50
mer 21 ott, scheduled 16:50
OC Transpo non indica un motivo per le singole corse, quindi non ne viene mostrato nessuno.
Did not come (no bus seen, no notice), last 7 days: 4 of 615 trips we could check.
Aprire l'analisi datata delle previsioni
Verdetto
What this route needs
Median provider predictions are 3,2 min later than the timetable in 1 hours of the day.
Predictions near the start are about 3,3 min later than the timetable; the difference grows by another 2,1 min along the route.
16:00 has 61% of predictions within five minutes of the timetable, against 90% the rest of the day.
Only 99% of scheduled trips were seen; the rest are not counted as missed.
Scenario: 3 min more running time on 86 trips. The schedule-block model estimates 20 additional buses; fleet and workforce feasibility are unverified.
Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.
Final provider predictions within five minutes of the timetable, by hour, last 14 days, 17 hours with samples
00:00: not enough data00
01:00: not enough data01
02:00: not enough data02
03:00: not enough data03
04:00: not enough data04
05:00: not enough data05
06:00: 96,8% of final predictions within five minutes of the timetable, 408 predictions, typically 1 min late06
07:00: 96,1% of final predictions within five minutes of the timetable, 907 predictions, typically 0,1 min early07
08:00: 91,5% of final predictions within five minutes of the timetable, 1520 predictions, typically 0,5 min late08
09:00: 89,6% of final predictions within five minutes of the timetable, 1714 predictions, typically 1,3 min late09
10:00: 90,2% of final predictions within five minutes of the timetable, 1752 predictions, typically 0,5 min late10
11:00: 92,6% of final predictions within five minutes of the timetable, 1861 predictions, typically 1,1 min late11
12:00: 92,6% of final predictions within five minutes of the timetable, 1868 predictions, typically 1,2 min late12
13:00: 87,9% of final predictions within five minutes of the timetable, 1868 predictions, typically 1,1 min late13
14:00: 87,3% of final predictions within five minutes of the timetable, 1896 predictions, typically 0,9 min late14
15:00: 79,5% of final predictions within five minutes of the timetable, 1802 predictions, typically 2 min late15
16:00: 60,5% of final predictions within five minutes of the timetable, 1819 predictions, typically 3,2 min late16
17:00: 72,1% of final predictions within five minutes of the timetable, 1437 predictions, typically 2,2 min late17
18:00: 92% of final predictions within five minutes of the timetable, 1304 predictions, typically 0,7 min late18
19:00: 90,8% of final predictions within five minutes of the timetable, 884 predictions, typically 1,1 min late19
20:00: 84,1% of final predictions within five minutes of the timetable, 760 predictions, typically 1,7 min late20
21:00: 83,4% of final predictions within five minutes of the timetable, 763 predictions, typically 1,3 min late21
22:00: 96,1% of final predictions within five minutes of the timetable, 129 predictions, typically 1,8 min late22
23:00: not enough data23
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
Quando
Misurato
Scenario or next investigation
Problem!Predictions later than timetable
16:00
3,2 min late
More running time
Problem!One hour has a lower prediction match
16:00
61%
Operations, not the timetable
Caveat?Coverage gap
All measured hours
99%
More observation, not a service change
Measurements
Predictions later than timetable · 16:00
Measured arrivals 1819
Hours affected 1
Spread 11,6 min
Median delay 3,2 min
Suggested running time change 3,2 min
One hour has a lower prediction match · 16:00
Ora 16:00
In orario 60,5%
Measured arrivals 1819
Shortfall 29,7 pts
Route median on time 90,2%
Coverage gap · All measured hours
Obiettivo 99,5%
Trips with a matching position 99,2%
Giorni di servizio 5
Trips with a matching position 610
Corse programmate 615
16:00 30 → to 3316:00 35 → to 38
Aprire storico, affidabilità e analisi della linea
Verifica della linea
How route 87 has been running
Un breve riepilogo di ciò che sappiamo. Lo diciamo quando non possiamo rispondere a una domanda.
In sintesi
Le previsioni dell'operatore erano di solito vicine all'orario, ma controlli qui sotto gli orari con problemi.
Dimensione del campione delle previsioni: Campione più ampio
Based on 42.022 eligible provider predictions over 27 measured days, from 5 ott 2026 to 2 nov 2026.
Updated 4 nov 2026, 01:43
Dove e quando le previsioni sono state diverse più volte?
Sono differenze ripetute tra previsione e orario, non disservizi misurati in modo indipendente. Usano le stesse previsioni idonee del risultato qui sopra, ma sono raggruppate per fermata anziché per ora, quindi gli elenchi possono non coincidere riga per riga.
16–17: 40 in 100 eligible predictions differed from the timetable by more than 5 minutes (1819 predictions over 14 days).
• Detour: Route 87 during Woodroffe Avenue closure (Byron/Richmond to Kichi Zibi Mikan)
Differenze di previsione per fermata
Non abbiamo ancora abbastanza storico per ligne e fermata per indicare una fermata con problemi ricorrenti. Le segnalazioni dei passeggeri sono usate come indizi, non come prove.
Controlli ogni corsa e ogni data
Apra un periodo per vedere ogni giorno di servizio, ogni corsa programmata, ogni lacuna nei dati, l'ID del veicolo pubblico osservato e i conteggi esatti alla base di questo riepilogo.
Cosa vogliono sapere i passeggeri
Qualche corsa è cancellata in questo momento?
0 of 5Vengono controllate le corse che partono dai capolinea della linea nelle prossime 4 ore. Non è un tasso storico di cancellazioni.
Possibili corse saltate dopo il controllo delle lacune del feed?
5 of 615 checked trips need a closer look5 of 615 trips with enough public-feed evidence had no matching position over 7 days. 0 of 615 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Come sono differite le previsioni dell'operatore rispetto all'orario?
Questo confronto riguarda l'orario ufficiale conservato attualmente e la versione conservata in precedenza. Le modifiche dell'orario sono fatti su ciò che era stato pianificato. Non provano che una corsa sia stata effettuata.
Current published schedule began 30 ottobre 2026
Giorno di servizio selezionato da ciascun orario pubblicato
Controlliamo il primo lunedì dopo l'inizio del nuovo orario e il lunedì di una settimana prima. Ogni dato proviene dalle versioni GTFS ufficiali conservate indicate qui sotto.
Almeno una data selezionata ha un servizio aggiunto o rimosso nel calendario. Lo consideri un contesto di giorno festivo o di servizio speciale, non una normale crescita dei giorni feriali.
Impronta del feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
Il servizio è migliorato dopo la modifica?
Confronteremo gli arrivi consolidati nei 14 giorni prima e dopo la modifica. Pubblichiamo il confronto solo quando entrambi i periodi hanno almeno 7 giorni di servizio e 200 arrivi.
Still collecting: before has 22.730 arrivals over 14 days; after has 7415 arrivals over 5 days. No improvement or decline is claimed yet.
I checksum permettono a chiunque di verificare quale orario conservato ha prodotto i conteggi. Una variazione del conteggio non indica una causa, una cancellazione, una decisione dell'esercente o un effetto sui passeggeri.
Come viene valutata questa ligne: Linea regolare con tutte le fermate
Confrontiamo l'ultima previsione idonea del fornitore per ogni arrivo programmato con l'orario ufficiale. Non sono arrivi misurati in modo indipendente. Per un risultato servono almeno 200 previsioni idonee. Qui si usa come obiettivo per i passeggeri "entro 5 minuti".
Che cosa questi dati non possono dimostrare
Il feed pubblico non fornisce conteggi affidabili dei passeggeri né eventi di passeggeri non imbarcati. Una posizione mancante non prova da sola una cancellazione, una mancata corsa, un'inversione anticipata o una causa.
Vedere le definizioni, le soglie e l'ordine dei dati
Feed ufficiale attuale: cancellazioni esplicite, fermate saltate e avvisi attivi.
Osservazioni abbinate: posizioni dei veicoli e previsioni consolidate collegate all'orario ufficiale.
Orario ufficiale: ciò che era previsto, tenuto separato da ciò che è stato osservato.
Segnalazioni di passeggeri e operatori: indizi su linee, orari e luoghi da verificare, non prove numeriche di per sé.
Risultati provvisori, dati probanti pubblicati
Come si sono confrontate le previsioni con l'orario?
Ogni ora confronta l'ultima previsione idonea del fornitore per un arrivo previsto a orario con l'orario ufficiale. «Entro 5 minuti» indica la differenza tra le previsioni, non un arrivo misurato né la prova che un autobus abbia circolato.
Periodo dei dati probatori: 5 ottobre 2026 to 2 novembre 2026
1 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
Autobus previsto a orario, ma non osservato in tempo reale
610 / 615 scheduled trips published at least one position across 5 service days (99,2%).
07:002 / 41 trips without a position95,1%
08:002 / 49 trips without a position95,9%
17:001 / 38 trips without a position97,4%
05:000 / 5 trips without a position100,0%
06:000 / 20 trips without a position100,0%
09:000 / 44 trips without a position100,0%
Questa non è una mancata corsa confermata. Una posizione mancante può indicare una corsa soppressa o saltata, ma può anche indicare un ID di corsa non assegnato o un'interruzione nel feed del gestore. Otranspo pubblica questa mancanza perché è importante per chi viaggia, senza trarre conclusioni non verificate.
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. Fonti e limiti.
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.
November 3, 2026 · 107 trips in the retained timetable · retained notices; capture coverage unverified
In short: 106 with a matched position · 1 with no matching position (to investigate) · 0 with an unknown outcome.
05:59– 06:14
Trip 10048030Vehicle position matchedFirst / last feed position: 6:01 a.m. EST / 6:12 a.m. EST; not actual start or end times.
06:27– 06:42
Trip 18016030Vehicle position matchedFirst / last feed position: 5:52 a.m. EST / 6:36 a.m. EST; not actual start or end times.
06:29– 06:44
Trip 3882030Vehicle position matchedFirst / last feed position: 6:25 a.m. EST / 6:47 a.m. EST; not actual start or end times.
06:48– 07:03
Trip 3370030Vehicle position matchedFirst / last feed position: 6:12 a.m. EST / 7:04 a.m. EST; not actual start or end times.
06:48– 07:03
Trip 5521030Vehicle position matchedFirst / last feed position: 6:42 a.m. EST / 7:13 a.m. EST; not actual start or end times.
07:05– 07:20
Trip 8202030Vehicle position matchedFirst / last feed position: 7:05 a.m. EST / 7:19 a.m. EST; not actual start or end times.
07:10– 07:29
Trip 30955030Vehicle position matchedFirst / last feed position: 6:37 a.m. EST / 7:25 a.m. EST; not actual start or end times.
07:17– 07:32
Trip 30641030Vehicle position matchedFirst / last feed position: 7:09 a.m. EST / 7:38 a.m. EST; not actual start or end times.
07:23– 07:52
Trip 32845030Vehicle position matchedFirst / last feed position: 7:20 a.m. EST / 7:50 a.m. EST; not actual start or end times.
07:32– 07:47
Trip 16628030Vehicle position matchedFirst / last feed position: 7:26 a.m. EST / 7:46 a.m. EST; not actual start or end times.
07:38– 08:07
Trip 24966030Vehicle position matchedFirst / last feed position: 6:55 a.m. EST / 8:03 a.m. EST; not actual start or end times.
07:39– 08:08
Trip 17800030Vehicle position matchedFirst / last feed position: 6:53 a.m. EST / 8:10 a.m. EST; not actual start or end times.