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

No 198 trips cancelled now · 0 did not run in novembroCancellations →

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

198

Rota 198: Limebank ⇄ Greenboro

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 29 de out. de 2026 – 4 de nov. de 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 de nov. de 2026, 03: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 de nov. de 2026, 03: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: 6.081
Weekdays with evidence: 18
Evidence window: 6 de out. de 2026 – 3 de nov. de 2026

The hours we have evidence for

05100% · 33 predictions · 11 days
0684% · 704 predictions · 11 days
0791% · 627 predictions · 11 days
0895% · 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 de nov. de 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

Ônibus chegando juntos

Last 28 days, 8 de outubro de 2026 to 4 de novembro de 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 de outubro de 2026, 15 de outubro de 2026.

Valores e interpretação

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.

Ônibus chegando juntos
Hora do dia	Pares verificados	Agrupados	Intervalo longo
Pico da tarde (das 3 às 6 da tarde)	482	4% (17)	0% (0)

Como isso é medido →How we got this numberComboios de ônibus e pontos lentos em todas as linhas →

Onde esta linha é mais lenta

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

Onde esta linha é mais lenta
De	Para	Distância	Velocidade planejada	Velocidade real	Trajetos medidos	Trajetos 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%

Um trajeto lento levou pelo menos 1.5 vez o tempo previsto.

Como isso é medido →

Obras viárias da cidade perto desta linha

Obras e fechamentos de vias por eventos publicados pela Cidade de Ottawa, medidos como próximos ao percurso desta linha. Próximo não prova que o ônibus tem desvio. Para isso, veja os alertas do próprio operador.

Obras na via
Ralph Hennessy between Markdale and Earl Armstrong
6 de out. de 2026, 00:00 to 6 de nov. de 2026, 17:00
Ralph Hennessy off-peak lane reductions between Markdale and Earl Armstrong due to construction, from October 6th to November 6th.
A Cidade indica que isto afeta o transporte coletivo.
about 0 m from the route
City record updated 9 de out. de 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.

Fonte: eventos de trânsito da Cidade de Ottawa (obras viárias e bloqueios). Contém informações licenciadas sob a Open Government Licence, City of Ottawa. A Cidade informa que esta lista é feita com o melhor esforço e pode estar incompleta. Mapa de trânsito da Cidade de Ottawa ↗

Cancelamentos nesta linha

O que estas palavras significam →

2 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from qui., 8 de out. to qua., 4 de nov..

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

Horas com mais cancelamentos: 15 (1)

Últimos trajetos cancelados

qua., 21 de out., scheduled 15:37

A OC Transpo não informa o motivo de viagens individuais, por isso nenhum é mostrado.

Não passou (nenhum ônibus visto, nenhum aviso), nos últimos 7 dias: nenhum dos trajetos que pudemos verificar.

Abrir a análise das previsões com datas

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	Quando	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 1.860; 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; Pontual 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%; Dias de serviço 5; Trips with a matching position 55; Viagens programadas 55

Abrir histórico, fiabilidade e análise da rota

Verificação da linha

How route 198 has been running

Um resumo curto do que sabemos. Dizemos isso quando não podemos responder a uma pergunta.

Em resumo

As previsões do provedor muitas vezes diferiram do horário previsto. As chegadas reais não foram medidas de forma independente.

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

Tamanho da amostra de previsão: Amostra maior

Based on 6.081 eligible provider predictions over 18 measured days, from 6 de out. de 2026 to 3 de nov. de 2026.

Updated 5 de nov. de 2026, 02:32

Onde e quando as previsões diferiram repetidamente?

Estas são diferenças repetidas entre a previsão e o horário, não falhas de serviço medidas de forma independente. Usam as mesmas previsões elegíveis do resultado acima, mas agrupam por parada, e não por hora. Por isso, as listas podem não coincidir linha por linha.

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

Diferenças de previsão 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

São previsões do fornecedor específicas da linha, comparadas com o horário. Elas mostram diferenças repetidas de previsão em um lugar e horário, não chegadas medidas nem a causa delas.

Verificar cada viagem e data

Abra um período para ver cada dia de serviço, trajeto previsto no horário, falha nos dados, ID público de veículo observado e os números exatos por trás deste resumo.

O que os passageiros querem saber

Alguma viagem está cancelada agora?: 0 of 5Verifica as viagens que começam nos terminais da linha nas próximas 4 horas. Não é uma taxa histórica de cancelamento.
Possíveis faltas de ônibus após verificar falhas no feed?: 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.
Como as previsões do fornecedor diferiram do horário?: 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.
Qual espera as previsões do provedor indicavam?: Nenhum resultado por linha atinge ainda o limite de dados probantes. Isso não significa que não houve falhas.

Verificação da mudança de horário

Horário publicado: antes e depois

Isto compara o horário oficial atual guardado com a versão anterior guardada. As mudanças de horário são fatos sobre o que foi planejado. Elas não provam que um trajeto foi realizado.

Current published schedule began 30 de outubro de 2026

Dia de serviço selecionado em cada horário publicado

Verificamos a primeira segunda-feira depois do início do novo horário e a segunda-feira uma semana antes. Todos os números vêm das versões oficiais do GTFS guardadas, indicadas abaixo.

Pelo menos uma data escolhida tem serviço incluído ou removido por data do calendário. Considere isso como contexto de feriado ou de serviço especial, não como aumento normal de dia útil.

Antes

Data de serviço verificada: 26 de outubro de 2026

Viagens programadas: 11
Paradas previstas distintas: 66
Percursos publicados distintos: 2
Período de serviço publicado: 5:57–18:56

Operator calendar-date records: 0 added · 2 removed

Impressão digital do feed: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

Novo horário

Data de serviço verificada: 2 de novembro de 2026

Viagens programadas: 11
Paradas previstas distintas: 66
Percursos publicados distintos: 2
Período de serviço publicado: 5:57–18:56

Operator calendar-date records: 0 added · 2 removed

Impressão digital do feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

O serviço melhorou depois da mudança?

Vamos comparar as chegadas confirmadas nos 14 dias antes e depois da mudança. Só publicamos a comparação quando os dois períodos tiverem pelo menos 7 dias de serviço e 200 chegadas.

Still collecting: before has 3.284 arrivals over 10 days; after has 1.331 arrivals over 4 days. No improvement or decline is claimed yet.

Os checksums permitem que qualquer pessoa verifique qual horário guardado gerou as contagens. Uma contagem alterada não indica a causa, um cancelamento, uma decisão da operadora ou um impacto para os passageiros.

Como esta linha é avaliada: Linha regular com todas as paradas

Comparamos a última previsão válida do provedor para cada chegada prevista no horário com o horário oficial. Não são chegadas medidas de forma independente. Um resultado precisa de pelo menos 200 previsões válidas. Dentro de 5 minutos é a meta usada aqui, do ponto de vista do passageiro.

O que estes dados não podem provar

Os dados públicos não trazem contagens confiáveis de passageiros nem registros de passageiros deixados na parada. A falta de uma posição não prova, por si só, um cancelamento, uma ausência de viagem, um retorno antecipado ou uma causa.

Veja as definições, os limites e a ordem dos dados probantes

Feed oficial atual: cancelamentos explícitos, paradas puladas e avisos ativos.
Observações correspondentes: posições de veículos e previsões consolidadas ligadas ao horário oficial.
Horário oficial: o que foi planejado, separado do que foi observado.
Relatos de passageiros e de exploradores: pistas sobre linhas, horários e locais a investigar, não prova numérica por si só.

Resultados provisórios, dados probantes publicados

Como as previsões se compararam com o horário?

A cada hora, comparamos a última previsão válida do provedor para uma chegada prevista no horário com o quadro de horários. “Em até 5 minutos” descreve a diferença entre as previsões. Não é uma chegada medida nem prova de que um ônibus circulou.

Período dos dados probantes: 6 de outubro de 2026 to 3 de novembro de 2026

Até 5 minutos do horário programado: 65,0%
Previsões elegíveis verificadas: 6.081
Dias úteis com dados: 18
Atraso previsto no percentil 95: 18,1 min late

Patterns by hour (8)

Patterns by hour (8)
Hora	Pontual	Mediana	Percentil 95	Evidências
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.

Ônibus previsto no horário, mas não observado em tempo 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%

Isto não é uma falta confirmada. Uma posição ausente pode indicar um ônibus cancelado ou perdido. Também pode indicar um ID de trajeto não atribuído ou uma falha no feed da operadora. O Otranspo publica essa lacuna porque ela importa para os passageiros, sem tirar conclusões que os dados não permitem.

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. Fontes e limitações.

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.