Detour Route 26 South: Route 26 diverted from Laval to Station Lyon.+1 more notice

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

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

Live times did not load

Showing the timetable. Buses may run early or late.

Last live: Hindi pa nasusukat
Last live: Hindi pa nasusukat
Then: Hindi pa nasusukat

Katayuan ng sistema

Ruta 26 ng STO: Le Plateau

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Okt 28, 2026 – Nob 3, 2026

Scheduled trips with cancellation notices

—

No retained notice returned; this does not prove zero cancellations.

Trips needing investigation

0 of 41 trips with a usable feed window (0%) had no matching position.

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

41 with position · 0 to investigate · 9 excluded · 50 scheduled trips

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

Coverage, exclusions and sources

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

Published position coverage: 41 / 50 (82%). 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 4, 2026, 9:56 PM

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

What does the evidence show?

Predictions against the timetable

69.9%

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

Predictions in the source: 5,084
Weekdays with evidence: 17
Evidence window: Okt 6, 2026 – Nob 3, 2026

The hours we have evidence for

0599% · 122 predictions · 7 days
0697% · 433 predictions · 7 days
0799% · 365 predictions · 6 days
0896% · 134 predictions · 6 days
1565% · 159 predictions · 9 days
1669% · 499 predictions · 10 days
1752% · 609 predictions · 9 days
1858% · 152 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?

8 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 7, 2026 to Nobyembre 3, 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

No bunched buses were measured on this route in the last 28 days (2,451 pairs checked at stops).

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

Mga bus na dumarating nang magkakasabay
Oras ng araw	Mga pares na sinuri	Nagkumpol	Mahabang pagitan
Rush hour sa umaga (6 hanggang 9 a.m.)	1,068	0% (0)	0% (0)
Rush hour sa hapon (3 hanggang 6 p.m.)	1,124	0% (0)	0% (0)
Gabi (6 hanggang 10 p.m.)	259	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: STATION LYON to du PORTAGE/AUBRY, 7 km/h actual against 8.7 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
STATION LYON	du PORTAGE/AUBRY	1.9 km	8.7 km/h	7 km/h	54	17%
PINK/de la SAPINIÈRE	des GRIVES/PINK	930 m	19.6 km/h	9.1 km/h	44	45%
du PORTAGE/AUBRY	LAURIER/EDDY	470 m	8.4 km/h	9.3 km/h	65	3%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	9.4 km/h	9.7 km/h	51	4%
de l'HÔTEL-de-VILLE/LAURIER	BANK/WELLINGTON	1.7 km	8.7 km/h	10.6 km/h	26	0%
LAURIER/EDDY	ALEXANDRE-TACHÉ/SAINT-JOSEPH	1 km	13.9 km/h	14.6 km/h	64	8%
ALEXANDRE-TACHÉ/SAINT-JOSEPH	ALEXANDRE-TACHÉ/CHÂTEAUBRIAND	530 m	17.5 km/h	15 km/h	63	22%
des GRIVES/PINK	ARRÊT DE COURTOISIE MONTAGNE/des GRIVES	780 m	15.6 km/h	16.4 km/h	51	0%

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

Paano ito sinusukat →

Gawaing-kalsada ng lungsod malapit sa rutang ito

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

Gawaing kalsada
Slater between Bay and Lyon
Okt 30, 2026, 12:00 AM to Nob 6, 2026, 5:00 PM
Slater lane reduction between Bay and Lyon due to construction, from November 2nd to 6th.
about 0 m from the route
City record updated Okt 30, 2026, 1:28 PM.
Gawaing kalsada
ALBERT at LYON
Hindi inilathala ang mga petsa
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 2 m from the route
City record updated Set 9, 2026, 6:32 PM.

A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.

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

Mga pagkansela sa rutang ito

Ano ang ibig sabihin ng mga salitang ito →

6 partial-capture days not counted.

Walang nabilang na kanselasyon sa rutang ito sa nakaraang apat na linggo. Ililista sa ibaba ang mga abisong hindi namin nasuri.

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 33 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 9 ng umaga	Karaniwang may upuan11.8% of 119 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
9 am hanggang 3 pm	Kulang ang mga pagbasa	Kulang ang mga pagbasa	Kulang ang mga pagbasa
3 hanggang 6 ng hapon	Karaniwang may upuan3.8% of 132 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 10 pm	Karaniwang may upuan0% of 24 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 3.5 to 4.3 min later than the timetable in 3 hours of the day.

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

Scenario: 4 min more running time on 12 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, 8 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: 99.2% of final predictions within five minutes of the timetable, 122 predictions, typically 1 min late
06:00: 96.5% of final predictions within five minutes of the timetable, 433 predictions, typically 0.3 min early
07:00: 99.2% of final predictions within five minutes of the timetable, 365 predictions, typically 0.7 min late
08:00: 95.5% of final predictions within five minutes of the timetable, 134 predictions, typically 1 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: not enough data
15:00: 64.8% of final predictions within five minutes of the timetable, 159 predictions, typically 3.5 min late
16:00: 69.1% of final predictions within five minutes of the timetable, 499 predictions, typically 2.9 min late
17:00: 52.4% of final predictions within five minutes of the timetable, 609 predictions, typically 4.8 min late
18:00: 57.9% of final predictions within five minutes of the timetable, 152 predictions, typically 3.7 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 · 17:00 to 19:00	3.5 min late · 4.3 min late	More running time
ProblemOne hour has a lower prediction match	17:00	52%	Operations, not the timetable

Measurements

Predictions later than timetable · 17:00 to 19:00: Measured arrivals 761; Hours affected 2; Spread 9.9 min; Median delay 4.3 min; Suggested running time change 4.3 min
Predictions later than timetable · 15:00: Measured arrivals 159; Hours affected 1; Spread 4.1 min; Median delay 3.5 min; Suggested running time change 3.5 min
One hour has a lower prediction match · 17:00: Oras 17:00; Nasa oras 52.4%; Measured arrivals 609; Shortfall 29.9 pts; Route median on time 82.3%

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 26 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.

70 in 100 eligible predictions were within 5 minutes of the timetable · 5,084 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 5,084 eligible provider predictions over 17 measured days, from Okt 6, 2026 to Nob 3, 2026.

Updated Nob 4, 2026, 10:32 PM

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

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

17–18: 48 in 100 eligible predictions differed from the timetable by more than 5 minutes (609 predictions over 9 days).
18–19: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (152 predictions over 8 days).
15–16: 35 in 100 eligible predictions differed from the timetable by more than 5 minutes (159 predictions over 9 days).
16–17: 31 in 100 eligible predictions differed from the timetable by more than 5 minutes (499 predictions over 10 days).

1 current notice affects this route

• Detour Route 26 South

Pagkakaiba ng hula ayon sa hintuan

du PORTAGE/LAVAL
63 in 100 eligible predictions differed from the timetable by more than 5 minutes (78 predictions over 18 days).
Buksan ang hintuang ito
du PORTAGE/AUBRY
63 in 100 eligible predictions differed from the timetable by more than 5 minutes (78 predictions over 18 days).
Buksan ang hintuang ito
ALEXANDRE-TACHÉ/SAINTE-THÉRÈSE
62 in 100 eligible predictions differed from the timetable by more than 5 minutes (77 predictions over 18 days).
Buksan ang hintuang ito
ALEXANDRE-TACHÉ/SAINT-DOMINIQUE
62 in 100 eligible predictions differed from the timetable by more than 5 minutes (76 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?: Walang live na sagot sa kanselasyonSTO’s live trip-update feed did not answer this check. That is a feed gap. It does not mean zero cancellations, and it is not proof of a cancellation. Open the evidence to see the schedule, retained explicit cancellation notices, and every labelled data gap.
Posibleng hindi sumipot matapos suriin ang mga puwang sa feed?: 0 of 41 checked trips need a closer look0 of 41 trips with enough public-feed evidence had no matching position over 7 days. 9 of 50 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 13.4 min (positive means later; negative means earlier)70 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 2, 2026

Piniling araw ng serbisyo mula sa bawat inilathalang iskedyul

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

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

Bago

Petsa ng serbisyo na sinuri: Oktubre 26, 2026

Mga biyaheng nakatakda sa iskedyul: 0
Mga natatanging hintuan na nasa iskedyul: 0
Iba't ibang inilathalang daanan: 0
Inilathalang oras ng serbisyo: —–—

Fingerprint ng feed: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

Bagong iskedyul

Petsa ng serbisyo na sinuri: Nobyembre 2, 2026

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

Operator calendar-date records: 1 added · 0 removed

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

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 2,778 arrivals over 10 days; after has 324 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 6, 2026 to Nobyembre 3, 2026

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

Patterns by hour (8)

Patterns by hour (8)
Oras	Nasa oras	Median	95th percentile	Ebidensya
05:00	99.2%	1 min late	2.1 min late	122 · 7 days
06:00	96.5%	0.3 min early	1.5 min late	433 · 7 days
07:00	99.2%	0.7 min late	2.8 min late	365 · 6 days
08:00	95.5%	1 min late	3.8 min late	134 · 6 days
15:00	64.8%	3.5 min late	7.5 min late	159 · 9 days
16:00	69.1%	2.9 min late	16.8 min late	499 · 10 days
17:00	52.4%	4.8 min late	14.6 min late	609 · 9 days
18:00	57.9%	3.7 min late	13.8 min late	152 · 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

41 / 50 scheduled trips published at least one position across 5 service days (82.0%).

07:004 / 10 trips without a position60.0%
06:003 / 10 trips without a position70.0%
05:001 / 5 trips without a position80.0%
17:001 / 5 trips without a position80.0%
15:000 / 10 trips without a position100.0%
16: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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 10 trips in the retained timetable · retained notices; capture coverage unverified

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

05:45– 06:33
Trip sto:63294892Insufficient coverage or identity; outcome unknown
06:15– 07:05
Trip sto:63295691Insufficient coverage or identity; outcome unknown
06:45– 07:37
Trip sto:63295923Insufficient coverage or identity; outcome unknown
07:15– 08:07
Trip sto:63295193Insufficient coverage or identity; outcome unknown
07:45– 08:37
Trip sto:63294601Insufficient coverage or identity; outcome unknown
15:28– 16:18
Trip sto:63294674Vehicle position matchedFirst / last feed position: 3:33 p.m. EST / 4:16 p.m. EST; not actual start or end times.
15:58– 16:50
Trip sto:63294600Vehicle position matchedFirst / last feed position: 3:59 p.m. EST / 5:05 p.m. EST; not actual start or end times.
16:28– 17:18
Trip sto:63290305Vehicle position matchedFirst / last feed position: 4:31 p.m. EST / 5:25 p.m. EST; not actual start or end times.
16:58– 17:48
Trip sto:63294873Vehicle position matchedFirst / last feed position: 5:04 p.m. EST / 5:51 p.m. EST; not actual start or end times.
17:28– 18:15
Trip sto:63295783Vehicle position matchedFirst / last feed position: 5:28 p.m. EST / 6:17 p.m. EST; not actual start or end times.