Detour Route 34 South: Route 34 diverted from Laval to Station Lyon.

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

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

Ruta 34 ng STO: Plateau/Des Trembles

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

CENTRE RIDEAU8 min sched.
ALBERT/METCALFE11 min sched.
ALBERT/BANK12 min sched.
KENT / SPARKS14 min sched.
WELLINGTON/LYON15 min sched.
du PORTAGE/AUBRY20 min sched.
du PORTAGE/LAVAL21 min sched.
LAURIER/EDDY24 min sched.
ALEXANDRE-TACHÉ/MILLAR1 min sched.
ALEXANDRE-TACHÉ/SAINT-JOSEPH2 min sched.
ALEXANDRE-TACHÉ/CHÂTEAUBRIAND3 min sched.
ALEXANDRE-TACHÉ/HORMIDAS-DUPUIS4 min sched.
ALEXANDRE-TACHÉ/BÉGIN5 min sched.
ALEXANDRE-TACHÉ/BOUDRIA6 min sched.
ALEXANDRE-TACHÉ/SAINTE-THÉRÈSE6 min sched.
ALEXANDRE-TACHÉ/SAINT-DOMINIQUE7 min sched.
ALEXANDRE-TACHÉ/SAINT-RAYMOND8 min sched.
SAINT-RAYMOND/des CAPUCINES9 min sched.
SAINT-RAYMOND/des JONQUILLES10 min sched.
SAINT-RAYMOND/des TREMBLES10 min sched.
des TREMBLES/SAINT-RAYMOND11 min sched.
des TREMBLES/BOYER12 min sched.
des TREMBLES/de la SITELLE12 min sched.
des TREMBLES/de L'ÉPERVIER13 min sched.
des TREMBLES/des PERDRIX14 min sched.
des TREMBLES/des TOURTERELLES14 min sched.
LOUISE-CAMPAGNA/du MARTIN-PÊCHEUR15 min sched.
LOUISE-CAMPAGNA/du BRUANT16 min sched.
LOUISE-CAMPAGNA/des MIGRATEURS16 min sched.
SAINT-RAYMOND/LOUISE-CAMPAGNA17 min sched.
du PLATEAU/SAINT-RAYMOND19 min sched.
du PLATEAU/des CÈDRES20 min sched.
de l'ATMOSPHÈRE/du PLATEAU21 min sched.
de l'ATMOSPHÈRE/de l'ASTROLABE21 min sched.
de l'ATMOSPHÈRE/de la SAPINIÈRE22 min sched.
de l'ATMOSPHÈRE/de L'ÉCLIPSE22 min sched.
de l'ATMOSPHÈRE/de l'ÉQUATEUR24 min sched.
de l'ATMOSPHÈRE/du FIRMAMENT24 min sched.
des GRIVES/de l'ATMOSPHERE25 min sched.
des GRIVES/du STRATUS26 min sched.
du PLATEAU/des GRIVES27 min sched.
du PLATEAU/du CUMULUS28 min sched.
du PLATEAU/de l'AUTOMNE29 min sched.
du PLATEAU/de BRUXELLES29 min sched.
AGORA0 min sched.
PLATEAU/EUROPE1 min sched.
du PLATEAU/du PRADO2 min sched.
du PLATEAU/de l'AMÉRIQUE-FRANÇAISE3 min sched.
du PLATEAU/d'AMSTERDAM5 min sched.
du PLATEAU/de LIVERPOOL6 min sched.
du PLATEAU/du MARIGOT8 min sched.
du PLATEAU/du MARIGOT9 min sched.
KATIMAVIK/DU PLATEAU9 min sched.
de SÉTO/KATIMAVIK10 min sched.
des ALLUMETTIÈRES/SAMUEL-EDEY15 min sched.
des ALLUMETTIÈRES/WILFRID-LAVIGNE16 min sched.
des ALLUMETTIÈRES/des CHAMPIGNONS17 min sched.
des ALLUMETTIÈRES/KLOCK18 min sched.
des ALLUMETTIÈRES/FRONT19 min sched.
PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée21 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: 2 trips with qualifying later matching vehicle observations. Trips with any notice: 2.

Trips needing investigation

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

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

387 with position · 2 to investigate · 53 excluded · 442 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 387 / 442 (87.6%). 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

79.5%

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

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

The hours we have evidence for

0081% · 719 predictions · 10 days
0690% · 652 predictions · 10 days
0789% · 803 predictions · 9 days
0887% · 1,249 predictions · 10 days
0986% · 2,286 predictions · 11 days
1087% · 2,363 predictions · 11 days
1186% · 2,410 predictions · 12 days
1274% · 2,523 predictions · 12 days
1384% · 2,624 predictions · 12 days
1475% · 2,421 predictions · 13 days
1565% · 2,307 predictions · 12 days
1675% · 1,524 predictions · 13 days
1755% · 1,551 predictions · 12 days
1869% · 2,373 predictions · 11 days
1983% · 2,249 predictions · 11 days
2083% · 2,214 predictions · 10 days
2182% · 2,236 predictions · 10 days
2288% · 2,317 predictions · 10 days
2390% · 2,085 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.

Mga halaga at paliwanag

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

0% of pairs (221) had a long gap: more than 1.75 times the planned wait between them.

Mga bus na dumarating nang magkakasabay
Oras ng araw	Mga pares na sinuri	Nagkumpol	Mahabang pagitan
Rush hour sa umaga (6 hanggang 9 a.m.)	1,590	0% (2)	0% (0)
Tanghali (9 a.m. hanggang 3 p.m.)	18,956	0% (38)	0% (42)
Rush hour sa hapon (3 hanggang 6 p.m.)	6,464	0% (32)	1% (82)
Gabi (6 hanggang 10 p.m.)	12,632	1% (70)	1% (81)
Gabi (10 p.m. hanggang 4 a.m.)	8,447	0% (1)	0% (16)

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

Kung saan pinakamabagal ang rutang ito

Slowest: CENTRE RIDEAU to KENT / SPARKS, 8.5 km/h actual against 14.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
CENTRE RIDEAU	KENT / SPARKS	1.2 km	14.5 km/h	8.5 km/h	485	41%
KENT / SPARKS	du PORTAGE/AUBRY	1.2 km	12.8 km/h	9.8 km/h	515	33%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	14.1 km/h	12 km/h	521	20%
PARC-O-BUS ALLUMETTIÈRES	VANIER/du PLATEAU	5.1 km	26.8 km/h	13 km/h	430	67%
du PORTAGE/AUBRY	LAURIER/EDDY	470 m	11.6 km/h	13.7 km/h	543	3%
de l'HÔTEL-de-VILLE/LAURIER	CENTRE RIDEAU	2.5 km	12.3 km/h	16.3 km/h	424	0%
SAINT-RAYMOND/LOUISE-CAMPAGNA	du PLATEAU/des CÈDRES	1 km	20 km/h	19.7 km/h	539	4%
VANIER/du PLATEAU	PLATEAU/EUROPE	2.2 km	21.6 km/h	19.9 km/h	509	6%

Ang mabagal na biyahe ay inabot nang hindi bababa sa 1.5 beses ng planadong oras.

Paano ito sinusukat →

Gawaing-kalsada ng lungsod malapit sa rutang ito

Mga gawaing kalsada at pagsasara ng kalsada para sa event na inilathala ng City of Ottawa, na sinukat bilang malapit sa daanan ng rutang ito. Ang malapit ay hindi patunay na iniiba ang daan ng bus. Tingnan po ang sariling abiso ng tagapagpatakbo para doon.

Hindi po mabasa ngayon ang listahan ng lungsod ng mga gawaing pangkalsada.

A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.

Pinagmulan: mga traffic event ng City of Ottawa (road work at mga pagsasara ng daan). May impormasyong lisensyado sa ilalim ng Open Government Licence, City of Ottawa. Ayon sa Lungsod, pinagsikapan lamang ang listahang ito at maaaring hindi kumpleto. Mapa ng trapiko ng Lungsod ng Ottawa ↗

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 389 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.

Kailan karaniwang siksikan ang rutang ito	Mga araw ng trabaho	Tuwing Sabado	Tuwing Linggo
Bago mag-6 am	Karaniwang may upuan0% of 27 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 9 ng umaga	Karaniwang may upuan0.4% of 256 trips	Karaniwang may upuan25.4% of 59 trips	Karaniwang may upuan10.2% of 49 trips
9 am hanggang 3 pm	Karaniwang may upuan15.4% of 908 trips	Karaniwang may upuan24.3% of 218 trips	Karaniwang may upuan19.8% of 197 trips
3 hanggang 6 ng hapon	Karaniwang may upuan22.6% of 380 trips	Karaniwang siksikan50.4% of 127 trips	Karaniwang may upuan15.4% of 136 trips
6 hanggang 10 pm	Karaniwang may upuan9.9% of 659 trips	Karaniwang may upuan31.6% of 152 trips	Karaniwang may upuan12.9% of 139 trips
Pagkatapos ng 10 pm	Karaniwang may upuan3.1% of 358 trips	Karaniwang may upuan3.8% of 79 trips	Karaniwang may upuan0% of 63 trips

Based on 56 computed days.

Pinagmulan: ang katayuan ng occupancy sa pampublikong real-time na vehicle feed ng STO, na itinatakda ng STO mula sa load sensor ng bawat bus (may bakanteng upuan kung wala pang 60% ang puno, may espasyo para tumayo kung wala pang 90%, puno kung higit sa 90%).
Isang beses lang binibilang ang bawat biyahe sa bawat bahagi ng araw, sa pinakamataas na dami ng sakay na iniulat nito.
Hindi isinama ang mga ulat ng walang laman na bus. Hindi kasi matukoy ng mga lumang talaan ang bus na walang laman mula sa bus na walang sensor.
Kailangan ng isang oras ng araw ng hindi bababa sa 12 biyahe sa hindi bababa sa 4 na magkakaibang araw bago may maipakita. Ang mga holiday ay binibilang ayon sa araw ng linggo nila.

Buksan ang may petsang pagsusuri ng hula

Hatol

What this route needs

Median provider predictions are 3.6 min later than the timetable in 1 hours of the day.

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

17:00 has 55% of predictions within five minutes of the timetable, against 83% the rest of the day.

Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.

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

00:00: 81.4% of final predictions within five minutes of the timetable, 719 predictions, typically 2.3 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: not enough data
06:00: 90.3% of final predictions within five minutes of the timetable, 652 predictions, typically 1.4 min late
07:00: 89% of final predictions within five minutes of the timetable, 803 predictions, typically 1.2 min late
08:00: 86.7% of final predictions within five minutes of the timetable, 1,249 predictions, typically 1.8 min late
09:00: 86% of final predictions within five minutes of the timetable, 2,286 predictions, typically 1.5 min late
10:00: 87.2% of final predictions within five minutes of the timetable, 2,363 predictions, typically 1.1 min late
11:00: 85.6% of final predictions within five minutes of the timetable, 2,410 predictions, typically 1.7 min late
12:00: 74.2% of final predictions within five minutes of the timetable, 2,523 predictions, typically 2.2 min late
13:00: 83.5% of final predictions within five minutes of the timetable, 2,624 predictions, typically 2 min late
14:00: 74.9% of final predictions within five minutes of the timetable, 2,421 predictions, typically 2.4 min late
15:00: 65.4% of final predictions within five minutes of the timetable, 2,307 predictions, typically 2.8 min late
16:00: 74.8% of final predictions within five minutes of the timetable, 1,524 predictions, typically 2 min late
17:00: 54.7% of final predictions within five minutes of the timetable, 1,551 predictions, typically 3.6 min late
18:00: 68.8% of final predictions within five minutes of the timetable, 2,373 predictions, typically 2.7 min late
19:00: 82.6% of final predictions within five minutes of the timetable, 2,249 predictions, typically 2.1 min late
20:00: 83.2% of final predictions within five minutes of the timetable, 2,214 predictions, typically 2 min late
21:00: 81.5% of final predictions within five minutes of the timetable, 2,236 predictions, typically 1.3 min late
22:00: 88.3% of final predictions within five minutes of the timetable, 2,317 predictions, typically 1.3 min late
23:00: 90.1% of final predictions within five minutes of the timetable, 2,085 predictions, typically 1.4 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	17:00	3.6 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	17:00	55%	Operations, not the timetable

Measurements

Predictions later than timetable · 17:00: Measured arrivals 1,551; Hours affected 1; Spread 15.2 min; Median delay 3.6 min; Suggested running time change 3.6 min
One hour has a lower prediction match · 17:00: Oras 17:00; Nasa oras 54.7%; Measured arrivals 1,551; Shortfall 28.5 pts; Route median on time 83.2%

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

How route 34 has been running

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

Pangunahing punto

Madalas na iba ang mga hula ng provider sa iskedyul; hindi nasukat nang hiwalay ang aktwal na pagdating.

80 in 100 eligible predictions were within 5 minutes of the timetable · 69,224 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 69,224 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.

17–18: 45 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,551 predictions over 12 days).
15–16: 35 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,307 predictions over 12 days).
18–19: 31 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,373 predictions over 11 days).

1 current notice affects this route

• Detour Route 34 South

Pagkakaiba ng hula ayon sa hintuan

PARC-O-BUS ALLUMETTIÈRES
65 in 100 eligible predictions differed from the timetable by more than 5 minutes (580 predictions over 24 days).
Buksan ang hintuang ito
du PORTAGE/AUBRY
37 in 100 eligible predictions differed from the timetable by more than 5 minutes (637 predictions over 24 days).
Buksan ang hintuang ito
du PORTAGE/LAVAL
32 in 100 eligible predictions differed from the timetable by more than 5 minutes (636 predictions over 24 days).
Buksan ang hintuang ito
ALEXANDRE-TACHÉ/SAINTE-THÉRÈSE
31 in 100 eligible predictions differed from the timetable by more than 5 minutes (640 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 11Sinusuri 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 389 checked trips need a closer look2 of 389 trips with enough public-feed evidence had no matching position over 7 days. 53 of 442 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 9.4 min (positive means later; negative means earlier)80 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: 62
Mga natatanging hintuan na nasa iskedyul: 122
Iba't ibang inilathalang daanan: 3
Inilathalang oras ng serbisyo: 05:55–00:41 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 38,780 arrivals over 13 days; after has 4,738 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: 79.5%
Mga karapat-dapat na hula na nasuri: 69,224
Mga araw ng linggo na may datos: 17
Tinatayang pagkaantala sa ika-95 na percentile: 9.4 min late

Patterns by hour (20)

Patterns by hour (20)
Oras	Nasa oras	Median	95th percentile	Ebidensya
00:00	81.4%	2.3 min late	10.8 min late	719 · 10 days
05:00	70.0%	0.9 min late	6.1 min late	20 · 7 days
06:00	90.3%	1.4 min late	9.2 min late	652 · 10 days
07:00	89.0%	1.2 min late	7.3 min late	803 · 9 days
08:00	86.7%	1.8 min late	6.3 min late	1,249 · 10 days
09:00	86.0%	1.5 min late	8.5 min late	2,286 · 11 days
10:00	87.2%	1.1 min late	6.6 min late	2,363 · 11 days
11:00	85.6%	1.7 min late	6.7 min late	2,410 · 12 days
12:00	74.2%	2.2 min late	12.9 min late	2,523 · 12 days
13:00	83.5%	2 min late	8.5 min late	2,624 · 12 days
14:00	74.9%	2.4 min late	11 min late	2,421 · 13 days
15:00	65.4%	2.8 min late	12 min late	2,307 · 12 days
16:00	74.8%	2 min late	8.3 min late	1,524 · 13 days
17:00	54.7%	3.6 min late	18.8 min late	1,551 · 12 days
18:00	68.8%	2.7 min late	13.6 min late	2,373 · 11 days
19:00	82.6%	2.1 min late	8 min late	2,249 · 11 days
20:00	83.2%	2 min late	7.7 min late	2,214 · 10 days
21:00	81.5%	1.3 min late	7.8 min late	2,236 · 10 days
22:00	88.3%	1.3 min late	6.1 min late	2,317 · 10 days
23:00	90.1%	1.4 min late	6.3 min late	2,085 · 10 days

3 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

387 / 442 scheduled trips published at least one position across 2 service days (87.6%).

06:004 / 12 trips without a position66.7%
19:008 / 28 trips without a position71.4%
20:008 / 28 trips without a position71.4%
21:008 / 28 trips without a position71.4%
23:006 / 21 trips without a position71.4%
22:007 / 26 trips without a position73.1%

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

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

05:55– 06:55
Trip sto:63295789Insufficient coverage or identity; outcome unknown
06:22– 07:23
Trip sto:63295154Insufficient coverage or identity; outcome unknown
06:53– 07:57
Trip sto:63294858Insufficient coverage or identity; outcome unknown
07:26– 08:33
Trip sto:63294878Insufficient coverage or identity; outcome unknown
07:56– 09:03
Trip sto:63294735Insufficient coverage or identity; outcome unknown
08:26– 09:28
Trip sto:63295448Vehicle position matchedFirst / last feed position: 9:22 a.m. EST / 9:30 a.m. EST; not actual start or end times.
08:40– 09:48
Trip sto:63295699Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 9:47 a.m. EST; not actual start or end times.
08:56– 09:58
Trip sto:63294860Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 9:54 a.m. EST; not actual start or end times.
09:13– 10:16
Trip sto:63294785Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 10:10 a.m. EST; not actual start or end times.
09:26– 10:26
Trip sto:63290351Vehicle position matchedFirst / last feed position: 9:26 a.m. EST / 11:10 a.m. EST; not actual start or end times.
09:43– 10:46
Trip sto:63294862Vehicle position matchedFirst / last feed position: 9:21 a.m. EST / 10:41 a.m. EST; not actual start or end times.
09:56– 10:56
Trip sto:63294737Vehicle position matchedFirst / last feed position: 10:01 a.m. EST / 11:02 a.m. EST; not actual start or end times.

· Open all evidence for this day