Detour: Routes 57, 61, 62, 63, 74, 75, 87 during nightly Kichi Zībī Mīkan closures: May 07 2026 - Until further notice, routes 57, 61, 62, 63, 74, 75, and 87 will detour on weeknights and weekends between 11:30 pm and 6 am in both directions around the Kichi Zībī Mīkan parkway, between Lincoln Fields station and Churchill Avenue. Please allow extra time for your travels. Affected stops Bus Stop (560#) not in use · Routes · Alternate Stop #3013 -- Dominion 2A · · 57 Tunney's Pasture · 61 Tunney's Pasture · 62 Tunney's Pasture · 63 Tunney's Pasture · 74 Tunney's Pasture · 75 Tunney's Pasture & N Rideau · 87 Tunney's Pasture · #4941 -- Richmond (south side) / Golden #3013 -- Dominion 1A · · 57 Crystal Bay · 61 Stittsville · 62 Stittsville · 63 Innovation · 74 Nepean Woods · 75 Barrhaven · #4922 -- Richmond (north side) / Golden #3014 -- Lincoln Fields 1A · · 61 Stittsville · 62 Stittsville · 63 Innovation · 74 Nepean Woods · 75 Barrhaven · 87 Baseline · #3014 -- Lincoln Fields 3B OR #3014 -- Lincoln Fields 5A #4944 -- Woodroffe (west side) / Saunders* · · 87 Baseline · #6244 -- Woodroffe (west side) / Knightsbridge #1832 -- Woodroffe (west side) / Richmond* · · 87 Baseline · #6244 -- Woodroffe (west side) / Knightsbridge #4942 -- Woodroffe (east side) / Saunders* · · 87 Tunney's Pasture · #6472 -- Woodroffe (east side) / Knightsbridge #2783 -- Woodroffe (east side) / Richmond* · · 87 Tunney's Pasture · #6472 -- Woodroffe (east side) / Knightsbridge *These stops are already not in use due to the closure of Woodroffe Avenue (Byron/Richmond to Kichi Zībī Mīkan) Detour routing 57 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 57 Bayshore: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe, right onto Carling, left onto J-Ramp, continue regular routing. 61 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 61 Stittsville / Terry Fox: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 62 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 62 Stittsville: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 63 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 63 Innovation/ Briarbrook: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 74 Tunney's Pasture: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 74 Limebank: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 75 Tunney's Pasture & N Rideau: From Lincoln Fields local bus loop, return to Transitway, left onto Transitway, left onto J-Ramp, right onto Carling, left onto Woodroffe, right onto Richmond, left onto Churchill, right onto Scott, continue regular routing. 75 Barrhaven Centre / Cambrian: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 87 Baseline: From Scott / Churchill, left onto Churchill, right onto Richmond, left onto Woodroffe, right onto Carling, left onto J-Ramp, right onto Transitway, right onto Access road to Lincoln Fields local bus loop, stop at 3B, continue to Transitway, left onto Transitway, continue regular routing. 87 Tunney's Pasture: From Woodroffe and Byron, turn right onto Byron, continue on Richmond, left onto Churchill, right onto Scott to regular route. Detour Map

No 75 trips cancelled now · 6 did not run in NovemberCancellations →

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

STO route 75: Notre-Dame

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 29, 2026 – Nov 4, 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. Trips with any notice: 1.

Trips needing investigation

7 of 321 trips with a usable feed window (2.2%) had no matching position.

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

314 with position · 7 to investigate · 71 excluded · 392 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 5, 2026, 1:55 a.m..

Coverage, exclusions and sources

0 of 1 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

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

Published position coverage: 314 / 392 (80.1%). 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 5, 2026, 1:08 a.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

92.8%

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

Predictions in the source: 32,392
Weekdays with evidence: 17
Evidence window: Oct 6, 2026 – Nov 3, 2026

The hours we have evidence for

12 a.m.98% · 274 predictions · 10 days
5 a.m.97% · 206 predictions · 8 days
6 a.m.96% · 888 predictions · 11 days
7 a.m.89% · 948 predictions · 10 days
8 a.m.87% · 970 predictions · 11 days
9 a.m.94% · 1,060 predictions · 12 days
10 a.m.97% · 989 predictions · 12 days
11 a.m.95% · 1,194 predictions · 13 days
12 p.m.94% · 1,210 predictions · 12 days
1 p.m.95% · 1,176 predictions · 12 days
2 p.m.96% · 1,092 predictions · 13 days
3 p.m.89% · 1,238 predictions · 12 days
4 p.m.85% · 938 predictions · 13 days
5 p.m.81% · 1,194 predictions · 12 days
6 p.m.90% · 827 predictions · 11 days
7 p.m.95% · 764 predictions · 10 days
8 p.m.97% · 567 predictions · 10 days
9 p.m.95% · 548 predictions · 10 days
10 p.m.98% · 582 predictions · 10 days
11 p.m.97% · 544 predictions · 10 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

6 partial-capture days not counted.

What about time of day?

20 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 8, 2026 to November 4, 2026: 20 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 12, 2026.

Values and interpretation

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

0% of pairs (39) 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.)	2,435	0% (5)	0% (1)
Midday (9 a.m. to 3 p.m.)	6,587	0% (4)	0% (6)
Afternoon rush (3 to 6 p.m.)	2,897	0% (7)	1% (20)
Evening (6 to 10 p.m.)	561	0% (0)	2% (12)

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

Where this route is slowest

Slowest: STATION LORRAIN to SAINTE-ROSE/ROBERT-CORBETT, 7.8 km/h actual against 17.9 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
STATION LORRAIN	SAINTE-ROSE/ROBERT-CORBETT	1.1 km	17.9 km/h	7.8 km/h	404	75%
QUAI LOCAL de la CITÉ #9	NOTRE-DAME/JEAN-RENÉ-MONETTE	2.8 km	21.2 km/h	12.5 km/h	371	56%
NOTRE-DAME/de VERSAILLES	MALONEY EST/BROADWAY	1.9 km	19.2 km/h	19.6 km/h	422	0%
MALONEY EST/LORRAIN	SAINTE-ROSE/ROBERT-CORBETT	1.4 km	22 km/h	20 km/h	407	9%
SAINTE-ROSE/ROBERT-CORBETT	Stop name not found	1.3 km	20.6 km/h	21.8 km/h	252	1%
SAINTE-ROSE/ROBERT-CORBETT	STATION LORRAIN arrêt d'arrivée	1.1 km	21.5 km/h	21.9 km/h	396	2%
NOTRE-DAME/JEAN-RENÉ-MONETTE	NOTRE-DAME/de VERSAILLES	1.8 km	23.1 km/h	23.5 km/h	419	1%
SAINTE-ROSE/ROBERT-CORBETT	NOTRE-DAME/de VERSAILLES	3.5 km	23.1 km/h	23.7 km/h	172	1%

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

How this is measured →

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from Thu, Oct 8 to Wed, Nov 4.

Not counted: 1 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. (1)

Latest cancelled trips

Thu, Oct 29, scheduled 17:55

A cause is shown only when STO’s own alert for that trip gives one.

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

When this route is usually busy

From the load level STO’s buses report, over the last eight weeks. A time is marked usually busy when at least half of the trips with a reading reached standing room or fuller.

No time of day was usually busy in the last eight weeks.

When this route is usually busy	Weekdays	Saturdays	Sundays
Before 6 am	Usually seats0% of 44 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats4.2% of 429 trips	Usually seats0% of 45 trips	Usually seats0% of 41 trips
9 am to 3 pm	Usually seats0.2% of 801 trips	Usually seats2.1% of 97 trips	Usually seats0% of 93 trips
3 to 6 pm	Usually seats5.2% of 458 trips	Usually seats2% of 50 trips	Usually seats0% of 54 trips
6 to 10 pm	Usually seats0.3% of 321 trips	Usually seats0% of 66 trips	Usually seats0% of 61 trips
After 10 pm	Usually seats0% of 170 trips	Usually seats0% of 34 trips	Usually seats0% of 30 trips

Based on 55 computed days.

Source: the occupancy status in STO’s public real-time vehicle feed, which STO sets from each bus’s load sensor (seats available under 60% full, standing room under 90%, full above 90%).
Each trip counts once per time of day, at the highest load it reported.
Reports of an empty bus are left out, because older records could not tell an empty bus from one with no sensor.
A time of day needs at least 12 trips on at least 4 different days before anything is shown. Holidays are counted with their day of the week.

Open the dated prediction analysis

Verdict

What this route needs

95% of predictions are within five minutes of the timetable in a typical sampled hour; the lowest sampled hour is 81%.

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

00:00: 97.8% of final predictions within five minutes of the timetable, 274 predictions, typically 1 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 96.6% of final predictions within five minutes of the timetable, 206 predictions, typically 0.2 min early
06:00: 96.4% of final predictions within five minutes of the timetable, 888 predictions, typically 0.2 min early
07:00: 89.1% of final predictions within five minutes of the timetable, 948 predictions, typically 0.7 min late
08:00: 87.2% of final predictions within five minutes of the timetable, 970 predictions, typically 0.9 min late
09:00: 94.1% of final predictions within five minutes of the timetable, 1,060 predictions, typically 0.4 min late
10:00: 97.3% of final predictions within five minutes of the timetable, 989 predictions, typically 0.3 min late
11:00: 95.1% of final predictions within five minutes of the timetable, 1,194 predictions, typically 0.5 min late
12:00: 93.9% of final predictions within five minutes of the timetable, 1,210 predictions, typically 0.9 min late
13:00: 94.7% of final predictions within five minutes of the timetable, 1,176 predictions, typically 0.9 min late
14:00: 96.2% of final predictions within five minutes of the timetable, 1,092 predictions, typically 0.9 min late
15:00: 89.1% of final predictions within five minutes of the timetable, 1,238 predictions, typically 0.8 min late
16:00: 85.2% of final predictions within five minutes of the timetable, 938 predictions, typically 1.3 min late
17:00: 81.1% of final predictions within five minutes of the timetable, 1,194 predictions, typically 0.9 min late
18:00: 89.5% of final predictions within five minutes of the timetable, 827 predictions, typically 1.4 min late
19:00: 94.9% of final predictions within five minutes of the timetable, 764 predictions, typically 1.2 min late
20:00: 96.8% of final predictions within five minutes of the timetable, 567 predictions, typically 1.3 min late
21:00: 94.9% of final predictions within five minutes of the timetable, 548 predictions, typically 1.5 min late
22:00: 98.1% of final predictions within five minutes of the timetable, 582 predictions, typically 1.2 min late
23:00: 97.4% of final predictions within five minutes of the timetable, 544 predictions, typically 0.8 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
StrengthPredictions consistently close to timetable	00:00, 05:00, 06:00, 07:00, 08:00, 09:00, 10:00, 11:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00, 20:00, 21:00, 22:00, 23:00	95%	Keep what works

Measurements

Predictions consistently close to timetable · 00:00, 05:00, 06:00, 07:00, 08:00, 09:00, 10:00, 11:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00, 20:00, 21:00, 22:00, 23:00: Measured arrivals 17,209; Hours measured 20; Worst hour on time 81.1%; Median hour on time 94.9%

Open history, reliability and route analysis

Route check

How route 75 has been running

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

Bottom line

Provider predictions were usually close to schedule in this dated sample.

93 in 100 eligible predictions were within 5 minutes of the timetable · 32,392 predictions checked

Prediction sample size: Larger sample

Based on 32,392 eligible provider predictions over 22 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 5, 2026, 1:32 a.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.

No repeated prediction-difference period has cleared the evidence threshold yet.

No current official notice matches this route.

Prediction differences by stop

STATION LORRAIN
42 in 100 eligible predictions differed from the timetable by more than 5 minutes (530 predictions over 24 days).
Open this stop
QUAI LOCAL de la CITÉ #9
41 in 100 eligible predictions differed from the timetable by more than 5 minutes (508 predictions over 24 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 1Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 7 of 321 checked trips need a closer look7 of 321 trips with enough public-feed evidence had no matching position over 7 days. 71 of 392 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 5.5 min (positive means later; negative means earlier)93 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.

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 November 3, 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: November 2, 2026

Scheduled trips: 64
Distinct scheduled stops: 63
Distinct published paths: 2
Published service span: 5:36 a.m.–12:23 a.m. next day

Operator calendar-date records: 1 added · 0 removed

Feed fingerprint: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

New schedule

Service date checked: November 9, 2026

Scheduled trips: 64
Distinct scheduled stops: 59
Distinct published paths: 2
Published service span: 5:36 a.m.–12:23 a.m. next day

Operator calendar-date records: 1 added · 0 removed

Feed fingerprint: 64b436d79ab51a76 · 623ad8b0-ad29-4d70-b8e6-e594a396233e

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 16,862 arrivals over 13 days; after has 1,903 arrivals over 2 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: 92.8%
Eligible predictions checked: 32,392
Weekdays with data: 17
95th-percentile predicted delay: 5.5 min late

Patterns by hour (20)

Patterns by hour (20)
Hour	On time	Median	95th percentile	Evidence
00:00	97.8%	1 min late	3.6 min late	274 · 10 days
05:00	96.6%	0.2 min early	4.7 min late	206 · 8 days
06:00	96.4%	0.2 min early	2.1 min late	888 · 11 days
07:00	89.1%	0.7 min late	6.1 min late	948 · 10 days
08:00	87.2%	0.9 min late	7.7 min late	970 · 11 days
09:00	94.1%	0.4 min late	4.6 min late	1,060 · 12 days
10:00	97.3%	0.3 min late	2.8 min late	989 · 12 days
11:00	95.1%	0.5 min late	4.6 min late	1,194 · 13 days
12:00	93.9%	0.9 min late	5 min late	1,210 · 12 days
13:00	94.7%	0.9 min late	4.9 min late	1,176 · 12 days
14:00	96.2%	0.9 min late	4.4 min late	1,092 · 13 days
15:00	89.1%	0.8 min late	5.8 min late	1,238 · 12 days
16:00	85.2%	1.3 min late	9 min late	938 · 13 days
17:00	81.1%	0.9 min late	9.9 min late	1,194 · 12 days
18:00	89.5%	1.4 min late	6.8 min late	827 · 11 days
19:00	94.9%	1.2 min late	4.3 min late	764 · 10 days
20:00	96.8%	1.3 min late	4.3 min late	567 · 10 days
21:00	94.9%	1.5 min late	4.1 min late	548 · 10 days
22:00	98.1%	1.2 min late	3.8 min late	582 · 10 days
23:00	97.4%	0.8 min late	3.2 min late	544 · 10 days

No repeated pattern below 70% is yet established across at least three service days.

Scheduled bus, but not observed in realtime

314 / 392 scheduled trips published at least one position across 7 service days (80.1%).

00:003 / 7 trips without a position57.1%
23:006 / 14 trips without a position57.1%
07:009 / 24 trips without a position62.5%
06:008 / 27 trips without a position70.4%
17:007 / 24 trips without a position70.8%
19:004 / 14 trips without a position71.4%

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 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

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

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

05:36– 06:02
Trip sto:63296721Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 5:59 a.m. EST; not actual start or end times.
06:06– 06:32
Trip sto:63296672Vehicle position matchedFirst / last feed position: 5:59 a.m. EST / 6:28 a.m. EST; not actual start or end times.
06:15– 06:39
Trip sto:63296710Vehicle position matchedFirst / last feed position: 6:08 a.m. EST / 6:38 a.m. EST; not actual start or end times.
06:26– 06:52
Trip sto:63296668Vehicle position matchedFirst / last feed position: 6:20 a.m. EST / 6:52 a.m. EST; not actual start or end times.
06:39– 07:07
Trip sto:63296670Vehicle position matchedFirst / last feed position: 6:31 a.m. EST / 7:05 a.m. EST; not actual start or end times.
06:55– 07:23
Trip sto:63296715Vehicle position matchedFirst / last feed position: 6:53 a.m. EST / 7:23 a.m. EST; not actual start or end times.
07:10– 07:38
Trip sto:63296671Vehicle position matchedFirst / last feed position: 7:04 a.m. EST / 7:35 a.m. EST; not actual start or end times.
07:15– 07:39
Trip sto:63296676Vehicle position matchedFirst / last feed position: 7:12 a.m. EST / 7:44 a.m. EST; not actual start or end times.
07:26– 07:54
Trip sto:63296662Vehicle position matchedFirst / last feed position: 7:20 a.m. EST / 7:53 a.m. EST; not actual start or end times.
07:43– 08:11
Trip sto:63296706Vehicle position matchedFirst / last feed position: 7:46 a.m. EST / 8:14 a.m. EST; not actual start or end times.
08:00– 08:24
Trip sto:63296734Vehicle position matchedFirst / last feed position: 7:54 a.m. EST / 8:22 a.m. EST; not actual start or end times.
08:05– 08:33
Trip sto:63296731Vehicle position matchedFirst / last feed position: 7:54 a.m. EST / 8:29 a.m. EST; not actual start or end times.

· Open all evidence for this day