Stop impacts: Baseline 1C and 1D relocated during Transitway closure: June 11 2026 - From 11:00 pm on Thursday, June 11, until 6:00 pm on Monday, November 16, stops 1C and 1D at Baseline Station will be relocated slightly north along the platform, out of the way of construction work. As a result, stops for routes 53 Tunney's Pasture, 75 Barrhaven Centre, 82 Lincoln Fields, 84 Centrepointe, and 187 Amberwood will be affected. The construction work will require routes 53 Tunney's Pasture, 75 Barrhaven Centre, 82 Lincoln Fields, 84 Centrepointe, 187 Baseline, 187 Amberwood, and 189 Colonnade to detour slightly when arriving at, driving through, and departing from Baseline Station. Affected stops Bus Stop (560#) not in use · Routes · Alternate Stop #3017 -- Baseline 1C · · 53 Tunney's Pasture · 82 Lincoln Fields · 84 Centrepointe · 187 Amberwood · #3017 -- Baseline 1A #3017 -- Baseline 1D · · 75 Barrhaven Centre · TEMP -- Between Baseline 1B and 1C Detour routing 53 Tunney's Pasture, 75 Barrhaven Centre, 82 Lincoln Fields, 84 Centrepointe, 187 Amberwood, 189 Colonnade: From Baseline Station, turn left onto buses-only roadway toward Adjidjàk Private, right onto Woodroffe, then continue to regular route. 187 Baseline: From Woodroffe northbound, turn left onto bus-only roadway at Adjidjàk Private, right onto Transitway to end route. Stops map

No 53 trips cancelled now · 7 did not run in NovemberCancellations →

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

Route 53: Tunney's Pasture ⇄ Baseline

Every 15 to 30 min

Toward Tunney's Pasture0 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: Oct 28, 2026 – Nov 3, 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: 15 trips with qualifying later matching vehicle observations. Trips with any notice: 26.

Trips needing investigation

16 of 635 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.

619 with position · 16 to investigate · 0 excluded · 635 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 11:03 p.m..

Coverage, exclusions and sources

0 of 4 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: 619 / 635 (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: Nov 4, 2026, 9:38 p.m.

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

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

Predictions in the source: 132,043
Weekdays with evidence: 19
Evidence window: Oct 6, 2026 – Nov 3, 2026

The hours we have evidence for

12 a.m.87% · 1,313 predictions · 14 days
1 a.m.76% · 695 predictions · 12 days
5 a.m.85% · 650 predictions · 12 days
6 a.m.91% · 2,677 predictions · 14 days
7 a.m.73% · 4,953 predictions · 14 days
8 a.m.58% · 4,881 predictions · 14 days
9 a.m.68% · 4,721 predictions · 14 days
10 a.m.66% · 3,259 predictions · 14 days
11 a.m.67% · 3,240 predictions · 14 days
12 p.m.62% · 3,200 predictions · 14 days
1 p.m.68% · 3,214 predictions · 14 days
2 p.m.62% · 3,441 predictions · 14 days
3 p.m.45% · 4,840 predictions · 14 days
4 p.m.47% · 5,348 predictions · 14 days
5 p.m.55% · 5,367 predictions · 14 days
6 p.m.51% · 4,458 predictions · 14 days
7 p.m.67% · 3,171 predictions · 14 days
8 p.m.85% · 3,262 predictions · 14 days
9 p.m.89% · 3,209 predictions · 14 days
10 p.m.87% · 2,212 predictions · 14 days
11 p.m.80% · 1,515 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: Nov 5, 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

Buses arriving bunched

Last 28 days, October 7, 2026 to November 3, 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: October 8, 2026, October 15, 2026.

Values and interpretation

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

2% of pairs (1,816) had a long gap: more than 1.75 times the planned wait between them.

Buses arriving bunched
Time of day	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	18,727	3% (525)	2% (332)
Midday (9 a.m. to 3 p.m.)	29,025	2% (467)	1% (183)
Afternoon rush (3 to 6 p.m.)	26,396	6% (1,474)	3% (789)
Evening (6 to 10 p.m.)	23,133	2% (576)	2% (489)
Night (10 p.m. to 4 a.m.)	4,850	0% (0)	0% (23)

How this is measured →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: HOLLAND / CARLING to TUNNEY'S PASTURE E, 9.5 km/h actual against 11.6 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
HOLLAND / CARLING	TUNNEY'S PASTURE E	1.8 km	11.6 km/h	9.5 km/h	26	12%
WOODROFFE / MEDHURST	BASELINE 2A	1.6 km	10.7 km/h	9.7 km/h	40	15%
HOLLAND / CARLING	LAPERRIÈRE / KIRKWOOD	2.8 km	18.8 km/h	14.9 km/h	1,041	17%
TUNNEY'S PASTURE D	HOLLAND / CARLING	1.8 km	15.7 km/h	15.2 km/h	1,033	13%
WOODFIELD / TANGLEWOOD PARK	CLYDE / BASELINE	3.1 km	20.6 km/h	16.4 km/h	1,105	14%
CLYDE / BASELINE	WOODFIELD / TANGLEWOOD PARK	3 km	18.3 km/h	18.1 km/h	1,042	3%
CLYDE / BASELINE	HOLLAND / CARLING	5.7 km	19.9 km/h	18.9 km/h	1,095	1%
BASELINE 1C	WOODFIELD / TANGLEWOOD PARK	3.7 km	21.3 km/h	21.7 km/h	888	5%

A slow trip took at least 1.5 times the planned time.

How this is measured →

City road work near this route

Road work and event road closures the City of Ottawa has published, measured as near this route’s path. Near is not proof that the bus is detoured: check the operator’s own alerts for that.

Road work
Anna - between Carling and General
May 4, 2026, 6:00 a.m. to Dec 1, 2026, 5:00 p.m.
Anna - closed between Carling and General due to construction. Access for local traffic maintained. Until 5 p.m. December 1.
about 0 m from the route
City record updated Sep 4, 2026, 9:39 a.m..
Road work
HOLLINGTON between SHILLINGTON and EMPEROR
Oct 15, 2026, 12:00 a.m. to Nov 13, 2026, 5:00 p.m.
HOLLINGTON off-peak lane reductions between SHILLINGTON and EMPEROR due to construction, from October 15th to November 13th.
The City marks this as affecting transit.
about 0 m from the route
City record updated Oct 16, 2026, 11:04 a.m..
Road work
Merivale N/B between Woodfield/Roydon and Viewmount
Oct 23, 2026, 12:00 a.m. to Dec 14, 2026, 5:00 p.m.
Merivale northbound right lane closed between Woodfield/Roydon and Viewmount due to construction, until December 14th.
The City marks this as affecting transit.
about 0 m from the route
City record updated Nov 4, 2026, 9:52 a.m..

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.

Source: City of Ottawa traffic events (road work and closures). Contains information licensed under the Open Government Licence, City of Ottawa. The City says this list is best effort and may be incomplete. City of Ottawa traffic map ↗

Cancellations on this route

What these words mean →

2 partial-capture days not counted.

27 scheduled trips with counted cancellation notices from Wed, Oct 7 to Tue, Nov 3.

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

Hours with the most cancellations: 5 p.m. (9), 4 p.m. (7), 2 p.m. (4)

Latest cancelled trips

Mon, Nov 2, scheduled 06:11
Sun, Nov 1, scheduled 20:54
Sun, Nov 1, scheduled 16:40
Sat, Oct 31, scheduled 17:50
Sat, Oct 31, scheduled 14:05

OC Transpo gives no reason for single trips, so none is shown.

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

Open the dated prediction analysis

Verdict

What this route needs

Median provider predictions are 3.1 to 4.9 min later than the timetable in 11 hours of the day.

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

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

Only 98% 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, 21 hours with samples

00:00: 87.4% of final predictions within five minutes of the timetable, 1,313 predictions, typically 1.8 min late
01:00: 75.5% of final predictions within five minutes of the timetable, 695 predictions, typically 1.7 min late
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 84.8% of final predictions within five minutes of the timetable, 650 predictions, typically 3.1 min late
06:00: 90.5% of final predictions within five minutes of the timetable, 2,677 predictions, typically 1.2 min late
07:00: 73.2% of final predictions within five minutes of the timetable, 4,953 predictions, typically 2.6 min late
08:00: 57.6% of final predictions within five minutes of the timetable, 4,881 predictions, typically 3.9 min late
09:00: 67.6% of final predictions within five minutes of the timetable, 4,721 predictions, typically 3.4 min late
10:00: 65.5% of final predictions within five minutes of the timetable, 3,259 predictions, typically 3.5 min late
11:00: 67.3% of final predictions within five minutes of the timetable, 3,240 predictions, typically 3.1 min late
12:00: 62.2% of final predictions within five minutes of the timetable, 3,200 predictions, typically 3.5 min late
13:00: 68.1% of final predictions within five minutes of the timetable, 3,214 predictions, typically 2.9 min late
14:00: 61.6% of final predictions within five minutes of the timetable, 3,441 predictions, typically 3.7 min late
15:00: 44.9% of final predictions within five minutes of the timetable, 4,840 predictions, typically 5.8 min late
16:00: 47% of final predictions within five minutes of the timetable, 5,348 predictions, typically 5.3 min late
17:00: 54.5% of final predictions within five minutes of the timetable, 5,367 predictions, typically 4.4 min late
18:00: 50.7% of final predictions within five minutes of the timetable, 4,458 predictions, typically 4.9 min late
19:00: 67.1% of final predictions within five minutes of the timetable, 3,171 predictions, typically 2.9 min late
20:00: 84.5% of final predictions within five minutes of the timetable, 3,262 predictions, typically 1.8 min late
21:00: 88.9% of final predictions within five minutes of the timetable, 3,209 predictions, typically 1.9 min late
22:00: 87.3% of final predictions within five minutes of the timetable, 2,212 predictions, typically 1.8 min late
23:00: 79.7% of final predictions within five minutes of the timetable, 1,515 predictions, typically 1.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	When	Measured	Scenario or next investigation
ProblemPredictions later than timetable	05:00 · 08:00 to 13:00 · 14:00 to 19:00	3.1 min late … 4.9 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	15:00	45%	Operations, not the timetable
CaveatCoverage gap	All measured hours	98%	More observation, not a service change

Measurements

Predictions later than timetable · 14:00 to 19:00: Measured arrivals 23,454; Hours affected 5; Spread 14.5 min; Median delay 4.9 min; Suggested running time change 4.9 min
Predictions later than timetable · 08:00 to 13:00: Measured arrivals 19,301; Hours affected 5; Spread 10.2 min; Median delay 3.5 min; Suggested running time change 3.5 min
Predictions later than timetable · 05:00: Measured arrivals 650; Hours affected 1; Spread 3.3 min; Median delay 3.1 min; Suggested running time change 3.1 min
One hour has a lower prediction match · 15:00: Hour 15:00; On time 44.9%; Measured arrivals 4,840; Shortfall 22.7 pts; Route median on time 67.6%
Coverage gap · All measured hours: Target 99.5%; Trips with a matching position 97.5%; Service days 7; Trips with a matching position 619; Scheduled trips 635

Open history, reliability and route analysis

Route check

How route 53 has been running

A short summary of what we know. We say so when we cannot answer a question.

Bottom line

Provider predictions often differed from the timetable; actual arrivals were not independently measured.

66 in 100 eligible predictions were within 5 minutes of the timetable · 132,043 predictions checked

Prediction sample size: Larger sample

Based on 132,043 eligible provider predictions over 27 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 4, 2026, 9:32 p.m.

Where and when did predictions differ repeatedly?

These are repeated prediction-to-timetable differences, not independently measured service failures. They use the same eligible predictions as the result above, but group by stop rather than hour, so the lists need not match line for line.

3 p.m.–4 p.m.: 55 in 100 eligible predictions differed from the timetable by more than 5 minutes (4,840 predictions over 14 days).
4 p.m.–5 p.m.: 53 in 100 eligible predictions differed from the timetable by more than 5 minutes (5,348 predictions over 14 days).
6 p.m.–7 p.m.: 49 in 100 eligible predictions differed from the timetable by more than 5 minutes (4,458 predictions over 14 days).
5 p.m.–6 p.m.: 46 in 100 eligible predictions differed from the timetable by more than 5 minutes (5,367 predictions over 14 days).

1 current notice affects this route

• Stop impacts: Baseline 1C and 1D relocated during Transitway closure

Prediction differences by stop

CLYDE / AD.1370
49 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,220 predictions over 30 days).
Open this stop
MERIVALE / VIEWMOUNT
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,219 predictions over 30 days).
Open this stop
MERIVALE / COLONNADE
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,219 predictions over 30 days).
Open this stop
MERIVALE / CLETO
46 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,220 predictions over 30 days).
Open this stop

These are route-specific provider predictions compared with the timetable. They identify repeated prediction differences at a place and time, not measured arrivals or their cause.

Check every trip and date

Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.

What riders want to know

Is any trip cancelled right now?: 0 of 4Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 16 of 635 checked trips need a closer look16 of 635 trips with enough public-feed evidence had no matching position over 7 days. 0 of 635 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
How did provider predictions differ from the timetable?: At the 95th percentile, the predicted difference was 15.9 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.
What wait did provider predictions imply?: 8.2 min average predicted wait1.2 min beyond the scheduled wait, based on 1,050 eligible predictions at 14 high-frequency stops over 15 days.

Schedule change check

Published schedule: before and after

This compares the current retained official schedule with the prior retained version. Schedule changes are facts about what was planned; they do not prove that a trip ran.

Current published schedule began October 30, 2026

Selected service day from each published schedule

We check the first Monday after the new schedule began and the Monday one week earlier. Every figure comes from the retained official GTFS versions named below.

At least one selected date uses added or removed calendar-date service. Treat this as holiday or special-service context, not ordinary weekday growth.

Before

Service date checked: October 26, 2026

Scheduled trips: 100
Distinct scheduled stops: 119
Distinct published paths: 4
Published service span: 5:30 a.m.–1:36 a.m. next day

Operator calendar-date records: 0 added · 2 removed

Feed fingerprint: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

New schedule

Service date checked: November 2, 2026

Scheduled trips: 100
Distinct scheduled stops: 119
Distinct published paths: 4
Published service span: 5:30 a.m.–1:36 a.m. next day

Operator calendar-date records: 0 added · 2 removed

Feed fingerprint: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

Did service improve after the change?

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 69,438 arrivals over 14 days; after has 24,110 arrivals over 5 days. No improvement or decline is claimed yet.

Checksums let anyone verify which retained timetable produced the counts. A changed count does not identify a cause, cancellation, operator decision, or passenger impact.

How this route is judged: Regular all-stop route

We compare the last eligible provider prediction for each scheduled arrival with the official schedule. These are not independently measured arrivals. A result needs at least 200 eligible predictions. Within 5 minutes is the rider-facing target used here.

What this data cannot prove

The public feed does not provide dependable passenger counts or passed-up-rider events. A missing position does not by itself prove a cancellation, no-show, short turn or cause.

See the definitions, thresholds and evidence order

Official current feed: explicit cancellations, skipped stops and active notices.
Matched observations: vehicle positions and settled predictions tied to the official schedule.
Official timetable: what was planned, kept separate from what was observed.
Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.

Provisional results, published evidence

How did predictions compare with the timetable?

Each hour compares the last eligible provider prediction for a scheduled arrival with the timetable. “Within 5 minutes” describes that prediction difference, not a measured arrival or proof that a bus ran.

Evidence window: October 6, 2026 to November 3, 2026

Within 5 minutes of schedule: 65.8%
Eligible predictions checked: 132,043
Weekdays with data: 19
95th-percentile predicted delay: 15.9 min late

Patterns by hour (21)

Patterns by hour (21)
Hour	On time	Median	95th percentile	Evidence
00:00	87.4%	1.8 min late	6.5 min late	1,313 · 14 days
01:00	75.5%	1.7 min late	11.2 min late	695 · 12 days
05:00	84.8%	3.1 min late	6.4 min late	650 · 12 days
06:00	90.5%	1.2 min late	6.8 min late	2,677 · 14 days
07:00	73.2%	2.6 min late	10.3 min late	4,953 · 14 days
08:00	57.6%	3.9 min late	15.8 min late	4,881 · 14 days
09:00	67.6%	3.4 min late	12 min late	4,721 · 14 days
10:00	65.5%	3.5 min late	11.5 min late	3,259 · 14 days
11:00	67.3%	3.1 min late	13.3 min late	3,240 · 14 days
12:00	62.2%	3.5 min late	18 min late	3,200 · 14 days
13:00	68.1%	2.9 min late	19.8 min late	3,214 · 14 days
14:00	61.6%	3.7 min late	14.9 min late	3,441 · 14 days
15:00	44.9%	5.8 min late	17.3 min late	4,840 · 14 days
16:00	47.0%	5.3 min late	19.8 min late	5,348 · 14 days
17:00	54.5%	4.4 min late	19.8 min late	5,367 · 14 days
18:00	50.7%	4.9 min late	22.8 min late	4,458 · 14 days
19:00	67.1%	2.9 min late	15.5 min late	3,171 · 14 days
20:00	84.5%	1.8 min late	9.9 min late	3,262 · 14 days
21:00	88.9%	1.9 min late	6.8 min late	3,209 · 14 days
22:00	87.3%	1.8 min late	7.4 min late	2,212 · 14 days
23:00	79.7%	1.1 min late	11.8 min late	1,515 · 14 days

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

Scheduled bus, but not observed in realtime

619 / 635 scheduled trips published at least one position across 7 service days (97.5%).

01:001 / 6 trips without a position83.3%
21:002 / 28 trips without a position92.9%
23:001 / 14 trips without a position92.9%
22:001 / 15 trips without a position93.3%
17:003 / 48 trips without a position93.8%
14:002 / 39 trips without a position94.9%

This is not a confirmed no-show. A missing position can mean a cancelled or missed bus, but it can also mean an unassigned trip ID or an operator-feed gap. Otranspo publishes the gap because it matters to riders while keeping the conclusion honest.

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. Sources and limitations.

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

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

05:30– 06:14
Trip 31447030Vehicle position matchedFirst / last feed position: 5:14 a.m. EST / 6:15 a.m. EST; not actual start or end times.
05:42– 05:56
Trip 20637030Vehicle position matchedFirst / last feed position: 5:41 a.m. EST / 6:00 a.m. EST; not actual start or end times.
06:00– 06:44
Trip 14007030Vehicle position matchedFirst / last feed position: 5:35 a.m. EST / 6:42 a.m. EST; not actual start or end times.
06:11– 06:25
Trip 23139030Vehicle position matchedFirst / last feed position: 6:15 a.m. EST / 6:32 a.m. EST; not actual start or end times.
06:15– 06:59
Trip 32197030Vehicle position matchedFirst / last feed position: 5:58 a.m. EST / 7:00 a.m. EST; not actual start or end times.
06:30– 07:15
Trip 26515030Vehicle position matchedFirst / last feed position: 6:08 a.m. EST / 7:15 a.m. EST; not actual start or end times.
06:38– 06:52
Trip 889030Vehicle position matchedFirst / last feed position: 6:39 a.m. EST / 6:58 a.m. EST; not actual start or end times.
06:45– 07:30
Trip 21206030Vehicle position matchedFirst / last feed position: 6:45 a.m. EST / 7:30 a.m. EST; not actual start or end times.
06:48– 07:31
Trip 8447030Vehicle position matchedFirst / last feed position: 6:43 a.m. EST / 7:47 a.m. EST; not actual start or end times.
06:59– 07:45
Trip 18454030Vehicle position matchedFirst / last feed position: 6:34 a.m. EST / 7:40 a.m. EST; not actual start or end times.
07:03– 07:48
Trip 17730030Vehicle position matchedFirst / last feed position: 7:01 a.m. EST / 7:46 a.m. EST; not actual start or end times.
07:08– 07:22
Trip 7223030Vehicle position matchedFirst / last feed position: 7:10 a.m. EST / 7:29 a.m. EST; not actual start or end times.

· Open all evidence for this day