No 56 trips cancelled now · 3 did not run in novembroCancellations →

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

Rota 56: King Edward & Civic ⇄ Tunney's Pasture

A cada 15 a 30 min

Sentido Civic0 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: 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: 24 trips with qualifying later matching vehicle observations. Trips with any notice: 41.

Trips needing investigation

16 of 637 trips with a usable feed window (2,5%) had no matching position.

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

621 with position · 16 to investigate · 0 excluded · 637 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, 12:46.

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: 621 / 637 (97,5%). 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, 11:49

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

67,5%

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

Predictions in the source: 59.455
Weekdays with evidence: 19
Evidence window: 7 de out. de 2026 – 4 de nov. de 2026

The hours we have evidence for

0079% · 408 predictions · 12 days
0133% · 90 predictions · 9 days
05100% · 58 predictions · 13 days
0680% · 2.011 predictions · 15 days
0781% · 3.084 predictions · 15 days
0860% · 3.603 predictions · 15 days
0979% · 2.568 predictions · 15 days
1072% · 1.851 predictions · 15 days
1171% · 853 predictions · 15 days
1266% · 858 predictions · 15 days
1378% · 836 predictions · 15 days
1459% · 1.489 predictions · 15 days
1547% · 2.824 predictions · 15 days
1655% · 3.451 predictions · 15 days
1757% · 2.825 predictions · 15 days
1871% · 2.939 predictions · 15 days
1970% · 1.098 predictions · 15 days
2077% · 872 predictions · 15 days
2181% · 853 predictions · 15 days
2268% · 654 predictions · 15 days
2380% · 478 predictions · 15 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?

21 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: 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

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

3% of pairs (927) 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)	7.809	5% (393)	5% (381)
Meio do dia (9 a.m. a 3 p.m.)	7.760	1% (105)	0% (34)
Pico da tarde (das 3 às 6 da tarde)	9.489	9% (819)	5% (451)
Noite (das 6 às 10 da noite)	6.606	1% (98)	1% (61)
Noite (10 p.m. às 4 a.m.)	2.084	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: TUNNEY'S PASTURE E to INGLEWOOD / MACFARLANE, 9,3 km/h actual against 12,4 km/h planned.

Onde esta linha é mais lenta
De	Para	Distância	Velocidade planejada	Velocidade real	Trajetos medidos	Trajetos lentos
TUNNEY'S PASTURE E	INGLEWOOD / MACFARLANE	2 km	12,4 km/h	9,3 km/h	33	24%
TUNNEY'S PASTURE E	PARKDALE / CARLING	1,9 km	12,1 km/h	10,7 km/h	495	15%
LEES B	KING EDWARD / UNION	3,3 km	15,7 km/h	11 km/h	27	30%
METCALFE / PRETORIA	LEES B	1,4 km	13,2 km/h	11,3 km/h	499	17%
INGLEWOOD / MACFARLANE	TUNNEY'S PASTURE E	2,1 km	19,2 km/h	11,6 km/h	54	28%
LEES A	DOW'S LAKE A	4,2 km	16 km/h	14,1 km/h	501	4%
KING EDWARD / UNION	LEES A	3,3 km	14 km/h	15,1 km/h	516	3%
CARLING / PRESTON	METCALFE / PRETORIA	2,5 km	16,3 km/h	15,2 km/h	497	4%

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

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.

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

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

Horas com mais cancelamentos: 16 (15), 15 (10), 17 (9)

Últimos trajetos cancelados

qua., 4 de nov., scheduled 18:25
qua., 4 de nov., scheduled 17:34
qua., 4 de nov., scheduled 15:29
qua., 4 de nov., scheduled 15:24
ter., 3 de nov., scheduled 16:55

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: 3 of 637 trips we could check.

Abrir a análise das previsões com datas

Veredicto

What this route needs

Median provider predictions are 3,1 to 7,2 min later than the timetable in 8 hours of the day.

Predictions near the start are about 2,9 min later than the timetable; the difference grows by another 3,7 min along the route.

Wide prediction spread 15:00, 17:00: the 95th percentile is 21,7 min later than the median.

Predicted waits All measured hours are 2,6 min longer than scheduled waits.

01:00 has 33% of predictions within five minutes of the timetable, against 71% the rest of the day.

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

Scenario: 3 to 4 min more running time on 552 trips. The schedule-block model estimates 62 additional buses; fleet and workforce feasibility are unverified.

Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.

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

00:00: 78,7% of final predictions within five minutes of the timetable, 408 predictions, typically 0,7 min late
01:00: 33,3% of final predictions within five minutes of the timetable, 90 predictions, typically 7,2 min late
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, 58 predictions, typically 0,2 min early
06:00: 80,3% of final predictions within five minutes of the timetable, 2.011 predictions, typically 1,3 min late
07:00: 81,2% of final predictions within five minutes of the timetable, 3.084 predictions, typically 1,8 min late
08:00: 60,3% of final predictions within five minutes of the timetable, 3.603 predictions, typically 3,1 min late
09:00: 78,6% of final predictions within five minutes of the timetable, 2.568 predictions, typically 1,7 min late
10:00: 71,8% of final predictions within five minutes of the timetable, 1.851 predictions, typically 2,3 min late
11:00: 71% of final predictions within five minutes of the timetable, 853 predictions, typically 2,5 min late
12:00: 66,1% of final predictions within five minutes of the timetable, 858 predictions, typically 3,3 min late
13:00: 77,5% of final predictions within five minutes of the timetable, 836 predictions, typically 2,8 min late
14:00: 59,4% of final predictions within five minutes of the timetable, 1.489 predictions, typically 3,5 min late
15:00: 47,3% of final predictions within five minutes of the timetable, 2.824 predictions, typically 5,7 min late. Provider predictions have a wide spread.
16:00: 55,3% of final predictions within five minutes of the timetable, 3.451 predictions, typically 3,9 min late
17:00: 57,3% of final predictions within five minutes of the timetable, 2.825 predictions, typically 3,3 min late. Provider predictions have a wide spread.
18:00: 70,8% of final predictions within five minutes of the timetable, 2.939 predictions, typically 1,7 min late
19:00: 69,9% of final predictions within five minutes of the timetable, 1.098 predictions, typically 3,1 min late
20:00: 76,9% of final predictions within five minutes of the timetable, 872 predictions, typically 2,4 min late
21:00: 81,4% of final predictions within five minutes of the timetable, 853 predictions, typically 1,1 min late
22:00: 68,3% of final predictions within five minutes of the timetable, 654 predictions, typically 2,2 min late
23:00: 79,5% of final predictions within five minutes of the timetable, 478 predictions, typically 1,4 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
ProblemPredictions later than timetable	01:00 · 08:00 · 12:00 · 14:00 to 18:00 · 19:00	7,2 min late … 3,7 min late	More running time
ProblemWide prediction spread	15:00 · 17:00	21,7 min swing · 20,3 min swing	Operations, not the timetable
ProblemPredicted spacing varies	All measured hours	2,6 min extra wait	Manage the headway
ProblemOne hour has a lower prediction match	01:00	33%	Overnight operations
CaveatCoverage gap	All measured hours	98%	More observation, not a service change

Measurements

Predictions later than timetable · 14:00 to 18:00: Measured arrivals 10.589; Hours affected 4; Spread 18,6 min; Median delay 3,7 min; Suggested running time change 3,7 min
Wide prediction spread · 15:00: Measured arrivals 2.824; Hours affected 1; Spread 21,7 min; Median delay 5,7 min; Suggested running time change 5,7 min
Predictions later than timetable · 08:00: Measured arrivals 3.603; Hours affected 1; Spread 13,2 min; Median delay 3,1 min; Suggested running time change 3,1 min
Wide prediction spread · 17:00: Measured arrivals 2.825; Hours affected 1; Spread 20,3 min; Median delay 3,3 min; Suggested running time change 3,3 min
Predicted spacing varies · All measured hours: Paradas 20; Extra wait share 42,3%; Chegadas correspondentes 1.456; Espera extra 2,6 min; Scheduled wait 6,2 min
Predictions later than timetable · 19:00: Measured arrivals 1.098; Hours affected 1; Spread 8,5 min; Median delay 3,1 min; Suggested running time change 3,1 min
Predictions later than timetable · 12:00: Measured arrivals 858; Hours affected 1; Spread 11,7 min; Median delay 3,3 min; Suggested running time change 3,3 min
Predictions later than timetable · 01:00: Measured arrivals 90; Hours affected 1; Spread 2,7 min; Median delay 7,2 min; Suggested running time change 7,2 min
One hour has a lower prediction match · 01:00: Hora 01:00; Pontual 33,3%; Measured arrivals 90; Shortfall 37,7 pts; Route median on time 71%
Coverage gap · All measured hours: Meta 99,5%; Trips with a matching position 97,5%; Dias de serviço 6; Trips with a matching position 621; Viagens programadas 637

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

Verificação da linha

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

68 in 100 eligible predictions were within 5 minutes of the timetable · 59.455 predictions checked

Tamanho da amostra de previsão: Amostra maior

Based on 59.455 eligible provider predictions over 27 measured days, from 7 de out. de 2026 to 4 de nov. de 2026.

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

01–02: 67 in 100 eligible predictions differed from the timetable by more than 5 minutes (90 predictions over 9 days).
15–16: 53 in 100 eligible predictions differed from the timetable by more than 5 minutes (2.824 predictions over 15 days).
16–17: 45 in 100 eligible predictions differed from the timetable by more than 5 minutes (3.451 predictions over 15 days).
17–18: 43 in 100 eligible predictions differed from the timetable by more than 5 minutes (2.825 predictions over 15 days).

Nenhum aviso oficial atual corresponde a esta linha.

Diferenças de previsão por parada

KING EDWARD / CATHCART
67 in 100 eligible predictions differed from the timetable by more than 5 minutes (582 predictions over 30 days).
Abrir esta parada
KING EDWARD / YORK
64 in 100 eligible predictions differed from the timetable by more than 5 minutes (584 predictions over 30 days).
Abrir esta parada
KING EDWARD / ST-PATRICK
64 in 100 eligible predictions differed from the timetable by more than 5 minutes (583 predictions over 30 days).
Abrir esta parada
LEES / ROSEMERE
58 in 100 eligible predictions differed from the timetable by more than 5 minutes (587 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?: 16 of 637 checked trips need a closer look16 of 637 trips with enough public-feed evidence had no matching position over 7 days. 0 of 637 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 15,5 min (positive means later; negative means earlier)68 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?: 8,9 min average predicted wait2,6 min beyond the scheduled wait, based on 1.456 eligible predictions at 20 high-frequency stops over 16 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: 101
Paradas previstas distintas: 88
Percursos publicados distintos: 5
Período de serviço publicado: 5:59–1:10 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: 101
Paradas previstas distintas: 88
Percursos publicados distintos: 5
Período de serviço publicado: 5:59–1:10 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 31.276 arrivals over 14 days; after has 13.170 arrivals over 6 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: 7 de outubro de 2026 to 4 de novembro de 2026

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

Patterns by hour (21)

Patterns by hour (21)
Hora	Pontual	Mediana	Percentil 95	Evidências
00:00	78,7%	0,7 min late	11,4 min late	408 · 12 days
01:00	33,3%	7,2 min late	9,9 min late	90 · 9 days
05:00	100,0%	0,2 min early	1,7 min late	58 · 13 days
06:00	80,3%	1,3 min late	8,2 min late	2.011 · 15 days
07:00	81,2%	1,8 min late	8,7 min late	3.084 · 15 days
08:00	60,3%	3,1 min late	16,2 min late	3.603 · 15 days
09:00	78,6%	1,7 min late	8,8 min late	2.568 · 15 days
10:00	71,8%	2,3 min late	11,9 min late	1.851 · 15 days
11:00	71,0%	2,5 min late	15,1 min late	853 · 15 days
12:00	66,1%	3,3 min late	14,9 min late	858 · 15 days
13:00	77,5%	2,8 min late	8,5 min late	836 · 15 days
14:00	59,4%	3,5 min late	17,8 min late	1.489 · 15 days
15:00	47,3%	5,7 min late	27,4 min late	2.824 · 15 days
16:00	55,3%	3,9 min late	20,8 min late	3.451 · 15 days
17:00	57,3%	3,3 min late	23,5 min late	2.825 · 15 days
18:00	70,8%	1,7 min late	11,9 min late	2.939 · 15 days
19:00	69,9%	3,1 min late	11,6 min late	1.098 · 15 days
20:00	76,9%	2,4 min late	6,8 min late	872 · 15 days
21:00	81,4%	1,1 min late	7,5 min late	853 · 15 days
22:00	68,3%	2,2 min late	10,5 min late	654 · 15 days
23:00	79,5%	1,4 min late	7,5 min late	478 · 15 days

9 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

621 / 637 scheduled trips published at least one position across 6 service days (97,5%).

15:005 / 43 trips without a position88,4%
11:002 / 28 trips without a position92,9%
17:003 / 43 trips without a position93,0%
16:002 / 48 trips without a position95,8%
21:001 / 27 trips without a position96,3%
13: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 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

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

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

05:59– 06:31
Trip 11544040Vehicle position matchedFirst / last feed position: 5:30 a.m. EST / 6:34 a.m. EST; not actual start or end times.
06:05– 06:10
Trip 11908040Vehicle position matchedFirst / last feed position: 5:43 a.m. EST / 6:18 a.m. EST; not actual start or end times.
06:08– 06:45
Trip 17467040Vehicle position matchedFirst / last feed position: 5:42 a.m. EST / 6:53 a.m. EST; not actual start or end times.
06:24– 06:58
Trip 9071040Vehicle position matchedFirst / last feed position: 6:19 a.m. EST / 7:04 a.m. EST; not actual start or end times.
06:40– 07:17
Trip 16165040Vehicle position matchedFirst / last feed position: 6:35 a.m. EST / 7:23 a.m. EST; not actual start or end times.
06:44– 06:51
Trip 21479040Vehicle position matchedFirst / last feed position: 6:39 a.m. EST / 6:57 a.m. EST; not actual start or end times.
06:59– 07:35
Trip 979040Vehicle position matchedFirst / last feed position: 6:55 a.m. EST / 7:41 a.m. EST; not actual start or end times.
07:09– 07:46
Trip 26935040Vehicle position matchedFirst / last feed position: 7:06 a.m. EST / 7:55 a.m. EST; not actual start or end times.
07:14– 07:23
Trip 25071040Vehicle position matchedFirst / last feed position: 7:10 a.m. EST / 7:24 a.m. EST; not actual start or end times.
07:23– 08:00
Trip 950040Vehicle position matchedFirst / last feed position: 7:02 a.m. EST / 8:13 a.m. EST; not actual start or end times.
07:27– 07:32
Trip 18373040Vehicle position matchedFirst / last feed position: 7:26 a.m. EST / 7:35 a.m. EST; not actual start or end times.
07:29– 08:13
Trip 23790040Vehicle position matchedFirst / last feed position: 7:24 a.m. EST / 8:23 a.m. EST; not actual start or end times.

· Open all evidence for this day