No 76 trips cancelled now · 5 did not run in NobyembreCancellations →

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

Ruta 76 ng STO: La Vérendrye

Papuntang Labrosse0 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

QUAI LOCAL de la CITÉ #829 min sched.
de la GAPPE/de ROUVILLE31 min sched.
de l'HÔPITAL/de ROUVILLE32 min sched.
de l'HÔPITAL/de la CITÉ-JARDIN33 min sched.
de la FUTAIE33 min sched.
de l'HÔPITAL/SAINT-RENÉ OUEST0 min sched.
HÔPITAL DE GATINEAU1 min sched.
de l'OASIS/du DÉSERT2 min sched.
de la CITÉ/la VÉRENDRYE OUEST4 min sched.
la VÉRENDRYE OUEST/de la CITÉ4 min sched.
la VÉRENDRYE OUEST/MONTÉE PAIEMENT5 min sched.
la VÉRENDRYE OUEST/GÉNÉREUX6 min sched.
la VÉRENDRYE OUEST/LAFRANCE7 min sched.
la VÉRENDRYE OUEST/GUINDON7 min sched.
la VÉRENDRYE OUEST/PAQUETTE9 min sched.
la VÉRENDRYE EST/MAIN10 min sched.
la VÉRENDRYE EST/R.H-LALONDE10 min sched.
la VÉRENDRYE EST/MAIN11 min sched.
la VÉRENDRYE EST/LABROSSE11 min sched.
LABROSSE/de CANDIAC12 min sched.
LABROSSE/MARQUETTE13 min sched.
LABROSSE/SAINT-RENÉ EST13 min sched.
Terminus Labrosse14 min sched.

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

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

6 of 341 trips with a usable feed window (1.8%) had no matching position.

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

335 with position · 6 to investigate · 73 excluded · 414 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 335 / 414 (80.9%). 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, 1:38 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

89.2%

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

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

The hours we have evidence for

0599% · 130 predictions · 7 days
0695% · 567 predictions · 7 days
0792% · 643 predictions · 9 days
0892% · 696 predictions · 10 days
0990% · 855 predictions · 11 days
1092% · 704 predictions · 11 days
1191% · 736 predictions · 12 days
1294% · 801 predictions · 12 days
1388% · 849 predictions · 12 days
1489% · 773 predictions · 13 days
1577% · 814 predictions · 12 days
1667% · 845 predictions · 13 days
1787% · 864 predictions · 12 days
1889% · 673 predictions · 11 days
1996% · 511 predictions · 10 days
2096% · 445 predictions · 10 days
2194% · 403 predictions · 10 days
2296% · 443 predictions · 10 days
2399% · 161 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 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: 38 of 12,244 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.

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.)	2,955	0% (4)	0% (3)
Tanghali (9 a.m. hanggang 3 p.m.)	5,553	0% (17)	0% (11)
Rush hour sa hapon (3 hanggang 6 p.m.)	2,678	1% (17)	1% (25)
Gabi (6 hanggang 10 p.m.)	1,058	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: QUAI LOCAL de la CITÉ #8 to HÔPITAL DE GATINEAU, 6.7 km/h actual against 17.2 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
QUAI LOCAL de la CITÉ #8	HÔPITAL DE GATINEAU	1.4 km	17.2 km/h	6.7 km/h	466	80%
Quai local LABROSSE #5	la VÉRENDRYE EST/MAIN	1.7 km	19.2 km/h	7.5 km/h	388	76%
HÔPITAL DE GATINEAU	la VÉRENDRYE OUEST/de la CITÉ	690 m	15.1 km/h	15.9 km/h	528	5%
HÔPITAL DE GATINEAU	QUAI LOCAL de la CITÉ arrivée	1.5 km	18.9 km/h	18.1 km/h	415	3%
de l'OASIS/de la CITÉ	HÔPITAL DE GATINEAU	590 m	17 km/h	20.2 km/h	443	3%
la VÉRENDRYE EST/MAIN	Terminus Labrosse	1.3 km	21.6 km/h	22.3 km/h	490	2%
la VÉRENDRYE EST/MAIN	de l'OASIS/de la CITÉ	2.8 km	28.7 km/h	28.6 km/h	439	3%
la VÉRENDRYE OUEST/de la CITÉ	la VÉRENDRYE EST/MAIN	3 km	32.7 km/h	31.1 km/h	518	3%

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.

1 scheduled trips with counted cancellation notices from Miy, Okt 7 to Mar, Nob 3.

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

Mga oras na may pinakamaraming kanseladong biyahe: 10 AM (1)

Mga pinakabagong kinanselang biyahe

Mar, Nob 3, scheduled 10:18

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

Did not come (no bus seen, no notice), last 7 days: 5 of 341 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 36 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 9 ng umaga	Karaniwang may upuan1.1% of 464 trips	Karaniwang may upuan0% of 37 trips	Karaniwang may upuan0% of 31 trips
9 am hanggang 3 pm	Karaniwang may upuan1.8% of 795 trips	Karaniwang may upuan0% of 96 trips	Karaniwang may upuan0% of 88 trips
3 hanggang 6 ng hapon	Karaniwang may upuan4.7% of 553 trips	Karaniwang may upuan0% of 46 trips	Karaniwang may upuan0% of 49 trips
6 hanggang 10 pm	Karaniwang may upuan0% of 342 trips	Karaniwang may upuan0% of 62 trips	Karaniwang may upuan0% of 54 trips
Pagkatapos ng 10 pm	Karaniwang may upuan0% of 112 trips	Karaniwang may upuan0% of 15 trips	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

16:00 has 67% of predictions within five minutes of the timetable, against 92% the rest of the day.

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: 99.2% of final predictions within five minutes of the timetable, 130 predictions, typically 0.3 min late
06:00: 94.7% of final predictions within five minutes of the timetable, 567 predictions, typically 1 min late
07:00: 91.9% of final predictions within five minutes of the timetable, 643 predictions, typically 1.6 min late
08:00: 91.5% of final predictions within five minutes of the timetable, 696 predictions, typically 1.2 min late
09:00: 89.8% of final predictions within five minutes of the timetable, 855 predictions, typically 1.4 min late
10:00: 92.3% of final predictions within five minutes of the timetable, 704 predictions, typically 1.8 min late
11:00: 91.3% of final predictions within five minutes of the timetable, 736 predictions, typically 1.4 min late
12:00: 93.8% of final predictions within five minutes of the timetable, 801 predictions, typically 0.9 min late
13:00: 88.2% of final predictions within five minutes of the timetable, 849 predictions, typically 1.9 min late
14:00: 89.3% of final predictions within five minutes of the timetable, 773 predictions, typically 1.8 min late
15:00: 76.5% of final predictions within five minutes of the timetable, 814 predictions, typically 2.2 min late
16:00: 66.9% of final predictions within five minutes of the timetable, 845 predictions, typically 2.9 min late
17:00: 86.7% of final predictions within five minutes of the timetable, 864 predictions, typically 2.3 min late
18:00: 88.9% of final predictions within five minutes of the timetable, 673 predictions, typically 1.3 min late
19:00: 95.7% of final predictions within five minutes of the timetable, 511 predictions, typically 1 min late
20:00: 96.4% of final predictions within five minutes of the timetable, 445 predictions, typically 0.9 min late
21:00: 94.3% of final predictions within five minutes of the timetable, 403 predictions, typically 0.7 min late
22:00: 96.4% of final predictions within five minutes of the timetable, 443 predictions, typically 0.5 min late
23:00: 99.4% of final predictions within five minutes of the timetable, 161 predictions, typically 0.6 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	Kailan	Nasukat	Scenario or next investigation
ProblemOne hour has a lower prediction match	16:00	67%	Operations, not the timetable

Measurements

One hour has a lower prediction match · 16:00: Oras 16:00; Nasa oras 66.9%; Measured arrivals 845; Shortfall 25 pts; Route median on time 91.9%

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 76 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 tagapagbigay ng serbisyo, pero tingnan po ang mga oras na may problema sa ibaba.

89 in 100 eligible predictions were within 5 minutes of the timetable · 23,476 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

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

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

16–17: 33 in 100 eligible predictions differed from the timetable by more than 5 minutes (845 predictions over 13 days).

Walang kasalukuyang opisyal na abiso na tumutugma sa rutang ito.

Pagkakaiba ng hula ayon sa hintuan

Quai local LABROSSE #5
59 in 100 eligible predictions differed from the timetable by more than 5 minutes (505 predictions over 24 days).
Buksan ang hintuang ito
QUAI LOCAL de la CITÉ #8
54 in 100 eligible predictions differed from the timetable by more than 5 minutes (602 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?: 6 of 341 checked trips need a closer look6 of 341 trips with enough public-feed evidence had no matching position over 7 days. 73 of 414 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 5.9 min (positive means later; negative means earlier)89 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: 70
Mga natatanging hintuan na nasa iskedyul: 45
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 05:38–00:02 next day

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 12,777 arrivals over 13 days; after has 1,726 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: 89.2%
Mga karapat-dapat na hula na nasuri: 23,476
Mga araw ng linggo na may datos: 17
Tinatayang pagkaantala sa ika-95 na percentile: 5.9 min late

Patterns by hour (19)

Patterns by hour (19)
Oras	Nasa oras	Median	95th percentile	Ebidensya
05:00	99.2%	0.3 min late	2.4 min late	130 · 7 days
06:00	94.7%	1 min late	3.2 min late	567 · 7 days
07:00	91.9%	1.6 min late	5.5 min late	643 · 9 days
08:00	91.5%	1.2 min late	5.7 min late	696 · 10 days
09:00	89.8%	1.4 min late	5.4 min late	855 · 11 days
10:00	92.3%	1.8 min late	5.4 min late	704 · 11 days
11:00	91.3%	1.4 min late	5.2 min late	736 · 12 days
12:00	93.8%	0.9 min late	4.7 min late	801 · 12 days
13:00	88.2%	1.9 min late	5.5 min late	849 · 12 days
14:00	89.3%	1.8 min late	5.7 min late	773 · 13 days
15:00	76.5%	2.2 min late	7.7 min late	814 · 12 days
16:00	66.9%	2.9 min late	12.3 min late	845 · 13 days
17:00	86.7%	2.3 min late	6 min late	864 · 12 days
18:00	88.9%	1.3 min late	6 min late	673 · 11 days
19:00	95.7%	1 min late	4.3 min late	511 · 10 days
20:00	96.4%	0.9 min late	3.3 min late	445 · 10 days
21:00	94.3%	0.7 min late	3.1 min late	403 · 10 days
22:00	96.4%	0.5 min late	2.4 min late	443 · 10 days
23:00	99.4%	0.6 min late	2.5 min late	161 · 8 days

1 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

335 / 414 scheduled trips published at least one position across 5 service days (80.9%).

06:0012 / 30 trips without a position60.0%
07:0013 / 34 trips without a position61.8%
21:005 / 14 trips without a position64.3%
08:0010 / 29 trips without a position65.5%
19:006 / 19 trips without a position68.4%
20: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 · 70 trips in the retained timetable · retained notices; capture coverage unverified

In short: 47 with a matched position · 3 with no matching position (to investigate) · 20 with an unknown outcome.

05:38– 05:56
Trip sto:63296800Insufficient coverage or identity; outcome unknown
06:08– 06:26
Trip sto:63296793Insufficient coverage or identity; outcome unknown
06:20– 06:37
Trip sto:63296765Insufficient coverage or identity; outcome unknown
06:30– 06:48
Trip sto:63296801Insufficient coverage or identity; outcome unknown
06:38– 06:55
Trip sto:63296769Insufficient coverage or identity; outcome unknown
06:48– 07:06
Trip sto:63296794Insufficient coverage or identity; outcome unknown
06:57– 07:14
Trip sto:63296766Insufficient coverage or identity; outcome unknown
07:07– 07:25
Trip sto:63296796Insufficient coverage or identity; outcome unknown
07:16– 07:37
Trip sto:63296767Insufficient coverage or identity; outcome unknown
07:31– 07:49
Trip sto:63296802Insufficient coverage or identity; outcome unknown
07:32– 07:53
Trip sto:63296768Insufficient coverage or identity; outcome unknown
07:53– 08:14
Trip sto:63296770Insufficient coverage or identity; outcome unknown

· Open all evidence for this day