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 11월Cancellations →

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.

58번 노선: Carling Campus/Abbott POC ~ Complexe Carling/Abbott POC ⇄ Bayshore / Tunney's Pasture

30분에서 31분마다

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 2026. 10. 28. – 2026. 11. 3.

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

Trips needing investigation

3 of 443 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.

440 with position · 3 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: 2026. 11. 4. 오전 4:04.

Coverage, exclusions and sources

0 of 7 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: 440 / 443 (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: 2026. 11. 4. 오전 3:09

Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.

What does the evidence show?

Predictions against the timetable

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: 2026. 10. 5. – 2026. 11. 2.

The hours we have evidence for

6시97% · 780 predictions · 10 days
7시92% · 1,130 predictions · 10 days
8시75% · 1,539 predictions · 12 days
9시89% · 1,983 predictions · 14 days
10시90% · 1,929 predictions · 14 days
11시91% · 1,966 predictions · 14 days
12시92% · 1,948 predictions · 14 days
13시91% · 1,896 predictions · 14 days
14시86% · 1,950 predictions · 14 days
15시85% · 1,718 predictions · 14 days
16시88% · 1,734 predictions · 14 days
17시69% · 1,561 predictions · 14 days
18시62% · 1,445 predictions · 14 days
19시86% · 1,241 predictions · 14 days
20시95% · 1,057 predictions · 12 days
21시93% · 1,010 predictions · 12 days
22시100% · 614 predictions · 12 days
23시99% · 469 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: 2026. 11. 4.

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

몰려서 도착하는 버스

Last 28 days, 2026년 10월 7일 to 2026년 11월 3일: 25 days counted.

2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: 2026년 10월 8일, 2026년 10월 15일.

값과 해석

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

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

몰려서 도착하는 버스
시간대	확인한 쌍	몰림	긴 배차 간격
아침 혼잡 시간 (오전 6시부터 9시)	1,081	0% (0)	0% (0)
낮 시간 (오전 9시부터 오후 3시)	14,527	0% (13)	0% (11)
오후 혼잡 시간 (오후 3시~6시)	4,744	0% (0)	0% (11)
저녁 (오후 6시~10시)	6,189	1% (61)	0% (20)
야간 (오후 10시부터 오전 4시까지)	796	0% (0)	0% (0)

측정 방법 →How we got this number모든 노선의 버스 몰림과 느린 구간 →

이 노선에서 가장 느린 구간

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

이 노선에서 가장 느린 구간
출발지	도착	거리	계획 속도	실제 속도	측정된 운행	느린 운행
LINCOLN FIELDS 4A	BAYSHORE C	3.8 km	15.3 km/h	14.1 km/h	398	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.8 km/h	15 km/h	49	0%
ABBOTT POINT OF CARE / MOODIE	DISCOVERY / NETWORK ACCESS	1.7 km	16.9 km/h	16.5 km/h	96	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	121	1%
RICHMOND / GOLDEN	LINCOLN FIELDS 4A	3.2 km	31.6 km/h	22 km/h	33	36%

느린 운행은 계획된 시간의 1.5배 이상 걸린 운행입니다.

측정 방법 →

이 노선 근처의 시 도로 공사

오타와시가 발표한 도로 공사와 행사 도로 통제 중 이 노선 경로 근처에 있는 것입니다. 근처라고 해서 버스가 우회한다는 뜻은 아닙니다. 우회 여부는 운영 기관의 서비스 알림을 확인하세요.

도로 공사
417 W/B off ramp at Bayshore
2026. 4. 29. 오전 6:00 to 2026. 12. 31. 오후 5:00
417 W/B off ramp at Bayshore left-turn lane to Richmond closed off-peak due to construction, from April 29th to December 31. Cyclists and pedestrians not affected.
시에서 대중교통에 영향을 준다고 표시했습니다.
about 17 m from the route
City record updated 2026. 8. 28. 오후 1:32.
도로 공사
Richmond E/B at Bayshore
2026. 9. 20. 오전 6:00 to 2026. 11. 16. 오후 11:00
Richmond eastbound left-turn lanes closed at Bayshore due to construction. Staring Monday, 21 September until Monday, 16 November.
시에서 대중교통에 영향을 준다고 표시했습니다.
about 5 m from the route
City record updated 2026. 9. 20. 오전 5:56.
도로 공사
CARLING E/B between Kichi Zibi Mikan on Ramp and EDGEWORTH
2026. 10. 30. 오전 12:00 to 2026. 11. 13. 오후 3: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 2026. 10. 30. 오전 11:40.
도로 공사
Kichi Zibi Mikan between ISLAND PARK and WOODROFFE
2026. 10. 30. 오전 9:30 to 2026. 11. 20. 오후 3:00
Kichi Zibi Mikan reduced to 1 lane in each direction between ISLAND PARK and WOODROFFE due to construction, from November 2nd to 20th between 9:30am and 3:00pm.
about 0 m from the route
City record updated 2026. 10. 30. 오전 9: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.

출처: 오타와시 교통 이벤트(도로 공사 및 통제). 오타와시 오픈 정부 라이선스에 따라 제공된 정보를 포함합니다. 시는 이 목록이 최선의 노력으로 작성되었으며 불완전할 수 있다고 밝히고 있습니다. 오타와시 교통 지도 ↗

이 노선의 취소

이 용어의 뜻 →

2 partial-capture days not counted.

11 scheduled trips with counted cancellation notices from 10월 7일 (수) to 11월 3일 (화).

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

취소가 가장 많은 시간대: 오후 6시 (4), 오후 12시 (1), 오후 1시 (1)

최근 취소된 운행

10월 30일 (금), scheduled 18:19
10월 28일 (수), scheduled 20:16
10월 24일 (토), scheduled 17:49
10월 24일 (토), scheduled 13:34
10월 24일 (토), scheduled 12:52

OC Transpo는 개별 운행의 사유를 제공하지 않아서 표시하지 않습니다.

오지 않음(버스가 보이지 않았고 안내도 없음), 최근 7일: 확인할 수 있었던 운행 중에는 없습니다.

날짜별 예측 분석 열기

결론

What this route needs

Median provider predictions are 3.8 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 62% of predictions within five minutes of the timetable, against 90% the rest of the day.

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

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.8% of final predictions within five minutes of the timetable, 780 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: 74.8% of final predictions within five minutes of the timetable, 1,539 predictions, typically 1.9 min late
09:00: 89.3% 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.3 min late
11:00: 91.1% of final predictions within five minutes of the timetable, 1,966 predictions, typically 0.7 min late
12:00: 91.8% of final predictions within five minutes of the timetable, 1,948 predictions, typically 0.7 min late
13:00: 91.4% of final predictions within five minutes of the timetable, 1,896 predictions, typically 0.9 min late
14:00: 85.6% of final predictions within five minutes of the timetable, 1,950 predictions, typically 0.3 min late
15:00: 84.7% of final predictions within five minutes of the timetable, 1,718 predictions, typically 0.8 min late
16:00: 87.6% of final predictions within five minutes of the timetable, 1,734 predictions, typically 2 min late
17:00: 69.4% of final predictions within five minutes of the timetable, 1,561 predictions, typically 2.6 min late
18:00: 62.3% of final predictions within five minutes of the timetable, 1,445 predictions, typically 3.8 min late
19:00: 85.8% of final predictions within five minutes of the timetable, 1,241 predictions, typically 1.9 min late
20:00: 94.5% of final predictions within five minutes of the timetable, 1,057 predictions, typically 0.4 min late
21:00: 93% of final predictions within five minutes of the timetable, 1,010 predictions, typically 0.7 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, 469 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	시간	측정됨	Scenario or next investigation
ProblemPredictions later than timetable	18:00	3.8 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	18:00	62%	Operations, not the timetable
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 18:00: Measured arrivals 1,445; Hours affected 1; Spread 13.3 min; Median delay 3.8 min; Suggested running time change 3.8 min
One hour has a lower prediction match · 18:00: 시간 18:00; 정시 62.3%; Measured arrivals 1,445; Shortfall 28.1 pts; Route median on time 90.4%
Coverage gap · All measured hours: 목표 99.5%; Trips with a matching position 99.3%; 운행 요일 5; Trips with a matching position 440; 시간표상 운행 443

이력, 신뢰도, 노선 분석 열기

노선 확인

How route 58 has been running

우리가 아는 내용을 짧게 정리했습니다. 답할 수 없는 질문은 그렇다고 알려 드립니다.

결론

운영사 예측은 대체로 예정 시간표와 가까웠습니다. 그래도 아래 문제 시간대를 확인하세요.

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

예측 표본 수: 표본 많음

Based on 48,770 eligible provider predictions over 27 measured days, from 2026년 10월 5일 to 2026년 11월 2일.

Updated 2026. 11. 4. 오전 2:41

예측이 반복해서 달랐던 곳과 시간은 언제인가요?

이 목록은 예측과 시간표의 차이가 반복된 경우이며, 독립적으로 측정한 운행 문제가 아니에요. 위 결과와 같은 대상 예측을 쓰지만 시간대가 아니라 정류장별로 묶기 때문에, 두 목록이 줄마다 같지는 않을 수 있어요.

18시–19시: 38 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,445 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

정류장별 예측 차이

반복되는 문제 정류장을 지목할 만큼 노선별 정류장 기록이 아직 충분하지 않습니다. 승객 신고는 증거가 아니라 단서로만 사용합니다.

모든 운행과 날짜 확인

기간을 열면 각 운행일, 시간표상 운행, 데이터 공백, 관측된 공개 차량 ID, 그리고 이 요약의 정확한 집계를 볼 수 있습니다.

승객이 알고 싶어 하는 것

지금 취소된 운행이 있나요?: 0 of 7앞으로 4시간 안에 노선 종점에서 출발하는 운행을 확인합니다. 과거의 운행 취소율이 아닙니다.
피드 공백을 확인한 후 무정차 가능성이 있나요?: 3 of 443 checked trips need a closer look3 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.
제공자의 예측은 시간표와 얼마나 달랐나요?: 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.
운영사의 예측은 어떤 대기 시간을 뜻했나요?: 표본 정류장에서 예측된 평균 추가 대기 시간은 30초 미만이었습니다0.1 min less than the scheduled wait, based on 70 eligible predictions at 1 stop hours across 14 service days.

시간표 변경 확인

게시된 시간표: 변경 전과 후

이 내용은 현재 보관 중인 공식 시간표를 이전에 보관한 버전과 비교한 것입니다. 시간표 변경은 계획된 내용에 대한 사실일 뿐입니다. 실제로 운행이 있었다는 증거는 아닙니다.

Current published schedule began 2026년 10월 30일

공개된 각 시간표에서 선택한 운행일

새 시간표가 시작된 후 첫 번째 월요일과 그 일주일 전 월요일을 확인합니다. 모든 수치는 아래에 나온 보관된 공식 GTFS 버전에서 가져옵니다.

선택한 날짜 중 하나 이상에 날짜 지정으로 추가되거나 제외된 운행이 있습니다. 일반 평일의 증가가 아니라 공휴일 또는 특별 운행 상황으로 봐 주세요.

변경 전

확인한 운행 날짜: 2026년 10월 26일

시간표상 운행: 69
서로 다른 정류장 수(시간표 기준): 79
공개된 고유 경로 수: 8
공고된 운행 시간대: 06:09–23:33

Operator calendar-date records: 0 added · 2 removed

피드 지문: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

새 시간표

확인한 운행 날짜: 2026년 11월 2일

시간표상 운행: 69
서로 다른 정류장 수(시간표 기준): 79
공개된 고유 경로 수: 8
공고된 운행 시간대: 06:09–23:33

Operator calendar-date records: 0 added · 2 removed

피드 지문: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

변경 후에 서비스가 좋아졌나요?

We will compare settled arrivals for the 14 days before and after the change. We publish the comparison only after both sides have at least 7 service days and 200 arrivals.

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

체크섬을 사용하면 어떤 시간표 보관본으로 집계 수치를 만들었는지 누구나 확인할 수 있습니다. 집계 수치가 바뀌어도 원인, 취소, 운영사의 결정, 승객에게 미친 영향은 알 수 없습니다.

이 노선을 평가하는 방법: 모든 정류장에 서는 일반 노선

각 예정 도착에 대해 마지막 유효한 제공자 예측을 공식 시간표와 비교합니다. 독립적으로 측정한 도착이 아닙니다. 결과를 내려면 유효한 예측이 200건 이상 필요합니다. 5분 이내는 여기서 승객 기준으로 사용하는 목표입니다.

이 데이터로 증명할 수 없는 것

공개 데이터에는 믿을 만한 승객 수나 승객을 태우지 못하고 지나친 기록이 없습니다. 위치 정보가 없다고 해서 그것만으로 운행 취소, 미운행, 단축 회차, 또는 그 원인이 확인되는 것은 아닙니다.

정의, 기준값, 데이터 순서 보기

공식 현재 데이터: 명시된 운행 취소, 건너뛴 정류장, 진행 중인 공지입니다.
일치한 관측값: 공식 시간표와 연결된 차량 위치와 확정된 예측입니다.
공식 시간표입니다. 계획된 운행은 관측된 운행과 따로 구분합니다.
이용자와 운영 기관의 신고: 조사할 노선, 시간, 장소에 대한 단서이며, 그것만으로 수치 증거가 되지는 않습니다.

잠정 결과, 공개된 근거 자료

예측은 시간표와 어떻게 달랐나요?

매시간 예정된 도착에 대해 마지막으로 유효한 제공자 예측을 시간표와 비교합니다. “5분 이내”는 이 예측 차이를 뜻합니다. 실제로 측정한 도착이나 버스 운행의 증거가 아닙니다.

근거 기간: 2026년 10월 5일 to 2026년 11월 2일

시간표 기준 5분 이내: 86.3%
확인한 적격 예측: 48,770
데이터가 있는 평일: 19
95번째 백분위수 예측 지연: 8.6 min late

Patterns by hour (18)

Patterns by hour (18)
시간	정시	중앙값	95번째 백분위수	증거 자료
06:00	96.8%	1 min late	4.6 min late	780 · 10 days
07:00	92.1%	1 min late	5.4 min late	1,130 · 10 days
08:00	74.8%	1.9 min late	13 min late	1,539 · 12 days
09:00	89.3%	0.7 min late	8.5 min late	1,983 · 14 days
10:00	89.7%	1.3 min late	7.8 min late	1,929 · 14 days
11:00	91.1%	0.7 min late	5.9 min late	1,966 · 14 days
12:00	91.8%	0.7 min late	6.9 min late	1,948 · 14 days
13:00	91.4%	0.9 min late	6 min late	1,896 · 14 days
14:00	85.6%	0.3 min late	14.9 min late	1,950 · 14 days
15:00	84.7%	0.8 min late	6.8 min late	1,718 · 14 days
16:00	87.6%	2 min late	7.1 min late	1,734 · 14 days
17:00	69.4%	2.6 min late	14.6 min late	1,561 · 14 days
18:00	62.3%	3.8 min late	17.1 min late	1,445 · 14 days
19:00	85.8%	1.9 min late	8.1 min late	1,241 · 14 days
20:00	94.5%	0.4 min late	5.1 min late	1,057 · 12 days
21:00	93.0%	0.7 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.9 min late	469 · 12 days

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

시간표에는 있지만 실시간으로 확인되지 않은 버스

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

18:002 / 28 trips without a position92.9%
20:001 / 24 trips without a position95.8%
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%

확인된 결행이 아닙니다. 위치가 없다면 버스가 취소되었거나 놓쳤을 수 있습니다. 하지만 운행 ID가 배정되지 않았거나 운영사 피드에 빈 구간이 있을 수도 있습니다. Otranspo는 승객에게 중요한 정보이므로 이 공백을 게시합니다. 다만 결론은 정직하게 유지합니다.

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. 출처와 한계.

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

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

06:09– 06:23
Trip 18817030Vehicle position matchedFirst / last feed position: 6:07 a.m. EST / 6:21 a.m. EST; not actual start or end times.
06:24– 07:00
Trip 22929030Vehicle 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 31904030Vehicle position matchedFirst / last feed position: 6:43 a.m. EST / 7:02 a.m. EST; not actual start or end times.
07:08– 07:54
Trip 6864030Vehicle position matchedFirst / last feed position: 6:34 a.m. EST / 7:56 a.m. EST; not actual start or end times.
07:17– 07:37
Trip 27631030Vehicle 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 23957030Vehicle position matchedFirst / last feed position: 7:04 a.m. EST / 8:36 a.m. EST; not actual start or end times.
07:47– 08:07
Trip 30322030Vehicle position matchedFirst / last feed position: 7:36 a.m. EST / 8:05 a.m. EST; not actual start or end times.
08:09– 09:00
Trip 31039030Vehicle position matchedFirst / last feed position: 8:13 a.m. EST / 9:36 a.m. EST; not actual start or end times.
08:17– 08:37
Trip 10570030Vehicle position matchedFirst / last feed position: 8:30 a.m. EST / 8:50 a.m. EST; not actual start or end times.
08:32– 09:18
Trip 28774030Vehicle position matchedFirst / last feed position: 8:37 a.m. EST / 9:26 a.m. EST; not actual start or end times.
08:39– 09:30
Trip 31021030Vehicle position matchedFirst / last feed position: 8:15 a.m. EST / 9:53 a.m. EST; not actual start or end times.
08:47– 09:05
Trip 30943030Vehicle position matchedFirst / last feed position: 8:42 a.m. EST / 9:04 a.m. EST; not actual start or end times.

· Open all evidence for this day