No 49 trips cancelled now · 1 did not run in 11月Cancellations →

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

路線 49: Elmvale ⇄ Hurdman

每 30 至 120 分鐘一班

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

HURDMAN D15 min sched.
LYCÉE CLAUDEL 1A (B)16 min sched.
SMYTH 1A (B)17 min sched.
RIVERSIDE 1A (B)17 min sched.
PLEASANT PARK / CABOT18 min sched.
PLEASANT PARK 3A18 min sched.
PLEASANT PARK / CAVENDISH19 min sched.
PLEASANT PARK / ALTA VISTA19 min sched.
PLEASANT PARK / AD. 32819 min sched.
PLEASANT PARK / FAIRBANKS20 min sched.
PLEASANT PARK / AD. 45220 min sched.
PLEASANT PARK / AD. 50420 min sched.
PLEASANT PARK / LYNDA21 min sched.
PLEASANT PARK / NORWAY21 min sched.
PLEASANT PARK / DORVAL22 min sched.
PLEASANT PARK / HAIG23 min sched.
PLEASANT PARK / CAMROSE24 min sched.
PLEASANT PARK / ARCH24 min sched.
PLEASANT PARK / SAUNDERSON25 min sched.
ST-LAURENT / AD. 197127 min sched.
ELMVALE B29 min sched.

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 2026年10月28日 – 2026年11月3日

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: 5 trips with qualifying later matching vehicle observations. Trips with any notice: 6.

Trips needing investigation

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

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

212 with position · 2 to investigate · 0 excluded · 214 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 212 / 214 (99.1%). This is not a delivered-service rate. 7 service days in this source.

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

Historical calculation: 2026年11月4日下午12:20

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.5%

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

Predictions in the source: 16,440
Weekdays with evidence: 19
Evidence window: 2026年10月6日 – 2026年11月3日

The hours we have evidence for

6時96% · 420 predictions · 10 days
7時81% · 420 predictions · 10 days
8時70% · 1,006 predictions · 12 days
9時79% · 409 predictions · 14 days
10時96% · 567 predictions · 14 days
12時94% · 574 predictions · 14 days
14時89% · 720 predictions · 14 days
15時78% · 887 predictions · 14 days
16時69% · 964 predictions · 14 days
17時73% · 1,015 predictions · 14 days
18時58% · 785 predictions · 12 days
19時88% · 393 predictions · 10 days
20時87% · 31 predictions · 10 days
22時85% · 200 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: 2026年11月4日

2 partial-capture days not counted.

What about time of day?

14 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月7日 to 2026年11月3日: 26 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月15日.

數值與說明

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

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

巴士扎堆到站
時段	已檢查的配對	擠成一團	間隔過長
早上繁忙時段(上午 6 時至 9 時)	2,154	0% (0)	0% (0)
中午(上午 9 時至下午 3 時)	335	0% (0)	0% (0)
下午繁忙時段(下午3時至6時)	2,207	0% (0)	0% (0)
晚間（下午 6 時至 10 時）	204	0% (0)	0% (0)

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

這條路線最慢的路段

Slowest: ELMVALE A to PLEASANT PARK / NORWAY, 25.3 km/h actual against 31 km/h planned.

這條路線最慢的路段
起點	目的地	距離	計劃速度	實際速度	已量測的行程	緩慢班次
ELMVALE A	PLEASANT PARK / NORWAY	2.2 km	31 km/h	25.3 km/h	395	30%
HURDMAN D	PLEASANT PARK / NORWAY	4.4 km	35.7 km/h	26.6 km/h	356	31%

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

此數據如何計算 →

此路線的取消班次

這些詞的意思 →

2 partial-capture days not counted.

4 scheduled trips with counted cancellation notices from 10月7日週三 to 11月3日週二.

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

取消班次最多的時段: 下午5時 (2), 下午4時 (1), 下午6時 (1)

What this route needs

Median provider predictions are 3.3 to 4.4 min later than the timetable in 4 hours of the day.

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

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

Only 99% of scheduled trips were seen; the rest are not counted as missed.

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, 16 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: not enough data
06:00: 96% of final predictions within five minutes of the timetable, 420 predictions, typically 1.2 min late
07:00: 81% of final predictions within five minutes of the timetable, 420 predictions, typically 2.8 min late
08:00: 70.4% of final predictions within five minutes of the timetable, 1,006 predictions, typically 3.7 min late
09:00: 78.5% of final predictions within five minutes of the timetable, 409 predictions, typically 2.9 min late
10:00: 95.9% of final predictions within five minutes of the timetable, 567 predictions, typically 1.5 min late
11:00: not enough data
12:00: 94.3% of final predictions within five minutes of the timetable, 574 predictions, typically 1.9 min late
13:00: not enough data
14:00: 89.3% of final predictions within five minutes of the timetable, 720 predictions, typically 1.8 min late
15:00: 77.5% of final predictions within five minutes of the timetable, 887 predictions, typically 2.5 min late
16:00: 68.5% of final predictions within five minutes of the timetable, 964 predictions, typically 3.6 min late
17:00: 73.1% of final predictions within five minutes of the timetable, 1,015 predictions, typically 2.6 min late
18:00: 57.6% of final predictions within five minutes of the timetable, 785 predictions, typically 4.4 min late
19:00: 88% of final predictions within five minutes of the timetable, 393 predictions, typically 2.3 min late
20:00: 87.1% of final predictions within five minutes of the timetable, 31 predictions, typically 2.2 min late
21:00: not enough data
22:00: 84.5% of final predictions within five minutes of the timetable, 200 predictions, typically 3.3 min late
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
ProblemPredictions later than timetable	08:00 · 16:00 · 18:00 · 22:00	3.7 min late … 3.3 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	18:00	58%	Operations, not the timetable
CaveatCoverage gap	All measured hours	99%	More observation, not a service change

Measurements

Predictions later than timetable · 08:00: Measured arrivals 1,006; Hours affected 1; Spread 9.5 min; Median delay 3.7 min; Suggested running time change 3.7 min
Predictions later than timetable · 16:00: Measured arrivals 964; Hours affected 1; Spread 9.6 min; Median delay 3.6 min; Suggested running time change 3.6 min
Predictions later than timetable · 18:00: Measured arrivals 785; Hours affected 1; Spread 6.1 min; Median delay 4.4 min; Suggested running time change 4.4 min
Predictions later than timetable · 22:00: Measured arrivals 200; Hours affected 1; Spread 2.2 min; Median delay 3.3 min; Suggested running time change 3.3 min
One hour has a lower prediction match · 18:00: 小時 18:00; 準點 57.6%; Measured arrivals 785; Shortfall 25.2 pts; Route median on time 82.8%
Coverage gap · All measured hours: 目標 99.5%; Trips with a matching position 99.1%; 服務日 5; Trips with a matching position 212; 時刻表班次 214

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

路線檢查

How route 49 has been running

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

重點結論

營運機構的預測常與時刻表不同；實際到站時間沒有獨立量測。

78 in 100 eligible predictions were within 5 minutes of the timetable · 16,440 predictions checked

預測樣本數: 樣本較大

Based on 16,440 eligible provider predictions over 27 measured days, from 2026年10月6日 to 2026年11月3日.

Updated 2026年11月4日下午12:32

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

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

18時–19時: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (785 predictions over 12 days).
16時–17時: 32 in 100 eligible predictions differed from the timetable by more than 5 minutes (964 predictions over 14 days).

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

各站的預測差異

PLEASANT PARK / NORWAY
49 in 100 eligible predictions differed from the timetable by more than 5 minutes (418 predictions over 30 days).
開啟此站牌
PLEASANT PARK / LYNDA
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (418 predictions over 30 days).
開啟此站牌
PLEASANT PARK / AD. 504
46 in 100 eligible predictions differed from the timetable by more than 5 minutes (418 predictions over 30 days).
開啟此站牌
PLEASANT PARK / AD. 452
45 in 100 eligible predictions differed from the timetable by more than 5 minutes (418 predictions over 30 days).
開啟此站牌

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

查看每個班次和日期

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

乘客想知道的事

現在有任何班次被取消嗎?: 0 of 12檢查未來 4 小時內從路線端點出發的行程。這不是歷史取消率。
檢查資料缺口後，可能的未到班次？: 2 of 214 checked trips need a closer look2 of 214 trips with enough public-feed evidence had no matching position over 7 days. 0 of 214 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 11.2 min (positive means later; negative means earlier)78 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
營運商的預測意味著要等多久？: 目前沒有任何路線層級的結果達到證據門檻。這不代表沒有出現服務空檔。

時刻表變更檢查

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

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

Current published schedule began 2026年10月30日

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

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

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

變更前

已核對的服務日期: 2026年10月26日

時刻表班次: 35
不同的預定停靠站數量: 43
已公布的不同路線: 2
已公布的服務時段: 06:10–22:33

Operator calendar-date records: 0 added · 2 removed

資料串流指紋: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

新時刻表

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

時刻表班次: 35
不同的預定停靠站數量: 43
已公布的不同路線: 2
已公布的服務時段: 06:10–22:33

Operator calendar-date records: 0 added · 2 removed

資料串流指紋: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

變更後，服務有改善嗎？

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

Still collecting: before has 8,709 arrivals over 14 days; after has 2,948 arrivals over 5 days. No improvement or decline is claimed yet.

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

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

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

這些數據無法證明的事

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

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

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

暫定結果，已公布的數據

預測與時刻表相比如何?

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

佐證期間: 2026年10月6日 to 2026年11月3日

與時刻表相差 5 分鐘內: 77.5%
已查核的合格預測: 16,440
有資料的平日: 19
第95百分位預測延誤: 11.2 min late

Patterns by hour (16)

Patterns by hour (16)
小時	準點	中位數	第 95 百分位	證據
06:00	96.0%	1.2 min late	4.5 min late	420 · 10 days
07:00	81.0%	2.8 min late	7.2 min late	420 · 10 days
08:00	70.4%	3.7 min late	13.2 min late	1,006 · 12 days
09:00	78.5%	2.9 min late	12.6 min late	409 · 14 days
10:00	95.9%	1.5 min late	4.6 min late	567 · 14 days
11:00	100.0%	0.2 min early	1.1 min late	164 · 4 days
12:00	94.3%	1.9 min late	5.4 min late	574 · 14 days
13:00	86.6%	0.9 min late	12.6 min late	164 · 4 days
14:00	89.3%	1.8 min late	5.8 min late	720 · 14 days
15:00	77.5%	2.5 min late	9.4 min late	887 · 14 days
16:00	68.5%	3.6 min late	13.2 min late	964 · 14 days
17:00	73.1%	2.6 min late	10.5 min late	1,015 · 14 days
18:00	57.6%	4.4 min late	10.5 min late	785 · 12 days
19:00	88.0%	2.3 min late	6.6 min late	393 · 10 days
20:00	87.1%	2.2 min late	5.5 min late	31 · 10 days
22:00	84.5%	3.3 min late	5.5 min late	200 · 10 days

2 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

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

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

18:001 / 17 trips without a position94.1%
17:001 / 24 trips without a position95.8%
06:000 / 10 trips without a position100.0%
07:000 / 10 trips without a position100.0%
08:000 / 26 trips without a position100.0%
09:000 / 9 trips without a position100.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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 35 trips in the retained timetable · retained notices; capture coverage unverified

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

06:10– 06:24
Trip 36085030Vehicle position matchedFirst / last feed position: 5:58 a.m. EST / 6:24 a.m. EST; not actual start or end times.
06:40– 06:54
Trip 5544030Vehicle position matchedFirst / last feed position: 6:31 a.m. EST / 6:58 a.m. EST; not actual start or end times.
07:10– 07:24
Trip 20693030Vehicle position matchedFirst / last feed position: 7:11 a.m. EST / 7:31 a.m. EST; not actual start or end times.
07:40– 07:56
Trip 9409030Vehicle position matchedFirst / last feed position: 6:56 a.m. EST / 8:00 a.m. EST; not actual start or end times.
08:00– 08:16
Trip 14137030Vehicle position matchedFirst / last feed position: 8:02 a.m. EST / 8:22 a.m. EST; not actual start or end times.
08:02– 08:16
Trip 32423030Vehicle position matchedFirst / last feed position: 8:15 a.m. EST / 8:31 a.m. EST; not actual start or end times.
08:21– 08:37
Trip 31859030Vehicle position matchedFirst / last feed position: 8:21 a.m. EST / 8:39 a.m. EST; not actual start or end times.
08:30– 08:44
Trip 1544030Vehicle position matchedFirst / last feed position: 8:38 a.m. EST / 9:17 a.m. EST; not actual start or end times.
08:51– 09:06
Trip 31757030Vehicle position matchedFirst / last feed position: 8:06 a.m. EST / 9:09 a.m. EST; not actual start or end times.
09:02– 09:16
Trip 9562030Vehicle position matchedFirst / last feed position: 9:13 a.m. EST / 9:27 a.m. EST; not actual start or end times.
10:02– 10:16
Trip 27657030Vehicle position matchedFirst / last feed position: 10:03 a.m. EST / 10:16 a.m. EST; not actual start or end times.
10:24– 10:38
Trip 5292030Vehicle position matchedFirst / last feed position: 10:24 a.m. EST / 10:41 a.m. EST; not actual start or end times.

· Open all evidence for this day

路線 49: Elmvale ⇄ Hurdman

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

What does the evidence show?

The hours we have evidence for

What about time of day?

巴士扎堆到站

這條路線最慢的路段

此路線的取消班次

最新取消的班次

What this route needs

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

查看每個班次和日期

乘客想知道的事

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

變更前

新時刻表

變更後，服務有改善嗎？

預測與時刻表相比如何?

Trips scheduled that day

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

What does the evidence show?

The hours we have evidence for

What about time of day?

巴士扎堆到站

這條路線最慢的路段

此路線的取消班次

最新取消的班次

What this route needs

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

查看每個班次和日期

乘客想知道的事

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

變更前

新時刻表

變更後，服務有改善嗎？

預測與時刻表相比如何?

Trips scheduled that day