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

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

Ruta 95 ng STO: Buckingham

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Okt 29, 2026 – Nob 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. Not counted: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 3.

Trips needing investigation

1 of 76 trips with a usable feed window (1.3%) had no matching position.

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

75 with position · 1 to investigate · 14 excluded · 90 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nob 5, 2026, 11:33 AM.

Coverage, exclusions and sources

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

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

Published position coverage: 75 / 90 (83.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: Nob 5, 2026, 10:39 AM

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

73.6%

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

Predictions in the source: 13,182
Weekdays with evidence: 17
Evidence window: Okt 7, 2026 – Nob 4, 2026

The hours we have evidence for

0578% · 489 predictions · 8 days
0684% · 1,571 predictions · 8 days
0781% · 1,049 predictions · 7 days
0893% · 284 predictions · 8 days
1490% · 73 predictions · 8 days
1558% · 1,059 predictions · 9 days
1659% · 1,282 predictions · 10 days
1750% · 1,062 predictions · 9 days
1861% · 402 predictions · 8 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 5, 2026

6 partial-capture days not counted.

What about time of day?

9 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 8, 2026 to Nobyembre 4, 2026: 21 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 12, 2026.

Mga halaga at paliwanag

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

1% of pairs (71) 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
Madaling-araw (4 hanggang 6 a.m.)	199	0% (0)	0% (0)
Rush hour sa umaga (6 hanggang 9 a.m.)	4,333	1% (58)	0% (8)
Tanghali (9 a.m. hanggang 3 p.m.)	25	Kulang ang mga bus
Rush hour sa hapon (3 hanggang 6 p.m.)	4,255	1% (48)	1% (61)
Gabi (6 hanggang 10 p.m.)	543	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: BANK/QUEEN to PLACE d'ACCUEIL est, 7.8 km/h actual against 9.6 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
BANK/QUEEN	PLACE d'ACCUEIL est	1.4 km	9.6 km/h	7.8 km/h	101	25%
PLACE d'ACCUEIL est	Station MONTCALM bretelle dir nord #2	1.3 km	10.9 km/h	10.2 km/h	109	3%
PLACE d'ACCUEIL ouest	STATION LYON	1.6 km	16.6 km/h	13.5 km/h	77	30%
Station CASINO #2	Station LAC LEAMY #2	800 m	17.7 km/h	18.2 km/h	117	5%
Station MONTCALM bretelle dir sud #1	PLACE d'ACCUEIL ouest	2 km	16.8 km/h	18.9 km/h	79	0%
ENCAN de MASSON	Av. de BUCKINGHAM/JOSEPH	5.6 km	19.5 km/h	19.1 km/h	98	1%
LÉPINE/FINDLAY	Av. de BUCKINGHAM/MACLAREN	5.2 km	23.9 km/h	19.4 km/h	53	26%
Station LAC LEAMY #1	Station CASINO #1	550 m	22 km/h	20.4 km/h	83	19%

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

Paano ito sinusukat →

Mga pagkansela sa rutang ito

Ano ang ibig sabihin ng mga salitang ito →

6 partial-capture days not counted.

2 scheduled trips with counted cancellation notices from Huw, Okt 8 to Miy, Nob 4.

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

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

Mga pinakabagong kinanselang biyahe

Mar, Nob 3, scheduled 16:18
Biy, Okt 30, scheduled 15:30

May ipinapakitang dahilan lamang kapag may binanggit ito sa sariling alerto ng STO para sa biyaheng iyon.

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

Kailan karaniwang siksikan ang rutang ito

Mula sa antas ng karga na iniuulat ng mga bus ng STO sa nakalipas na walong linggo. Minarkahang karaniwang matao ang isang oras kapag kalahati o higit pa sa mga biyahe na may datos ay umabot sa standing room o mas puno.

Walang oras ng araw na karaniwang matao sa nakaraang walong linggo.

Kailan karaniwang siksikan ang rutang ito	Mga araw ng trabaho	Tuwing Sabado	Tuwing Linggo
Bago mag-6 am	Karaniwang may upuan0% of 92 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 9 ng umaga	Karaniwang may upuan46.8% of 205 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
9 am hanggang 3 pm	Karaniwang may upuan37.8% of 74 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
3 hanggang 6 ng hapon	Karaniwang may upuan37.7% of 257 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 10 pm	Karaniwang may upuan0% of 43 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
Pagkatapos ng 10 pm	Kulang ang mga pagbasa	Kulang ang mga pagbasa	Kulang ang mga pagbasa

Based on 56 computed days.

Pinagmulan: ang katayuan ng occupancy sa pampublikong real-time na vehicle feed ng STO, na itinatakda ng STO mula sa load sensor ng bawat bus (may bakanteng upuan kung wala pang 60% ang puno, may espasyo para tumayo kung wala pang 90%, puno kung higit sa 90%).
Isang beses lang binibilang ang bawat biyahe sa bawat bahagi ng araw, sa pinakamataas na dami ng sakay na iniulat nito.
Hindi isinama ang mga ulat ng walang laman na bus. Hindi kasi matukoy ng mga lumang talaan ang bus na walang laman mula sa bus na walang sensor.
Kailangan ng isang oras ng araw ng hindi bababa sa 12 biyahe sa hindi bababa sa 4 na magkakaibang araw bago may maipakita. Ang mga holiday ay binibilang ayon sa araw ng linggo nila.

Buksan ang may petsang pagsusuri ng hula

Hatol

What this route needs

Median provider predictions are 4.1 min later than the timetable in 4 hours of the day.

Predictions near the start are about 2.1 min later than the timetable; the difference grows by another 2.7 min along the route.

17:00 has 50% of predictions within five minutes of the timetable, against 78% the rest of the day.

Scenario: 4 min more running time on 29 trips. The schedule-block model adds no buses; fleet and workforce feasibility are unverified.

Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 9 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: 78.1% of final predictions within five minutes of the timetable, 489 predictions, typically 2.1 min late
06:00: 84% of final predictions within five minutes of the timetable, 1,571 predictions, typically 1 min late
07:00: 81.1% of final predictions within five minutes of the timetable, 1,049 predictions, typically 2.7 min late
08:00: 93% of final predictions within five minutes of the timetable, 284 predictions, typically 2 min late
09:00: not enough data
10:00: not enough data
11:00: not enough data
12:00: not enough data
13:00: not enough data
14:00: 90.4% of final predictions within five minutes of the timetable, 73 predictions, typically 1.3 min late
15:00: 57.8% of final predictions within five minutes of the timetable, 1,059 predictions, typically 4.3 min late
16:00: 59.3% of final predictions within five minutes of the timetable, 1,282 predictions, typically 3.7 min late
17:00: 49.6% of final predictions within five minutes of the timetable, 1,062 predictions, typically 4.4 min late
18:00: 61.2% of final predictions within five minutes of the timetable, 402 predictions, typically 3.9 min late
19:00: not enough data
20:00: not enough data
21:00: not enough data
22:00: not enough data
23:00: not enough data

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	15:00 to 19:00	4.1 min late	More running time
ProblemOne hour has a lower prediction match	17:00	50%	Operations, not the timetable

Measurements

Predictions later than timetable · 15:00 to 19:00: Measured arrivals 3,805; Hours affected 4; Spread 8 min; Median delay 4.1 min; Suggested running time change 4.1 min
One hour has a lower prediction match · 17:00: Oras 17:00; Nasa oras 49.6%; Measured arrivals 1,062; Shortfall 28.5 pts; Route median on time 78.1%

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 95 has been running

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

Pangunahing punto

Madalas na iba ang mga hula ng provider sa iskedyul; hindi nasukat nang hiwalay ang aktwal na pagdating.

74 in 100 eligible predictions were within 5 minutes of the timetable · 13,182 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 13,182 eligible provider predictions over 17 measured days, from Okt 7, 2026 to Nob 4, 2026.

Updated Nob 5, 2026, 10:32 AM

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.

17–18: 50 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,062 predictions over 9 days).
15–16: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,059 predictions over 9 days).
16–17: 41 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,282 predictions over 10 days).
18–19: 39 in 100 eligible predictions differed from the timetable by more than 5 minutes (402 predictions over 8 days).

Walang kasalukuyang opisyal na abiso na tumutugma sa rutang ito.

Pagkakaiba ng hula ayon sa hintuan

STATION LYON
49 in 100 eligible predictions differed from the timetable by more than 5 minutes (104 predictions over 16 days).
Buksan ang hintuang ito
BÉLANGER/ROSS
48 in 100 eligible predictions differed from the timetable by more than 5 minutes (149 predictions over 18 days).
Buksan ang hintuang ito
BANK/QUEEN
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (106 predictions over 16 days).
Buksan ang hintuang ito
MACLAREN EST/JAMES
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (149 predictions over 18 days).
Buksan ang hintuang ito

Ito ay mga hula ng provider para sa partikular na ruta, na inihambing sa iskedyul. Ipinapakita nito ang paulit-ulit na pagkakaiba ng hula sa isang lugar at oras. Hindi ito nasukat na pagdating at hindi nito sinasabi ang dahilan.

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 5Sinusuri 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?: 1 of 76 checked trips need a closer look1 of 76 trips with enough public-feed evidence had no matching position over 7 days. 14 of 90 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 11.1 min (positive means later; negative means earlier)74 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?: Wala pang resulta sa antas ng ruta na umaabot sa pamantayan ng evidence. Hindi po ibig sabihin nito na walang nangyaring puwang sa serbisyo.

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

Mga biyaheng nakatakda sa iskedyul: 18
Mga natatanging hintuan na nasa iskedyul: 126
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 05:30–18:30

Operator calendar-date records: 1 added · 0 removed

Fingerprint ng feed: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

Bagong iskedyul

Petsa ng serbisyo na sinuri: Nobyembre 9, 2026

Mga biyaheng nakatakda sa iskedyul: 18
Mga natatanging hintuan na nasa iskedyul: 126
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 05:30–18:30

Operator calendar-date records: 1 added · 0 removed

Fingerprint ng feed: 64b436d79ab51a76 · 623ad8b0-ad29-4d70-b8e6-e594a396233e

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 7,065 arrivals over 10 days; after has 1,047 arrivals over 2 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 7, 2026 to Nobyembre 4, 2026

Sa loob ng 5 minuto mula sa iskedyul: 73.6%
Mga karapat-dapat na hula na nasuri: 13,182
Mga araw ng linggo na may datos: 17
Tinatayang pagkaantala sa ika-95 na percentile: 11.1 min late

Patterns by hour (9)

Patterns by hour (9)
Oras	Nasa oras	Median	95th percentile	Ebidensya
05:00	78.1%	2.1 min late	11.6 min late	489 · 8 days
06:00	84.0%	1 min late	7.4 min late	1,571 · 8 days
07:00	81.1%	2.7 min late	10.8 min late	1,049 · 7 days
08:00	93.0%	2 min late	5.2 min late	284 · 8 days
14:00	90.4%	1.3 min late	6.1 min late	73 · 8 days
15:00	57.8%	4.3 min late	10.6 min late	1,059 · 9 days
16:00	59.3%	3.7 min late	10.9 min late	1,282 · 10 days
17:00	49.6%	4.4 min late	13.2 min late	1,062 · 9 days
18:00	61.2%	3.9 min late	13.8 min late	402 · 8 days

4 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

75 / 90 scheduled trips published at least one position across 5 service days (83.3%).

07:002 / 5 trips without a position60.0%
06:007 / 20 trips without a position65.0%
05:003 / 15 trips without a position80.0%
16:002 / 15 trips without a position86.7%
15:001 / 20 trips without a position95.0%
14:000 / 10 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 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

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

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

05:30– 06:47
Trip sto:63295158Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 7:00 a.m. EST; not actual start or end times.
05:45– 07:02
Trip sto:63290294Vehicle position matchedFirst / last feed position: 5:48 a.m. EST / 7:09 a.m. EST; not actual start or end times.
05:58– 07:15
Trip sto:63294835Vehicle position matchedFirst / last feed position: 5:57 a.m. EST / 7:25 a.m. EST; not actual start or end times.
06:15– 07:37
Trip sto:63295909Vehicle position matchedFirst / last feed position: 6:17 a.m. EST / 7:52 a.m. EST; not actual start or end times.
06:30– 07:57
Trip sto:63295120Vehicle position matchedFirst / last feed position: 6:31 a.m. EST / 8:08 a.m. EST; not actual start or end times.
06:45– 08:12
Trip sto:63295267Vehicle position matchedFirst / last feed position: 6:46 a.m. EST / 8:17 a.m. EST; not actual start or end times.
06:59– 08:26
Trip sto:63295866Vehicle position matchedFirst / last feed position: 7:01 a.m. EST / 8:24 a.m. EST; not actual start or end times.
07:15– 08:42
Trip sto:63294750Vehicle position matchedFirst / last feed position: 7:12 a.m. EST / 8:46 a.m. EST; not actual start or end times.
14:30– 15:49
Trip sto:63295773Vehicle position matchedFirst / last feed position: 2:37 p.m. EST / 2:46 p.m. EST; not actual start or end times.
14:45– 16:06
Trip sto:63295875Vehicle position matchedFirst / last feed position: 2:46 p.m. EST / 2:46 p.m. EST; not actual start or end times.
15:00– 16:22
Trip sto:63295767Vehicle position matchedFirst / last feed position: 4:17 p.m. EST / 4:17 p.m. EST; not actual start or end times.
15:15– 16:40
Trip sto:63294655Vehicle position matchedFirst / last feed position: 4:17 p.m. EST / 4:41 p.m. EST; not actual start or end times.

· Open all evidence for this day