Detour Route 52 South: Route 52 diverted from Eastern to Deschênes.+1 more notice

No 52 trips cancelled now · 3 did not run in NobyembreCancellations →

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

Ruta 52 ng STO: Des Cèdre/Rivermead/Vanier

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

KATIMAVIK/DU PLATEAU16 min sched.
de SÉTO/KATIMAVIK17 min sched.
VANIER/ATTIKAMEKS20 min sched.
MCCONNELL/MORLEY-WALTERS21 min sched.
MCCONNELL/CASTELBEAU21 min sched.
MCCONNELL/JEAN-DE LA FONTAINE22 min sched.
MCCONNELL/des MANOIRS22 min sched.
RIVERMEAD/ÉMILE-ZOLA23 min sched.
RIVERMEAD/JEAN-DE LA FONTAINE24 min sched.
PARC-O-BUS RIVERMEAD25 min sched.
chemin d'AYLMER/de l'HIPPODROME28 min sched.
chemin d'AYLMER/MORLEY-WALTERS29 min sched.
VANIER/LYNN30 min sched.
VANIER/CRESCENT30 min sched.
VANIER/des VÉTÉRANS31 min sched.
VANIER/CRESCENT32 min sched.
VANIER/CALVADOS32 min sched.
VANIER/de LUCERNE33 min sched.
CÔTÉ/LUCERNE34 min sched.
CÔTÉ/DESCHÊNES34 min sched.
CÔTÉ/LAMOUREUX34 min sched.
LAMOUREUX/VANIER35 min sched.
VANIER/MADAIRE36 min sched.
VANIER/SAINT-MÉDARD36 min sched.
de LUCERNE/GARDEN37 min sched.
de LUCERNE/VICTOR-BEAUDRY37 min sched.
de LUCERNE/FRASER39 min sched.
de LUCERNE/EASTERN40 min sched.
de LUCERNE/RIESLING41 min sched.
de LUCERNE/ÉLIZABETH43 min sched.
FRANK-ROBINSON/CENTRE WESTERN QUÉBEC43 min sched.
FRANK-ROBINSON/DU PATRIMOINE45 min sched.
PRINCIPALE/WILFRID-LAVIGNE45 min sched.
chemin d'AYLMER/du BORDEAUX46 min sched.
de la COLLINE/chemin d'AYLMER47 min sched.
de la COLLINE/des EXPLORATEURS48 min sched.
de la COLLINE/du VALLON49 min sched.
du VALLON/des DRAVEURS50 min sched.
du VALLON/du CAVEAU51 min sched.
du CAVEAU/SAMUEL-EDEY51 min sched.
SAMUEL-EDEY/des PAYSANS52 min sched.
SAMUEL-EDEY/MCCONNELL53 min sched.
des ALLUMETTIÈRES/SAMUEL-EDEY54 min sched.
WILFRID-LAVIGNE/des ALLUMETTIÈRES56 min sched.
WILFRID-LAVIGNE/des PINACÉES57 min sched.
WILFRID-LAVIGNE/du BOIS-FRANC57 min sched.
WILFRID-LAVIGNE/des THUYAS58 min sched.
WILFRID-LAVIGNE/MAURICE-DUPLESSIS59 min sched.
WILFRID-LAVIGNE/LYSE-DANIELS59 min sched.
WILFRID-LAVIGNE/KLOCK60 min sched.
du RATON-LAVEUR/de la MARMOTTE0 min sched.
du RATON-LAVEUR/du LOUP-GRIS1 min sched.
du RATON-LAVEUR/FRONT2 min sched.
FRONT/du RENARD2 min sched.
FRONT/du MARCHÉ3 min sched.
FRONT/du VERGER3 min sched.
FRONT/des ALLUMETTIÈRES4 min sched.
des ALLUMETTIÈRES/FRONT4 min sched.
PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée7 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: 2.

Trips needing investigation

4 of 218 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.

214 with position · 4 to investigate · 34 excluded · 252 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 214 / 252 (84.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:08 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

54.9%

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

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

The hours we have evidence for

05100% · 41 predictions · 6 days
0668% · 951 predictions · 10 days
0756% · 850 predictions · 9 days
0854% · 920 predictions · 10 days
0954% · 1,055 predictions · 11 days
1065% · 1,147 predictions · 11 days
1151% · 1,224 predictions · 12 days
1254% · 1,294 predictions · 12 days
1362% · 1,345 predictions · 12 days
1457% · 1,209 predictions · 13 days
1552% · 1,249 predictions · 12 days
1646% · 1,109 predictions · 12 days
1747% · 1,117 predictions · 12 days
1846% · 1,079 predictions · 11 days
1945% · 1,205 predictions · 11 days
2043% · 1,076 predictions · 10 days
2165% · 1,126 predictions · 10 days
2280% · 1,183 predictions · 10 days
2372% · 1,069 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?

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.

Too few buses were measured to judge bunching: 0 pairs checked, 30 needed.

Paano ito sinusukat →How we got this numberMagkakadikit na bus at mabagal na bahagi sa bawat ruta →

Kung saan pinakamabagal ang rutang ito

Slowest: PARC-O-BUS ALLUMETTIÈRES to FRONT/des ALLUMETTIÈRES, 5.1 km/h actual against 16.7 km/h planned.

Kung saan pinakamabagal ang rutang ito
Mula sa	Patungo sa	Layo	Planong bilis	Aktuwal na bilis	Mga biyaheng sinukat	Mabagal na biyahe
PARC-O-BUS ALLUMETTIÈRES	FRONT/des ALLUMETTIÈRES	830 m	16.7 km/h	5.1 km/h	223	76%
KATIMAVIK/DU PLATEAU	VANIER/ATTIKAMEKS	970 m	13.5 km/h	7.9 km/h	194	49%
de LUCERNE/FRASER	VANIER/SAINT-MÉDARD	2.2 km	22.9 km/h	12.1 km/h	298	76%
PARC-O-BUS RIVERMEAD	chemin d'AYLMER/MORLEY-WALTERS	790 m	11.8 km/h	14.8 km/h	281	2%
MCCONNELL/MORLEY-WALTERS	VANIER/de SETO	990 m	16.2 km/h	16.2 km/h	288	7%
FRONT/des ALLUMETTIÈRES	PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée	830 m	15.6 km/h	16.5 km/h	299	2%
chemin d'AYLMER/MORLEY-WALTERS	de LUCERNE/FRASER	4.6 km	30.4 km/h	17.3 km/h	282	66%
PARC-O-BUS RIVERMEAD	MCCONNELL/MORLEY-WALTERS	1.7 km	16.7 km/h	18.8 km/h	278	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.

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

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

Mga oras na may pinakamaraming kanseladong biyahe: 4 PM (2), 6 PM (2), 9 AM (1)

Mga pinakabagong kinanselang biyahe

Biy, Okt 30, scheduled 20:00
Mar, Okt 27, scheduled 18:00
Biy, Okt 23, scheduled 16:59
Mar, Okt 20, scheduled 18:00
Mar, Okt 20, scheduled 09:00

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: 3 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 58 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 9 ng umaga	Karaniwang may upuan0% of 236 trips	Karaniwang may upuan0% of 51 trips	Karaniwang may upuan0% of 48 trips
9 am hanggang 3 pm	Karaniwang may upuan0% of 474 trips	Karaniwang may upuan0% of 102 trips	Karaniwang may upuan0% of 101 trips
3 hanggang 6 ng hapon	Karaniwang may upuan1.3% of 226 trips	Karaniwang may upuan0% of 61 trips	Karaniwang may upuan0% of 67 trips
6 hanggang 10 pm	Karaniwang may upuan0.6% of 361 trips	Karaniwang may upuan0% of 75 trips	Karaniwang may upuan0% of 65 trips
Pagkatapos ng 10 pm	Karaniwang may upuan0% of 126 trips	Karaniwang may upuan2.2% of 46 trips	Karaniwang may upuan0% of 34 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.9 to 5.1 min later than the timetable in 13 hours of the day.

The prediction difference from the timetable grows by about 3.7 min along the route.

Wide prediction spread 08:00 to 11:00, 15:00 to 18:00: the 95th percentile is 26.6 min later than the median.

Scenario: 4 to 5 min more running time on 198 trips. The schedule-block model adds no buses; fleet and workforce feasibility are unverified.

Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 20 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: 100% of final predictions within five minutes of the timetable, 41 predictions, typically 0.2 min early
06:00: 67.9% of final predictions within five minutes of the timetable, 951 predictions, typically 2.7 min late
07:00: 56% of final predictions within five minutes of the timetable, 850 predictions, typically 4 min late
08:00: 54.1% of final predictions within five minutes of the timetable, 920 predictions, typically 3.2 min late. Provider predictions have a wide spread.
09:00: 54.2% of final predictions within five minutes of the timetable, 1,055 predictions, typically 3.9 min late. Provider predictions have a wide spread.
10:00: 64.5% of final predictions within five minutes of the timetable, 1,147 predictions, typically 2 min late. Provider predictions have a wide spread.
11:00: 51.4% of final predictions within five minutes of the timetable, 1,224 predictions, typically 4.8 min late
12:00: 53.7% of final predictions within five minutes of the timetable, 1,294 predictions, typically 4.3 min late
13:00: 61.8% of final predictions within five minutes of the timetable, 1,345 predictions, typically 3.2 min late
14:00: 56.9% of final predictions within five minutes of the timetable, 1,209 predictions, typically 4 min late
15:00: 51.7% of final predictions within five minutes of the timetable, 1,249 predictions, typically 4.7 min late. Provider predictions have a wide spread.
16:00: 45.7% of final predictions within five minutes of the timetable, 1,109 predictions, typically 5.8 min late. Provider predictions have a wide spread.
17:00: 46.9% of final predictions within five minutes of the timetable, 1,117 predictions, typically 6.7 min late. Provider predictions have a wide spread.
18:00: 45.8% of final predictions within five minutes of the timetable, 1,079 predictions, typically 5.9 min late
19:00: 45.4% of final predictions within five minutes of the timetable, 1,205 predictions, typically 5.3 min late
20:00: 43.4% of final predictions within five minutes of the timetable, 1,076 predictions, typically 5.5 min late
21:00: 64.9% of final predictions within five minutes of the timetable, 1,126 predictions, typically 2.9 min late
22:00: 79.5% of final predictions within five minutes of the timetable, 1,183 predictions, typically 1.8 min late
23:00: 72.1% of final predictions within five minutes of the timetable, 1,069 predictions, typically 2.8 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
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	Kailan	Nasukat	Scenario or next investigation
ProblemPredictions later than timetable	07:00 to 10:00 · 11:00 to 21:00	3.9 min late · 5.1 min late	More running time
ProblemWide prediction spread	08:00 to 11:00 · 15:00 to 18:00	22.8 min swing · 26.6 min swing	Operations, not the timetable

Measurements

Predictions later than timetable · 11:00 to 21:00: Measured arrivals 11,907; Hours affected 10; Spread 16 min; Median delay 5.1 min; Suggested running time change 5.1 min
Wide prediction spread · 15:00 to 18:00: Measured arrivals 3,475; Hours affected 3; Spread 26.6 min; Median delay 5.8 min; Suggested running time change 5.8 min
Predictions later than timetable · 07:00 to 10:00: Measured arrivals 2,825; Hours affected 3; Spread 22.8 min; Median delay 3.9 min; Suggested running time change 3.9 min
Wide prediction spread · 08:00 to 11:00: Measured arrivals 3,122; Hours affected 3; Spread 22.8 min; Median delay 3.2 min; Suggested running time change 3.2 min

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 52 has been running

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

Pangunahing punto

Madalas na malayo sa iskedyul ang mga hula ng tagapagbigay sa sample na may petsang ito.

55 in 100 eligible predictions were within 5 minutes of the timetable · 38,425 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 38,425 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.

20–21: 57 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,076 predictions over 10 days).
19–20: 55 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,205 predictions over 11 days).
16–17: 54 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,109 predictions over 12 days).
18–19: 54 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,079 predictions over 11 days).

2 current notices affect this route

• Detour Route 52 South
• Detour Route 52 North

Pagkakaiba ng hula ayon sa hintuan

de la COLLINE/des EXPLORATEURS
84 in 100 eligible predictions differed from the timetable by more than 5 minutes (344 predictions over 24 days).
Buksan ang hintuang ito
de LUCERNE/EASTERN
83 in 100 eligible predictions differed from the timetable by more than 5 minutes (346 predictions over 24 days).
Buksan ang hintuang ito
de LUCERNE/RIESLING
83 in 100 eligible predictions differed from the timetable by more than 5 minutes (349 predictions over 24 days).
Buksan ang hintuang ito
de la COLLINE/du VALLON
81 in 100 eligible predictions differed from the timetable by more than 5 minutes (349 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 8Sinusuri 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?: 4 of 218 checked trips need a closer look4 of 218 trips with enough public-feed evidence had no matching position over 7 days. 34 of 252 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 20.9 min (positive means later; negative means earlier)55 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: 36
Mga natatanging hintuan na nasa iskedyul: 122
Iba't ibang inilathalang daanan: 2
Inilathalang oras ng serbisyo: 05:53–23:45

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 21,400 arrivals over 13 days; after has 2,624 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: 54.9%
Mga karapat-dapat na hula na nasuri: 38,425
Mga araw ng linggo na may datos: 17
Tinatayang pagkaantala sa ika-95 na percentile: 20.9 min late

Patterns by hour (20)

Patterns by hour (20)
Oras	Nasa oras	Median	95th percentile	Ebidensya
00:00	35.0%	6.8 min late	19 min late	60 · 2 days
05:00	100.0%	0.2 min early	3.2 min late	41 · 6 days
06:00	67.9%	2.7 min late	12.7 min late	951 · 10 days
07:00	56.0%	4 min late	20.8 min late	850 · 9 days
08:00	54.1%	3.2 min late	36.4 min late	920 · 10 days
09:00	54.2%	3.9 min late	26.7 min late	1,055 · 11 days
10:00	64.5%	2 min late	24.3 min late	1,147 · 11 days
11:00	51.4%	4.8 min late	20.9 min late	1,224 · 12 days
12:00	53.7%	4.3 min late	17.5 min late	1,294 · 12 days
13:00	61.8%	3.2 min late	16.8 min late	1,345 · 12 days
14:00	56.9%	4 min late	20.3 min late	1,209 · 13 days
15:00	51.7%	4.7 min late	27.3 min late	1,249 · 12 days
16:00	45.7%	5.8 min late	33.8 min late	1,109 · 12 days
17:00	46.9%	6.7 min late	33.3 min late	1,117 · 12 days
18:00	45.8%	5.9 min late	21.9 min late	1,079 · 11 days
19:00	45.4%	5.3 min late	18.5 min late	1,205 · 11 days
20:00	43.4%	5.5 min late	16.5 min late	1,076 · 10 days
21:00	64.9%	2.9 min late	14.8 min late	1,126 · 10 days
22:00	79.5%	1.8 min late	16.3 min late	1,183 · 10 days
23:00	72.1%	2.8 min late	12 min late	1,069 · 10 days

16 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

214 / 252 scheduled trips published at least one position across 5 service days (84.9%).

23:004 / 9 trips without a position55.6%
05:002 / 5 trips without a position60.0%
20:005 / 14 trips without a position64.3%
21:004 / 14 trips without a position71.4%
22:004 / 14 trips without a position71.4%
19:005 / 19 trips without a position73.7%

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

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

05:53– 06:40
Trip sto:63294804Insufficient coverage or identity; outcome unknown
06:00– 06:45
Trip sto:63296198Insufficient coverage or identity; outcome unknown
06:50– 07:41
Trip sto:63295042Insufficient coverage or identity; outcome unknown
07:00– 07:49
Trip sto:63296200Insufficient coverage or identity; outcome unknown
07:55– 08:49
Trip sto:63294583Insufficient coverage or identity; outcome unknown
08:03– 08:51
Trip sto:63296199Insufficient coverage or identity; outcome unknown
08:53– 09:43
Trip sto:63296167Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 9:56 a.m. EST; not actual start or end times.
09:00– 09:48
Trip sto:63294608Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 10:07 a.m. EST; not actual start or end times.
09:53– 10:42
Trip sto:63295911Vehicle position matchedFirst / last feed position: 9:51 a.m. EST / 10:51 a.m. EST; not actual start or end times.
10:01– 10:50
Trip sto:63295255Vehicle position matchedFirst / last feed position: 10:01 a.m. EST / 10:51 a.m. EST; not actual start or end times.
10:54– 11:43
Trip sto:63294609Vehicle position matchedFirst / last feed position: 10:52 a.m. EST / 11:56 a.m. EST; not actual start or end times.
11:00– 11:49
Trip sto:63295174Vehicle position matchedFirst / last feed position: 10:52 a.m. EST / 11:52 a.m. EST; not actual start or end times.

· Open all evidence for this day