1 trip cancelled now · 13 did not run in novembroCancellations →

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

Rota 105: Airport ~ Aéroport ⇄ Hurdman / St-Laurent & N Rideau

A cada 30 a 32 min

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

ST-LAURENT A11 min sched.
ST-LAURENT / TREMBLAY17 min
TREMBLAY / AD. 52917 min
TREMBLAY / AVENUE U17 min
TREMBLAY / AVENUE R18 min
TREMBLAY / BELFAST18 min
TREMBLAY B19 min
TERMINAL / RIVERSIDE22 min
HURDMAN C23 min
LYCÉE CLAUDEL 1A (B)26 min
SMYTH 1A (B)0 min
RIVERSIDE 1A (B)1 min
PLEASANT PARK 1A (B)2 min
BILLINGS BRIDGE 1A (A)3 min
HERON 1A (A)5 min
WALKLEY B7 min
GREENBORO B9 min
SOUTH KEYS D10 min
TRANSITWAY / HUNT CLUB11 min
AIRPORT / UPLANDS15 min
AIRPORT PARKWAY / AIRBUS17 min
AIRPORT PARKWAY / AIR CANADA CARGO18 min
AIRPORT / AÉROPORT (A)19 min
AIRPORT PARKWAY / AIRBUS21 min
AIRPORT / UPLANDS22 min
UPLANDS A18 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: 9 trips with qualifying later matching vehicle observations. Trips with any notice: 10.

Trips needing investigation

13 of 675 trips with a usable feed window (1,9%) had no matching position.

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

662 with position · 13 to investigate · 7 excluded · 682 scheduled trips

Current feed. 1 distinct trips on this route are explicitly marked cancelled or deleted in the current feed. Observed: 4 de nov. de 2026, 12:14.

Coverage, exclusions and sources

0 of 12 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

7 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 662 / 682 (97,1%). 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, 11:10

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

88,2%

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

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

The hours we have evidence for

0087% · 1.697 predictions · 14 days
0190% · 1.608 predictions · 14 days
0293% · 1.402 predictions · 14 days
0389% · 1.418 predictions · 14 days
0489% · 1.655 predictions · 14 days
0589% · 1.631 predictions · 14 days
0681% · 1.488 predictions · 14 days
0788% · 1.426 predictions · 14 days
0894% · 1.474 predictions · 14 days
0995% · 1.328 predictions · 14 days
1087% · 1.300 predictions · 14 days
1180% · 1.392 predictions · 14 days
1282% · 1.423 predictions · 14 days
1391% · 1.405 predictions · 14 days
1489% · 1.427 predictions · 14 days
1593% · 1.554 predictions · 14 days
1683% · 1.448 predictions · 14 days
1768% · 1.387 predictions · 14 days
1885% · 1.306 predictions · 14 days
1992% · 1.462 predictions · 14 days
2096% · 1.379 predictions · 14 days
2192% · 1.408 predictions · 14 days
2293% · 1.381 predictions · 14 days
2391% · 1.322 predictions · 14 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: 4 de nov. de 2026

2 partial-capture days not counted.

What about time of day?

24 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: 193 of 51.085 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (125) 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)	4.924	0% (6)	0% (7)
Pico da manhã (6 às 9 h)	5.392	0% (23)	0% (4)
Meio do dia (9 a.m. a 3 p.m.)	13.494	0% (22)	0% (5)
Pico da tarde (das 3 às 6 da tarde)	6.723	2% (104)	1% (99)
Noite (das 6 às 10 da noite)	8.577	0% (14)	0% (2)
Noite (10 p.m. às 4 a.m.)	11.975	0% (24)	0% (8)

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

Onde esta linha é mais lenta

Slowest: RIDEAU B to LEES A, 14,4 km/h actual against 15,5 km/h planned.

Onde esta linha é mais lenta
De	Para	Distância	Velocidade planejada	Velocidade real	Trajetos medidos	Trajetos lentos
RIDEAU B	LEES A	2,3 km	15,5 km/h	14,4 km/h	223	4%
SOUTH KEYS A	GREENBORO A	730 m	23,2 km/h	20,6 km/h	1.224	20%
ST-LAURENT A	HURDMAN C	3,2 km	17,5 km/h	22,7 km/h	997	0%
BOWESVILLE B	LEITRIM B	2,3 km	27,9 km/h	23,4 km/h	33	6%
UPLANDS A	AIRPORT / AÉROPORT (A)	1,6 km	22,9 km/h	25,1 km/h	1.153	13%
HURDMAN C	BILLINGS BRIDGE 1A (A)	3,3 km	29,3 km/h	29,2 km/h	1.018	3%
GREENBORO B	SOUTH KEYS D	800 m	31,6 km/h	30,2 km/h	1.247	15%
LEES A	HURDMAN A	1,7 km	20,3 km/h	32 km/h	228	0%

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
Bank between Riverside W/B and Collins
25 de mar. de 2026, 07:00 to 31 de dez. de 2026, 17:00
Bank lane reductions in both directions between Riverside westbound and Collins due to construction. Cyclists and pedestrians not affected. From March 25 to December 2026.
A Cidade indica que isto afeta o transporte coletivo.
about 0 m from the route
City record updated 8 de set. de 2026, 16:24.
Obras na via
KING EDWARD between SOMERSET / MARIE-CURIE, PRIVE and TEMPLETON
6 de out. de 2026, 00:00 to 6 de nov. de 2026, 17:00
KING EDWARD off-peak lane reductions between SOMERSET / MARIE-CURIE, PRIVE and TEMPLETON due to construction. From 12:00am, 06/10/26 to 5:00pm, 06/11/26
A Cidade indica que isto afeta o transporte coletivo.
about 0 m from the route
City record updated 9 de out. de 2026, 10:28.
Obras na via
LAURIER between CUMBERLAND and COPERNICUS
6 de out. de 2026, 00:00 to 6 de nov. de 2026, 17:00
LAURIER off-peak lane reduction between CUMBERLAND and COPERNICUS 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, 11:12.
Obras na via
STEWART between CUMBERLAND and WALLER
2 de nov. de 2026, 07:00 to 5 de nov. de 2026, 17:00
STEWART lane reduction between CUMBERLAND and WALLER due to construction, Thursday November 5th.
about 0 m from the route
City record updated 2 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.

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

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

Horas com mais cancelamentos: 01 (1), 05 (1), 09 (1)

Últimos trajetos cancelados

qua., 28 de out., scheduled 05:34
sex., 23 de out., scheduled 10:02
seg., 19 de out., scheduled 25:14
dom., 18 de out., scheduled 09:37
sex., 16 de out., scheduled 17:20

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: 13 of 675 trips we could check.

Abrir a análise das previsões com datas

Veredicto

What this route needs

Wide prediction spread 17:00: the 95th percentile is 25,1 min later than the median.

17:00 has 68% of predictions within five minutes of the timetable, against 89% the rest of the day.

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

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

00:00: 87,2% of final predictions within five minutes of the timetable, 1.697 predictions, typically 1 min late
01:00: 90,3% of final predictions within five minutes of the timetable, 1.608 predictions, typically 1,3 min late
02:00: 92,9% of final predictions within five minutes of the timetable, 1.402 predictions, typically 0,7 min late
03:00: 89,1% of final predictions within five minutes of the timetable, 1.418 predictions, typically 0,3 min late
04:00: 89,1% of final predictions within five minutes of the timetable, 1.655 predictions, typically 0,9 min late
05:00: 88,8% of final predictions within five minutes of the timetable, 1.631 predictions, typically 1,5 min late
06:00: 81% of final predictions within five minutes of the timetable, 1.488 predictions, typically 1,3 min late
07:00: 88,3% of final predictions within five minutes of the timetable, 1.426 predictions, typically 0,4 min late
08:00: 93,5% of final predictions within five minutes of the timetable, 1.474 predictions, typically 0,9 min late
09:00: 94,8% of final predictions within five minutes of the timetable, 1.328 predictions, typically 0,4 min late
10:00: 86,8% of final predictions within five minutes of the timetable, 1.300 predictions, typically 0,7 min late
11:00: 79,5% of final predictions within five minutes of the timetable, 1.392 predictions, typically 1,8 min late
12:00: 81,7% of final predictions within five minutes of the timetable, 1.423 predictions, typically 1,2 min late
13:00: 91,1% of final predictions within five minutes of the timetable, 1.405 predictions, typically 0,4 min late
14:00: 89,3% of final predictions within five minutes of the timetable, 1.427 predictions, typically 0,9 min late
15:00: 93,3% of final predictions within five minutes of the timetable, 1.554 predictions, typically 0,9 min late
16:00: 83,2% of final predictions within five minutes of the timetable, 1.448 predictions, typically 1 min late
17:00: 68,2% of final predictions within five minutes of the timetable, 1.387 predictions, typically 2 min late. Provider predictions have a wide spread.
18:00: 84,7% of final predictions within five minutes of the timetable, 1.306 predictions, typically 0,8 min late
19:00: 92,1% of final predictions within five minutes of the timetable, 1.462 predictions, typically 0,7 min late
20:00: 95,9% of final predictions within five minutes of the timetable, 1.379 predictions, typically 0,6 min late
21:00: 91,9% of final predictions within five minutes of the timetable, 1.408 predictions, typically 1 min late
22:00: 92,8% of final predictions within five minutes of the timetable, 1.381 predictions, typically 0,8 min late
23:00: 90,5% of final predictions within five minutes of the timetable, 1.322 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
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	Quando	Medido	Scenario or next investigation
ProblemWide prediction spread	17:00	25,1 min swing	Operations, not the timetable
ProblemOne hour has a lower prediction match	17:00	68%	Operations, not the timetable
CaveatCoverage gap	All measured hours	97%	More observation, not a service change

Measurements

Wide prediction spread · 17:00: Measured arrivals 1.387; Hours affected 1; Spread 25,1 min; Median delay 2 min; Suggested running time change 2 min
One hour has a lower prediction match · 17:00: Hora 17:00; Pontual 68,2%; Measured arrivals 1.387; Shortfall 21 pts; Route median on time 89,2%
Coverage gap · All measured hours: Meta 99,5%; Trips with a matching position 97,1%; Dias de serviço 7; Trips with a matching position 662; Viagens programadas 682

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

Verificação da linha

How route 105 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 · 67.367 predictions checked

Tamanho da amostra de previsão: Amostra maior

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

Updated 4 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.

17–18: 32 in 100 eligible predictions differed from the timetable by more than 5 minutes (1.387 predictions over 14 days).

Nenhum aviso oficial atual corresponde a esta linha.

Diferenças de previsão por parada

UOTTAWA A
43 in 100 eligible predictions differed from the timetable by more than 5 minutes (249 predictions over 30 days).
Abrir esta parada
KING EDWARD / OSGOODE
42 in 100 eligible predictions differed from the timetable by more than 5 minutes (248 predictions over 30 days).
Abrir esta parada
LAURIER E / COPERNICUS
41 in 100 eligible predictions differed from the timetable by more than 5 minutes (248 predictions over 30 days).
Abrir esta parada
KING EDWARD / TEMPLETON
41 in 100 eligible predictions differed from the timetable by more than 5 minutes (249 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?: 13 of 675 checked trips need a closer look13 of 675 trips with enough public-feed evidence had no matching position over 7 days. 7 of 682 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,1 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?: A espera extra média prevista foi menor que 30 segundos na parada amostrada0,1 min beyond the scheduled wait, based on 144 eligible predictions at 2 high-frequency stops over 12 days.

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: 97
Paradas previstas distintas: 75
Percursos publicados distintos: 5
Período de serviço publicado: 3:10–3:17 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: 97
Paradas previstas distintas: 75
Percursos publicados distintos: 5
Período de serviço publicado: 3:10–3:17 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 34.736 arrivals over 14 days; after has 12.624 arrivals over 5 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: 88,2%
Previsões elegíveis verificadas: 67.367
Dias úteis com dados: 19
Atraso previsto no percentil 95: 7,1 min late

Patterns by hour (24)

Patterns by hour (24)
Hora	Pontual	Mediana	Percentil 95	Evidências
00:00	87,2%	1 min late	6,2 min late	1.697 · 14 days
01:00	90,3%	1,3 min late	5,9 min late	1.608 · 14 days
02:00	92,9%	0,7 min late	5,3 min late	1.402 · 14 days
03:00	89,1%	0,3 min late	6,1 min late	1.418 · 14 days
04:00	89,1%	0,9 min late	8,2 min late	1.655 · 14 days
05:00	88,8%	1,5 min late	6,6 min late	1.631 · 14 days
06:00	81,0%	1,3 min late	12,7 min late	1.488 · 14 days
07:00	88,3%	0,4 min late	8,1 min late	1.426 · 14 days
08:00	93,5%	0,9 min late	5,3 min late	1.474 · 14 days
09:00	94,8%	0,4 min late	5,1 min late	1.328 · 14 days
10:00	86,8%	0,7 min late	6,8 min late	1.300 · 14 days
11:00	79,5%	1,8 min late	6,2 min late	1.392 · 14 days
12:00	81,7%	1,2 min late	8,9 min late	1.423 · 14 days
13:00	91,1%	0,4 min late	5,6 min late	1.405 · 14 days
14:00	89,3%	0,9 min late	6,3 min late	1.427 · 14 days
15:00	93,3%	0,9 min late	5,2 min late	1.554 · 14 days
16:00	83,2%	1 min late	9,8 min late	1.448 · 14 days
17:00	68,2%	2 min late	27,1 min late	1.387 · 14 days
18:00	84,7%	0,8 min late	9,6 min late	1.306 · 14 days
19:00	92,1%	0,7 min late	6,9 min late	1.462 · 14 days
20:00	95,9%	0,6 min late	4,5 min late	1.379 · 14 days
21:00	91,9%	1 min late	5 min late	1.408 · 14 days
22:00	92,8%	0,8 min late	5,4 min late	1.381 · 14 days
23:00	90,5%	1 min late	5,7 min late	1.322 · 14 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

662 / 682 scheduled trips published at least one position across 7 service days (97,1%).

03:007 / 32 trips without a position78,1%
02:004 / 28 trips without a position85,7%
01:003 / 28 trips without a position89,3%
09:001 / 23 trips without a position95,7%
05:001 / 28 trips without a position96,4%
08:001 / 28 trips without a position96,4%

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 · 97 trips in the retained timetable · retained notices; capture coverage unverified

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

03:10– 03:47
Trip 35911030Vehicle position matchedFirst / last feed position: 4:00 a.m. EST / 4:22 a.m. EST; not actual start or end times.
03:19– 03:55
Trip 5840030Insufficient coverage or identity; outcome unknown
03:44– 04:21
Trip 3133030Vehicle position matchedFirst / last feed position: 4:00 a.m. EST / 4:35 a.m. EST; not actual start or end times.
03:47– 04:23
Trip 6519030Vehicle position matchedFirst / last feed position: 4:00 a.m. EST / 4:35 a.m. EST; not actual start or end times.
04:13– 04:50
Trip 6423030Vehicle position matchedFirst / last feed position: 4:00 a.m. EST / 4:47 a.m. EST; not actual start or end times.
04:17– 04:53
Trip 25273030Vehicle position matchedFirst / last feed position: 4:23 a.m. EST / 4:51 a.m. EST; not actual start or end times.
04:40– 05:17
Trip 6324030Vehicle position matchedFirst / last feed position: 4:17 a.m. EST / 5:12 a.m. EST; not actual start or end times.
04:47– 05:20
Trip 24840030Vehicle position matchedFirst / last feed position: 4:36 a.m. EST / 6:04 a.m. EST; not actual start or end times.
05:00– 05:58
Trip 5989030Vehicle position matchedFirst / last feed position: 4:46 a.m. EST / 6:25 a.m. EST; not actual start or end times.
05:09– 05:48
Trip 7676030Vehicle position matchedFirst / last feed position: 4:58 a.m. EST / 5:45 a.m. EST; not actual start or end times.
05:28– 06:26
Trip 21432030Vehicle position matchedFirst / last feed position: 5:07 a.m. EST / 6:27 a.m. EST; not actual start or end times.
05:34– 06:14
Trip 18389030Vehicle position matchedFirst / last feed position: 5:23 a.m. EST / 6:19 a.m. EST; not actual start or end times.

· Open all evidence for this day