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 99 trips cancelled now · 5 did not run in novembroCancellations →

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

Rota 99: Barrhaven Centre ⇄ Limebank

A cada 29 a 32 min

Sentido Barrhaven Centre2 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 27 de out. de 2026 – 2 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: 4 trips with qualifying later matching vehicle observations. Trips with any notice: 5.

Trips needing investigation

5 of 501 trips with a usable feed window (1%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

496 with position · 5 to investigate · 0 excluded · 501 scheduled trips

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

Coverage, exclusions and sources

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: 496 / 501 (99%). 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 de nov. de 2026, 11:18

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

83,5%

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

Predictions in the source: 41.423
Weekdays with evidence: 19
Evidence window: 5 de out. de 2026 – 2 de nov. de 2026

The hours we have evidence for

0090% · 504 predictions · 12 days
0583% · 539 predictions · 11 days
0690% · 1.084 predictions · 15 days
0787% · 1.189 predictions · 14 days
0886% · 1.129 predictions · 14 days
0987% · 1.177 predictions · 14 days
1087% · 1.238 predictions · 14 days
1188% · 1.257 predictions · 14 days
1291% · 1.251 predictions · 14 days
1390% · 1.215 predictions · 14 days
1479% · 1.392 predictions · 14 days
1575% · 1.190 predictions · 14 days
1679% · 1.136 predictions · 14 days
1783% · 1.202 predictions · 14 days
1885% · 1.223 predictions · 14 days
1987% · 1.209 predictions · 14 days
2077% · 1.146 predictions · 14 days
2181% · 1.155 predictions · 14 days
2276% · 832 predictions · 14 days
2362% · 463 predictions · 13 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: 3 de nov. de 2026

2 partial-capture days not counted.

What about time of day?

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.

Explore the dated evidence Source of this result

Ônibus chegando juntos

Last 28 days, 6 de outubro de 2026 to 2 de novembro de 2026: 26 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

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

0% of pairs (24) 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
Madrugada (das 4 às 6 h)	102	0% (0)	0% (0)
Pico da manhã (6 às 9 h)	2.775	1% (18)	0% (13)
Meio do dia (9 a.m. a 3 p.m.)	12.396	0% (4)	0% (0)
Pico da tarde (das 3 às 6 da tarde)	3.758	0% (0)	0% (11)
Noite (das 6 às 10 da noite)	7.389	0% (0)	0% (0)
Noite (10 p.m. às 4 a.m.)	1.080	0% (0)	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: BARRHAVEN CENTRE B to NEPEAN WOODS A, 21,4 km/h actual against 17,3 km/h planned.

Onde esta linha é mais lenta
De	Para	Distância	Velocidade planejada	Velocidade real	Trajetos medidos	Trajetos lentos
BARRHAVEN CENTRE B	NEPEAN WOODS A	2,7 km	17,3 km/h	21,4 km/h	873	2%
SPRATT / CANYON WALK	NEPEAN WOODS B	4,7 km	24,3 km/h	22,1 km/h	864	2%
NEPEAN WOODS A	BORBRIDGE / STARGAZER	2,2 km	19,6 km/h	23 km/h	881	2%
LIMEBANK F	SPRATT / CANYON WALK	2,6 km	33,3 km/h	23,9 km/h	861	33%
BORBRIDGE / STARGAZER	SPRATT / CANYON WALK	3,1 km	27,1 km/h	25,7 km/h	881	3%

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
SPRATT between CANYON WALK / GOLDENEYE and HOLLOW TRAIL
6 de out. de 2026, 00:00 to 6 de nov. de 2026, 17:00
SPRATT off-peak lane reductions between CANYON WALK / GOLDENEYE and HOLLOW TRAIL 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:16.

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.

7 scheduled trips with counted cancellation notices from ter., 6 de out. to seg., 2 de nov..

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

Horas com mais cancelamentos: 16 (2), 08 (1), 09 (1)

Últimos trajetos cancelados

qua., 28 de out., scheduled 19:56
qui., 22 de out., scheduled 16:36
qui., 22 de out., scheduled 15:54
ter., 20 de out., scheduled 16:06
seg., 19 de out., scheduled 09:35

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

Did not come (no bus seen, no notice), last 7 days: 5 of 501 trips we could check.

Abrir a análise das previsões com datas

Veredicto

What this route needs

Median provider predictions are 3,9 min later than the timetable in 1 hours of the day.

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

23:00 has 62% of predictions within five minutes of the timetable, against 86% the rest of the day.

Only 99% of scheduled trips were seen; the rest are not counted as missed.

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

00:00: 89,5% of final predictions within five minutes of the timetable, 504 predictions, typically 0,9 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 83,3% of final predictions within five minutes of the timetable, 539 predictions, typically 0,9 min early
06:00: 89,9% of final predictions within five minutes of the timetable, 1.084 predictions, typically 2 min late
07:00: 87,3% of final predictions within five minutes of the timetable, 1.189 predictions, typically 1,7 min late
08:00: 85,7% of final predictions within five minutes of the timetable, 1.129 predictions, typically 1 min late
09:00: 87,1% of final predictions within five minutes of the timetable, 1.177 predictions, typically 1,5 min late
10:00: 87,2% of final predictions within five minutes of the timetable, 1.238 predictions, typically 1,9 min late
11:00: 87,6% of final predictions within five minutes of the timetable, 1.257 predictions, typically 2,2 min late
12:00: 91,4% of final predictions within five minutes of the timetable, 1.251 predictions, typically 0,8 min late
13:00: 89,5% of final predictions within five minutes of the timetable, 1.215 predictions, typically 2,2 min late
14:00: 78,7% of final predictions within five minutes of the timetable, 1.392 predictions, typically 2,2 min late
15:00: 74,5% of final predictions within five minutes of the timetable, 1.190 predictions, typically 2,5 min late
16:00: 78,6% of final predictions within five minutes of the timetable, 1.136 predictions, typically 2 min late
17:00: 82,7% of final predictions within five minutes of the timetable, 1.202 predictions, typically 2,2 min late
18:00: 85,2% of final predictions within five minutes of the timetable, 1.223 predictions, typically 2,3 min late
19:00: 87,3% of final predictions within five minutes of the timetable, 1.209 predictions, typically 1,6 min late
20:00: 76,9% of final predictions within five minutes of the timetable, 1.146 predictions, typically 1,5 min late
21:00: 80,5% of final predictions within five minutes of the timetable, 1.155 predictions, typically 2,2 min late
22:00: 75,6% of final predictions within five minutes of the timetable, 832 predictions, typically 2,5 min late
23:00: 61,6% of final predictions within five minutes of the timetable, 463 predictions, typically 3,9 min late

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	Medido	Scenario or next investigation
ProblemPredictions later than timetable	23:00	3,9 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	23:00	62%	Overnight operations
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 23:00: Measured arrivals 463; Hours affected 1; Spread 6,2 min; Median delay 3,9 min; Suggested running time change 3,9 min
One hour has a lower prediction match · 23:00: Hora 23:00; Pontual 61,6%; Measured arrivals 463; Shortfall 23,9 pts; Route median on time 85,5%
Coverage gap · All measured hours: Meta 99,5%; Trips with a matching position 99%; Dias de serviço 6; Trips with a matching position 496; Viagens programadas 501

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

Verificação da linha

How route 99 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 operador ficaram quase sempre perto do horário previsto, mas veja abaixo os horários com problema.

84 in 100 eligible predictions were within 5 minutes of the timetable · 41.423 predictions checked

Tamanho da amostra de previsão: Amostra maior

Based on 41.423 eligible provider predictions over 27 measured days, from 5 de out. de 2026 to 2 de nov. de 2026.

Updated 3 de nov. de 2026, 11: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.

23–00: 38 in 100 eligible predictions differed from the timetable by more than 5 minutes (463 predictions over 13 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

BEATRICE B
33 in 100 eligible predictions differed from the timetable by more than 5 minutes (986 predictions over 30 days).
Abrir esta parada
MARKETPLACE / RIOCAN
32 in 100 eligible predictions differed from the timetable by more than 5 minutes (1.013 predictions over 30 days).
Abrir esta parada
NEPEAN WOODS B
30 in 100 eligible predictions differed from the timetable by more than 5 minutes (986 predictions over 30 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 12Verifica 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?: 5 of 501 checked trips need a closer look5 of 501 trips with enough public-feed evidence had no matching position over 7 days. 0 of 501 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 8,3 min (positive means later; negative means earlier)84 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: 76
Paradas previstas distintas: 54
Percursos publicados distintos: 4
Período de serviço publicado: 5:26–0:52 next day

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: 76
Paradas previstas distintas: 54
Percursos publicados distintos: 4
Período de serviço publicado: 5:26–0:52 next day

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 21.431 arrivals over 14 days; after has 6.057 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: 5 de outubro de 2026 to 2 de novembro de 2026

Até 5 minutos do horário programado: 83,5%
Previsões elegíveis verificadas: 41.423
Dias úteis com dados: 19
Atraso previsto no percentil 95: 8,3 min late

Patterns by hour (20)

Patterns by hour (20)
Hora	Pontual	Mediana	Percentil 95	Evidências
00:00	89,5%	0,9 min late	2,9 min late	504 · 12 days
05:00	83,3%	0,9 min early	7,4 min late	539 · 11 days
06:00	89,9%	2 min late	6,3 min late	1.084 · 15 days
07:00	87,3%	1,7 min late	6,8 min late	1.189 · 14 days
08:00	85,7%	1 min late	9,7 min late	1.129 · 14 days
09:00	87,1%	1,5 min late	6,3 min late	1.177 · 14 days
10:00	87,2%	1,9 min late	6,2 min late	1.238 · 14 days
11:00	87,6%	2,2 min late	7 min late	1.257 · 14 days
12:00	91,4%	0,8 min late	5,8 min late	1.251 · 14 days
13:00	89,5%	2,2 min late	5,8 min late	1.215 · 14 days
14:00	78,7%	2,2 min late	10,8 min late	1.392 · 14 days
15:00	74,5%	2,5 min late	10,6 min late	1.190 · 14 days
16:00	78,6%	2 min late	10,1 min late	1.136 · 14 days
17:00	82,7%	2,2 min late	9,7 min late	1.202 · 14 days
18:00	85,2%	2,3 min late	7 min late	1.223 · 14 days
19:00	87,3%	1,6 min late	6,6 min late	1.209 · 14 days
20:00	76,9%	1,5 min late	11 min late	1.146 · 14 days
21:00	80,5%	2,2 min late	9,1 min late	1.155 · 14 days
22:00	75,6%	2,5 min late	11,3 min late	832 · 14 days
23:00	61,6%	3,9 min late	10,1 min late	463 · 13 days

1 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

496 / 501 scheduled trips published at least one position across 6 service days (99,0%).

05:001 / 15 trips without a position93,3%
08:001 / 26 trips without a position96,2%
09:001 / 28 trips without a position96,4%
10:001 / 28 trips without a position96,4%
07:001 / 29 trips without a position96,6%
00:000 / 12 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 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026 October 27, 2026

November 2, 2026 · 76 trips in the retained timetable · retained notices; capture coverage unverified

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

05:26– 05:55
Trip 16646020Vehicle position matchedFirst / last feed position: 4:57 a.m. EST / 5:55 a.m. EST; not actual start or end times.
05:31– 05:51
Trip 26587020Vehicle position matchedFirst / last feed position: 5:26 a.m. EST / 5:48 a.m. EST; not actual start or end times.
05:51– 06:20
Trip 4618020Vehicle position matchedFirst / last feed position: 5:35 a.m. EST / 6:29 a.m. EST; not actual start or end times.
06:01– 06:24
Trip 23693020Vehicle position matchedFirst / last feed position: 5:56 a.m. EST / 6:23 a.m. EST; not actual start or end times.
06:26– 06:57
Trip 36624020Vehicle position matchedFirst / last feed position: 6:24 a.m. EST / 7:02 a.m. EST; not actual start or end times.
06:35– 06:58
Trip 19717020Vehicle position matchedFirst / last feed position: 6:30 a.m. EST / 7:04 a.m. EST; not actual start or end times.
06:56– 07:27
Trip 13447020Vehicle position matchedFirst / last feed position: 6:46 a.m. EST / 7:27 a.m. EST; not actual start or end times.
07:01– 07:26
Trip 24298020Vehicle position matchedFirst / last feed position: 6:57 a.m. EST / 7:28 a.m. EST; not actual start or end times.
07:28– 08:03
Trip 27483020Vehicle position matchedFirst / last feed position: 7:29 a.m. EST / 8:06 a.m. EST; not actual start or end times.
07:29– 07:40
Trip 19877020Vehicle position matchedFirst / last feed position: 7:09 a.m. EST / 7:40 a.m. EST; not actual start or end times.
07:33– 08:00
Trip 31624020Vehicle position matchedFirst / last feed position: 6:47 a.m. EST / 8:02 a.m. EST; not actual start or end times.
07:56– 08:31
Trip 13418020Vehicle position matchedFirst / last feed position: 7:42 a.m. EST / 8:29 a.m. EST; not actual start or end times.

· Open all evidence for this day