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 aviso más
No 87 trips cancelled now · 4 no circularon en noviembreCancellations →
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.
87
Ruta 87: Tunney's Pasture ⇄ Baseline
Cada 15 a 30 min
Hacia Tunney's Pasture1 buses · sube en · bajo cada parada: el siguiente bus (punto verde = en vivo, gris = programado)
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: 3 trips with qualifying later matching vehicle observations. Trips with any notice: 7.
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: 3 nov 2026, 21:02.
Coverage, exclusions and sources
0 of 4 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: 3 nov 2026, 19:39
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 oct 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.
Últimos 28 días, del 6 de octubre de 2026 al 2 de noviembre de 2026: 26 días contados.
2 días excluidos porque el flujo en vivo solo se registró en parte o sus números de viaje no coincidían con el horario: 8 de octubre de 2026, 15 de octubre de 2026.
Hora punta de la mañana (6 a 9 a. m.)0 %
Mediodía (9 a. m. a 3 p. m.)0 %
Hora punta de la tarde (de 3 a 6 p. m.)2 %
Tarde-noche (de 6 a 10 p. m.)0 %
Noche (de 10 p. m. a 4 a. m.)0 %
Valores e interpretación
1 % of back-to-back buses on this route arrived bunched together: 285 of 37.444 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
1 % of pairs (262) had a long gap: more than 1.75 times the planned wait between them.
Obras viales y cierres de calles por eventos que la Ciudad de Ottawa ha publicado, medidos como cercanos al recorrido de esta ruta. Cerca no es prueba de que el autobús tenga desvío: para eso, revisa las alertas del propio operador.
Obras
FAIRLAWN between LENESTER and ESTERLAWN
15 oct 2026, 0:00 to 13 nov 2026, 17:00
FAIRLAWN off-peak lane reductions between LENESTER and ESTERLAWN due to construction, from October 15th to November 13th.
La Ciudad indica que esto afecta al transporte público.
about 0 m from the route
City record updated 16 oct 2026, 11:20.
Obras
RICHMOND W/B between CLEARY and WOODROFFE
26 oct 2026, 0:00 to 6 nov 2026, 17:00
RICHMOND westbound lane reduction between CLEARY and WOODROFFE due to construction, until November 6th.
La Ciudad indica que esto afecta al transporte público.
about 0 m from the route
City record updated 3 nov 2026, 6:40.
Obras
Kichi Zibi Mikan between ISLAND PARK and WOODROFFE
30 oct 2026, 9:30 to 20 nov 2026, 15:00
Kichi Zibi Mikan reduced to 1 lane in each direction between ISLAND PARK and WOODROFFE due to construction, from November 2nd to 20th between 9:30am and 3:00pm.
about 0 m from the route
City record updated 30 oct 2026, 9:28.
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.
Fuente: eventos de tráfico de la Ciudad de Ottawa (obras y cierres de calles). Contiene información con licencia de Open Government Licence, City of Ottawa. La Ciudad indica que esta lista es de mejor esfuerzo y puede estar incompleta. Mapa de tráfico de la Ciudad de Ottawa ↗
8 scheduled trips with counted cancellation notices from mar, 6 oct to lun, 2 nov.
Not counted: 16 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Horas con más cancelaciones: 16 (4), 14 (2), 8 (1)
Últimos viajes cancelados
lun, 2 nov, scheduled 16:28
lun, 2 nov, scheduled 14:27
mié, 28 oct, scheduled 08:40
mar, 27 oct, scheduled 16:50
mié, 21 oct, scheduled 16:50
OC Transpo no da el motivo de cada viaje, así que no se muestra ninguno.
Did not come (no bus seen, no notice), last 7 days: 4 of 615 trips we could check.
Abre el análisis de predicciones con fechas
Veredicto
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
Cuándo
Medido
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
Hora 16:00
A tiempo 60,5%
Measured arrivals 1819
Shortfall 29,7 pts
Route median on time 90,2%
Coverage gap · All measured hours
Meta 99,5%
Trips with a matching position 99,2%
Días de servicio 5
Trips with a matching position 610
Trayectos programados 615
16:00 30 → to 3316:00 35 → to 38
Abrir historial, fiabilidad y análisis de la ruta
Revisión de ruta
How route 87 has been running
Un resumen breve de lo que sabemos. Lo decimos cuando no podemos responder una pregunta.
En resumen
Las predicciones del proveedor solían estar cerca del horario, pero revisa las horas con problemas que aparecen abajo.
Tamaño de la muestra de predicción: Muestra más grande
Based on 42.022 eligible provider predictions over 27 measured days, from 5 oct 2026 to 2 nov 2026.
Updated 3 nov 2026, 19:32
¿Dónde y cuándo difirieron las predicciones de forma repetida?
Son diferencias repetidas entre la predicción y el horario. No son fallas de servicio medidas de forma independiente. Usan las mismas predicciones válidas del resultado de arriba, pero se agrupan por parada y no por hora. Por eso las listas pueden no coincidir línea por línea.
16–17: 40 in 100 eligible predictions differed from the timetable by more than 5 minutes (1819 predictions over 14 days).
32 in 100 eligible predictions differed from the timetable by more than 5 minutes (74 predictions over 4 days).
Abrir esta parada
Son predicciones del proveedor para cada ruta, comparadas con el horario. Muestran diferencias repetidas en un lugar y una hora. No son llegadas medidas ni explican su causa.
Revisa cada viaje y fecha
Abre un período para ver cada día de servicio, viaje programado, hueco en los datos, ID público del vehículo observado y los conteos exactos detrás de este resumen.
Lo que quieren saber los pasajeros
¿Hay algún viaje cancelado ahora?
0 of 4Revisa los viajes que salen de los extremos de la ruta en las próximas 4 horas. No es una tasa histórica de cancelaciones.
¿Posibles autobuses que no pasaron tras revisar las lagunas de la fuente?
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.
¿En qué se diferenciaron las predicciones del proveedor y el horario?
Esto compara el horario oficial guardado actual con la versión guardada anterior. Los cambios de horario son datos sobre lo que estaba planificado. No prueban que un viaje se haya realizado.
Current published schedule began 30 de octubre de 2026
Día de servicio elegido de cada horario publicado
Revisamos el primer lunes después de que empezó el nuevo horario y el lunes de una semana antes. Todas las cifras vienen de las versiones oficiales GTFS guardadas que se nombran abajo.
Al menos una fecha elegida tiene servicio agregado o quitado del calendario. Toma esto como un caso de feriado o servicio especial, no como un aumento normal de un día laborable.
Huella digital del feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
¿Mejoró el servicio después del cambio?
Compararemos las llegadas ya consolidadas de los 14 días antes y después del cambio. Solo publicamos la comparación cuando ambos periodos tienen al menos 7 días de servicio y 200 llegadas.
Still collecting: before has 22.730 arrivals over 14 days; after has 5470 arrivals over 4 days. No improvement or decline is claimed yet.
Las sumas de verificación permiten a cualquier persona comprobar qué horario conservado produjo los conteos. Un cambio en un conteo no indica una causa, una cancelación, una decisión del operador ni un efecto en los pasajeros.
Cómo se evalúa esta ruta: Ruta regular con todas las paradas
Comparamos la última predicción válida del proveedor para cada llegada programada con el horario oficial. No son llegadas medidas de forma independiente. Un resultado necesita al menos 200 predicciones válidas. Dentro de 5 minutos es la meta para los pasajeros que se usa aquí.
Lo que estos datos no pueden demostrar
Los datos públicos no ofrecen conteos fiables de pasajeros ni eventos de pasajeros que se quedaron sin subir. Si falta una posición, eso no prueba por sí solo una cancelación, un servicio que no se presentó, un viaje acortado ni su causa.
Mira las definiciones, los umbrales y el orden de los datos probantes
Fuente oficial actual: cancelaciones explícitas, paradas omitidas y avisos activos.
Observaciones emparejadas: posiciones de vehículos y predicciones ya definitivas, vinculadas al horario oficial.
Horario oficial: lo que estaba planeado, separado de lo que se observó.
Reportes de pasajeros y operadores: pistas sobre rutas, horarios y lugares que investigar, no prueba numérica por sí solos.
Resultados provisionales, datos probatorios publicados
¿Cómo se compararon las predicciones con el horario?
Cada hora compara la última predicción válida del proveedor para una llegada prevista en el horario con el horario. «Dentro de 5 minutos» describe esa diferencia entre predicciones. No es una llegada medida ni una prueba de que un autobús circuló.
Período de datos probantes: 5 de octubre de 2026 to 2 de noviembre de 2026
1 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
Autobús programado, pero no observado en tiempo real
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 %
16:001 / 43 trips without a position97,7 %
05:000 / 5 trips without a position100,0 %
06:000 / 20 trips without a position100,0 %
09:000 / 44 trips without a position100,0 %
Esto no es una ausencia confirmada. Una posición ausente puede significar un autobús cancelado o perdido, pero también un ID de viaje sin asignar o un vacío en los datos del operador. Otranspo publica el vacío porque les importa a los pasajeros, y mantiene la conclusión honesta.
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. Fuentes y límites.
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 2, 2026 · 107 trips in the retained timetable · retained notices; capture coverage unverified
In short: 107 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.
05:59– 06:14
Trip 10048020Vehicle position matchedFirst / last feed position: 6:00 a.m. EST / 6:12 a.m. EST; not actual start or end times.
06:27– 06:42
Trip 18016020Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:38 a.m. EST; not actual start or end times.
06:29– 06:44
Trip 3882020Vehicle position matchedFirst / last feed position: 6:30 a.m. EST / 6:49 a.m. EST; not actual start or end times.
06:48– 07:03
Trip 3370020Vehicle position matchedFirst / last feed position: 6:12 a.m. EST / 6:59 a.m. EST; not actual start or end times.
06:48– 07:03
Trip 5521020Vehicle position matchedFirst / last feed position: 6:40 a.m. EST / 7:14 a.m. EST; not actual start or end times.
07:05– 07:20
Trip 8202020Vehicle position matchedFirst / last feed position: 7:00 a.m. EST / 7:23 a.m. EST; not actual start or end times.
07:10– 07:29
Trip 30955020Vehicle position matchedFirst / last feed position: 7:15 a.m. EST / 7:25 a.m. EST; not actual start or end times.
07:17– 07:32
Trip 30641020Vehicle position matchedFirst / last feed position: 7:10 a.m. EST / 7:32 a.m. EST; not actual start or end times.
07:23– 07:52
Trip 32845020Vehicle position matchedFirst / last feed position: 7:23 a.m. EST / 7:50 a.m. EST; not actual start or end times.
07:32– 07:47
Trip 16628020Vehicle position matchedFirst / last feed position: 7:27 a.m. EST / 7:47 a.m. EST; not actual start or end times.
07:38– 08:07
Trip 24966020Vehicle position matchedFirst / last feed position: 6:55 a.m. EST / 8:04 a.m. EST; not actual start or end times.
07:39– 08:08
Trip 17800020Vehicle position matchedFirst / last feed position: 6:54 a.m. EST / 8:15 a.m. EST; not actual start or end times.