No 71 trips cancelled now · 4 did not run in NobyembreCancellations →

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

Ruta 71 ng STO: Davidson

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

QUAI LOCAL de la CITÉ #76 min sched.
de la GAPPE/de ROUVILLE8 min sched.
de la GAPPE/de la CITÉ9 min sched.
de la CITÉ/de la GAPPE10 min sched.
du CARREFOUR/MONTÉE PAIEMENT11 min sched.
MONTÉE PAIEMENT/GRAVELINE12 min sched.
MONTÉE PAIEMENT/JEAN-GARDY-BIENVENU12 min sched.
MONTÉE PAIEMENT/SAINT-RENÉ OUEST12 min sched.
MONTÉE PAIEMENT/FILIATREAULT13 min sched.
MONTÉE PAIEMENT/la VÉRENDRYE OUEST13 min sched.
MONTÉE PAIEMENT/LAHAIE14 min sched.
NOBERT/MONTÉE PAIEMENT15 min sched.
NOBERT/de SAUTERNES16 min sched.
NOBERT/du PINOT16 min sched.
NOBERT/RADMORE17 min sched.
NOBERT/DAVIDSON17 min sched.
DAVIDSON/d'AOUST18 min sched.
DAVIDSON/de LANGELIER19 min sched.
DAVIDSON/MAIN19 min sched.
DAVIDSON/P.-LABINE19 min sched.
DAVIDSON/LARCHER20 min sched.
DAVIDSON/LABROSSE21 min sched.
DAVIDSON/de CASTAGNIER21 min sched.
DAVIDSON/de DUPARQUET22 min sched.
DAVIDSON/A.-GIBEAULT23 min sched.
DAVIDSON/de CHARNY24 min sched.
la VÉRENDRYE EST/de CANDIAC25 min sched.
LABROSSE/de CANDIAC26 min sched.
LABROSSE/MARQUETTE28 min sched.
LABROSSE/SAINT-RENÉ EST28 min sched.
Terminus Labrosse29 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: 2.

Trips needing investigation

5 of 404 trips with a usable feed window (1.2%) had no matching position.

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

399 with position · 5 to investigate · 75 excluded · 479 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 399 / 479 (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 4, 2026, 12:09 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%

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

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

The hours we have evidence for

00100% · 246 predictions · 8 days
0596% · 411 predictions · 7 days
0695% · 1,051 predictions · 7 days
0795% · 990 predictions · 9 days
0893% · 1,131 predictions · 10 days
0992% · 1,065 predictions · 11 days
1094% · 1,027 predictions · 11 days
1196% · 941 predictions · 12 days
1296% · 985 predictions · 12 days
1395% · 1,081 predictions · 12 days
1492% · 927 predictions · 12 days
1589% · 1,561 predictions · 12 days
1673% · 1,593 predictions · 13 days
1783% · 1,566 predictions · 12 days
1878% · 1,118 predictions · 11 days
1991% · 825 predictions · 10 days
2085% · 617 predictions · 10 days
2197% · 563 predictions · 10 days
2288% · 606 predictions · 10 days
2398% · 518 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: Nob 4, 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

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

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

0% of pairs (25) 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.)	45	13% (6)	0% (0)
Rush hour sa umaga (6 hanggang 9 a.m.)	5,048	1% (40)	0% (9)
Tanghali (9 a.m. hanggang 3 p.m.)	6,994	0% (3)	0% (5)
Rush hour sa hapon (3 hanggang 6 p.m.)	6,686	1% (90)	0% (3)
Gabi (6 hanggang 10 p.m.)	2,186	0% (0)	0% (8)

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É #7 to du CARREFOUR/MONTÉE PAIEMENT, 5.3 km/h actual against 13.5 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É #7	du CARREFOUR/MONTÉE PAIEMENT	990 m	13.5 km/h	5.3 km/h	543	84%
Quai local LABROSSE #5	DAVIDSON/MAIN	3.5 km	21.8 km/h	11.9 km/h	498	64%
DAVIDSON/MAIN	Terminus Labrosse	3.4 km	21.5 km/h	20.7 km/h	531	2%
NOBERT/MONTÉE PAIEMENT	du CARREFOUR/ MONTÉE PAIEMENT	1.8 km	23.4 km/h	21.1 km/h	531	10%
du CARREFOUR/ MONTÉE PAIEMENT	QUAI LOCAL de la CITÉ arrivée	1.1 km	21.3 km/h	21.3 km/h	507	2%
DAVIDSON/NOBERT	NOBERT/MONTÉE PAIEMENT	890 m	25 km/h	22.2 km/h	550	6%
du CARREFOUR/MONTÉE PAIEMENT	NOBERT/MONTÉE PAIEMENT	1.9 km	24.2 km/h	23.1 km/h	557	5%
NOBERT/MONTÉE PAIEMENT	NOBERT/DAVIDSON	890 m	24.5 km/h	23.4 km/h	575	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.

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

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: 8 AM (1), 12 PM (1), 4 PM (1)

Mga pinakabagong kinanselang biyahe

Mar, Nob 3, scheduled 17:01
Biy, Okt 30, scheduled 16:46
Mar, Okt 27, scheduled 08:18
Huw, Okt 22, scheduled 12:30

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: 4 of 404 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 121 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 9 ng umaga	Karaniwang may upuan3.5% of 626 trips	Karaniwang may upuan0% of 24 trips	Karaniwang may upuan0% of 27 trips
9 am hanggang 3 pm	Karaniwang may upuan0.6% of 800 trips	Karaniwang may upuan0% of 97 trips	Karaniwang may upuan0% of 92 trips
3 hanggang 6 ng hapon	Karaniwang may upuan2.9% of 716 trips	Karaniwang may upuan0% of 51 trips	Karaniwang may upuan0% of 49 trips
6 hanggang 10 pm	Karaniwang may upuan0.7% of 402 trips	Karaniwang may upuan1.6% of 61 trips	Karaniwang may upuan0% of 61 trips
Pagkatapos ng 10 pm	Karaniwang may upuan0% of 133 trips	Karaniwang may upuan0% of 22 trips	Karaniwang may upuan0% of 18 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

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

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

00:00: 100% of final predictions within five minutes of the timetable, 246 predictions, typically 1.6 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 95.6% of final predictions within five minutes of the timetable, 411 predictions, typically 0.3 min late
06:00: 95.1% of final predictions within five minutes of the timetable, 1,051 predictions, typically 0.4 min late
07:00: 94.8% of final predictions within five minutes of the timetable, 990 predictions, typically 1.1 min late
08:00: 92.6% of final predictions within five minutes of the timetable, 1,131 predictions, typically 1.7 min late
09:00: 91.6% of final predictions within five minutes of the timetable, 1,065 predictions, typically 0.7 min late
10:00: 94.2% of final predictions within five minutes of the timetable, 1,027 predictions, typically 0.7 min late
11:00: 95.5% of final predictions within five minutes of the timetable, 941 predictions, typically 1 min late
12:00: 96.4% of final predictions within five minutes of the timetable, 985 predictions, typically 1 min late
13:00: 94.7% of final predictions within five minutes of the timetable, 1,081 predictions, typically 0.4 min late
14:00: 92.1% of final predictions within five minutes of the timetable, 927 predictions, typically 0.5 min late
15:00: 88.7% of final predictions within five minutes of the timetable, 1,561 predictions, typically 1.8 min late
16:00: 73% of final predictions within five minutes of the timetable, 1,593 predictions, typically 2.9 min late
17:00: 83.3% of final predictions within five minutes of the timetable, 1,566 predictions, typically 1.8 min late
18:00: 78.4% of final predictions within five minutes of the timetable, 1,118 predictions, typically 2.2 min late
19:00: 91.4% of final predictions within five minutes of the timetable, 825 predictions, typically 1.6 min late
20:00: 84.6% of final predictions within five minutes of the timetable, 617 predictions, typically 0.9 min late
21:00: 97% of final predictions within five minutes of the timetable, 563 predictions, typically 1.4 min late
22:00: 88% of final predictions within five minutes of the timetable, 606 predictions, typically 1 min late
23:00: 97.5% of final predictions within five minutes of the timetable, 518 predictions, typically 0.5 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	73%	Operations, not the timetable

Measurements

One hour has a lower prediction match · 16:00: Oras 16:00; Nasa oras 73%; Measured arrivals 1,593; Shortfall 20.4 pts; Route median on time 93.4%

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

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

91 in 100 eligible predictions were within 5 minutes of the timetable · 36,606 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

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

Updated Nob 4, 2026, 12: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 CITÉ #7
54 in 100 eligible predictions differed from the timetable by more than 5 minutes (656 predictions over 24 days).
Buksan ang hintuang ito
Quai local LABROSSE #5
49 in 100 eligible predictions differed from the timetable by more than 5 minutes (626 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?: 5 of 404 checked trips need a closer look5 of 404 trips with enough public-feed evidence had no matching position over 7 days. 75 of 479 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)91 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: 83
Mga natatanging hintuan na nasa iskedyul: 61
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 05:28–00:31 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 20,217 arrivals over 13 days; after has 2,855 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.0%
Mga karapat-dapat na hula na nasuri: 36,606
Mga araw ng linggo na may datos: 17
Tinatayang pagkaantala sa ika-95 na percentile: 5.9 min late

Patterns by hour (20)

Patterns by hour (20)
Oras	Nasa oras	Median	95th percentile	Ebidensya
00:00	100.0%	1.6 min late	3.8 min late	246 · 8 days
05:00	95.6%	0.3 min late	2.3 min late	411 · 7 days
06:00	95.1%	0.4 min late	3.1 min late	1,051 · 7 days
07:00	94.8%	1.1 min late	4.8 min late	990 · 9 days
08:00	92.6%	1.7 min late	5.3 min late	1,131 · 10 days
09:00	91.6%	0.7 min late	5.4 min late	1,065 · 11 days
10:00	94.2%	0.7 min late	4.8 min late	1,027 · 11 days
11:00	95.5%	1 min late	3.7 min late	941 · 12 days
12:00	96.4%	1 min late	4.4 min late	985 · 12 days
13:00	94.7%	0.4 min late	4.4 min late	1,081 · 12 days
14:00	92.1%	0.5 min late	5.2 min late	927 · 12 days
15:00	88.7%	1.8 min late	7.3 min late	1,561 · 12 days
16:00	73.0%	2.9 min late	10.7 min late	1,593 · 13 days
17:00	83.3%	1.8 min late	11.7 min late	1,566 · 12 days
18:00	78.4%	2.2 min late	10.4 min late	1,118 · 11 days
19:00	91.4%	1.6 min late	5.2 min late	825 · 10 days
20:00	84.6%	0.9 min late	6 min late	617 · 10 days
21:00	97.0%	1.4 min late	3.8 min late	563 · 10 days
22:00	88.0%	1 min late	7.8 min late	606 · 10 days
23:00	97.5%	0.5 min late	3.5 min late	518 · 10 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

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

07:0014 / 32 trips without a position56.3%
21:005 / 14 trips without a position64.3%
06:0010 / 30 trips without a position66.7%
20:004 / 14 trips without a position71.4%
22:004 / 14 trips without a position71.4%
08:009 / 34 trips without a position73.5%

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

In short: 56 with a matched position · 4 with no matching position (to investigate) · 23 with an unknown outcome.

05:28– 05:51
Trip sto:63296636Insufficient coverage or identity; outcome unknown
05:35– 05:57
Trip sto:63296610Insufficient coverage or identity; outcome unknown
05:57– 06:19
Trip sto:63296605Insufficient coverage or identity; outcome unknown
05:58– 06:21
Trip sto:63296644Insufficient coverage or identity; outcome unknown
06:12– 06:37
Trip sto:63296601Insufficient coverage or identity; outcome unknown
06:25– 06:48
Trip sto:63296635Insufficient coverage or identity; outcome unknown
06:32– 06:57
Trip sto:63296602Insufficient coverage or identity; outcome unknown
06:43– 07:06
Trip sto:63296645Insufficient coverage or identity; outcome unknown
06:52– 07:17
Trip sto:63296603Insufficient coverage or identity; outcome unknown
06:58– 07:23
Trip sto:63296640Insufficient coverage or identity; outcome unknown
07:06– 07:31
Trip sto:63296604Insufficient coverage or identity; outcome unknown
07:12– 07:37
Trip sto:63296646Insufficient coverage or identity; outcome unknown

· Open all evidence for this day