跳至主要內容

下一班巴士

回報問題

發生了什麼事
完整報告 不需要帳戶

現在的巴士:準時晚點您

OC Transpo station · 3050

Bayshore

Buses at Bayshore · live30 秒前更新
每 54 分鐘一班 · 然後 53（預定）
11
11Waller · platform A · every 54 to 54 min
尚未測量
現在即時
然後 53（預定）
每 30 分鐘一班 · 然後 30（預定）
58
58Tunney's Pasture · platform A · every 30 to 30 min
尚未測量
現在即時
然後 30（預定）
每 15 至 16 分鐘一班 · 按時刻表,然後 下午2:11
85
85Bayshore · platform B · every 15 to 16 min
尚未測量
下午1:56
按時刻表,然後 下午2:11
每 30 分鐘一班 · 然後 39（預定）
61
61Terry Fox · platform B · every 30 to 30 min
尚未測量
9分鐘即時
然後 39（預定）
每 30 分鐘一班 · 然後 39（預定）
58
58Carling Campus ~ Complexe Carling · platform C · every 30 to 30 min
尚未測量
9分鐘即時
然後 39（預定）
每 15 分鐘一班 · 按時刻表,然後 下午2:14
85
85Lees · platform A · every 15 to 15 min
尚未測量
下午1:59
按時刻表,然後 下午2:14
每 29 分鐘一班 · 按時刻表,然後 下午2:29
81
81Bayshore · platform B · every 29 to 29 min
尚未測量
下午2:00
按時刻表,然後 下午2:29
每 31 分鐘一班 · 然後 46（預定）
81
81Tunney's Pasture · platform A · every 31 to 31 min
尚未測量
15分鐘即時
然後 46（預定）
每 28 分鐘一班 · 按時刻表,然後 下午2:31
11
11Bayshore · platform B · every 28 to 28 min
尚未測量
下午2:03
按時刻表,然後 下午2:31
每 10 至 21 分鐘一班 · 然後 36 · 41（預定）
61
61Tunney's Pasture · platform A · every 10 to 21 min
尚未測量
17分鐘即時
然後 36 · 41（預定）
每 30 分鐘一班 · 然後 27（預定）
57
57Tunney's Pasture · platform A · every 30 to 30 min
尚未測量
17分鐘即時
然後 27（預定）
每 32 分鐘一班 · 然後 55（預定）
61
61Stittsville · platform B · every 32 to 32 min
尚未測量
17分鐘即時
然後 55（預定）
每 30 分鐘一班 · 然後 50（預定）
62
62Stittsville · platform B · every 30 to 30 min
尚未測量
18分鐘即時
然後 50（預定）
每 30 分鐘一班 · 然後 52（預定）
57
57Carling Campus ~ Complexe Carling · platform C · every 30 to 30 min
尚未測量
19分鐘即時
然後 52（預定）
每 33 分鐘一班 · 然後 54（預定）
63
63Innovation · platform B · every 33 to 33 min
尚未測量
21分鐘即時
然後 54（預定）
每 29 分鐘一班 · 按時刻表,然後 下午2:38
88
88Hurdman · platform C · every 29 to 29 min
尚未測量
下午2:09
按時刻表,然後 下午2:38
每 1 至 10 分鐘一班 · 按時刻表,然後 下午2:22
88
88Bayshore · platform B · every 1 to 10 min
尚未測量
下午2:12
按時刻表,然後 下午2:22
62
62Tunney's Pasture
platform A
尚未測量
25分鐘即時
303
303Dunrobin / Carp
platform C
尚未測量
下午2:37
來自時刻表
Entrances and elevators

目前無法確認電梯的狀態。

86.5% 預測與時刻表相差在五分鐘內. 4,019 eligible provider predictions; arrivals not independently measured
原因 →

More at this station

Save, plan, shareSave the station, plan a trip from it, or share it
從這裡規劃
Bike parking hereBike racks, covered · 步行 2 分鐘Bike parking: OpenStreetMap, data as of 2026年6月1日. The walk is an estimate.
Details →
Print this stationA print sheet with the page link at the foot
Station dataDownload the station as JSON or CSV
JSON · CSV
Report a station problemSent to our station log and counted on this page
未啟用 JavaScriptBoards and departures still show without JavaScript

Station details

Step-free route

目前無法確認通知的涵蓋範圍。以下保留的通知，其時間或來源佐證可能未經確認。出行前，請向營運商查詢。

All elevators in the network

Buses from here

Tap a route for live buses and how full they are.

In the station

No published source lists amenities here yet.

表現

服務提供情況 · 證據狀態

Service at BAYSHORE

Cancellations at this station

Local count unavailable

The exact stop-call lookup did not finish within this page’s time budget. No zero, cancellation, or missed call is inferred.

Departure-board snapshot
40 listed departures · 19 live provider predictions

Server snapshot assembled 2026年11月4日 下午1:48; open Departures for a refreshed board. This is not a cancellation count.

Prediction agreement
86.5% 預測與時刻表相差在五分鐘內. 4,019 eligible provider predictions; arrivals not independently measured
此車站的巴士預測可靠度

結論

此車站的巴士預測可靠度

Early evidence: 6 of 20 weekdays with eligible final provider predictions. This updates hourly; more records will make the estimate steadier.

86.5% of final provider predictions within 5 minutes of the timetable, from 4,019 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 72%.

Median predicted difference from the timetable: 57 s 晚點. At the 95th percentile: 8 min 晚點.

這是業者對 OC Transpo 和 STO 車站常規巴士到站的最終預測。實際到站情況未經獨立核實。 快線（200/500）、購物/社區線（300）、活動線（400）和學校線（600）不在計算範圍內，因為每一種都需要針對其用途設計的衡量方式。 STO 的路線也納入計算，並按各自的類別評分：Rapibus 的 100、200、400 和 800 納入計算，而編號 300 以上的 STO 學生班次則排除在外，與 OC Transpo 的 600 系列做法相同。每個營運單位只與自己的服務比較，不會與另一個單位比較。

We use the agency’s last prediction within ten minutes of each scheduled arrival. 6 weekdays with eligible predictions, 2026-10-28 to 2026-11-04. Within five minutes means the final prediction differs from the schedule by no more than five minutes.

Final provider predictions within five minutes of the timetable, by hour, 6 weekdays
  1. 00:00: 90.1% of final predictions within five minutes of the timetable, 71 predictions, typically 0.9 min late
  2. 01:00: 90.2% of final predictions within five minutes of the timetable, 41 predictions, typically 1 min late
  3. 02:00: not enough data
  4. 03:00: not enough data
  5. 04:00: 95.8% of final predictions within five minutes of the timetable, 48 predictions, typically 0.4 min late
  6. 05:00: 91.6% of final predictions within five minutes of the timetable, 107 predictions, typically 0.1 min late
  7. 06:00: 91.1% of final predictions within five minutes of the timetable, 213 predictions, typically 1 min late
  8. 07:00: 88.7% of final predictions within five minutes of the timetable, 266 predictions, typically 1.2 min late
  9. 08:00: 81.2% of final predictions within five minutes of the timetable, 261 predictions, typically 1.2 min late
  10. 09:00: 85.6% of final predictions within five minutes of the timetable, 243 predictions, typically 1 min late
  11. 10:00: 89.1% of final predictions within five minutes of the timetable, 229 predictions, typically 0.5 min late
  12. 11:00: 92.3% of final predictions within five minutes of the timetable, 235 predictions, typically 0.3 min late
  13. 12:00: 89.5% of final predictions within five minutes of the timetable, 220 predictions, typically 0.8 min late
  14. 13:00: 94.1% of final predictions within five minutes of the timetable, 204 predictions, typically 0.7 min late
  15. 14:00: 92.1% of final predictions within five minutes of the timetable, 202 predictions, typically 0.5 min late
  16. 15:00: 82.3% of final predictions within five minutes of the timetable, 220 predictions, typically 1 min late
  17. 16:00: 71.7% of final predictions within five minutes of the timetable, 240 predictions, typically 1.5 min late
  18. 17:00: 75.8% of final predictions within five minutes of the timetable, 223 predictions, typically 1.7 min late
  19. 18:00: 80.7% of final predictions within five minutes of the timetable, 218 predictions, typically 1.3 min late
  20. 19:00: 88% of final predictions within five minutes of the timetable, 167 predictions, typically 1.1 min late
  21. 20:00: 85.5% of final predictions within five minutes of the timetable, 172 predictions, typically 1 min late
  22. 21:00: 91.6% of final predictions within five minutes of the timetable, 154 predictions, typically 1 min late
  23. 22:00: 87.7% of final predictions within five minutes of the timetable, 130 predictions, typically 1.1 min late
  24. 23:00: 91.7% of final predictions within five minutes of the timetable, 121 predictions, typically 1.2 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時間已測量Scenario or next investigation
ProblemOne hour has a lower prediction match16:0072%Operations in that hour

How BAYSHORE is doing

這些指標可區分重複出現的延誤,以及營運單位到站預測的變動。它們可為規劃人員和營運人員提供問題方向,但不能確定原因,也不能證明公車實際何時到達。每項數字都會顯示其路線時段的樣本數。

Measured over 22 route-hours. 0 more were observed too thinly to count, and are excluded rather than assumed good.

排班

預測一再延遲，可能表示這個時刻表值得檢討。在決定是否要調整行駛時間之前，請先查核實際到達和發車的記錄。

誰能解決
服務規劃人員
費用
在車輛、人力、回收和轉乘影響經過測試前，成本無法提供。

與時刻表接近的預測

100%

路線時段中，符合資格的到站預測中位數，早到不足一分鐘，且晚到不足三分鐘。

多次預測late的路線時段

0of 22

符合條件的到站預測中位數至少晚三分鐘的路線時段。請對照實際營運記錄，檢視行車時間。

有提早預測的路線時數

0of 22

路線小時數中，符合條件的到站預測中位數至少提早一分鐘。這不能證明巴士提早發車。

一般預測延誤

本月證據不足，無法公布此指標。

被標記路線時段中預測延誤的典型中位數;這不是可加到時刻表上的已驗證數值。

營運: not measurable here

本網站記錄的是每個站點每小時的延誤中位數，沒有百分位數，因此無法算出正常行程與糟糕行程之間的差距。這是我們自身測量方式的限制，並非對此地點的調查結果。

Measurements

計算時間: · 方法: settled-arrivals-oc-sto-conventional-v5

One hour has a lower prediction match · 16:00
準點 71.7%
Other hours on time 89.5%
Measured arrivals 240
Station evidence and sources
Français
評分或回報問題

Rider evidence

Community reports

Signals below are moderated community aggregates, not official operator notices or reliability scores.

You can report without signing in. Anonymous reports count a little less when we calculate public patterns. You can add an account after submitting.

Report a specific problem

Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.

本頁背後的證據開啟定義、方法、來源、日期、涵蓋範圍及已知限制。

所顯示的內容

目前的車站看板，由匯入的時刻表和每班次可用的營運單位預測組合而成。

How it was produced

Platforms sharing the station stop code are grouped, scheduled trips are read from the current GTFS, and a live time is used only when the operator publishes a matching prediction.

證據日期

計算或整合時間
樣本
40 departures across 3 published platform records in the current four-hour board.
涵蓋範圍
19 departures have a published live prediction; 21 are timetable-only.

來源

請注意的限制

  • OC Transpo 在此使用的資料中，不提供鐵路即時位置或預測，所以鐵路時間只有時刻表時間。
  • 站點資料來源沒有發布完整的車站無障礙路線、出入口或室內通道。
建議更正事實錯誤

Contains information licensed under the Open Government Licence – City of Ottawa.