No 51 trips cancelled now · 1 did not run in novembreCancellations →

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

Linea 51: Tunney's Pasture ⇄ Britannia

Ogni 28-36 min

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

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

Trips needing investigation

3 of 453 trips with a usable feed window (0,7%) had no matching position.

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

450 with position · 3 to investigate · 0 excluded · 453 scheduled trips

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

Coverage, exclusions and sources

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

Published position coverage: 450 / 453 (99,3%). 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 nov 2026, 23: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

65,7%

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

Predictions in the source: 95.833
Weekdays with evidence: 19
Evidence window: 5 ott 2026 – 2 nov 2026

The hours we have evidence for

591% · 385 predictions · 11 days
681% · 837 predictions · 13 days
763% · 2337 predictions · 12 days
859% · 3170 predictions · 14 days
973% · 3361 predictions · 14 days
1073% · 3174 predictions · 14 days
1169% · 3156 predictions · 14 days
1257% · 3158 predictions · 14 days
1352% · 3173 predictions · 14 days
1467% · 3089 predictions · 14 days
1556% · 3092 predictions · 14 days
1653% · 3048 predictions · 14 days
1750% · 3040 predictions · 14 days
1869% · 3282 predictions · 14 days
1973% · 3213 predictions · 14 days
2071% · 3046 predictions · 14 days
2180% · 2842 predictions · 14 days
2277% · 1899 predictions · 14 days
2383% · 766 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 nov 2026

2 partial-capture days not counted.

What about time of day?

19 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

Autobus che arrivano ravvicinati

Last 28 days, 6 ottobre 2026 to 2 novembre 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 ottobre 2026, 15 ottobre 2026.

Valori e interpretazione

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

0% of pairs (233) had a long gap: more than 1.75 times the planned wait between them.

Autobus che arrivano ravvicinati
Ora del giorno	Coppie verificate	Corse ravvicinate	Lungo intervallo
Ora di punta del mattino (dalle 6 alle 9)	4001	0% (14)	0% (17)
Metà giornata (dalle 9 del mattino alle 3 del pomeriggio)	28.659	0% (108)	0% (96)
Ora di punta pomeridiana (dalle 3 alle 6 del pomeriggio)	8379	0% (7)	0% (18)
Sera (dalle 6 alle 10 di sera)	20.004	1% (157)	1% (102)
Notte (dalle 10 di sera alle 4 del mattino)	2117	0% (0)	0% (0)

Come viene misurato →How we got this numberBus ravvicinati e punti lenti su ogni linea →

Dove questa linea è più lenta

Slowest: LINCOLN FIELDS MALL WEST to LINCOLN FIELDS 3B, 8,9 km/h actual against 10,8 km/h planned.

Dove questa linea è più lenta
Da	A	Distanza	Velocità prevista	Velocità effettiva	Corse misurate	Corse lente
LINCOLN FIELDS MALL WEST	LINCOLN FIELDS 3B	710 m	10,8 km/h	8,9 km/h	643	11%
LINCOLN FIELDS 4B	LINCOLN FIELDS MALL EAST	790 m	11,7 km/h	9,7 km/h	785	20%
LINCOLN FIELDS 3B	CARLINGWOOD - LOBLAWS	1,4 km	11,1 km/h	12,1 km/h	793	2%
CARLINGWOOD / CARLING	LINCOLN FIELDS 4B	1,3 km	12 km/h	12,9 km/h	783	2%
RICHMOND / FOREST	LINCOLN FIELDS 3B	1,5 km	12,5 km/h	12,9 km/h	135	1%
CASSELS / BRADFORD	RICHMOND / FOREST	1,6 km	15,6 km/h	13,7 km/h	135	4%
DOVERCOURT / BROADVIEW	CARLINGWOOD / CARLING	2,1 km	14,3 km/h	13,9 km/h	806	2%
TUNNEY'S PASTURE D	DOVERCOURT / BROADVIEW	4,1 km	18 km/h	15,8 km/h	812	6%

Un viaggio lento ha richiesto almeno 1.5 volte il tempo previsto.

Come viene misurato →

Lavori stradali della città vicino a questa ligne

Lavori stradali e chiusure di strade per eventi pubblicati dalla Città di Ottawa, misurati come vicini al percorso di questa linea. Vicino non prova che l'autobus sia deviato. Per questo, controlli gli avvisi dell'esercente.

Lavori stradali
Clare E/B between Churchill and Kirkwood
23 mar 2026, 06:00 to 1 dic 2026, 19:00
Clare eastbound closed between Churchill and Kirkwood due to construction. Follow the signed detour. From 6am Monday, March 23 to 7pm Tuesday December 1.
La Città indica che questo riguarda il trasporto pubblico.
about 0 m from the route
City record updated 4 set 2026, 08:08.
Lavori stradali
Lincoln between Eden and Edgewood
6 apr 2026, 06:00 to 20 dic 2026, 19:00
Lincoln closed between Eden and Edgewood due to construction. Monday, 6 April at 6am to Sunday, 20 December at 7pm.
about 31 m from the route
City record updated 4 set 2026, 09:04.
Lavori stradali
Edgewood between Lincoln and Richmond
6 apr 2026, 06:00 to 20 dic 2026, 19:00
Edgewood closed between Lincoln and Richmond due to construction. Monday, 6 April at 6am to Sunday, 20 December at 7pm.
about 6 m from the route
City record updated 22 set 2026, 15:32.
Lavori stradali
Dovercourt between Churchill and Tweedsmuir
4 mag 2026, 06:00 to 27 nov 2026, 19:00
Dovercourt closed between Churchill and Tweedsmuir due to construction, May 4th to November 27th. Access for local traffic maintained.
about 8 m from the route
City record updated 4 set 2026, 08:20.
Lavori stradali
RICHMOND E/B between LEIGHTON and ISLAND PARK
7 ott 2026, 00:00 to 20 nov 2026, 15:00
RICHMOND eastbound off-peak lane reductions between LEIGHTON and ISLAND PARK due to construction, until November 20th.
La Città indica che questo riguarda il trasporto pubblico.
about 0 m from the route
City record updated 7 ott 2026, 11:08.
Lavori stradali
FOREST between BOND and RICHMOND
16 ott 2026, 07:00 to 6 nov 2026, 17:00
FOREST closed between BOND and RICHMOND due to construction. Follow the signed detour. From October 19th to November 6th.
La Città indica che questo riguarda il trasporto pubblico.
about 0 m from the route
City record updated 16 ott 2026, 06:56.
Lavori stradali
CARLING E/B between Kichi Zibi Mikan on Ramp and EDGEWORTH
30 ott 2026, 00:00 to 13 nov 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 ott 2026, 11:40.
Lavori stradali
BOND between CROYDON and FOREST
30 ott 2026, 00:00 to 20 nov 2026, 17:00
BOND closed between CROYDON and FOREST due to construction, from November 2nd to 20th. Access for local traffic maintained.
about 0 m from the route
City record updated 30 ott 2026, 13:12.

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: eventi di traffico della Città di Ottawa (lavori stradali e chiusure). Contiene informazioni concesse in licenza ai sensi della Open Government Licence, City of Ottawa. La Città precisa che questo elenco è fornito al meglio delle sue possibilità e può essere incompleto. Mappa del traffico della Città di Ottawa ↗

Cancellazioni su questa linea

Che cosa significano queste parole →

2 partial-capture days not counted.

7 scheduled trips with counted cancellation notices from mar 6 ott to lun 2 nov.

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

Ore con più cancellazioni: 15 (2), 17 (2), 18 (2)

Ultime corse cancellate

dom 1 nov, scheduled 18:45
mar 27 ott, scheduled 17:21
dom 25 ott, scheduled 19:31
gio 22 ott, scheduled 17:21
gio 22 ott, scheduled 15:10

OC Transpo non indica un motivo per le singole corse, quindi non ne viene mostrato nessuno.

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

Aprire l'analisi datata delle previsioni

Verdetto

What this route needs

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

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

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

Scenario: 4 min more running time on 508 trips. The schedule-block model estimates 126 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, 20 hours with samples

00:00: not enough data
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 91,4% of final predictions within five minutes of the timetable, 385 predictions, typically 1,9 min late
06:00: 80,6% of final predictions within five minutes of the timetable, 837 predictions, typically 2,2 min late
07:00: 62,9% of final predictions within five minutes of the timetable, 2337 predictions, typically 3,6 min late
08:00: 59,4% of final predictions within five minutes of the timetable, 3170 predictions, typically 4,1 min late
09:00: 73,2% of final predictions within five minutes of the timetable, 3361 predictions, typically 2,7 min late
10:00: 72,8% of final predictions within five minutes of the timetable, 3174 predictions, typically 2,9 min late
11:00: 69% of final predictions within five minutes of the timetable, 3156 predictions, typically 3,2 min late
12:00: 56,9% of final predictions within five minutes of the timetable, 3158 predictions, typically 4,3 min late
13:00: 51,6% of final predictions within five minutes of the timetable, 3173 predictions, typically 4,9 min late
14:00: 66,6% of final predictions within five minutes of the timetable, 3089 predictions, typically 3,3 min late
15:00: 55,5% of final predictions within five minutes of the timetable, 3092 predictions, typically 4,1 min late
16:00: 52,5% of final predictions within five minutes of the timetable, 3048 predictions, typically 4,5 min late
17:00: 49,9% of final predictions within five minutes of the timetable, 3040 predictions, typically 5 min late
18:00: 69% of final predictions within five minutes of the timetable, 3282 predictions, typically 2,9 min late
19:00: 73% of final predictions within five minutes of the timetable, 3213 predictions, typically 2,3 min late
20:00: 71% of final predictions within five minutes of the timetable, 3046 predictions, typically 2,8 min late
21:00: 79,8% of final predictions within five minutes of the timetable, 2842 predictions, typically 2,2 min late
22:00: 76,5% of final predictions within five minutes of the timetable, 1899 predictions, typically 2,3 min late
23:00: 83,3% of final predictions within five minutes of the timetable, 766 predictions, typically 2,3 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	Misurato	Scenario or next investigation
ProblemPredictions later than timetable	07:00 to 09:00 · 11:00 to 18:00	3,9 min late · 4,3 min late	More running time
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 11:00 to 18:00: Measured arrivals 21.756; Hours affected 7; Spread 9,5 min; Median delay 4,3 min; Suggested running time change 4,3 min
Predictions later than timetable · 07:00 to 09:00: Measured arrivals 5507; Hours affected 2; Spread 6,2 min; Median delay 3,9 min; Suggested running time change 3,9 min
Coverage gap · All measured hours: Obiettivo 99,5%; Trips with a matching position 99,3%; Giorni di servizio 5; Trips with a matching position 450; Corse programmate 453

Aprire storico, affidabilità e analisi della linea

Verifica della linea

How route 51 has been running

Un breve riepilogo di ciò che sappiamo. Lo diciamo quando non possiamo rispondere a una domanda.

In sintesi

Le previsioni del fornitore sono spesso risultate diverse dall'orario; gli arrivi effettivi non sono stati misurati in modo indipendente.

66 in 100 eligible predictions were within 5 minutes of the timetable · 95.833 predictions checked

Dimensione del campione delle previsioni: Campione più ampio

Based on 95.833 eligible provider predictions over 27 measured days, from 5 ott 2026 to 2 nov 2026.

Updated 3 nov 2026, 23:32

Dove e quando le previsioni sono state diverse più volte?

Sono differenze ripetute tra previsione e orario, non disservizi misurati in modo indipendente. Usano le stesse previsioni idonee del risultato qui sopra, ma sono raggruppate per fermata anziché per ora, quindi gli elenchi possono non coincidere riga per riga.

17–18: 50 in 100 eligible predictions differed from the timetable by more than 5 minutes (3040 predictions over 14 days).
13–14: 48 in 100 eligible predictions differed from the timetable by more than 5 minutes (3173 predictions over 14 days).
16–17: 48 in 100 eligible predictions differed from the timetable by more than 5 minutes (3048 predictions over 14 days).
15–16: 45 in 100 eligible predictions differed from the timetable by more than 5 minutes (3092 predictions over 14 days).

Nessun avviso ufficiale attuale riguarda questa ligne.

Differenze di previsione per fermata

RICHMOND / CROYDON
56 in 100 eligible predictions differed from the timetable by more than 5 minutes (901 predictions over 30 days).
Aprire questa fermata
CARLING / WOODROFFE
55 in 100 eligible predictions differed from the timetable by more than 5 minutes (922 predictions over 30 days).
Aprire questa fermata
RICHMOND / ASSALY
55 in 100 eligible predictions differed from the timetable by more than 5 minutes (901 predictions over 30 days).
Aprire questa fermata
RICHMOND / PLAZA
54 in 100 eligible predictions differed from the timetable by more than 5 minutes (901 predictions over 30 days).
Aprire questa fermata

Sono previsioni del fornitore specifiche per la linea, confrontate con l'orario. Mostrano differenze di previsione ripetute in un luogo e a un'ora precisi. Non sono arrivi misurati e non ne indicano la causa.

Controlli ogni corsa e ogni data

Apra un periodo per vedere ogni giorno di servizio, ogni corsa programmata, ogni lacuna nei dati, l'ID del veicolo pubblico osservato e i conteggi esatti alla base di questo riepilogo.

Cosa vogliono sapere i passeggeri

Qualche corsa è cancellata in questo momento?: Nessuna corsa parte nelle prossime 4 oreVengono controllate le corse che partono dai capolinea della linea nelle prossime 4 ore. Non è un tasso storico di cancellazioni.
Possibili corse saltate dopo il controllo delle lacune del feed?: 3 of 453 checked trips need a closer look3 of 453 trips with enough public-feed evidence had no matching position over 7 days. 0 of 453 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Come sono differite le previsioni dell'operatore rispetto all'orario?: At the 95th percentile, the predicted difference was 13,2 min (positive means later; negative means earlier)66 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
Quale attesa implicavano le previsioni del fornitore?: Nessun risultato per singola ligne raggiunge ancora la soglia dei dati probanti. Ciò non significa che le interruzioni non siano avvenute.

Verifica della modifica dell'orario

Orario pubblicato: prima e dopo

Questo confronto riguarda l'orario ufficiale conservato attualmente e la versione conservata in precedenza. Le modifiche dell'orario sono fatti su ciò che era stato pianificato. Non provano che una corsa sia stata effettuata.

Current published schedule began 30 ottobre 2026

Giorno di servizio selezionato da ciascun orario pubblicato

Controlliamo il primo lunedì dopo l'inizio del nuovo orario e il lunedì di una settimana prima. Ogni dato proviene dalle versioni GTFS ufficiali conservate indicate qui sotto.

Almeno una data selezionata ha un servizio aggiunto o rimosso nel calendario. Lo consideri un contesto di giorno festivo o di servizio speciale, non una normale crescita dei giorni feriali.

Prima

Data di servizio verificata: 26 ottobre 2026

Corse programmate: 67
Fermate previste all'orario distinte: 113
Percorsi pubblicati distinti: 5
Fascia oraria del servizio pubblicata: 5:35–23:31

Operator calendar-date records: 0 added · 2 removed

Impronta del feed: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

Nuovo orario

Data di servizio verificata: 2 novembre 2026

Corse programmate: 67
Fermate previste all'orario distinte: 113
Percorsi pubblicati distinti: 5
Fascia oraria del servizio pubblicata: 5:35–23:31

Operator calendar-date records: 0 added · 2 removed

Impronta del feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

Il servizio è migliorato dopo la modifica?

Confronteremo gli arrivi consolidati nei 14 giorni prima e dopo la modifica. Pubblichiamo il confronto solo quando entrambi i periodi hanno almeno 7 giorni di servizio e 200 arrivi.

Still collecting: before has 50.187 arrivals over 14 days; after has 14.004 arrivals over 4 days. No improvement or decline is claimed yet.

I checksum permettono a chiunque di verificare quale orario conservato ha prodotto i conteggi. Una variazione del conteggio non indica una causa, una cancellazione, una decisione dell'esercente o un effetto sui passeggeri.

Come viene valutata questa ligne: Linea regolare con tutte le fermate

Confrontiamo l'ultima previsione idonea del fornitore per ogni arrivo programmato con l'orario ufficiale. Non sono arrivi misurati in modo indipendente. Per un risultato servono almeno 200 previsioni idonee. Qui si usa come obiettivo per i passeggeri "entro 5 minuti".

Che cosa questi dati non possono dimostrare

Il feed pubblico non fornisce conteggi affidabili dei passeggeri né eventi di passeggeri non imbarcati. Una posizione mancante non prova da sola una cancellazione, una mancata corsa, un'inversione anticipata o una causa.

Vedere le definizioni, le soglie e l'ordine dei dati

Feed ufficiale attuale: cancellazioni esplicite, fermate saltate e avvisi attivi.
Osservazioni abbinate: posizioni dei veicoli e previsioni consolidate collegate all'orario ufficiale.
Orario ufficiale: ciò che era previsto, tenuto separato da ciò che è stato osservato.
Segnalazioni di passeggeri e operatori: indizi su linee, orari e luoghi da verificare, non prove numeriche di per sé.

Risultati provvisori, dati probanti pubblicati

Come si sono confrontate le previsioni con l'orario?

Ogni ora confronta l'ultima previsione idonea del fornitore per un arrivo previsto a orario con l'orario ufficiale. «Entro 5 minuti» indica la differenza tra le previsioni, non un arrivo misurato né la prova che un autobus abbia circolato.

Periodo dei dati probatori: 5 ottobre 2026 to 2 novembre 2026

Entro 5 minuti dall'orario: 65,7%
Previsioni idonee verificate: 95.833
Giorni feriali con dati: 19
Ritardo previsto al 95º percentile: 13,2 min late

Patterns by hour (20)

Patterns by hour (20)
Ora	In orario	Mediana	95º percentile	Dati probanti
00:00	100,0%	2,2 min late	4,3 min late	156 · 4 days
05:00	91,4%	1,9 min late	7 min late	385 · 11 days
06:00	80,6%	2,2 min late	9,8 min late	837 · 13 days
07:00	62,9%	3,6 min late	8,9 min late	2337 · 12 days
08:00	59,4%	4,1 min late	11,3 min late	3170 · 14 days
09:00	73,2%	2,7 min late	11,1 min late	3361 · 14 days
10:00	72,8%	2,9 min late	10,4 min late	3174 · 14 days
11:00	69,0%	3,2 min late	13 min late	3156 · 14 days
12:00	56,9%	4,3 min late	11,1 min late	3158 · 14 days
13:00	51,6%	4,9 min late	13,6 min late	3173 · 14 days
14:00	66,6%	3,3 min late	12,8 min late	3089 · 14 days
15:00	55,5%	4,1 min late	15,7 min late	3092 · 14 days
16:00	52,5%	4,5 min late	19,2 min late	3048 · 14 days
17:00	49,9%	5 min late	14,4 min late	3040 · 14 days
18:00	69,0%	2,9 min late	11,4 min late	3282 · 14 days
19:00	73,0%	2,3 min late	9,5 min late	3213 · 14 days
20:00	71,0%	2,8 min late	9,3 min late	3046 · 14 days
21:00	79,8%	2,2 min late	8,3 min late	2842 · 14 days
22:00	76,5%	2,3 min late	7,5 min late	1899 · 14 days
23:00	83,3%	2,3 min late	6,7 min late	766 · 14 days

10 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

Autobus previsto a orario, ma non osservato in tempo reale

450 / 453 scheduled trips published at least one position across 5 service days (99,3%).

18:002 / 28 trips without a position92,9%
17:001 / 28 trips without a position96,4%
05:000 / 5 trips without a position100,0%
06:000 / 11 trips without a position100,0%
07:000 / 22 trips without a position100,0%
08:000 / 31 trips without a position100,0%

Questa non è una mancata corsa confermata. Una posizione mancante può indicare una corsa soppressa o saltata, ma può anche indicare un ID di corsa non assegnato o un'interruzione nel feed del gestore. Otranspo pubblica questa mancanza perché è importante per chi viaggia, senza trarre conclusioni non verificate.

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. Fonti e limiti.

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

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

05:35– 06:19
Trip 5529020Vehicle position matchedFirst / last feed position: 5:25 a.m. EST / 6:42 a.m. EST; not actual start or end times.
06:34– 07:23
Trip 33538020Vehicle position matchedFirst / last feed position: 6:23 a.m. EST / 7:25 a.m. EST; not actual start or end times.
06:50– 07:33
Trip 30226020Vehicle position matchedFirst / last feed position: 6:54 a.m. EST / 7:34 a.m. EST; not actual start or end times.
07:01– 07:53
Trip 15249020Vehicle position matchedFirst / last feed position: 6:33 a.m. EST / 7:58 a.m. EST; not actual start or end times.
07:20– 08:05
Trip 18282020Vehicle position matchedFirst / last feed position: 7:18 a.m. EST / 8:05 a.m. EST; not actual start or end times.
07:40– 08:37
Trip 22715020Vehicle position matchedFirst / last feed position: 7:35 a.m. EST / 8:47 a.m. EST; not actual start or end times.
07:50– 08:38
Trip 20542020Vehicle position matchedFirst / last feed position: 7:59 a.m. EST / 8:39 a.m. EST; not actual start or end times.
08:10– 09:07
Trip 18049020Vehicle position matchedFirst / last feed position: 8:06 a.m. EST / 9:08 a.m. EST; not actual start or end times.
08:18– 09:08
Trip 26944020Vehicle position matchedFirst / last feed position: 8:21 a.m. EST / 9:05 a.m. EST; not actual start or end times.
08:33– 09:23
Trip 11538020Vehicle position matchedFirst / last feed position: 8:33 a.m. EST / 9:22 a.m. EST; not actual start or end times.
08:41– 09:34
Trip 21765020Vehicle position matchedFirst / last feed position: 8:40 a.m. EST / 9:30 a.m. EST; not actual start or end times.
08:48– 09:38
Trip 396020Vehicle position matchedFirst / last feed position: 8:22 a.m. EST / 9:35 a.m. EST; not actual start or end times.

· Open all evidence for this day