No 79 trips cancelled now · 2 did not run in 11月Cancellations →

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

STO 路線 79: Bellevue

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

STATION LORRAIN32 min sched.
LORRAIN/SAINT-RENÉ EST33 min sched.
LORRAIN/VINCENT-LEGRIS EST33 min sched.
LORRAIN/MARLENE-GOYET34 min sched.
LORRAIN/AUGUSTE-RENOIR35 min sched.
LORRAIN/des FLEURS35 min sched.
LORRAIN/des POMMETIERS37 min sched.
LORRAIN/JEAN-MARC37 min sched.
LORRAIN/CROTEAU38 min sched.
LORRAIN/THÉRÈSE39 min sched.
de CHAMBORD/de ROBERVAL40 min sched.
de SAINTE-MONIQUE/DE CHAMBORD41 min sched.
SAINT-THOMAS/de SAINTE-MONIQUE42 min sched.
SAINT-THOMAS/d'ARVIDA0 min
SAINT-THOMAS/d'ALMA0 min
SAINT-THOMAS/ELZÉAR1 min
ELZÉAR/IRÈNE2 min
ELZÉAR/de CHAMBORD3 min
des AFFAIRES/LABROSSE6 min
des AFFAIRES/des ENTREPRISES7 min
des AFFAIRES/LABROSSE9 min
LABROSSE/DAVIDSON10 min
LABROSSE/A.-GIBEAULT11 min
LABROSSE/DOCTEUR J.-COUSINEAU12 min
LABROSSE/de CANDIAC13 min
LABROSSE/MARQUETTE14 min
LABROSSE/SAINT-RENÉ EST14 min
Terminus Labrosse15 min

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 2026年10月29日 – 2026年11月4日

Scheduled trips with cancellation notices

—

No retained notice returned; this does not prove zero cancellations.

Trips needing investigation

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

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

64 with position · 2 to investigate · 19 excluded · 85 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 2026年11月5日下午6:21.

Coverage, exclusions and sources

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

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

Published position coverage: 64 / 85 (75.3%). This is not a delivered-service rate. 7 service days in this source.

Timetables retained before the service day: 7 / 7 requested days · 0 missing days.

Historical calculation: 2026年11月5日下午5:48

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

95.5%

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

Predictions in the source: 5,503
Weekdays with evidence: 17
Evidence window: 2026年10月7日 – 2026年11月4日

The hours we have evidence for

5時100% · 165 predictions · 8 days
6時99% · 163 predictions · 8 days
7時91% · 279 predictions · 7 days
8時96% · 417 predictions · 8 days
9時82% · 34 predictions · 7 days
12時95% · 271 predictions · 9 days
13時97% · 204 predictions · 8 days
14時90% · 30 predictions · 5 days
15時95% · 392 predictions · 9 days
16時94% · 319 predictions · 9 days
17時94% · 314 predictions · 9 days
18時96% · 262 predictions · 8 days
19時96% · 158 predictions · 8 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: 2026年11月5日

6 partial-capture days not counted.

What about time of day?

13 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

巴士扎堆到站

Last 28 days, 2026年10月8日 to 2026年11月4日: 21 days counted.

2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: 2026年10月8日, 2026年10月12日.

數值與說明

No bunched buses were measured on this route in the last 28 days (1,352 pairs checked at stops).

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

巴士扎堆到站
時段	已檢查的配對	擠成一團	間隔過長
早上繁忙時段(上午 6 時至 9 時)	477	0% (0)	0% (0)
中午(上午 9 時至下午 3 時)	46	0% (0)	0% (0)
下午繁忙時段(下午3時至6時)	829	0% (0)	0% (0)

此數據如何計算 →How we got this number每條路線的車輛擠在一起和慢速路段 →

這條路線最慢的路段

Slowest: STATION LORRAIN to LORRAIN/des FLEURS, 7.5 km/h actual against 19.8 km/h planned.

這條路線最慢的路段
起點	目的地	距離	計劃速度	實際速度	已量測的行程	緩慢班次
STATION LORRAIN	LORRAIN/des FLEURS	1.2 km	19.8 km/h	7.5 km/h	114	70%
Quai local LABROSSE #6	des AFFAIRES/des ENTREPRISES	3.4 km	24.2 km/h	12.3 km/h	57	65%
LORRAIN/SAINT-RENÉ EST	STATION LORRAIN arrêt d'arrivée	400 m	13.1 km/h	13.3 km/h	54	2%
des AFFAIRES/des ENTREPRISES	Terminus Labrosse	3.4 km	23.3 km/h	23.6 km/h	100	1%
LORRAIN/THÉRÈSE	des AFFAIRES/des ENTREPRISES	4.8 km	24.5 km/h	25.7 km/h	113	0%
des AFFAIRES/des ENTREPRISES	LORRAIN/SAINT-RENÉ EST	8 km	25.8 km/h	27.6 km/h	55	0%
LORRAIN/des FLEURS	LORRAIN/THÉRÈSE	2.4 km	31.6 km/h	33.9 km/h	116	1%

慢速行程是指所需時間至少為計畫時間的 1.5 倍。

此數據如何計算 →

此路線的取消班次

這些詞的意思 →

6 partial-capture days not counted.

過去四週內,這條路線沒有計入的取消班次。我們無法核實的通知會列在下方。

Did not come (no bus seen, no notice), last 7 days: 2 of 66 trips we could check.

此路線通常何時較擁擠

根據 STO 巴士回報的載客量，涵蓋過去八週。如果有讀數的班次中，至少有一半達到站立或更擠，該時段就會標示為通常擁擠。

過去八週內，沒有任何時段通常很擁擠。

此路線通常何時較擁擠	平日	星期六	逢星期日
上午6點前	通常有座位0% of 32 trips	讀數不足	讀數不足
上午 6 時至 9 時	通常有座位0% of 188 trips	讀數不足	讀數不足
上午 9 時至下午 3 時	通常有座位0.7% of 143 trips	讀數不足	讀數不足
下午 3 時至 6 時	通常有座位3.3% of 214 trips	讀數不足	讀數不足
晚上 6 時至 10 時	通常有座位1.7% of 58 trips	讀數不足	讀數不足
晚上 10 點後	讀數不足	讀數不足	讀數不足

Based on 56 computed days.

來源：STO 公開即時車輛資料中的載客狀態。STO 根據每輛巴士的載重感應器設定此狀態（有座位：滿載率低於 60%，有站位：低於 90%，已滿：高於 90%）。
每個班次在每個時段只計算一次，以其回報的最高載客量為準。
我們不採用空車的回報，因為舊紀錄無法分辨是空車，還是車上沒有感應器。
某個時段至少要有 12 個行程，且分布在至少 4 個不同的日子，才會顯示資料。公眾假期按當天是星期幾來計算。

開啟附日期的預測分析

結論

What this route needs

95% of predictions are within five minutes of the timetable in a typical sampled hour; the lowest sampled hour is 82%.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 13 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, 165 predictions, typically 0.2 min late
06:00: 98.8% of final predictions within five minutes of the timetable, 163 predictions, typically 1.7 min late
07:00: 91.4% of final predictions within five minutes of the timetable, 279 predictions, typically 3 min late
08:00: 95.9% of final predictions within five minutes of the timetable, 417 predictions, typically 1.2 min late
09:00: 82.4% of final predictions within five minutes of the timetable, 34 predictions, typically 0.8 min late
10:00: not enough data
11:00: not enough data
12:00: 95.2% of final predictions within five minutes of the timetable, 271 predictions, typically 0.2 min late
13:00: 96.6% of final predictions within five minutes of the timetable, 204 predictions, typically 0.5 min late
14:00: 90% of final predictions within five minutes of the timetable, 30 predictions, typically 0.3 min early
15:00: 94.6% of final predictions within five minutes of the timetable, 392 predictions, typically 0.1 min early
16:00: 93.7% of final predictions within five minutes of the timetable, 319 predictions, typically 0.5 min late
17:00: 94.3% of final predictions within five minutes of the timetable, 314 predictions, typically 0.2 min early
18:00: 95.8% of final predictions within five minutes of the timetable, 262 predictions, typically 0.9 min late
19:00: 95.6% of final predictions within five minutes of the timetable, 158 predictions, typically 1.4 min late
20:00: not enough data
21:00: not enough data
22:00: not enough data
23:00: not enough data

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	時間	已測量	Scenario or next investigation
StrengthPredictions consistently close to timetable	05:00, 06:00, 07:00, 08:00, 09:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00	95%	Keep what works

Measurements

Predictions consistently close to timetable · 05:00, 06:00, 07:00, 08:00, 09:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00: Measured arrivals 3,008; Hours measured 13; Worst hour on time 82.4%; Median hour on time 95.2%

開啟歷史紀錄、可靠度與路線分析

路線檢查

How route 79 has been running

這是我們所知內容的簡短摘要。如果無法回答某個問題，我們會說明。

重點結論

在這個有日期的樣本中，業者的預測通常與時刻表接近。

96 in 100 eligible predictions were within 5 minutes of the timetable · 5,503 predictions checked

預測樣本數: 樣本較大

Based on 5,503 eligible provider predictions over 17 measured days, from 2026年10月7日 to 2026年11月4日.

Updated 2026年11月5日下午5:32

預測在哪些地點和時間多次出現差異？

這些是預測與班表之間反覆出現的差異，並非獨立測得的服務失誤。它們使用與上方結果相同的合格預測，但按站點而非時段分組，因此兩份清單不一定逐行相符。

目前還沒有重複出現的預測差異時段達到證據門檻。

目前沒有與此路線相符的官方通知。

各站的預測差異

STATION LORRAIN
46 in 100 eligible predictions differed from the timetable by more than 5 minutes (145 predictions over 18 days).
開啟此站牌
Quai local LABROSSE #6
46 in 100 eligible predictions differed from the timetable by more than 5 minutes (81 predictions over 16 days).
開啟此站牌

這些是各路線業者提供的預測,並與時刻表比較。它們顯示某個地點和時段反覆出現的預測差異,不是實測的到站時間,也不能說明原因。

查看每個班次和日期

打開一個時段,即可查看每個服務日、預定班次、資料空檔、已觀察到的公開車輛編號,以及此摘要背後的確切數字。

乘客想知道的事

現在有任何班次被取消嗎?: 0 of 1檢查未來 4 小時內從路線端點出發的行程。這不是歷史取消率。
檢查資料缺口後，可能的未到班次？: 2 of 66 checked trips need a closer look2 of 66 trips with enough public-feed evidence had no matching position over 7 days. 19 of 85 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
服務提供者的預測與時刻表有何不同?: At the 95th percentile, the predicted difference was 4.6 min (positive means later; negative means earlier)96 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
營運商的預測意味著要等多久？: 目前沒有任何路線層級的結果達到證據門檻。這不代表沒有出現服務空檔。

時刻表變更檢查

已發布的時刻表：變更前與變更後

此頁面比較目前保留的官方時刻表與先前保留的版本。時刻表變更只說明原本的計劃,不能證明某個班次已經行駛。

Current published schedule began 2026年11月3日

從每份已發布時刻表中選出的服務日

我們會檢查新時刻表開始後的第一個星期一，以及一週前的星期一。所有數字都來自下列保留的官方 GTFS 版本。

所選日期中，至少有一個日期有新增或取消的特定日期服務。請將此視為假日或特別服務的情況，而不是平日一般的服務增加。

變更前

已核對的服務日期: 2026年11月2日

時刻表班次: 17
不同的預定停靠站數量: 56
已公布的不同路線: 3
已公布的服務時段: 05:38–19:22

Operator calendar-date records: 1 added · 0 removed

資料串流指紋: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

新時刻表

已核對的服務日期: 2026年11月9日

時刻表班次: 17
不同的預定停靠站數量: 56
已公布的不同路線: 3
已公布的服務時段: 05:38–19:22

Operator calendar-date records: 1 added · 0 removed

資料串流指紋: 64b436d79ab51a76 · 623ad8b0-ad29-4d70-b8e6-e594a396233e

變更後，服務有改善嗎？

我們會比較變更前後各 14 天已確認的到站紀錄。只有在變更前後兩段時間都至少有 7 個服務日和 200 次到站紀錄時，我們才會公布比較結果。

Still collecting: before has 2,949 arrivals over 10 days; after has 411 arrivals over 2 days. No improvement or decline is claimed yet.

校驗碼可讓任何人核對，是哪一份留存的時刻表產生這些數量。數量有變動，並不能說明原因、取消、營運單位的決定或對乘客的影響。

如何評估這條路線: 每站停靠的一般路線

我們把每個預定到達班次的最後一筆合資格業者預測，與官方時刻表比較。這些不是獨立量測的到達時間。結果至少需要 200 筆合資格預測。這裡採用乘客角度的目標：誤差在 5 分鐘內。

這些數據無法證明的事

公開資料來源沒有提供可靠的乘客人數，也沒有提供漏載乘客的事件。缺少車輛位置，本身並不能證明班次取消、未出車、中途折返或其原因。

查看定義、門檻和數據順序

官方即時資料：明確的取消班次、跳過的站點及目前有效的通知。
配對觀測資料:與官方時刻表相連的車輛位置和已確定的預測。
官方時刻表:原本的計畫,與實際觀察到的情況分開顯示。
乘客和營運單位的回報:這些是關於路線、時間和地點的線索,值得調查,但本身不是數字證明。

暫定結果，已公布的數據

預測與時刻表相比如何?

每個小時都會把某班預定到站的最後一次合格業者預測與時刻表比較。「5 分鐘內」是指預測與時刻表的差距，不是實際量到的到站時間，也不能證明巴士有行駛。

佐證期間: 2026年10月7日 to 2026年11月4日

與時刻表相差 5 分鐘內: 95.5%
已查核的合格預測: 5,503
有資料的平日: 17
第95百分位預測延誤: 4.6 min late

Patterns by hour (13)

Patterns by hour (13)
小時	準點	中位數	第 95 百分位	證據
05:00	100.0%	0.2 min late	1.6 min late	165 · 8 days
06:00	98.8%	1.7 min late	3.6 min late	163 · 8 days
07:00	91.4%	3 min late	5.2 min late	279 · 7 days
08:00	95.9%	1.2 min late	4.8 min late	417 · 8 days
09:00	82.4%	0.8 min late	6.8 min late	34 · 7 days
12:00	95.2%	0.2 min late	4.8 min late	271 · 9 days
13:00	96.6%	0.5 min late	4.6 min late	204 · 8 days
14:00	90.0%	0.3 min early	0.7 min late	30 · 5 days
15:00	94.6%	0.1 min early	4.7 min late	392 · 9 days
16:00	93.7%	0.5 min late	3.8 min late	319 · 9 days
17:00	94.3%	0.2 min early	5.1 min late	314 · 9 days
18:00	95.8%	0.9 min late	4.2 min late	262 · 8 days
19:00	95.6%	1.4 min late	4.8 min late	158 · 8 days

目前在至少三個服務日中，尚未確認有低於 70% 的重複模式。

有排定班次的巴士，但沒有即時觀察記錄

64 / 85 scheduled trips published at least one position across 5 service days (75.3%).

06:002 / 5 trips without a position60.0%
07:004 / 10 trips without a position60.0%
08:003 / 10 trips without a position70.0%
12:003 / 10 trips without a position70.0%
05:001 / 5 trips without a position80.0%
13:001 / 5 trips without a position80.0%

這不是已確認的未發車。 找不到車輛位置，可能是班次取消或漏班，也可能是班次編號未指派，或是營運單位的資料來源出現缺口。Otranspo 公布這項缺口，因為這對乘客很重要，同時也會如實處理，不作過度推論。

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. 來源與限制.

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 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

November 4, 2026 · 17 trips in the retained timetable · retained notices; capture coverage unverified

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

05:38– 06:05
Trip sto:63296824Vehicle position matchedFirst / last feed position: 5:46 a.m. EST / 6:02 a.m. EST; not actual start or end times.
06:38– 07:06
Trip sto:63296826Vehicle position matchedFirst / last feed position: 6:39 a.m. EST / 7:07 a.m. EST; not actual start or end times.
07:09– 07:40
Trip sto:63296827Vehicle position matchedFirst / last feed position: 6:50 a.m. EST / 7:36 a.m. EST; not actual start or end times.
07:42– 08:13
Trip sto:63296823Vehicle position matchedFirst / last feed position: 7:28 a.m. EST / 8:10 a.m. EST; not actual start or end times.
08:08– 08:36
Trip sto:63296825Vehicle position matchedFirst / last feed position: 7:46 a.m. EST / 8:35 a.m. EST; not actual start or end times.
08:38– 09:05
Trip sto:63296828Vehicle position matchedFirst / last feed position: 8:15 a.m. EST / 9:01 a.m. EST; not actual start or end times.
12:10– 12:17
Trip sto:63296814Insufficient coverage or identity; outcome unknown
12:24– 12:50
Trip sto:63296817Vehicle position matchedFirst / last feed position: 12:51 p.m. EST / 1:04 p.m. EST; not actual start or end times.
13:24– 13:50
Trip sto:63296818Insufficient coverage or identity; outcome unknown
14:54– 15:25
Trip sto:63296815Vehicle position matchedFirst / last feed position: 2:46 p.m. EST / 2:46 p.m. EST; not actual start or end times.
15:24– 15:55
Trip sto:63296816Insufficient coverage or identity; outcome unknown
15:56– 16:27
Trip sto:63296819Vehicle position matchedFirst / last feed position: 4:21 p.m. EST / 4:27 p.m. EST; not actual start or end times.

· Open all evidence for this day