Limebank Station: Passenger pick-up and drop-off area relocation: December 12 2025 - At 10:00 am on Thursday, December 18, Town Square Road and the connector road at Limebank Station will re-open to general traffic. As a result, the temporarily-relocated passenger pick-up and drop-off zone will be moved back to its original location, on the north side of Limebank Station. Customers are reminded to use the designated pedestrian crossing zones when travelling between the O-Train station and the passenger pick-up and drop-off area. Routes 70, 73, 74, 99, 110, 198, 283, 299 will continue to follow a detour by entering and exiting Limebank Station via Limebank Road. Detour routing 99 Limebank: From Limebank, right onto Limebank Station Bus Only Roadway, Loop around bus loop, right onto Connector Roadway, continue regular route (and regular service stops within Limebank Station). 99 Barrhaven Centre: From Limebank Station, loop around bus loop, right onto Connector Roadway, left onto Limebank, continue regular route. 110 Limebank: From Earl Armstrong, right onto Limebank, right onto Limebank Station Bus Only Roadway, Loop around bus loop, right onto Connector Roadway, continue regular route (and regular service stops within Limebank Station). 110 Innovation: No detour required. 70, 73, 74, 198, 283, 299 Limebank: From Earl Armstrong, right onto Limebank, right onto Limebank Station Bus Only Roadway, Loop around bus loop, right onto Connector Roadway, continue regular route (and regular service stops within Limebank Station). 70, 73, 74, 198, 283, 299 Outbound trips: From Limebank Station, loop around bus loop, right onto Connector Roadway, left onto Limebank, left onto Earl Armstrong, continue regular route. Maps (effective December 18)+1 aviso más

No 198 trips cancelled now · 0 no circularon en noviembreCancellations →

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

198

Ruta 198: Limebank ⇄ Greenboro

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 29 oct 2026 – 4 nov 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: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 1.

Trips needing investigation

0 of 55 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.

55 with position · 0 to investigate · 0 excluded · 55 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 5 nov 2026, 3:56.

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: 55 / 55 (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: 5 nov 2026, 3: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.

What does the evidence show?

Predictions against the timetable

65%

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

Predictions in the source: 6081
Weekdays with evidence: 18
Evidence window: 6 oct 2026 – 3 nov 2026

The hours we have evidence for

5100 % · 33 predictions · 11 days
684 % · 704 predictions · 11 days
791 % · 627 predictions · 11 days
895 % · 407 predictions · 11 days
1521 % · 248 predictions · 11 days
1650 % · 532 predictions · 11 days
1736 % · 660 predictions · 11 days
1853 % · 420 predictions · 9 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: 5 nov 2026

2 partial-capture days not counted.

What about time of day?

8 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

Autobuses que llegan juntos

Últimos 28 días, del 8 de octubre de 2026 al 4 de noviembre de 2026: 25 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.

Valores e interpretación

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

0 % of pairs (0) had a long gap: more than 1.75 times the planned wait between them.

Autobuses que llegan juntos
Hora del día	Pares comprobados	Agrupados	Intervalo largo
Hora punta de la tarde (de 3 a 6 p. m.)	482	4 % (17)	0 % (0)

Cómo se mide esto →Cómo llegamos a esta cifraAgrupamientos y puntos lentos en cada ruta →

Dónde es más lenta esta ruta

Slowest: LIMEBANK A to RIVERVIEW B, 19,3 km/h actual against 30,8 km/h planned.

Dónde es más lenta esta ruta
Desde	Hasta	Distancia	Velocidad planificada	Velocidad real	Trayectos medidos	Viajes lentos
LIMEBANK A	RIVERVIEW B	2,6 km	30,8 km/h	19,3 km/h	92	53 %
SOUTH KEYS E	RIVERSIDE / HUNT CLUB	3,9 km	21,8 km/h	20,5 km/h	76	11 %
GREENBORO B	SOUTH KEYS E	830 m	20,9 km/h	24,1 km/h	65	11 %
RIVERVIEW B	RIVER / LEITRIM	2,7 km	27,3 km/h	26,3 km/h	92	5 %
RIVER / LEITRIM	RIVERVIEW A	2,7 km	30,4 km/h	28,3 km/h	76	14 %
HUNT CLUB / RIVERSIDE	SOUTH KEYS A	4,1 km	31 km/h	29,9 km/h	89	3 %
RIVER / LEITRIM	HUNT CLUB / RIVERSIDE	4,8 km	28,5 km/h	40,7 km/h	91	3 %
RIVERSIDE / HUNT CLUB	RIVER / LEITRIM	4,8 km	53,3 km/h	51,4 km/h	76	7 %

Un viaje lento duró al menos 1.5 veces el tiempo previsto.

Cómo se mide esto →

Obras viales de la ciudad cerca de esta ruta

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
Ralph Hennessy between Markdale and Earl Armstrong
6 oct 2026, 0:00 to 6 nov 2026, 17:00
Ralph Hennessy off-peak lane reductions between Markdale and Earl Armstrong due to construction, from October 6th to November 6th.
La Ciudad indica que esto afecta al transporte público.
about 0 m from the route
City record updated 9 oct 2026, 10:24.

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 ↗

Cancelaciones en esta ruta

Qué significan estas palabras →

2 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from jue, 8 oct to mié, 4 nov.

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

Horas con más cancelaciones: 15 (1)

Últimos viajes cancelados

mié, 21 oct, scheduled 15:37

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.

Abre el análisis de predicciones con fechas

Veredicto

What this route needs

Median provider predictions are 6,2 min later than the timetable in 4 hours of the day.

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

Wide prediction spread 18:00: the 95th percentile is 20,2 min later than the median.

15:00 has 21% of predictions within five minutes of the timetable, against 68% 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.

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, 8 hours with samples

00:00: not enough data
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 100% of final predictions within five minutes of the timetable, 33 predictions, typically 1,3 min late
06:00: 83,5% of final predictions within five minutes of the timetable, 704 predictions, typically 2,3 min late
07:00: 91,1% of final predictions within five minutes of the timetable, 627 predictions, typically 1,7 min late
08:00: 95,1% of final predictions within five minutes of the timetable, 407 predictions, typically 0,3 min late
09:00: not enough data
10:00: not enough data
11:00: not enough data
12:00: not enough data
13:00: not enough data
14:00: not enough data
15:00: 21% of final predictions within five minutes of the timetable, 248 predictions, typically 11,3 min late
16:00: 50,2% of final predictions within five minutes of the timetable, 532 predictions, typically 5 min late
17:00: 35,5% of final predictions within five minutes of the timetable, 660 predictions, typically 7,5 min late
18:00: 52,6% of final predictions within five minutes of the timetable, 420 predictions, typically 4,6 min late. Provider predictions have a wide spread.
19:00: not enough data
20:00: not enough data
21:00: not enough data
22:00: not enough data
23:00: not enough data

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
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	Cuándo	Medido	Scenario or next investigation
ProblemPredictions later than timetable	15:00 to 19:00	6,2 min late	Recovery time at the terminal
ProblemWide prediction spread	18:00	20,2 min swing	Operations, not the timetable
ProblemOne hour has a lower prediction match	15:00	21 %	Operations, not the timetable
StrengthObserved-position lower bound	All measured hours	100 %	Keep what works

Measurements

Predictions later than timetable · 15:00 to 19:00: Measured arrivals 1860; Hours affected 4; Spread 13,1 min; Median delay 6,2 min; Suggested running time change 6,2 min
Wide prediction spread · 18:00: Measured arrivals 420; Hours affected 1; Spread 20,2 min; Median delay 4,6 min; Suggested running time change 4,6 min
One hour has a lower prediction match · 15:00: Hora 15:00; A tiempo 21%; Measured arrivals 248; Shortfall 47,1 pts; Route median on time 68,1%
Observed-position lower bound · All measured hours: Meta 99,5%; Trips with a matching position 100%; Días de servicio 5; Trips with a matching position 55; Trayectos programados 55

Abrir historial, fiabilidad y análisis de la ruta

Revisión de ruta

How route 198 has been running

Un resumen breve de lo que sabemos. Lo decimos cuando no podemos responder una pregunta.

En resumen

Las predicciones del proveedor a menudo diferían del horario. Las llegadas reales no se midieron de forma independiente.

65 in 100 eligible predictions were within 5 minutes of the timetable · 6081 predictions checked

Tamaño de la muestra de predicción: Muestra más grande

Based on 6081 eligible provider predictions over 18 measured days, from 6 oct 2026 to 3 nov 2026.

Updated 5 nov 2026, 2: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.

15–16: 79 in 100 eligible predictions differed from the timetable by more than 5 minutes (248 predictions over 11 days).
17–18: 65 in 100 eligible predictions differed from the timetable by more than 5 minutes (660 predictions over 11 days).
16–17: 50 in 100 eligible predictions differed from the timetable by more than 5 minutes (532 predictions over 11 days).
18–19: 47 in 100 eligible predictions differed from the timetable by more than 5 minutes (420 predictions over 9 days).

2 current notices affect this route

• Limebank Station: Passenger pick-up and drop-off area relocation
• Detour: Routes entering and exiting Limebank Station

Diferencias de predicción por parada

RIVER / SHORELINE PATHWAY
71 in 100 eligible predictions differed from the timetable by more than 5 minutes (117 predictions over 20 days).
Abrir esta parada
RIVER / AD. 540
68 in 100 eligible predictions differed from the timetable by more than 5 minutes (117 predictions over 20 days).
Abrir esta parada
RIVER / HONEY GABLES
65 in 100 eligible predictions differed from the timetable by more than 5 minutes (117 predictions over 20 days).
Abrir esta parada
RIVER / RYEBURN
64 in 100 eligible predictions differed from the timetable by more than 5 minutes (117 predictions over 20 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 5Revisa 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?: 0 of 55 checked trips need a closer look0 of 55 trips with enough public-feed evidence had no matching position over 7 days. 0 of 55 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?: At the 95th percentile, the predicted difference was 18,1 min (positive means later; negative means earlier)65 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
¿Qué espera implicaban las predicciones del proveedor?: Todavía ningún resultado por ruta cumple el umbral de datos probantes. Esto no significa que no hubo interrupciones.

Revisión de cambios de horario

Horario publicado: antes y después

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.

Antes

Fecha de servicio revisada: 26 de octubre de 2026

Trayectos programados: 11
Paradas programadas distintas: 66
Recorridos publicados distintos: 2
Horario de servicio publicado: 5:57–18:56

Operator calendar-date records: 0 added · 2 removed

Huella digital del feed: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

Nuevo horario

Fecha de servicio revisada: 2 de noviembre de 2026

Trayectos programados: 11
Paradas programadas distintas: 66
Recorridos publicados distintos: 2
Horario de servicio publicado: 5:57–18:56

Operator calendar-date records: 0 added · 2 removed

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 3284 arrivals over 10 days; after has 1331 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: 6 de octubre de 2026 to 3 de noviembre de 2026

Dentro de 5 minutos del horario: 65,0 %
Predicciones válidas revisadas: 6081
Días laborables con datos: 18
Retraso previsto del percentil 95: 18,1 min late

Patterns by hour (8)

Patterns by hour (8)
Hora	A tiempo	Mediana	Percentil 95	Pruebas
05:00	100,0 %	1,3 min late	3,8 min late	33 · 11 days
06:00	83,5 %	2,3 min late	7,1 min late	704 · 11 days
07:00	91,1 %	1,7 min late	5,9 min late	627 · 11 days
08:00	95,1 %	0,3 min late	4,6 min late	407 · 11 days
15:00	21,0 %	11,3 min late	16,9 min late	248 · 11 days
16:00	50,2 %	5 min late	13,6 min late	532 · 11 days
17:00	35,5 %	7,5 min late	25,1 min late	660 · 11 days
18:00	52,6 %	4,6 min late	24,8 min late	420 · 9 days

4 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

55 / 55 scheduled trips published at least one position across 5 service days (100,0%).

05:000 / 5 trips without a position100,0 %
06:000 / 10 trips without a position100,0 %
07:000 / 10 trips without a position100,0 %
15:000 / 5 trips without a position100,0 %
16:000 / 10 trips without a position100,0 %
17:000 / 10 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.

Service day

November 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

November 4, 2026 · 11 trips in the retained timetable · retained notices; capture coverage unverified

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

05:57– 06:20
Trip 12749040Vehicle position matchedFirst / last feed position: 5:27 a.m. EST / 6:48 a.m. EST; not actual start or end times.
06:44– 07:13
Trip 7831040Vehicle position matchedFirst / last feed position: 6:30 a.m. EST / 7:42 a.m. EST; not actual start or end times.
06:48– 07:13
Trip 12264040Vehicle position matchedFirst / last feed position: 6:49 a.m. EST / 7:29 a.m. EST; not actual start or end times.
07:43– 08:16
Trip 28012040Vehicle position matchedFirst / last feed position: 7:34 a.m. EST / 8:25 a.m. EST; not actual start or end times.
07:48– 08:20
Trip 15143040Vehicle position matchedFirst / last feed position: 7:43 a.m. EST / 8:20 a.m. EST; not actual start or end times.
15:37– 16:09
Trip 34447040Vehicle position matchedFirst / last feed position: 3:25 p.m. EST / 4:24 p.m. EST; not actual start or end times.
16:06– 16:38
Trip 11881040Vehicle position matchedFirst / last feed position: 3:43 p.m. EST / 4:41 p.m. EST; not actual start or end times.
16:44– 17:17
Trip 6054040Vehicle position matchedFirst / last feed position: 4:19 p.m. EST / 5:28 p.m. EST; not actual start or end times.
17:08– 17:40
Trip 36020040Vehicle position matchedFirst / last feed position: 4:48 p.m. EST / 5:40 p.m. EST; not actual start or end times.
17:45– 18:17
Trip 10364040Vehicle position matchedFirst / last feed position: 5:18 p.m. EST / 6:18 p.m. EST; not actual start or end times.
18:24– 18:56
Trip 35953040Vehicle position matchedFirst / last feed position: 6:19 p.m. EST / 6:52 p.m. EST; not actual start or end times.