Stop impacts: #4036 -- Holly Acres (south-side) / Ramp temporary relocation: October 30 2026 - From 11:00 pm on Monday, November 2, until 11:00 pm on Friday, December 4, stop #4036 -- Holly Acres (south-side) / Ramp will be temporarily relocated 120 metres closer to Richmond Road due to construction work near the Highway 417 off-ramp. There will be no detours, but the routes below will be impacted by the stop relocation: 57 Carling Campus ~ Complexe Carling 60 Terry Fox / Tunney's Pasture 61 Tunney's Pasture & N Rideau 62 Tunney's Pasture 63 Tunney's Pasture 66 Tunneys Pasture 67 Terry Fox / Tunney's Pasture 88 Hurdman 261 Tunney's Pasture 262 Tunney's Pasture 263 Tunney's Pasture 265 Tunney's Pasture 266 Tunney's Pasture+1 more notice

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

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

Rota 60: Cope ⇄ Terry Fox / Tunney's Pasture

A cada 30 min

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

TERRY FOX 3C5 min sched.
LORD BYNG / KANATA9 min
CASTLEFRANK / AIRD10 min
CASTLEFRANK / KATIMAVIK11 min
CASTLEFRANK / MCCURDY11 min
CASTLEFRANK / KAKULU12 min
CASTLEFRANK / HUNGERFORD12 min
CASTLEFRANK / MCCURDY12 min
CASTLEFRANK / MACNEIL13 min
CASTLEFRANK / HAZELDEAN13 min
CASTLEFRANK / WINCHESTER14 min
CASTLEFRANK / MCKITRICK15 min
CASTLEFRANK / ABBEYHILL15 min
CASTLEFRANK / AD. 11416 min
CASTLEFRANK / SHELDRAKE16 min
CASTLEFRANK / GLAMORGAN17 min
TERRY FOX / ABBOTT18 min
TERRY FOX / WESTPHALIAN19 min
FERNBANK / TERRY FOX21 min
ROMINA / OPUS21 min
ROMINA / BRIGITTA22 min
EAGLESON / FERNBANK23 min
EAGLESON / CADENCE23 min
EAGLESON / CADENCE24 min
MICHAEL COWPLAND / TERRENCE MATHEWS21 min sched.

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 28 de out. de 2026 – 3 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: 11 trips with qualifying later matching vehicle observations. Trips with any notice: 11.

Trips needing investigation

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: 4 de nov. de 2026, 23:57.

Coverage, exclusions and sources

0 of 2 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: 4 de nov. de 2026, 23:09

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

87,5%

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

Predictions in the source: 32.160
Weekdays with evidence: 18
Evidence window: 6 de out. de 2026 – 3 de nov. de 2026

The hours we have evidence for

00100% · 450 predictions · 10 days
0580% · 363 predictions · 11 days
0685% · 934 predictions · 11 days
0781% · 1.332 predictions · 11 days
0882% · 1.242 predictions · 11 days
0995% · 992 predictions · 11 days
1096% · 989 predictions · 11 days
1194% · 990 predictions · 11 days
1297% · 990 predictions · 11 days
1397% · 990 predictions · 11 days
1494% · 990 predictions · 11 days
1594% · 1.194 predictions · 11 days
1667% · 1.398 predictions · 11 days
1765% · 1.463 predictions · 11 days
1874% · 1.364 predictions · 11 days
1988% · 1.077 predictions · 11 days
2087% · 991 predictions · 11 days
2192% · 968 predictions · 11 days
2294% · 451 predictions · 11 days
23100% · 458 predictions · 11 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?

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, 7 de outubro de 2026 to 3 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: 28 of 21.312 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.

Ônibus chegando juntos
Hora do dia	Pares verificados	Agrupados	Intervalo longo
Pico da manhã (6 às 9 h)	2.795	0% (0)	0% (0)
Meio do dia (9 a.m. a 3 p.m.)	7.897	0% (0)	0% (0)
Pico da tarde (das 3 às 6 da tarde)	4.070	0% (19)	0% (0)
Noite (das 6 às 10 da noite)	5.856	0% (7)	0% (2)
Noite (10 p.m. às 4 a.m.)	694	0% (2)	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: PINECREST B to LINCOLN FIELDS 2A, 18 km/h actual against 11 km/h planned.

Onde esta linha é mais lenta
De	Para	Distância	Velocidade planejada	Velocidade real	Trajetos medidos	Trajetos lentos
PINECREST B	LINCOLN FIELDS 2A	1,8 km	11 km/h	18 km/h	82	0%
TERRY FOX 3C	CASTLEFRANK / MCCURDY	3 km	29,9 km/h	19 km/h	119	62%
EAGLESON C	TERRY FOX 3C	2,8 km	17,3 km/h	20,3 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,5 km/h	458	1%
CASTLEFRANK / MACNEIL	FERNBANK / TERRY FOX	3,9 km	23,3 km/h	24,6 km/h	118	0%
LINCOLN FIELDS 1A	BAYSHORE B	3,1 km	15,6 km/h	24,6 km/h	119	0%
FERNBANK / TERRY FOX	MICHAEL COWPLAND / TERRENCE MATHEWS	2,2 km	66,7 km/h	25,1 km/h	25	68%

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
417 W/B off ramp at Bayshore
29 de abr. de 2026, 06:00 to 31 de dez. de 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.
A Cidade indica que isto afeta o transporte coletivo.
about 17 m from the route
City record updated 28 de ago. de 2026, 13:32.
Obras na via
417 E/B between March and Moodie
27 de out. de 2026, 10:00 to 6 de nov. de 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.
A Cidade indica que isto afeta o transporte coletivo.
about 0 m from the route
City record updated 3 de nov. de 2026, 07:08.
Obras na via
CARLING E/B between Kichi Zibi Mikan on Ramp and EDGEWORTH
30 de out. de 2026, 00:00 to 13 de nov. de 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 de out. de 2026, 11:40.
Obras na via
Kichi Zibi Mikan between ISLAND PARK and WOODROFFE
30 de out. de 2026, 09:30 to 20 de nov. de 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 de out. de 2026, 09:28.
Obras na via
CORKSTOWN between MOODIE and MARCH
31 de out. de 2026, 09:30 to 5 de nov. de 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 de out. de 2026, 09:28.
Obras na via
Moodie S/B at 417 overpass
2 de nov. de 2026, 06:00 to 9 de nov. de 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.
A Cidade indica que isto afeta o transporte coletivo.
about 0 m from the route
City record updated 2 de nov. de 2026, 13:12.
Obras na via
COPE between TERRY FOX and TEMPLEFORD
3 de nov. de 2026, 07:00 to 16 de nov. de 2026, 17:00
COPE closed between TERRY FOX and TEMPLEFORD due to construction, from November 6th to 16th. Follow the signed detour.
A Cidade indica que isto afeta o transporte coletivo.
about 0 m from the route
City record updated 3 de nov. de 2026, 06: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.

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.

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

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

Horas com mais cancelamentos: 19 (1), 20 (1)

Últimos trajetos cancelados

sex., 9 de out., scheduled 20:00
qua., 7 de out., scheduled 19:33

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

17:00 has 65% 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.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 20 hours with samples

00:00: 99,6% of final predictions within five minutes of the timetable, 450 predictions, typically 0 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 79,9% of final predictions within five minutes of the timetable, 363 predictions, typically 2,6 min late
06:00: 85,3% of final predictions within five minutes of the timetable, 934 predictions, typically 1,3 min late
07:00: 80,5% of final predictions within five minutes of the timetable, 1.332 predictions, typically 1,5 min late
08:00: 81,8% of final predictions within five minutes of the timetable, 1.242 predictions, typically 1,7 min late
09:00: 95,1% of final predictions within five minutes of the timetable, 992 predictions, typically 0,8 min late
10:00: 96,1% of final predictions within five minutes of the timetable, 989 predictions, typically 0,6 min late
11:00: 94% of final predictions within five minutes of the timetable, 990 predictions, typically 1 min late
12:00: 97,3% of final predictions within five minutes of the timetable, 990 predictions, typically 1 min late
13:00: 96,5% of final predictions within five minutes of the timetable, 990 predictions, typically 0,8 min late
14:00: 93,9% of final predictions within five minutes of the timetable, 990 predictions, typically 0,3 min late
15:00: 93,6% of final predictions within five minutes of the timetable, 1.194 predictions, typically 0,1 min early
16:00: 66,7% of final predictions within five minutes of the timetable, 1.398 predictions, typically 2,8 min late
17:00: 65% of final predictions within five minutes of the timetable, 1.463 predictions, typically 2,6 min late
18:00: 73,5% of final predictions within five minutes of the timetable, 1.364 predictions, typically 2,3 min late
19:00: 88,3% of final predictions within five minutes of the timetable, 1.077 predictions, typically 2 min late
20:00: 86,8% of final predictions within five minutes of the timetable, 991 predictions, typically 1,2 min late
21:00: 92,1% of final predictions within five minutes of the timetable, 968 predictions, typically 1,7 min late
22:00: 93,8% of final predictions within five minutes of the timetable, 451 predictions, typically 1,5 min late
23:00: 100% of final predictions within five minutes of the timetable, 458 predictions, typically 1 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
ProblemOne hour has a lower prediction match	17:00	65%	Operations, not the timetable
StrengthObserved-position lower bound	All measured hours	100%	Keep what works

Measurements

One hour has a lower prediction match · 17:00: Hora 17:00; Pontual 65%; Measured arrivals 1.463; Shortfall 27,8 pts; Route median on time 92,9%
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 350; Viagens programadas 350

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

Verificação da linha

How route 60 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.

88 in 100 eligible predictions were within 5 minutes of the timetable · 32.160 predictions checked

Tamanho da amostra de previsão: Amostra maior

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

Updated 4 de nov. de 2026, 23: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.

17–18: 35 in 100 eligible predictions differed from the timetable by more than 5 minutes (1.463 predictions over 11 days).
16–17: 33 in 100 eligible predictions differed from the timetable by more than 5 minutes (1.398 predictions over 11 days).

2 current notices affect this route

• Stop impacts: #4036 -- Holly Acres (south-side) / Ramp temporary relocation
• Stop impacts: #3019 -- Pinecrest A and B relocation

Diferenças de previsão por parada

EAGLESON B
54 in 100 eligible predictions differed from the timetable by more than 5 minutes (103 predictions over 21 days).
Abrir esta parada
DOMINION 1A
48 in 100 eligible predictions differed from the timetable by more than 5 minutes (147 predictions over 21 days).
Abrir esta parada
EAGLESON A
45 in 100 eligible predictions differed from the timetable by more than 5 minutes (103 predictions over 21 days).
Abrir esta parada
LINCOLN FIELDS 1A
44 in 100 eligible predictions differed from the timetable by more than 5 minutes (147 predictions over 21 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 2Verifica 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 350 checked trips need a closer look0 of 350 trips with enough public-feed evidence had no matching position over 7 days. 0 of 350 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 7,9 min (positive means later; negative means earlier)88 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: 70
Paradas previstas distintas: 85
Percursos publicados distintos: 4
Período de serviço publicado: 5:30–0:19 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: 70
Paradas previstas distintas: 85
Percursos publicados distintos: 4
Período de serviço publicado: 5:30–0:19 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 17.858 arrivals over 10 days; after has 5.405 arrivals over 3 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: 87,5%
Previsões elegíveis verificadas: 32.160
Dias úteis com dados: 18
Atraso previsto no percentil 95: 7,9 min late

Patterns by hour (20)

Patterns by hour (20)
Hora	Pontual	Mediana	Percentil 95	Evidências
00:00	99,6%	0 min late	1,8 min late	450 · 10 days
05:00	79,9%	2,6 min late	7,2 min late	363 · 11 days
06:00	85,3%	1,3 min late	7,6 min late	934 · 11 days
07:00	80,5%	1,5 min late	12 min late	1.332 · 11 days
08:00	81,8%	1,7 min late	8,4 min late	1.242 · 11 days
09:00	95,1%	0,8 min late	5 min late	992 · 11 days
10:00	96,1%	0,6 min late	4,8 min late	989 · 11 days
11:00	94,0%	1 min late	5,7 min late	990 · 11 days
12:00	97,3%	1 min late	4,3 min late	990 · 11 days
13:00	96,5%	0,8 min late	4,7 min late	990 · 11 days
14:00	93,9%	0,3 min late	6,4 min late	990 · 11 days
15:00	93,6%	0,1 min early	4,8 min late	1.194 · 11 days
16:00	66,7%	2,8 min late	13,3 min late	1.398 · 11 days
17:00	65,0%	2,6 min late	17,3 min late	1.463 · 11 days
18:00	73,5%	2,3 min late	18,2 min late	1.364 · 11 days
19:00	88,3%	2 min late	8 min late	1.077 · 11 days
20:00	86,8%	1,2 min late	5,7 min late	991 · 11 days
21:00	92,1%	1,7 min late	6 min late	968 · 11 days
22:00	93,8%	1,5 min late	7,6 min late	451 · 11 days
23:00	100,0%	1 min late	3,6 min late	458 · 11 days

2 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

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

00:000 / 10 trips without a position100,0%
05:000 / 5 trips without a position100,0%
06:000 / 15 trips without a position100,0%
07:000 / 20 trips without a position100,0%
08:000 / 20 trips without a position100,0%
09:000 / 20 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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 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.

05:30– 06:20
Trip 9996030Vehicle position matchedFirst / last feed position: 5:06 a.m. EST / 6:21 a.m. EST; not actual start or end times.
06:03– 06:20
Trip 30227030Vehicle position matchedFirst / last feed position: 5:58 a.m. EST / 6:21 a.m. EST; not actual start or end times.
06:30– 07:30
Trip 29853030Vehicle position matchedFirst / last feed position: 5:45 a.m. EST / 7:27 a.m. EST; not actual start or end times.
06:33– 06:50
Trip 5916030Vehicle position matchedFirst / last feed position: 5:47 a.m. EST / 6:51 a.m. EST; not actual start or end times.
07:00– 08:00
Trip 18889030Vehicle position matchedFirst / last feed position: 6:52 a.m. EST / 8:05 a.m. EST; not actual start or end times.
07:03– 07:20
Trip 20855030Vehicle position matchedFirst / last feed position: 6:47 a.m. EST / 7:24 a.m. EST; not actual start or end times.
07:29– 08:29
Trip 21752030Vehicle position matchedFirst / last feed position: 7:25 a.m. EST / 8:46 a.m. EST; not actual start or end times.
07:33– 07:50
Trip 14794030Vehicle position matchedFirst / last feed position: 6:58 a.m. EST / 7:53 a.m. EST; not actual start or end times.
08:00– 09:02
Trip 34867030Vehicle position matchedFirst / last feed position: 7:15 a.m. EST / 9:19 a.m. EST; not actual start or end times.
08:04– 08:21
Trip 15935030Vehicle position matchedFirst / last feed position: 8:05 a.m. EST / 8:26 a.m. EST; not actual start or end times.
08:30– 08:50
Trip 25771030Vehicle position matchedFirst / last feed position: 8:29 a.m. EST / 9:02 a.m. EST; not actual start or end times.
08:33– 08:50
Trip 16367030Vehicle position matchedFirst / last feed position: 8:13 a.m. EST / 8:58 a.m. EST; not actual start or end times.

· Open all evidence for this day