Detour Route 55 South: Route 55 diverted from Laval to Station Lyon.+1 more notice

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

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

Ruta 55 ng STO: Ottawa

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

CENTRE RIDEAU4 min sched.
ALBERT/METCALFE6 min sched.
ALBERT/BANK8 min sched.
KENT / SPARKS9 min sched.
WELLINGTON/LYON10 min sched.
du PORTAGE/AUBRY16 min sched.
du PORTAGE/LAVAL17 min sched.
LAURIER/EDDY18 min sched.
ALEXANDRE-TACHÉ/MILLAR20 min sched.
ALEXANDRE-TACHÉ/SAINT-JOSEPH21 min sched.
ALEXANDRE-TACHÉ/CHÂTEAUBRIAND22 min sched.
ALEXANDRE-TACHÉ/HORMIDAS-DUPUIS0 min sched.
ALEXANDRE-TACHÉ/BÉGIN0 min sched.
ALEXANDRE-TACHÉ/BOUDRIA1 min sched.
ALEXANDRE-TACHÉ/SAINTE-THÉRÈSE1 min sched.
ALEXANDRE-TACHÉ/SAINT-DOMINIQUE2 min sched.
ALEXANDRE-TACHÉ/SAINT-RAYMOND3 min sched.
chemin d'AYLMER/ROYALE3 min sched.
chemin d'AYLMER/SAMUEL-DE-CHAMPLAIN4 min sched.
chemin d'AYLMER/d'AUGUSTA5 min sched.
chemin d'AYLMER/CHAUDIÈRE6 min sched.
chemin d'AYLMER/ALLEN6 min sched.
chemin d'AYLMER/ATHOLL DOUNE7 min sched.
chemin d'AYLMER/d'AMOUR7 min sched.
PARC-O-BUS RIVERMEAD8 min sched.
chemin d'AYLMER/de l'HIPPODROME10 min sched.
chemin d'AYLMER/MORLEY-WALTERS11 min sched.
chemin d'AYLMER/VANIER12 min sched.
chemin d'AYLMER/VANIER12 min sched.
chemin d'AYLMER/GARDEN13 min sched.
chemin d'AYLMER/du GOLF14 min sched.
chemin d'AYLMER/GRIMES15 min sched.
chemin d'AYLMER/FRASER17 min sched.
chemin d'AYLMER/SAMUEL-EDEY18 min sched.
chemin d'AYLMER/BELMONT19 min sched.
chemin d'AYLMER/de la COLLINE19 min sched.
PRINCIPALE/du BORDEAUX20 min sched.
WILFRID-LAVIGNE/PRINCIPALE21 min sched.
WILFRID-LAVIGNE/LEGUERRIER21 min sched.
WILFRID-LAVIGNE/JOHN-EGAN22 min sched.
WILFRID-LAVIGNE/de la CORSE22 min sched.
WILFRID-LAVIGNE/CHARLES-DEVLIN23 min sched.
WILFRID-LAVIGNE/des RÉDEMPTORISTES24 min sched.
WILFRID-LAVIGNE/de BRUYNE24 min sched.
WILFRID-LAVIGNE/des ALLUMETTIÈRES25 min sched.
du VERGER/des TRÈFLES26 min sched.
du VERGER/des CHAMPIGNONS26 min sched.
du VERGER/des HYDRANGÉES27 min sched.
KLOCK/du VERGER28 min sched.
KLOCK/des TILLEULS28 min sched.
BROAD/WRIGHT29 min sched.
BROAD/LOUIS-SAINT-LAURENT0 min sched.
BROAD/LOUIS-SAINT-LAURENT0 min sched.
BAGOT/BROAD2 min sched.
BAGOT/PARKER2 min sched.
BAGOT/CORMIER3 min sched.
CORMIER/CHARTIER4 min sched.
FRONT/CORMIER4 min sched.
FRONT/de la TERRASSE-EARDLEY5 min sched.
FRONT/de la TERRASSE-EARDLEY6 min sched.
des ALLUMETTIÈRES/FRONT6 min sched.
PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée9 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: 4.

Trips needing investigation

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

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

522 with position · 6 to investigate · 80 excluded · 608 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 522 / 608 (85.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, 12:48 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

77.1%

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

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

The hours we have evidence for

0079% · 1,447 predictions · 10 days
01100% · 120 predictions · 8 days
0591% · 1,102 predictions · 7 days
0696% · 1,714 predictions · 10 days
0788% · 2,185 predictions · 9 days
0883% · 2,684 predictions · 10 days
0986% · 2,783 predictions · 11 days
1091% · 2,527 predictions · 11 days
1188% · 2,361 predictions · 12 days
1277% · 2,600 predictions · 12 days
1391% · 2,633 predictions · 12 days
1478% · 2,802 predictions · 13 days
1576% · 3,178 predictions · 12 days
1658% · 3,030 predictions · 13 days
1757% · 3,737 predictions · 12 days
1877% · 3,700 predictions · 11 days
1983% · 2,508 predictions · 11 days
2087% · 2,300 predictions · 10 days
2187% · 2,328 predictions · 10 days
2282% · 2,322 predictions · 10 days
2384% · 2,100 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?

21 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

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

1% of pairs (858) 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.)	1,250	0% (3)	0% (2)
Rush hour sa umaga (6 hanggang 9 a.m.)	9,800	2% (229)	1% (95)
Tanghali (9 a.m. hanggang 3 p.m.)	21,583	0% (47)	0% (94)
Rush hour sa hapon (3 hanggang 6 p.m.)	12,828	5% (587)	4% (467)
Gabi (6 hanggang 10 p.m.)	16,458	2% (295)	1% (199)
Gabi (10 p.m. hanggang 4 a.m.)	9,534	0% (0)	0% (1)

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, 7.5 km/h actual against 13.3 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	13.3 km/h	7.5 km/h	667	45%
KENT / SPARKS	du PORTAGE/AUBRY	1.2 km	11.9 km/h	9.1 km/h	719	30%
PARC-O-BUS ALLUMETTIÈRES	BROAD/JOHN-RONEY	2.7 km	20.1 km/h	9.9 km/h	578	68%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	14.1 km/h	11.5 km/h	704	19%
du PORTAGE/AUBRY	LAURIER/EDDY	470 m	11.7 km/h	12.8 km/h	749	4%
PARC-O-BUS RIVERMEAD	chemin d'AYLMER/MORLEY-WALTERS	790 m	14.6 km/h	14.4 km/h	761	8%
de l'HÔTEL-de-VILLE/LAURIER	CENTRE RIDEAU	2.5 km	13.1 km/h	16.4 km/h	606	0%
BROAD/WRIGHT	PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée	2.8 km	17.2 km/h	18.2 km/h	696	2%

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.

Gawaing kalsada
ALBERT between ELGIN and METCALFE
Okt 29, 2026, 12:00 AM to Ene 26, 2027, 5:00 PM
ALBERT lane reduction between ELGIN and METCALFE due to construction, from October 29th to January 26th.
Minarkahan ito ng Lungsod na nakakaapekto sa transit.
about 0 m from the route
City record updated Nob 2, 2026, 12:44 PM.
Gawaing kalsada
Slater between Bay and Lyon
Okt 30, 2026, 12:00 AM to Nob 6, 2026, 5:00 PM
Slater lane reduction between Bay and Lyon due to construction, from November 2nd to 6th.
about 0 m from the route
City record updated Okt 30, 2026, 1:28 PM.
Gawaing kalsada
ALBERT at LYON
Hindi inilathala ang mga petsa
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 2 m from the route
City record updated Set 9, 2026, 6:32 PM.

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.

3 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: 6 PM (2), 7 AM (1)

Mga pinakabagong kinanselang biyahe

Mar, Nob 3, scheduled 18:03
Huw, Okt 29, scheduled 18:24
Lun, Okt 19, scheduled 07:44

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

Did not come (no bus seen, no notice), last 7 days: 5 of 528 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 upuan1.4% of 144 trips	Kulang ang mga pagbasa	Kulang ang mga pagbasa
6 hanggang 9 ng umaga	Karaniwang may upuan29.4% of 656 trips	Karaniwang may upuan2.2% of 90 trips	Karaniwang may upuan0% of 71 trips
9 am hanggang 3 pm	Karaniwang may upuan19.4% of 1,083 trips	Karaniwang may upuan9.8% of 205 trips	Karaniwang may upuan1.1% of 181 trips
3 hanggang 6 ng hapon	Karaniwang may upuan49.9% of 815 trips	Karaniwang may upuan20% of 120 trips	Karaniwang may upuan4.5% of 112 trips
6 hanggang 10 pm	Karaniwang may upuan14.5% of 813 trips	Karaniwang may upuan5.4% of 148 trips	Karaniwang may upuan0.8% of 133 trips
Pagkatapos ng 10 pm	Karaniwang may upuan2.2% of 416 trips	Karaniwang may upuan3.8% of 79 trips	Karaniwang may upuan0% of 66 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 4.1 min later than the timetable in 2 hours of the day.

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

17:00 has 57% of predictions within five minutes of the timetable, against 84% 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, 21 hours with samples

00:00: 79.4% of final predictions within five minutes of the timetable, 1,447 predictions, typically 1.8 min late
01:00: 100% of final predictions within five minutes of the timetable, 120 predictions, typically 0.4 min late
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 90.7% of final predictions within five minutes of the timetable, 1,102 predictions, typically 2.1 min late
06:00: 96.4% of final predictions within five minutes of the timetable, 1,714 predictions, typically 1 min late
07:00: 88.3% of final predictions within five minutes of the timetable, 2,185 predictions, typically 1.3 min late
08:00: 83.4% of final predictions within five minutes of the timetable, 2,684 predictions, typically 1.7 min late
09:00: 85.6% of final predictions within five minutes of the timetable, 2,783 predictions, typically 2 min late
10:00: 90.9% of final predictions within five minutes of the timetable, 2,527 predictions, typically 1.2 min late
11:00: 87.5% of final predictions within five minutes of the timetable, 2,361 predictions, typically 1.6 min late
12:00: 76.6% of final predictions within five minutes of the timetable, 2,600 predictions, typically 1.5 min late
13:00: 90.9% of final predictions within five minutes of the timetable, 2,633 predictions, typically 1.1 min late
14:00: 78.3% of final predictions within five minutes of the timetable, 2,802 predictions, typically 1.9 min late
15:00: 75.6% of final predictions within five minutes of the timetable, 3,178 predictions, typically 2 min late
16:00: 58.3% of final predictions within five minutes of the timetable, 3,030 predictions, typically 4.1 min late
17:00: 57.3% of final predictions within five minutes of the timetable, 3,737 predictions, typically 4 min late
18:00: 77% of final predictions within five minutes of the timetable, 3,700 predictions, typically 2.2 min late
19:00: 83% of final predictions within five minutes of the timetable, 2,508 predictions, typically 1.9 min late
20:00: 86.7% of final predictions within five minutes of the timetable, 2,300 predictions, typically 1.3 min late
21:00: 86.5% of final predictions within five minutes of the timetable, 2,328 predictions, typically 1.6 min late
22:00: 82.2% of final predictions within five minutes of the timetable, 2,322 predictions, typically 1.8 min late
23:00: 84.3% of final predictions within five minutes of the timetable, 2,100 predictions, typically 1.3 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 to 18:00	4.1 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	17:00	57%	Operations, not the timetable

Measurements

Predictions later than timetable · 16:00 to 18:00: Measured arrivals 6,767; Hours affected 2; Spread 15.1 min; Median delay 4.1 min; Suggested running time change 4.1 min
One hour has a lower prediction match · 17:00: Oras 17:00; Nasa oras 57.3%; Measured arrivals 3,737; Shortfall 27 pts; Route median on time 84.3%

Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta

Pagsusuri ng ruta

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

77 in 100 eligible predictions were within 5 minutes of the timetable · 94,935 predictions checked

Laki ng sample ng prediksyon: Mas malaking sample

Based on 94,935 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.

17–18: 43 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,737 predictions over 12 days).
16–17: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (3,030 predictions over 13 days).

1 current notice affects this route

• Detour Route 55 South

Pagkakaiba ng hula ayon sa hintuan

PARC-O-BUS ALLUMETTIÈRES
55 in 100 eligible predictions differed from the timetable by more than 5 minutes (757 predictions over 24 days).
Buksan ang hintuang ito
sto:1294
40 in 100 eligible predictions differed from the timetable by more than 5 minutes (132 predictions over 3 days).
Buksan ang hintuang ito
du PORTAGE/AUBRY
36 in 100 eligible predictions differed from the timetable by more than 5 minutes (887 predictions over 24 days).
Buksan ang hintuang ito
chemin d'AYLMER/ROYALE
34 in 100 eligible predictions differed from the timetable by more than 5 minutes (898 predictions over 24 days).
Buksan ang hintuang ito

Ito ay mga hula ng provider para sa partikular na ruta, na inihambing sa iskedyul. Ipinapakita nito ang paulit-ulit na pagkakaiba ng hula sa isang lugar at oras. Hindi ito nasukat na pagdating at hindi nito sinasabi ang dahilan.

Suriin ang bawat biyahe at petsa

Magbukas ng yugto ng panahon para makita ang bawat araw ng serbisyo, nakatakdang biyahe, puwang sa feed, naobserbahang pampublikong ID ng sasakyan, at ang eksaktong bilang sa likod ng buod na ito.

Ang gustong malaman ng mga pasahero

May kanseladong biyahe ba ngayon?: 0 of 12Sinusuri ang mga biyaheng magsisimula sa dulo ng ruta sa susunod na 4 na oras. Hindi ito makasaysayang bilang ng pagkansela.
Posibleng hindi sumipot matapos suriin ang mga puwang sa feed?: 6 of 528 checked trips need a closer look6 of 528 trips with enough public-feed evidence had no matching position over 7 days. 80 of 608 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 11.0 min (positive means later; negative means earlier)77 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?: 6.1 min average predicted wait0.7 min beyond the scheduled wait, based on 6,988 eligible predictions at 97 high-frequency stops over 13 days.

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: 94
Mga natatanging hintuan na nasa iskedyul: 122
Iba't ibang inilathalang daanan: 4
Inilathalang oras ng serbisyo: 05:01–01:12 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 53,376 arrivals over 13 days; after has 6,404 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: 77.1%
Mga karapat-dapat na hula na nasuri: 94,935
Mga araw ng linggo na may datos: 17
Tinatayang pagkaantala sa ika-95 na percentile: 11 min late

Patterns by hour (21)

Patterns by hour (21)
Oras	Nasa oras	Median	95th percentile	Ebidensya
00:00	79.4%	1.8 min late	7.2 min late	1,447 · 10 days
01:00	100.0%	0.4 min late	1.9 min late	120 · 8 days
05:00	90.7%	2.1 min late	5.7 min late	1,102 · 7 days
06:00	96.4%	1 min late	4.3 min late	1,714 · 10 days
07:00	88.3%	1.3 min late	6.7 min late	2,185 · 9 days
08:00	83.4%	1.7 min late	8.3 min late	2,684 · 10 days
09:00	85.6%	2 min late	8.9 min late	2,783 · 11 days
10:00	90.9%	1.2 min late	6 min late	2,527 · 11 days
11:00	87.5%	1.6 min late	6.6 min late	2,361 · 12 days
12:00	76.6%	1.5 min late	9.2 min late	2,600 · 12 days
13:00	90.9%	1.1 min late	5.8 min late	2,633 · 12 days
14:00	78.3%	1.9 min late	8.5 min late	2,802 · 13 days
15:00	75.6%	2 min late	10.8 min late	3,178 · 12 days
16:00	58.3%	4.1 min late	19 min late	3,030 · 13 days
17:00	57.3%	4 min late	19.4 min late	3,737 · 12 days
18:00	77.0%	2.2 min late	9.3 min late	3,700 · 11 days
19:00	83.0%	1.9 min late	6.9 min late	2,508 · 11 days
20:00	86.7%	1.3 min late	7 min late	2,300 · 10 days
21:00	86.5%	1.6 min late	6.9 min late	2,328 · 10 days
22:00	82.2%	1.8 min late	8.4 min late	2,322 · 10 days
23:00	84.3%	1.3 min late	6.9 min late	2,100 · 10 days

2 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

522 / 608 scheduled trips published at least one position across 7 service days (85.9%).

22:009 / 28 trips without a position67.9%
23:007 / 24 trips without a position70.8%
00:002 / 7 trips without a position71.4%
19:008 / 28 trips without a position71.4%
20:008 / 28 trips without a position71.4%
21:008 / 28 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 · 94 trips in the retained timetable · retained notices; capture coverage unverified

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

05:01– 05:51
Trip sto:63294978Insufficient coverage or identity; outcome unknown
05:16– 06:06
Trip sto:63295153Insufficient coverage or identity; outcome unknown
05:29– 06:20
Trip sto:63295149Insufficient coverage or identity; outcome unknown
05:44– 06:38
Trip sto:63294695Insufficient coverage or identity; outcome unknown
05:58– 06:54
Trip sto:63295779Insufficient coverage or identity; outcome unknown
06:17– 07:10
Trip sto:63294644Insufficient coverage or identity; outcome unknown
06:19– 07:16
Trip sto:63295716Insufficient coverage or identity; outcome unknown
06:27– 07:24
Trip sto:63294639Insufficient coverage or identity; outcome unknown
06:39– 07:42
Trip sto:63296142Insufficient coverage or identity; outcome unknown
06:54– 07:57
Trip sto:63295339Insufficient coverage or identity; outcome unknown
07:07– 08:13
Trip sto:63295476Insufficient coverage or identity; outcome unknown
07:15– 08:16
Trip sto:63295150Insufficient coverage or identity; outcome unknown

· Open all evidence for this day