No 97 trips cancelled now · 2 did not run in NobyembreCancellations →

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

Ruta 97 ng STO: Masson-Angers/Buckingham

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

STATION LORRAIN0 min sched.
LORRAIN/SAINT-RENÉ EST1 min sched.
LORRAIN/VINCENT-LEGRIS EST1 min sched.
LORRAIN/MARLENE-GOYET2 min sched.
LORRAIN/AUGUSTE-RENOIR3 min sched.
LORRAIN/des FLEURS3 min sched.
des LAURENTIDES/de NEUVILLE12 min sched.
des LAURENTIDES/de GRANDPRÉ13 min sched.
des LAURENTIDES/de CHERISY13 min sched.
ROUTE 148/des LAURENTIDES14 min sched.
ROUTE 148/du RUISSEAU14 min sched.
ROUTE 148/ de SAINT-MARIN14 min sched.
ROUTE 148/ des BALBUZARDS15 min sched.
ROUTE 148/de la PAPETIÈRE15 min sched.
ROUTE 148/de la FORTERESSE15 min sched.
ROUTE 148/des HAUTS-BOIS16 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant16 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant17 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant18 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant19 min sched.
ARRÊT DE COURTOISIE Montréal/Brabant20 min sched.
ARRÊT DE COURTOISIE Montréal/Kendall21 min sched.
PARC-O-BUS GEORGES/ROUTE 14822 min sched.
GEORGES/JEAN-BAPTISTE-ROUTHIER23 min sched.
ENCAN de MASSON24 min sched.
GEORGES/des LIARDS25 min sched.
GEORGES/de l'ÉCORCE25 min sched.
GEORGES/de l'ÉCORCE26 min sched.
GEORGES/FOUCAULT26 min sched.
PARC-O-BUS GEORGES/FOUCAULT27 min sched.
GEORGES/DAMIEN-CHARRON27 min sched.
GEORGES/CARDINAL28 min sched.
BERTRAND/ARTHUR-GRATTON28 min sched.
BERTRAND/CHARETTE29 min sched.
CHARETTE/RACAN29 min sched.
CHARETTE/BOULADIER30 min sched.
PIERRE-LAPORTE/ALBERT-FILLION30 min sched.
PIERRE-LAPORTE/ARTHUR-GRATTON31 min sched.
CURÉ-ROY/ELZÉAR-LAFLEUR31 min sched.
CURÉ-ROY/L'ABBÉ32 min sched.
l'ABBÉ/BERGERON32 min sched.
BERGERON/GÉRARD-GAUTHIER33 min sched.
BERGERON/BRIDGE33 min sched.
KENNY/BRIDGE34 min sched.
KENNY/SPENCER35 min sched.
KENNY/MACLAREN35 min sched.
MACLAREN OUEST/GEORGES36 min sched.
Av. de BUCKINGHAM/JOSEPH37 min sched.
Av. de BUCKINGHAM/JEAN-XXIII38 min sched.
JEAN-XXIII/des PINS39 min sched.
BÉLANGER/ROSS39 min sched.
BÉLANGER/JOSEPH40 min sched.
BÉLANGER/MACLAREN EST40 min sched.
MACLAREN EST/JAMES41 min sched.
MACLAREN EST/PAUL42 min sched.
MACLAREN EST/LAFRAMBOISE43 min sched.
ÉCOLE HORMISDAS-GAMELIN43 min sched.
MACLAREN/SAUVÉ44 min sched.
MACLAREN/MOISE-GAUTHIER45 min sched.
MACLAREN/ELISABETH-CHAUVIN45 min sched.
MACLAREN/ALPHONSE-LABELLE46 min sched.
LÉPINE/MACLAREN EST47 min sched.
LÉPINE47 min sched.
LÉPINE/DOLLARD48 min sched.
121, AVENUE LÉPINE48 min sched.
LÉPINE/Av. de BUCKINGHAM49 min sched.
AV. DE BUCKINGHAM/ODILE-DAOUST52 min sched.
de MASSON/des CHUTES-RHÉAUME54 min sched.
de MASSON/SAINT-CHARLES54 min sched.
ROUTE 148/NAPOLÉON55 min sched.
ROUTE 148/GUY-DUBUC56 min sched.
ROUTE 148/DANIEL-KELLY56 min sched.
ROUTE 148/LOMBARD56 min sched.
de l'ARÉNA/LOMBARD arrivée57 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. Not counted: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 1.

Trips needing investigation

2 of 218 trips with a usable feed window (0.9%) had no matching position.

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

216 with position · 2 to investigate · 33 excluded · 251 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 216 / 251 (86.1%). 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

87.3%

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

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

The hours we have evidence for

0098% · 687 predictions · 10 days
01100% · 60 predictions · 9 days
0694% · 565 predictions · 7 days
0791% · 1,067 predictions · 9 days
0894% · 1,149 predictions · 10 days
0997% · 1,404 predictions · 11 days
1090% · 1,463 predictions · 11 days
1191% · 1,544 predictions · 12 days
1287% · 1,559 predictions · 12 days
1388% · 1,642 predictions · 12 days
1489% · 1,471 predictions · 13 days
1575% · 1,533 predictions · 12 days
1661% · 1,435 predictions · 13 days
1775% · 1,480 predictions · 12 days
1878% · 1,834 predictions · 11 days
1987% · 1,826 predictions · 11 days
2088% · 1,419 predictions · 10 days
2187% · 1,332 predictions · 10 days
2294% · 1,379 predictions · 10 days
2393% · 756 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

No bunched buses were measured on this route in the last 28 days (1,535 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.)	166	0% (0)	0% (0)
Gabi (6 hanggang 10 p.m.)	1,369	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 LORRAIN to LORRAIN/des FLEURS, 7.9 km/h actual against 22.8 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 LORRAIN	LORRAIN/des FLEURS	1.2 km	22.8 km/h	7.9 km/h	300	79%
KENNY/MACLAREN	Av. de BUCKINGHAM/JOSEPH	640 m	14.7 km/h	14.4 km/h	324	7%
Av. de BUCKINGHAM/MACLAREN	KENNY/MACLAREN	580 m	13.6 km/h	15 km/h	278	8%
de l'ARÉNA/LOMBARD	130, AVENUE LÉPINE	4.8 km	33.7 km/h	18.6 km/h	266	67%
QUAI LOCAL de la CITÉ #6	Station LABROSSE #04	3.2 km	32.1 km/h	19.1 km/h	36	56%
130, AVENUE LÉPINE	Av. de BUCKINGHAM/MACLAREN	4.1 km	22.3 km/h	21.7 km/h	271	0%
KENNY/MACLAREN	CURÉ-ROY/PIERRE-LAPORTE	1.6 km	23 km/h	22 km/h	275	2%
CURÉ-ROY/ELZÉAR-LAFLEUR	KENNY/MACLAREN	1.5 km	22.1 km/h	22 km/h	319	2%

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: 2 of 218 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 15 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 9 ng umaga	Karaniwang may upuan27.4% of 164 trips	Karaniwang may upuan0% of 28 trips	Karaniwang may upuan0% of 21 trips
9 am hanggang 3 pm	Karaniwang may upuan7.8% of 477 trips	Karaniwang may upuan6.6% of 106 trips	Karaniwang may upuan1% of 98 trips
3 hanggang 6 ng hapon	Karaniwang may upuan14% of 322 trips	Karaniwang may upuan8.1% of 62 trips	Karaniwang may upuan1.5% of 65 trips
6 hanggang 10 pm	Karaniwang may upuan3% of 401 trips	Karaniwang may upuan0% of 74 trips	Karaniwang may upuan0% of 71 trips
Pagkatapos ng 10 pm	Karaniwang may upuan1.4% of 207 trips	Karaniwang may upuan0% of 43 trips	Karaniwang may upuan0% of 37 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.4 min later than the timetable in 1 hours of the day.

Predictions near the start are about 2.9 min later than the timetable, with a similar difference near the end. This does not establish the cause.

16:00 has 61% of predictions within five minutes of the timetable, against 89% 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, 20 hours with samples

00:00: 98.4% of final predictions within five minutes of the timetable, 687 predictions, typically 0.2 min late
01:00: 100% of final predictions within five minutes of the timetable, 60 predictions, typically 0.4 min early
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: not enough data
06:00: 94.2% of final predictions within five minutes of the timetable, 565 predictions, typically 0.2 min late
07:00: 90.6% of final predictions within five minutes of the timetable, 1,067 predictions, typically 0.9 min late
08:00: 94.4% of final predictions within five minutes of the timetable, 1,149 predictions, typically 1.1 min late
09:00: 97.4% of final predictions within five minutes of the timetable, 1,404 predictions, typically 1.5 min late
10:00: 90% of final predictions within five minutes of the timetable, 1,463 predictions, typically 1.3 min late
11:00: 91.2% of final predictions within five minutes of the timetable, 1,544 predictions, typically 1 min late
12:00: 86.8% of final predictions within five minutes of the timetable, 1,559 predictions, typically 1.4 min late
13:00: 88.2% of final predictions within five minutes of the timetable, 1,642 predictions, typically 1.4 min late
14:00: 88.8% of final predictions within five minutes of the timetable, 1,471 predictions, typically 1.4 min late
15:00: 74.9% of final predictions within five minutes of the timetable, 1,533 predictions, typically 2.6 min late
16:00: 60.8% of final predictions within five minutes of the timetable, 1,435 predictions, typically 3.4 min late
17:00: 75.3% of final predictions within five minutes of the timetable, 1,480 predictions, typically 2.8 min late
18:00: 77.7% of final predictions within five minutes of the timetable, 1,834 predictions, typically 1.5 min late
19:00: 86.9% of final predictions within five minutes of the timetable, 1,826 predictions, typically 1.1 min late
20:00: 87.5% of final predictions within five minutes of the timetable, 1,419 predictions, typically 2.1 min late
21:00: 86.7% of final predictions within five minutes of the timetable, 1,332 predictions, typically 1.9 min late
22:00: 93.5% of final predictions within five minutes of the timetable, 1,379 predictions, typically 1.3 min late
23:00: 92.6% of final predictions within five minutes of the timetable, 756 predictions, typically 0.9 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
ProblemPredictions later than timetable	16:00	3.4 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	16:00	61%	Operations, not the timetable

Measurements

Predictions later than timetable · 16:00: Measured arrivals 1,435; Hours affected 1; Spread 8.9 min; Median delay 3.4 min; Suggested running time change 3.4 min
One hour has a lower prediction match · 16:00: Oras 16:00; Nasa oras 60.8%; Measured arrivals 1,435; Shortfall 28.6 pts; Route median on time 89.4%

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

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

87 in 100 eligible predictions were within 5 minutes of the timetable · 47,925 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 47,925 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: 39 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,435 predictions over 13 days).

Walang kasalukuyang opisyal na abiso na tumutugma sa rutang ito.

Pagkakaiba ng hula ayon sa hintuan

de l'ARÉNA/LOMBARD
59 in 100 eligible predictions differed from the timetable by more than 5 minutes (320 predictions over 24 days).
Buksan ang hintuang ito
STATION LORRAIN
44 in 100 eligible predictions differed from the timetable by more than 5 minutes (366 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 9Sinusuri 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?: 2 of 218 checked trips need a closer look2 of 218 trips with enough public-feed evidence had no matching position over 7 days. 33 of 251 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 7.7 min (positive means later; negative means earlier)87 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: 37
Mga natatanging hintuan na nasa iskedyul: 152
Iba't ibang inilathalang daanan: 3
Inilathalang oras ng serbisyo: 05:59–01:03 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 27,203 arrivals over 13 days; after has 3,168 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: 87.3%
Mga karapat-dapat na hula na nasuri: 47,925
Mga araw ng linggo na may datos: 17
Tinatayang pagkaantala sa ika-95 na percentile: 7.7 min late

Patterns by hour (20)

Patterns by hour (20)
Oras	Nasa oras	Median	95th percentile	Ebidensya
00:00	98.4%	0.2 min late	2.8 min late	687 · 10 days
01:00	100.0%	0.4 min early	3.5 min late	60 · 9 days
06:00	94.2%	0.2 min late	5 min late	565 · 7 days
07:00	90.6%	0.9 min late	6.5 min late	1,067 · 9 days
08:00	94.4%	1.1 min late	4.8 min late	1,149 · 10 days
09:00	97.4%	1.5 min late	4.3 min late	1,404 · 11 days
10:00	90.0%	1.3 min late	6.7 min late	1,463 · 11 days
11:00	91.2%	1 min late	6 min late	1,544 · 12 days
12:00	86.8%	1.4 min late	6.7 min late	1,559 · 12 days
13:00	88.2%	1.4 min late	6.8 min late	1,642 · 12 days
14:00	88.8%	1.4 min late	6.7 min late	1,471 · 13 days
15:00	74.9%	2.6 min late	9.7 min late	1,533 · 12 days
16:00	60.8%	3.4 min late	12.3 min late	1,435 · 13 days
17:00	75.3%	2.8 min late	12.7 min late	1,480 · 12 days
18:00	77.7%	1.5 min late	12.7 min late	1,834 · 11 days
19:00	86.9%	1.1 min late	6.7 min late	1,826 · 11 days
20:00	87.5%	2.1 min late	6.5 min late	1,419 · 10 days
21:00	86.7%	1.9 min late	6.3 min late	1,332 · 10 days
22:00	93.5%	1.3 min late	4.9 min late	1,379 · 10 days
23:00	92.6%	0.9 min late	6.6 min late	756 · 10 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

216 / 251 scheduled trips published at least one position across 7 service days (86.1%).

06:004 / 10 trips without a position60.0%
21:005 / 14 trips without a position64.3%
22:005 / 14 trips without a position64.3%
00:002 / 7 trips without a position71.4%
07:002 / 7 trips without a position71.4%
19: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 · 37 trips in the retained timetable · retained notices; capture coverage unverified

In short: 29 with a matched position · 2 with no matching position (to investigate) · 6 with an unknown outcome.

05:59– 07:00
Trip sto:63296984Insufficient coverage or identity; outcome unknown
06:40– 07:39
Trip sto:63297001Insufficient coverage or identity; outcome unknown
06:57– 07:58
Trip sto:63296985Insufficient coverage or identity; outcome unknown
07:10– 08:13
Trip sto:63297002Insufficient coverage or identity; outcome unknown
08:08– 09:09
Trip sto:63296986Insufficient coverage or identity; outcome unknown
08:10– 09:07
Trip sto:63297003Insufficient coverage or identity; outcome unknown
09:10– 10:07
Trip sto:63297004Vehicle position matchedFirst / last feed position: 9:22 a.m. EST / 10:03 a.m. EST; not actual start or end times.
09:17– 10:18
Trip sto:63296987Vehicle position matchedFirst / last feed position: 9:22 a.m. EST / 10:15 a.m. EST; not actual start or end times.
10:10– 11:07
Trip sto:63297005Vehicle position matchedFirst / last feed position: 10:04 a.m. EST / 11:07 a.m. EST; not actual start or end times.
10:17– 11:17
Trip sto:63296988Vehicle position matchedFirst / last feed position: 10:04 a.m. EST / 11:18 a.m. EST; not actual start or end times.
11:10– 12:07
Trip sto:63297006Vehicle position matchedFirst / last feed position: 11:05 a.m. EST / 12:06 p.m. EST; not actual start or end times.
11:17– 12:17
Trip sto:63296989Vehicle position matchedFirst / last feed position: 11:20 a.m. EST / 12:18 p.m. EST; not actual start or end times.

· Open all evidence for this day