No 52 trips cancelled now · 3 did not run in 11月Cancellations →

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.

STO 路線 52: Des Cèdre/Rivermead/Vanier

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

KATIMAVIK/DU PLATEAU18 min sched.
de SÉTO/KATIMAVIK19 min sched.
VANIER/ATTIKAMEKS22 min sched.
MCCONNELL/MORLEY-WALTERS23 min sched.
MCCONNELL/CASTELBEAU23 min sched.
MCCONNELL/JEAN-DE LA FONTAINE24 min sched.
MCCONNELL/des MANOIRS24 min sched.
RIVERMEAD/ÉMILE-ZOLA25 min sched.
RIVERMEAD/JEAN-DE LA FONTAINE26 min sched.
PARC-O-BUS RIVERMEAD27 min sched.
chemin d'AYLMER/de l'HIPPODROME30 min sched.
chemin d'AYLMER/MORLEY-WALTERS31 min sched.
VANIER/LYNN32 min sched.
VANIER/CRESCENT32 min sched.
VANIER/des VÉTÉRANS33 min sched.
VANIER/CRESCENT33 min sched.
VANIER/CALVADOS34 min sched.
VANIER/de LUCERNE34 min sched.
CÔTÉ/LUCERNE35 min sched.
CÔTÉ/DESCHÊNES35 min sched.
CÔTÉ/LAMOUREUX36 min sched.
LAMOUREUX/VANIER36 min sched.
VANIER/MADAIRE37 min sched.
VANIER/SAINT-MÉDARD37 min sched.
de LUCERNE/GARDEN38 min sched.
de LUCERNE/VICTOR-BEAUDRY39 min sched.
de LUCERNE/FRASER40 min sched.
de LUCERNE/EASTERN41 min sched.
de LUCERNE/RIESLING41 min sched.
de LUCERNE/ÉLIZABETH43 min sched.
FRANK-ROBINSON/CENTRE WESTERN QUÉBEC44 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 DRAVEURS49 min sched.
du VALLON/du CAVEAU50 min sched.
du CAVEAU/SAMUEL-EDEY51 min sched.
SAMUEL-EDEY/des PAYSANS52 min sched.
SAMUEL-EDEY/MCCONNELL52 min sched.
des ALLUMETTIÈRES/SAMUEL-EDEY53 min sched.
WILFRID-LAVIGNE/des ALLUMETTIÈRES55 min sched.
WILFRID-LAVIGNE/des PINACÉES56 min sched.
WILFRID-LAVIGNE/du BOIS-FRANC56 min sched.
WILFRID-LAVIGNE/des THUYAS57 min sched.
WILFRID-LAVIGNE/MAURICE-DUPLESSIS58 min sched.
WILFRID-LAVIGNE/LYSE-DANIELS58 min sched.
WILFRID-LAVIGNE/KLOCK59 min sched.
du RATON-LAVEUR/de la MARMOTTE1 min sched.
du RATON-LAVEUR/du LOUP-GRIS2 min sched.
du RATON-LAVEUR/FRONT3 min sched.
FRONT/du RENARD3 min sched.
FRONT/du MARCHÉ4 min sched.
FRONT/du VERGER4 min sched.
FRONT/des ALLUMETTIÈRES5 min sched.
des ALLUMETTIÈRES/FRONT6 min sched.
PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée10 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: 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: 2026年11月4日下午6:50.

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: 2026年11月4日下午5:38

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: 2026年10月6日 – 2026年11月3日

The hours we have evidence for

5時100% · 41 predictions · 6 days
6時68% · 951 predictions · 10 days
7時56% · 850 predictions · 9 days
8時54% · 920 predictions · 10 days
9時54% · 1,055 predictions · 11 days
10時65% · 1,147 predictions · 11 days
11時51% · 1,224 predictions · 12 days
12時54% · 1,294 predictions · 12 days
13時62% · 1,345 predictions · 12 days
14時57% · 1,209 predictions · 13 days
15時52% · 1,249 predictions · 12 days
16時46% · 1,109 predictions · 12 days
17時47% · 1,117 predictions · 12 days
18時46% · 1,079 predictions · 11 days
19時45% · 1,205 predictions · 11 days
20時43% · 1,076 predictions · 10 days
21時65% · 1,126 predictions · 10 days
22時80% · 1,183 predictions · 10 days
23時72% · 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: 2026年11月4日

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

巴士扎堆到站

Last 28 days, 2026年10月7日 to 2026年11月3日: 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日.

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

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

這條路線最慢的路段

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

這條路線最慢的路段
起點	目的地	距離	計劃速度	實際速度	已量測的行程	緩慢班次
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%

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

此數據如何計算 →

此路線的取消班次

這些詞的意思 →

6 partial-capture days not counted.

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

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

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

此路線通常何時較擁擠

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

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

此路線通常何時較擁擠	平日	星期六	逢星期日
上午6點前	通常有座位0% of 58 trips	讀數不足	讀數不足
上午 6 時至 9 時	通常有座位0% of 236 trips	通常有座位0% of 51 trips	通常有座位0% of 48 trips
上午 9 時至下午 3 時	通常有座位0% of 474 trips	通常有座位0% of 102 trips	通常有座位0% of 101 trips
下午 3 時至 6 時	通常有座位1.3% of 226 trips	通常有座位0% of 61 trips	通常有座位0% of 67 trips
晚上 6 時至 10 時	通常有座位0.6% of 361 trips	通常有座位0% of 75 trips	通常有座位0% of 65 trips
晚上 10 點後	通常有座位0% of 126 trips	通常有座位2.2% of 46 trips	通常有座位0% of 34 trips

Based on 56 computed days.

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

開啟附日期的預測分析

結論

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 4.1 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	時間	已測量	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

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

路線檢查

How route 52 has been running

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

重點結論

在此有日期的樣本中，營運單位的預測常與時刻表相差很大。

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

預測樣本數: 樣本較大

Based on 38,425 eligible provider predictions over 22 measured days, from 2026年10月6日 to 2026年11月3日.

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

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

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

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

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

各站的預測差異

de la COLLINE/des EXPLORATEURS
84 in 100 eligible predictions differed from the timetable by more than 5 minutes (344 predictions over 24 days).
開啟此站牌
de LUCERNE/EASTERN
83 in 100 eligible predictions differed from the timetable by more than 5 minutes (346 predictions over 24 days).
開啟此站牌
de LUCERNE/RIESLING
83 in 100 eligible predictions differed from the timetable by more than 5 minutes (349 predictions over 24 days).
開啟此站牌
de la COLLINE/du VALLON
81 in 100 eligible predictions differed from the timetable by more than 5 minutes (349 predictions over 24 days).
開啟此站牌

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

查看每個班次和日期

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

乘客想知道的事

現在有任何班次被取消嗎?: 0 of 8檢查未來 4 小時內從路線端點出發的行程。這不是歷史取消率。
檢查資料缺口後，可能的未到班次？: 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.
服務提供者的預測與時刻表有何不同?: 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.
營運商的預測意味著要等多久？: 目前沒有任何路線層級的結果達到證據門檻。這不代表沒有出現服務空檔。

時刻表變更檢查

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

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

Current published schedule began 2026年11月2日

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

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

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

變更前

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

時刻表班次: 0
不同的預定停靠站數量: 0
已公布的不同路線: 0
已公布的服務時段: —–—

資料串流指紋: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

新時刻表

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

時刻表班次: 36
不同的預定停靠站數量: 122
已公布的不同路線: 2
已公布的服務時段: 05:53–23:45

Operator calendar-date records: 1 added · 0 removed

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

變更後，服務有改善嗎？

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

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.

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

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

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

這些數據無法證明的事

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

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

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

暫定結果，已公布的數據

預測與時刻表相比如何?

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

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

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

Patterns by hour (20)

Patterns by hour (20)
小時	準點	中位數	第 95 百分位	證據
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.

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

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%

這不是已確認的未發車。 找不到車輛位置，可能是班次取消或漏班，也可能是班次編號未指派，或是營運單位的資料來源出現缺口。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 · 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

STO 路線 52: Des Cèdre/Rivermead/Vanier

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