UPDATED -- Detour: EB routes 11, 57, 58, 81, 691 around Richmond and Bayshore lane closures: September 18 2026 - Detour end date updated on October 23. From 6:00 am on Monday, September 21, until 6:00 pm on Wednesday, November 4, the southbound left turn lane from Bayshore Drive to Richmond Road, as well as the left turn lane from the Highway 417 off-ramp to Richmond southbound, will be closed for work related to the Bayshore Bridge Rehabilitation Project. As a result, routes 11 Waller, 57 Tunney's Pasture, 58 Tunney's Pasture, 81 Tunney's Pasture, and 691 Omer-Deslauriers will detour along Holly Acres and Richmond before continuing on their regular routes. Please allow extra time for your travels. Affected stops Bus Stop (560#) not in use · Routes · Alternate Stop #1222 -- Woodbridge / Bayshore · · 11 Waller · 57 Tunney's Pasture · 58 Tunney's Pasture · 81 Tunney's Pasture · 691 Omer-Deslauriers · #6455 -- Richmond / Bayshore or #3050 -- Bayshore A or #3050 -- Bayshore C Detour routing 11 Waller, 57 Tunney's Pasture, 58 Tunney's Pasture, 81 Tunney's Pasture, 691 Omer-Deslauriers: From Bayshore Station, exit at west access and follow Transitway toward Holly Acres, left onto Holly Acres, left onto Richmond, continue to regular route.

No 58 trips cancelled now · 0 did not run in NobyembreCancellations →

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

Ruta 58: Carling Campus/Abbott POC ~ Complexe Carling/Abbott POC ⇄ Bayshore / Tunney's Pasture

Bawat 30 hanggang 31 min

Papuntang Carling Campus ~ Complexe Carling1 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: Okt 27, 2026 – Nob 2, 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: 7 trips with qualifying later matching vehicle observations. Trips with any notice: 9.

Trips needing investigation

2 of 443 trips with a usable feed window (0.5%) had no matching position.

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

441 with position · 2 to investigate · 0 excluded · 443 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nob 3, 2026, 10:46 PM.

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: 441 / 443 (99.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: Nob 3, 2026, 9:48 PM

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

86.3%

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

Predictions in the source: 48,770
Weekdays with evidence: 19
Evidence window: Okt 5, 2026 – Nob 2, 2026

The hours we have evidence for

0696% · 783 predictions · 11 days
0792% · 1,130 predictions · 10 days
0880% · 1,539 predictions · 12 days
0991% · 1,983 predictions · 14 days
1090% · 1,929 predictions · 14 days
1191% · 1,966 predictions · 14 days
1292% · 1,948 predictions · 14 days
1392% · 1,896 predictions · 14 days
1486% · 1,950 predictions · 14 days
1585% · 1,718 predictions · 14 days
1687% · 1,734 predictions · 14 days
1769% · 1,561 predictions · 14 days
1866% · 1,444 predictions · 14 days
1984% · 1,235 predictions · 14 days
2094% · 1,056 predictions · 12 days
2193% · 1,010 predictions · 12 days
22100% · 614 predictions · 12 days
2399% · 470 predictions · 12 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: Nob 4, 2026

2 partial-capture days not counted.

What about time of day?

18 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

Mga bus na dumarating nang magkakasabay

Last 28 days, Oktubre 6, 2026 to Nobyembre 2, 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: Oktubre 8, 2026, Oktubre 15, 2026.

Mga halaga at paliwanag

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

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

Mga bus na dumarating nang magkakasabay
Oras ng araw	Mga pares na sinuri	Nagkumpol	Mahabang pagitan
Rush hour sa umaga (6 hanggang 9 a.m.)	1,151	0% (0)	0% (0)
Tanghali (9 a.m. hanggang 3 p.m.)	15,275	0% (48)	0% (24)
Rush hour sa hapon (3 hanggang 6 p.m.)	4,999	0% (0)	0% (11)
Gabi (6 hanggang 10 p.m.)	6,358	1% (61)	0% (20)
Gabi (10 p.m. hanggang 4 a.m.)	796	0% (0)	0% (0)

Paano ito sinusukat →How we got this numberMagkakadikit na bus at mabagal na bahagi sa bawat ruta →

Kung saan pinakamabagal ang rutang ito

Slowest: LINCOLN FIELDS 4A to BAYSHORE C, 14 km/h actual against 15.3 km/h planned.

Kung saan pinakamabagal ang rutang ito
Mula sa	Patungo sa	Layo	Planong bilis	Aktuwal na bilis	Mga biyaheng sinukat	Mabagal na biyahe
LINCOLN FIELDS 4A	BAYSHORE C	3.8 km	15.3 km/h	14 km/h	417	2%
BAYSHORE A	LINCOLN FIELDS 3A	3.4 km	13.5 km/h	14.6 km/h	322	1%
BAYSHORE A	LINCOLN FIELDS 2A	3.3 km	14.2 km/h	14.8 km/h	65	0%
ABBOTT POINT OF CARE / MOODIE	DISCOVERY / NETWORK ACCESS	1.7 km	16.9 km/h	16.6 km/h	102	6%
TUNNEY'S PASTURE B	RICHMOND / GOLDEN	2.4 km	16.6 km/h	17.3 km/h	33	3%
LINCOLN FIELDS 3A	RICHMOND / GOLDEN	3.2 km	21.5 km/h	18 km/h	33	3%
BAYSHORE C	DISCOVERY / NETWORK ACCESS	5.8 km	20.1 km/h	19.4 km/h	128	1%
RICHMOND / GOLDEN	LINCOLN FIELDS 4A	3.2 km	31.6 km/h	22 km/h	33	36%

Ang mabagal na biyahe ay inabot nang hindi bababa sa 1.5 beses ng planadong oras.

Paano ito sinusukat →

Gawaing-kalsada ng lungsod malapit sa rutang ito

Mga gawaing kalsada at pagsasara ng kalsada para sa event na inilathala ng City of Ottawa, na sinukat bilang malapit sa daanan ng rutang ito. Ang malapit ay hindi patunay na iniiba ang daan ng bus. Tingnan po ang sariling abiso ng tagapagpatakbo para doon.

Hindi po mabasa ngayon ang listahan ng lungsod ng mga gawaing pangkalsada.

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.

Pinagmulan: mga traffic event ng City of Ottawa (road work at mga pagsasara ng daan). May impormasyong lisensyado sa ilalim ng Open Government Licence, City of Ottawa. Ayon sa Lungsod, pinagsikapan lamang ang listahang ito at maaaring hindi kumpleto. Mapa ng trapiko ng Lungsod ng Ottawa ↗

Mga pagkansela sa rutang ito

Ano ang ibig sabihin ng mga salitang ito →

2 partial-capture days not counted.

11 scheduled trips with counted cancellation notices from Mar, Okt 6 to Lun, Nob 2.

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

Mga oras na may pinakamaraming kanseladong biyahe: 6 PM (4), 12 PM (1), 1 PM (1)

Mga pinakabagong kinanselang biyahe

Biy, Okt 30, scheduled 18:19
Miy, Okt 28, scheduled 20:16
Sab, Okt 24, scheduled 17:49
Sab, Okt 24, scheduled 13:34
Sab, Okt 24, scheduled 12:52

Hindi nagbibigay ang OC Transpo ng dahilan para sa isang biyahe, kaya walang ipinapakita.

Hindi dumating (walang nakitang bus, walang abiso), huling 7 araw: wala sa mga biyaheng nasuri namin.

Buksan ang may petsang pagsusuri ng hula

Hatol

What this route needs

Median provider predictions are 3.6 min later than the timetable in 1 hours of the day.

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

18:00 has 66% of predictions within five minutes of the timetable, against 91% 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.

Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 18 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: not enough data
06:00: 96.4% of final predictions within five minutes of the timetable, 783 predictions, typically 1 min late
07:00: 92.1% of final predictions within five minutes of the timetable, 1,130 predictions, typically 1 min late
08:00: 79.7% of final predictions within five minutes of the timetable, 1,539 predictions, typically 1.7 min late
09:00: 90.7% of final predictions within five minutes of the timetable, 1,983 predictions, typically 0.7 min late
10:00: 89.7% of final predictions within five minutes of the timetable, 1,929 predictions, typically 1.2 min late
11:00: 91% of final predictions within five minutes of the timetable, 1,966 predictions, typically 0.7 min late
12:00: 92.3% of final predictions within five minutes of the timetable, 1,948 predictions, typically 0.6 min late
13:00: 91.8% of final predictions within five minutes of the timetable, 1,896 predictions, typically 0.8 min late
14:00: 85.7% of final predictions within five minutes of the timetable, 1,950 predictions, typically 0.3 min late
15:00: 84.5% of final predictions within five minutes of the timetable, 1,718 predictions, typically 0.8 min late
16:00: 86.7% of final predictions within five minutes of the timetable, 1,734 predictions, typically 2 min late
17:00: 69.3% of final predictions within five minutes of the timetable, 1,561 predictions, typically 2.8 min late
18:00: 66% of final predictions within five minutes of the timetable, 1,444 predictions, typically 3.6 min late
19:00: 84% of final predictions within five minutes of the timetable, 1,235 predictions, typically 2.1 min late
20:00: 94.3% of final predictions within five minutes of the timetable, 1,056 predictions, typically 0.5 min late
21:00: 93% of final predictions within five minutes of the timetable, 1,010 predictions, typically 0.8 min late
22:00: 100% of final predictions within five minutes of the timetable, 614 predictions, typically 0.2 min late
23:00: 99.1% of final predictions within five minutes of the timetable, 470 predictions, typically 0.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	Kailan	Nasukat	Scenario or next investigation
ProblemPredictions later than timetable	18:00	3.6 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	18:00	66%	Operations, not the timetable
StrengthObserved-position lower bound	All measured hours	100%	Keep what works

Measurements

Predictions later than timetable · 18:00: Measured arrivals 1,444; Hours affected 1; Spread 9.9 min; Median delay 3.6 min; Suggested running time change 3.6 min
One hour has a lower prediction match · 18:00: Oras 18:00; Nasa oras 66%; Measured arrivals 1,444; Shortfall 24.8 pts; Route median on time 90.9%
Observed-position lower bound · All measured hours: Target 99.5%; Trips with a matching position 99.5%; Mga araw ng serbisyo 5; Trips with a matching position 441; Mga biyaheng nakatakda sa iskedyul 443

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 58 has been running

Maikling buod ng alam namin. Sinasabi namin kapag hindi namin masagot ang isang tanong.

Pangunahing punto

Karaniwang malapit sa iskedyul ang mga hula ng tagapagbigay ng serbisyo, pero tingnan po ang mga oras na may problema sa ibaba.

86 in 100 eligible predictions were within 5 minutes of the timetable · 48,770 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 48,770 eligible provider predictions over 27 measured days, from Okt 5, 2026 to Nob 2, 2026.

Updated Nob 3, 2026, 10:32 PM

Saan at kailan paulit-ulit na nagkaiba ang mga hula?

Ito ay mga paulit-ulit na pagkakaiba ng hula at ng iskedyul, hindi mga pagkabigo sa serbisyo na sinukat nang hiwalay. Ginagamit nito ang parehong karapat-dapat na mga hula gaya ng resulta sa itaas, pero pinagsasama-sama ayon sa hintuan, hindi ayon sa oras. Kaya maaaring hindi magkapareho ang mga listahan sa bawat linya.

18–19: 34 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,444 predictions over 14 days).
17–18: 31 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,561 predictions over 14 days).

1 current notice affects this route

• UPDATED -- Detour: EB routes 11, 57, 58, 81, 691 around Richmond and Bayshore lane closures

Pagkakaiba ng hula ayon sa hintuan

Wala pa kaming sapat na kasaysayan ng ruta bawat hintuan para pangalanan ang paulit-ulit na problemang hintuan. Ginagamit lang na pahiwatig ang mga ulat ng mga sakay, hindi patunay.

Suriin ang bawat biyahe at petsa

Magbukas ng yugto ng panahon para makita ang bawat araw ng serbisyo, nakatakdang biyahe, puwang sa feed, naobserbahang pampublikong ID ng sasakyan, at ang eksaktong bilang sa likod ng buod na ito.

Ang gustong malaman ng mga pasahero

May kanseladong biyahe ba ngayon?: 0 of 2Sinusuri ang mga biyaheng magsisimula sa dulo ng ruta sa susunod na 4 na oras. Hindi ito makasaysayang bilang ng pagkansela.
Posibleng hindi sumipot matapos suriin ang mga puwang sa feed?: 2 of 443 checked trips need a closer look2 of 443 trips with enough public-feed evidence had no matching position over 7 days. 0 of 443 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Paano naiba ang mga hula ng tagapagbigay ng serbisyo sa iskedyul?: At the 95th percentile, the predicted difference was 8.6 min (positive means later; negative means earlier)86 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
Gaano katagal na paghihintay ang ipinahiwatig ng mga tinatayang oras ng operator?: Ang karaniwang inaasahang dagdag na paghihintay ay wala pang 30 segundo sa hintuang kinunan ng sample0.1 min less than the scheduled wait, based on 70 eligible predictions at 1 stop hours across 14 service days.

Pagsusuri ng pagbabago sa iskedyul

Nailathalang iskedyul: bago at pagkatapos

Ikinukumpara po nito ang kasalukuyang opisyal na iskedyul na iniingatan sa naunang bersyon na iniingatan. Ang mga pagbabago sa iskedyul ay mga katotohanan tungkol sa kung ano ang binalak. Hindi po nito pinatutunayan na naganap ang isang biyahe.

Current published schedule began Oktubre 30, 2026

Piniling araw ng serbisyo mula sa bawat inilathalang iskedyul

Sinusuri po namin ang unang Lunes pagkatapos magsimula ang bagong iskedyul at ang Lunes isang linggo bago nito. Ang bawat bilang ay galing sa mga opisyal na bersyon ng GTFS na itinabi at nakasaad sa ibaba.

Hindi bababa sa isa sa mga napiling petsa ang may idinagdag o inalis na serbisyo sa petsa ng kalendaryo. Ituring po ito bilang konteksto ng holiday o espesyal na serbisyo, hindi karaniwang paglago tuwing karaniwang araw.

Bago

Petsa ng serbisyo na sinuri: Oktubre 26, 2026

Mga biyaheng nakatakda sa iskedyul: 69
Mga natatanging hintuan na nasa iskedyul: 79
Iba't ibang inilathalang daanan: 8
Inilathalang oras ng serbisyo: 06:09–23:33

Operator calendar-date records: 0 added · 2 removed

Fingerprint ng feed: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

Bagong iskedyul

Petsa ng serbisyo na sinuri: Nobyembre 2, 2026

Mga biyaheng nakatakda sa iskedyul: 69
Mga natatanging hintuan na nasa iskedyul: 79
Iba't ibang inilathalang daanan: 8
Inilathalang oras ng serbisyo: 06:09–23:33

Operator calendar-date records: 0 added · 2 removed

Fingerprint ng feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

Gumanda po ba ang serbisyo pagkatapos ng pagbabago?

Ihahambing po namin ang mga natapos na dating ng sasakyan sa loob ng 14 na araw bago at pagkatapos ng pagbabago. Ilalathala lamang po namin ang paghahambing kapag may hindi bababa sa 7 araw ng serbisyo at 200 dating ang magkabilang panig.

Still collecting: before has 25,900 arrivals over 14 days; after has 6,900 arrivals over 4 days. No improvement or decline is claimed yet.

Sa checksum, maaaring tiyakin ng sinuman kung aling iskedyul na itinabi ang pinagmulan ng mga bilang. Ang pagbabago sa bilang ay hindi nagpapakita ng dahilan, pagkansela, desisyon ng operator, o epekto sa mga pasahero.

Paano hinuhusgahan ang rutang ito: Regular na ruta na humihinto sa lahat ng hintuan

Inihahambing namin ang huling karapat-dapat na hula ng provider para sa bawat nakaiskedyul na pagdating sa opisyal na iskedyul. Hindi ito mga pagdating na sinukat nang hiwalay. Kailangan ng hindi bababa sa 200 karapat-dapat na hula para magkaroon ng resulta. Ang loob ng 5 minuto ang target para sa mga sakay na ginagamit dito.

Ang hindi mapatutunayan ng datos na ito

Ang public feed po ay hindi nagbibigay ng maaasahang bilang ng pasahero o ng mga pagkakataong nilampasan ang mga naghihintay na pasahero. Ang kawalan ng posisyon ay hindi nangangahulugang patunay ng pagkansela, hindi pagdating, maikling biyahe o sanhi nito.

Tingnan ang mga kahulugan, hangganan at pagkakasunod-sunod ng ebidensya

Opisyal na kasalukuyang feed: mga tahasang pagkansela, mga nilaktawang hintuan, at mga aktibong abiso.
Mga tugmang obserbasyon: mga posisyon ng sasakyan at mga pinal na prediksyon na iniugnay sa opisyal na iskedyul.
Opisyal na iskedyul: ang plano, hiwalay sa naobserbahan.
Mga ulat ng pasahero at operator: mga lead tungkol sa ruta, oras, at lugar na dapat imbestigahan. Hindi ito sapat na patunay na numerikal sa sarili nito.

Pansamantalang resulta, inilathalang ebidensya

Paano ikinumpara ang mga hula sa iskedyul?

Sa bawat oras, inihahambing ang huling karapat-dapat na predicted na dating mula sa provider para sa isang scheduled na pagdating sa timetable. Ang "Within 5 minutes" ay naglalarawan ng pagkakaiba ng prediksyon, hindi ng nasukat na pagdating o patunay na bumiyahe ang bus.

Saklaw ng ebidensya: Oktubre 5, 2026 to Nobyembre 2, 2026

Sa loob ng 5 minuto mula sa iskedyul: 86.3%
Mga karapat-dapat na hula na nasuri: 48,770
Mga araw ng linggo na may datos: 19
Tinatayang pagkaantala sa ika-95 na percentile: 8.6 min late

Patterns by hour (18)

Patterns by hour (18)
Oras	Nasa oras	Median	95th percentile	Ebidensya
06:00	96.4%	1 min late	4.7 min late	783 · 11 days
07:00	92.1%	1 min late	5.5 min late	1,130 · 10 days
08:00	79.7%	1.7 min late	11 min late	1,539 · 12 days
09:00	90.7%	0.7 min late	6.6 min late	1,983 · 14 days
10:00	89.7%	1.2 min late	7.8 min late	1,929 · 14 days
11:00	91.0%	0.7 min late	5.8 min late	1,966 · 14 days
12:00	92.3%	0.6 min late	6.9 min late	1,948 · 14 days
13:00	91.8%	0.8 min late	5.9 min late	1,896 · 14 days
14:00	85.7%	0.3 min late	14.9 min late	1,950 · 14 days
15:00	84.5%	0.8 min late	6.8 min late	1,718 · 14 days
16:00	86.7%	2 min late	7.5 min late	1,734 · 14 days
17:00	69.3%	2.8 min late	14.6 min late	1,561 · 14 days
18:00	66.0%	3.6 min late	13.5 min late	1,444 · 14 days
19:00	84.0%	2.1 min late	9 min late	1,235 · 14 days
20:00	94.3%	0.5 min late	5.1 min late	1,056 · 12 days
21:00	93.0%	0.8 min late	5.7 min late	1,010 · 12 days
22:00	100.0%	0.2 min late	2.2 min late	614 · 12 days
23:00	99.1%	0.1 min late	2.7 min late	470 · 12 days

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

Nakaiskedyul na bus, ngunit hindi naobserbahan sa real-time

441 / 443 scheduled trips published at least one position across 5 service days (99.5%).

20:001 / 24 trips without a position95.8%
18:001 / 28 trips without a position96.4%
06:000 / 15 trips without a position100.0%
07:000 / 20 trips without a position100.0%
08:000 / 28 trips without a position100.0%
09:000 / 27 trips without a position100.0%

Hindi ito kumpirmadong hindi pagsipot. Ang nawawalang posisyon ay maaaring mangahulugang kinansela o nalagpasang bus, pero maaari rin itong mangahulugang walang nakatalagang ID ng biyahe o may puwang sa feed ng operator. Inilalathala ng Otranspo ang puwang dahil mahalaga ito sa mga sakay, habang nananatiling tapat ang konklusyon.

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. Mga pinagmulan at limitasyon.

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

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

06:09– 06:23
Trip 18817020Vehicle position matchedFirst / last feed position: 6:09 a.m. EST / 6:21 a.m. EST; not actual start or end times.
06:24– 07:00
Trip 22929020Vehicle position matchedFirst / last feed position: 5:57 a.m. EST / 7:03 a.m. EST; not actual start or end times.
06:46– 07:06
Trip 31904020Vehicle position matchedFirst / last feed position: 6:48 a.m. EST / 7:04 a.m. EST; not actual start or end times.
07:08– 07:54
Trip 6864020Vehicle position matchedFirst / last feed position: 6:35 a.m. EST / 7:56 a.m. EST; not actual start or end times.
07:17– 07:37
Trip 27631020Vehicle position matchedFirst / last feed position: 7:13 a.m. EST / 7:35 a.m. EST; not actual start or end times.
07:39– 08:27
Trip 23957020Vehicle position matchedFirst / last feed position: 7:05 a.m. EST / 8:34 a.m. EST; not actual start or end times.
07:47– 08:07
Trip 30322020Vehicle position matchedFirst / last feed position: 7:35 a.m. EST / 8:04 a.m. EST; not actual start or end times.
08:09– 09:00
Trip 31039020Vehicle position matchedFirst / last feed position: 8:10 a.m. EST / 9:04 a.m. EST; not actual start or end times.
08:17– 08:37
Trip 10570020Vehicle position matchedFirst / last feed position: 8:22 a.m. EST / 8:46 a.m. EST; not actual start or end times.
08:32– 09:18
Trip 28774020Vehicle position matchedFirst / last feed position: 8:35 a.m. EST / 9:25 a.m. EST; not actual start or end times.
08:39– 09:30
Trip 31021020Vehicle position matchedFirst / last feed position: 8:11 a.m. EST / 9:41 a.m. EST; not actual start or end times.
08:47– 09:05
Trip 30943020Vehicle position matchedFirst / last feed position: 8:42 a.m. EST / 9:02 a.m. EST; not actual start or end times.

· Open all evidence for this day