Mapa
Previous measure: 87,9 % of arrivals were within five minutes of the timetable (32.161 arrivals over 18 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
Cada 30 min
Scheduled service and available evidence
Evidence period: 27 oct 2026 – 2 nov 2026
0
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: 13 trips with qualifying later matching vehicle observations. Trips with any notice: 13.
0
0 of 350 trips with a usable feed window (0%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
350 with position · 0 to investigate · 0 excluded · 350 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 3 nov 2026, 18:49.
0 of 12 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: 350 / 350 (100 %). 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, 18:08
Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.
Predictions against the timetable
87,9%
of eligible provider predictions were within five minutes of the timetable.
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: 3 nov 2026
2 partial-capture days not counted.
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.
Ú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.
0 % of back-to-back buses on this route arrived bunched together: 27 of 21.310 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
0 % of pairs (2) had a long gap: more than 1.75 times the planned wait between them.
| Hora del día | Pares comprobados | Agrupados | Intervalo largo |
|---|---|---|---|
| Hora punta de la mañana (6 a 9 a. m.) | 2793 | 0 % (0) | 0 % (0) |
| Mediodía (9 a. m. a 3 p. m.) | 7897 | 0 % (0) | 0 % (0) |
| Hora punta de la tarde (de 3 a 6 p. m.) | 4070 | 0 % (19) | 0 % (0) |
| Tarde-noche (de 6 a 10 p. m.) | 5856 | 0 % (6) | 0 % (2) |
| Noche (de 10 p. m. a 4 a. m.) | 694 | 0 % (2) | 0 % (0) |
Slowest: PINECREST B to LINCOLN FIELDS 2A, 18,4 km/h actual against 11 km/h planned.
| Desde | Hasta | Distancia | Velocidad planificada | Velocidad real | Trayectos medidos | Viajes lentos |
|---|---|---|---|---|---|---|
| PINECREST B | LINCOLN FIELDS 2A | 1,8 km | 11 km/h | 18,4 km/h | 82 | 0 % |
| TERRY FOX 3C | CASTLEFRANK / MCCURDY | 3 km | 29,9 km/h | 18,8 km/h | 119 | 64 % |
| EAGLESON C | TERRY FOX 3C | 2,8 km | 17,3 km/h | 20,4 km/h | 119 | 0 % |
| MCCURDY / 1ST CASTLEFRANK | TERRY FOX 4A | 2,9 km | 28,6 km/h | 20,7 km/h | 82 | 18 % |
| TERRY FOX 3C | CASTLEFRANK / HAZELDEAN | 2,4 km | 18 km/h | 21,4 km/h | 457 | 1 % |
| CASTLEFRANK / MACNEIL | FERNBANK / TERRY FOX | 3,9 km | 23,3 km/h | 24,5 km/h | 118 | 0 % |
| LINCOLN FIELDS 1A | BAYSHORE B | 3,1 km | 15,6 km/h | 24,5 km/h | 119 | 0 % |
| FERNBANK / TERRY FOX | MICHAEL COWPLAND / TERRENCE MATHEWS | 2,2 km | 66,7 km/h | 25,3 km/h | 26 | 69 % |
Un viaje lento duró al menos 1.5 veces el tiempo previsto.
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
417 W/B off ramp at Bayshore
29 abr 2026, 6:00 to 31 dic 2026, 17:00
417 W/B off ramp at Bayshore left-turn lane to Richmond closed off-peak due to construction, from April 29th to December 31. Cyclists and pedestrians not affected.
La Ciudad indica que esto afecta al transporte público.
about 17 m from the route
City record updated 28 ago 2026, 13:32.
Obras
417 E/B between March and Moodie
27 oct 2026, 10:00 to 6 nov 2026, 14:00
417 eastbound HOV lane closed between March and Moodie due to construction, from October 27th to November 6th between 10:00am and 2:00pm.
La Ciudad indica que esto afecta al transporte público.
about 0 m from the route
City record updated 3 nov 2026, 7:08.
Obras
CARLING E/B between Kichi Zibi Mikan on Ramp and EDGEWORTH
30 oct 2026, 0:00 to 13 nov 2026, 15:00
CARLING eastbound reduced to 1 lane between Kichi Zibi Mikan on Ramp and EDGEWORTH due to construction, from November 2nd to 13th between 9:30am and 3:00pm.
about 0 m from the route
City record updated 30 oct 2026, 11: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.
Obras
CORKSTOWN between MOODIE and MARCH
31 oct 2026, 9:30 to 5 nov 2026, 19:00
CORKSTOWN closed between MOODIE and MARCH due to construction, from November 3rd to 5th between 9:30am and 7:00pm.
about 0 m from the route
City record updated 31 oct 2026, 9:28.
Obras
Moodie S/B at 417 overpass
2 nov 2026, 6:00 to 9 nov 2026, 14:30
Moodie southbound reduced to 1 lane at 417 overpass due to construction, from November 4th to 9th between 6:00 and 2:30pm.
La Ciudad indica que esto afecta al transporte público.
about 0 m from the route
City record updated 2 nov 2026, 13:12.
Obras
COPE between TERRY FOX and TEMPLEFORD
3 nov 2026, 7:00 to 16 nov 2026, 17:00
COPE closed between TERRY FOX and TEMPLEFORD due to construction, from November 6th to 16th. Follow the signed detour.
La Ciudad indica que esto afecta al transporte público.
about 0 m from the route
City record updated 3 nov 2026, 6:56.
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 ↗
2 partial-capture days not counted.
2 scheduled trips with counted cancellation notices from mar, 6 oct to lun, 2 nov.
Not counted: 47 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Horas con más cancelaciones: 19 (1), 20 (1)
OC Transpo no da el motivo de cada viaje, así que no se muestra ninguno.
No llegó (no se vio ningún autobús y no hubo aviso), últimos 7 días: ninguno de los trayectos que pudimos revisar.
Veredicto
Median provider predictions are 3,2 min later than the timetable in 1 hours of the day.
16:00 has 67% of predictions within five minutes of the timetable, against 93% the rest of the day.
Matched public positions cover 100% of scheduled trips. This is a lower bound on operated service, not an audited delivery result.
Scenario: 3 min more running time on 10 trips. The schedule-block model adds no 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.
| What | Cuándo | Medido | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable | 05:00 | 3,2 min late | More running time |
| ProblemOne hour has a lower prediction match | 16:00 | 67 % | Operations, not the timetable |
| StrengthObserved-position lower bound | All measured hours | 100 % | Keep what works |
Revisión de ruta
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.
88 in 100 eligible predictions were within 5 minutes of the timetable · 32.161 predictions checkedTamaño de la muestra de predicción: Muestra más grande
Based on 32.161 eligible provider predictions over 18 measured days, from 5 oct 2026 to 2 nov 2026.
Updated 3 nov 2026, 18:32
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.
2 current notices affect this route
Diferencias de predicción por parada
54 in 100 eligible predictions differed from the timetable by more than 5 minutes (98 predictions over 20 days).
Abrir esta parada47 in 100 eligible predictions differed from the timetable by more than 5 minutes (140 predictions over 20 days).
Abrir esta parada45 in 100 eligible predictions differed from the timetable by more than 5 minutes (98 predictions over 20 days).
Abrir esta parada43 in 100 eligible predictions differed from the timetable by more than 5 minutes (140 predictions over 20 days).
Abrir esta paradaSon 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.
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.
Revisión de cambios de 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
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.
Fecha de servicio revisada: 26 de octubre de 2026
Operator calendar-date records: 0 added · 2 removed
Huella digital del feed: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad
Fecha de servicio revisada: 2 de noviembre de 2026
Operator calendar-date records: 0 added · 2 removed
Huella digital del feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
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 17.858 arrivals over 10 days; after has 3603 arrivals over 2 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.
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í.
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.
Resultados provisionales, datos probatorios publicados
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
| Hora | A tiempo | Mediana | Percentil 95 | Pruebas |
|---|---|---|---|---|
| 00:00 | 99,6 % | 0 min late | 1,8 min late | 450 · 10 days |
| 05:00 | 76,9 % | 3,2 min late | 7,5 min late | 363 · 11 days |
| 06:00 | 83,9 % | 1,2 min late | 7,6 min late | 862 · 11 days |
| 07:00 | 75,7 % | 1,9 min late | 12,1 min late | 1208 · 10 days |
| 08:00 | 81,4 % | 1,5 min late | 8,3 min late | 1128 · 10 days |
| 09:00 | 94,6 % | 1 min late | 5,4 min late | 902 · 10 days |
| 10:00 | 97,3 % | 0,4 min late | 4,2 min late | 899 · 10 days |
| 11:00 | 95,2 % | 1 min late | 4,8 min late | 900 · 10 days |
| 12:00 | 97,4 % | 0,9 min late | 3,9 min late | 900 · 10 days |
| 13:00 | 96,1 % | 0,8 min late | 4,8 min late | 901 · 10 days |
| 14:00 | 93,3 % | 0,3 min late | 6,6 min late | 900 · 10 days |
| 15:00 | 93,4 % | 0,1 min early | 4,9 min late | 1085 · 10 days |
| 16:00 | 66,9 % | 2,7 min late | 10,7 min late | 1271 · 10 days |
| 17:00 | 67,3 % | 2,6 min late | 12,9 min late | 1329 · 10 days |
| 18:00 | 73,1 % | 2,4 min late | 12,7 min late | 1240 · 10 days |
| 19:00 | 91,7 % | 1,6 min late | 6,6 min late | 979 · 10 days |
| 20:00 | 85,5 % | 1,2 min late | 5,8 min late | 901 · 10 days |
| 21:00 | 90,8 % | 1,7 min late | 6,7 min late | 878 · 10 days |
| 22:00 | 99,0 % | 1,5 min late | 4,3 min late | 406 · 10 days |
| 23:00 | 100,0 % | 1 min late | 3,7 min late | 426 · 10 days |
2 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
350 / 350 scheduled trips published at least one position across 5 service days (100,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
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 · 70 trips in the retained timetable · retained notices; capture coverage unverified
In short: 70 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.