No 69 trips cancelled now · 1 did not run in NobyembreCancellations →

Previous measure: 91.6% of arrivals were within five minutes of the timetable (18,013 arrivals over 22 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 69 ng STO: St-Louis

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

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

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

222 with position · 1 to investigate · 47 excluded · 270 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 222 / 270 (82.2%). 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, 12:49 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

91.6%

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

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

The hours we have evidence for

0596% · 124 predictions · 6 days
0689% · 278 predictions · 7 days
0771% · 178 predictions · 6 days
0878% · 631 predictions · 10 days
0992% · 477 predictions · 11 days
1092% · 518 predictions · 11 days
1198% · 502 predictions · 11 days
1298% · 543 predictions · 12 days
1395% · 469 predictions · 11 days
1495% · 467 predictions · 13 days
1596% · 728 predictions · 12 days
1679% · 615 predictions · 12 days
1790% · 803 predictions · 12 days
1891% · 873 predictions · 11 days
1973% · 457 predictions · 10 days
2098% · 491 predictions · 10 days
2194% · 464 predictions · 10 days
2299% · 513 predictions · 10 days
2398% · 219 predictions · 9 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 4, 2026

6 partial-capture days not counted.

What about time of day?

19 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

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

0% of pairs (1) 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,180	0% (1)	0% (1)
Tanghali (9 a.m. hanggang 3 p.m.)	119	0% (0)	0% (0)
Rush hour sa hapon (3 hanggang 6 p.m.)	1,112	0% (0)	0% (0)
Gabi (6 hanggang 10 p.m.)	604	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: des GRANDS-JARDINS/de la POINTE-TAILLON to des ÉRABLES/SAINT-ALEXANDRE, 16.3 km/h actual against 22.4 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
des GRANDS-JARDINS/de la POINTE-TAILLON	des ÉRABLES/SAINT-ALEXANDRE	1.9 km	22.4 km/h	16.3 km/h	291	24%
Av. GATINEAU/SAINT-LOUIS	de PROVENCE/d'AUVERGNE	610 m	18.2 km/h	19.5 km/h	310	4%
des FLANDRES/de PIEDMONT	de PROVENCE/d'AUVERGNE	830 m	16.6 km/h	20.2 km/h	309	2%
de PROVENCE/d'AUVERGNE	des FLANDRES/de PIEDMONT	780 m	21.5 km/h	20.7 km/h	296	6%
de PROVENCE/d'AUVERGNE	SAINT-LOUIS/Av. GATINEAU	970 m	19.4 km/h	21.4 km/h	311	0%
des ÉRABLES/SAINT-ALEXANDRE	des GRANDS-JARDINS/de la POINTE-TAILLON (fin)	2.1 km	25.9 km/h	24.4 km/h	281	9%
des ÉRABLES/SAINT-ALEXANDRE	Av. GATINEAU/SAINT-LOUIS	3.8 km	25.9 km/h	25.1 km/h	296	1%
SAINT-LOUIS/Av. GATINEAU	des ÉRABLES/SAINT-ALEXANDRE	3.5 km	26.3 km/h	25.6 km/h	312	1%

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.

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

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

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 31 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 9 ng umaga	Karaniwang may upuan0% of 228 trips	Karaniwang may upuan0% of 14 trips	Karaniwang may upuan0% of 14 trips
9 am hanggang 3 pm	Karaniwang may upuan0% of 398 trips	Karaniwang may upuan0% of 87 trips	Karaniwang may upuan0% of 91 trips
3 hanggang 6 ng hapon	Karaniwang may upuan0.3% of 304 trips	Karaniwang may upuan0% of 47 trips	Karaniwang may upuan0% of 48 trips
6 hanggang 10 pm	Karaniwang may upuan0% of 276 trips	Karaniwang may upuan0% of 63 trips	Karaniwang may upuan0% of 56 trips
Pagkatapos ng 10 pm	Karaniwang may upuan0% of 45 trips	Karaniwang may upuan0% of 15 trips	Karaniwang may upuan0% of 17 trips

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.6 min later than the timetable in 1 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.

07:00 has 71% of predictions within five minutes of the timetable, against 94% the rest of the day.

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, 19 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: 96% of final predictions within five minutes of the timetable, 124 predictions, typically 2.1 min late
06:00: 88.5% of final predictions within five minutes of the timetable, 278 predictions, typically 2.1 min late
07:00: 71.3% of final predictions within five minutes of the timetable, 178 predictions, typically 1.8 min late
08:00: 78.1% of final predictions within five minutes of the timetable, 631 predictions, typically 1.4 min late
09:00: 91.8% of final predictions within five minutes of the timetable, 477 predictions, typically 0.5 min late
10:00: 92.1% of final predictions within five minutes of the timetable, 518 predictions, typically 1.2 min late
11:00: 98% of final predictions within five minutes of the timetable, 502 predictions, typically 0.7 min late
12:00: 98.3% of final predictions within five minutes of the timetable, 543 predictions, typically 0.5 min late
13:00: 94.9% of final predictions within five minutes of the timetable, 469 predictions, typically 1.1 min late
14:00: 94.6% of final predictions within five minutes of the timetable, 467 predictions, typically 1.1 min late
15:00: 95.7% of final predictions within five minutes of the timetable, 728 predictions, typically 1.6 min late
16:00: 79.3% of final predictions within five minutes of the timetable, 615 predictions, typically 2.5 min late
17:00: 89.5% of final predictions within five minutes of the timetable, 803 predictions, typically 1.5 min late
18:00: 91.1% of final predictions within five minutes of the timetable, 873 predictions, typically 1.8 min late
19:00: 73.1% of final predictions within five minutes of the timetable, 457 predictions, typically 3.6 min late
20:00: 97.6% of final predictions within five minutes of the timetable, 491 predictions, typically 0.6 min late
21:00: 93.8% of final predictions within five minutes of the timetable, 464 predictions, typically 0.2 min late
22:00: 98.8% of final predictions within five minutes of the timetable, 513 predictions, typically 0.1 min early
23:00: 97.7% of final predictions within five minutes of the timetable, 219 predictions, typically 0.2 min early

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	19:00	3.6 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	07:00	71%	Operations, not the timetable

Measurements

Predictions later than timetable · 19:00: Measured arrivals 457; Hours affected 1; Spread 4.1 min; Median delay 3.6 min; Suggested running time change 3.6 min
One hour has a lower prediction match · 07:00: Oras 07:00; Nasa oras 71.3%; Measured arrivals 178; Shortfall 22.5 pts; Route median on time 93.8%

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 69 has been running

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

Pangunahing punto

Karaniwang malapit sa iskedyul ang mga hula ng provider sa sample na may petsang ito.

92 in 100 eligible predictions were within 5 minutes of the timetable · 18,013 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 18,013 eligible provider predictions over 22 measured days, from Okt 6, 2026 to Nob 3, 2026.

Updated Nob 4, 2026, 1: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.

Wala pang paulit-ulit na panahon ng pagkakaiba ng prediksyon na umabot sa threshold ng ebidensya.

Walang kasalukuyang opisyal na abiso na tumutugma sa rutang ito.

Pagkakaiba ng hula ayon sa hintuan

Quai local de la GAPPE #5
61 in 100 eligible predictions differed from the timetable by more than 5 minutes (357 predictions over 24 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 12Sinusuri 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 223 checked trips need a closer look1 of 223 trips with enough public-feed evidence had no matching position over 7 days. 47 of 270 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 6.0 min (positive means later; negative means earlier)92 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: 42
Mga natatanging hintuan na nasa iskedyul: 54
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 05:37–23:31

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 9,899 arrivals over 13 days; after has 1,416 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: 91.6%
Mga karapat-dapat na hula na nasuri: 18,013
Mga araw ng linggo na may datos: 17
Tinatayang pagkaantala sa ika-95 na percentile: 6 min late

Patterns by hour (19)

Patterns by hour (19)
Oras	Nasa oras	Median	95th percentile	Ebidensya
05:00	96.0%	2.1 min late	4.8 min late	124 · 6 days
06:00	88.5%	2.1 min late	8.7 min late	278 · 7 days
07:00	71.3%	1.8 min late	9.4 min late	178 · 6 days
08:00	78.1%	1.4 min late	9.8 min late	631 · 10 days
09:00	91.8%	0.5 min late	6.5 min late	477 · 11 days
10:00	92.1%	1.2 min late	8.3 min late	518 · 11 days
11:00	98.0%	0.7 min late	3.8 min late	502 · 11 days
12:00	98.3%	0.5 min late	2.7 min late	543 · 12 days
13:00	94.9%	1.1 min late	4.7 min late	469 · 11 days
14:00	94.6%	1.1 min late	4.2 min late	467 · 13 days
15:00	95.7%	1.6 min late	4.7 min late	728 · 12 days
16:00	79.3%	2.5 min late	12.4 min late	615 · 12 days
17:00	89.5%	1.5 min late	6.3 min late	803 · 12 days
18:00	91.1%	1.8 min late	5.5 min late	873 · 11 days
19:00	73.1%	3.6 min late	7.7 min late	457 · 10 days
20:00	97.6%	0.6 min late	3.9 min late	491 · 10 days
21:00	93.8%	0.2 min late	2.9 min late	464 · 10 days
22:00	98.8%	0.1 min early	2.1 min late	513 · 10 days
23:00	97.7%	0.2 min early	2.5 min late	219 · 9 days

Wala pang natatag na paulit-ulit na pattern na mas mababa sa 70% sa hindi bababa sa tatlong araw ng serbisyo.

Nakaiskedyul na bus, ngunit hindi naobserbahan sa real-time

222 / 270 scheduled trips published at least one position across 5 service days (82.2%).

19:006 / 14 trips without a position57.1%
07:004 / 10 trips without a position60.0%
06:003 / 10 trips without a position70.0%
20:004 / 14 trips without a position71.4%
21:004 / 14 trips without a position71.4%
22:004 / 14 trips without a position71.4%

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

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

05:37– 05:56
Trip sto:63296900Insufficient coverage or identity; outcome unknown
06:07– 06:26
Trip sto:63296901Insufficient coverage or identity; outcome unknown
06:37– 06:56
Trip sto:63296902Insufficient coverage or identity; outcome unknown
07:05– 07:27
Trip sto:63296903Insufficient coverage or identity; outcome unknown
07:41– 08:03
Trip sto:63296904Insufficient coverage or identity; outcome unknown
08:03– 08:22
Trip sto:63296905Insufficient coverage or identity; outcome unknown
08:27– 08:48
Trip sto:63296922Insufficient coverage or identity; outcome unknown
08:31– 08:50
Trip sto:63296906Insufficient coverage or identity; outcome unknown
08:49– 09:08
Trip sto:63296907Insufficient coverage or identity; outcome unknown
09:30– 09:51
Trip sto:63296923Vehicle position matchedFirst / last feed position: 9:20 a.m. EST / 9:47 a.m. EST; not actual start or end times.
09:52– 10:11
Trip sto:63296908Vehicle position matchedFirst / last feed position: 9:50 a.m. EST / 10:10 a.m. EST; not actual start or end times.
10:29– 10:50
Trip sto:63296924Vehicle position matchedFirst / last feed position: 10:29 a.m. EST / 10:48 a.m. EST; not actual start or end times.

· Open all evidence for this day