跳至主要內容

下一班巴士

回報問題

已填寫：車站 3053 · 下午6:47 · 請選一項

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

現在的巴士:準時晚點您

OC Transpo station · 3053

Elmvale

Buses at Elmvale · live30 秒前更新
每 28 至 30 分鐘一班 · 然後 27 · 56（預定）
40
40Greenboro · platform A · every 28 to 30 min
尚未測量
現在即時
然後 27 · 56（預定）
每 29 至 32 分鐘一班 · 然後 26 · 64（預定）
40
40St-Laurent · platform B · every 29 to 32 min
尚未測量
3分鐘即時
然後 26 · 64（預定）
每 15 至 30 分鐘一班 · 然後 22 · 37（預定）
41
41Billings Bridge · platform A · every 15 to 30 min
尚未測量
3分鐘即時
然後 22 · 37（預定）
每 11 至 15 分鐘一班 · 按時刻表,然後 下午7:04
5
5Elmvale · platform A · every 11 to 15 min
尚未測量
下午6:51
按時刻表,然後 下午7:04
每 26 至 28 分鐘一班 · 然後 36 · 58（預定）
48
48Hurdman · platform B · every 26 to 28 min
尚未測量
6分鐘即時
然後 36 · 58（預定）
每 29 至 30 分鐘一班 · 然後 42 · 72（預定）
48
48Carleton · platform A · every 29 to 30 min
尚未測量
12分鐘即時
然後 42 · 72（預定）
每 20 至 30 分鐘一班 · 然後 27 · 45（預定）
5
5Waller · platform A · every 20 to 30 min
尚未測量
14分鐘即時
然後 27 · 45（預定）
每 60 分鐘一班 · 按時刻表,然後 下午8:02
49
49Elmvale · platform B · every 60 to 60 min
尚未測量
下午7:02
按時刻表,然後 下午8:02
49
49Hurdman
platform A
尚未測量
23分鐘即時
每 27 至 29 分鐘一班 · 然後 43 · 72（預定）
41
41St-Laurent · platform B · every 27 to 29 min
尚未測量
42分鐘即時
然後 43 · 72（預定）
Entrances and elevators

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

82.9% 預測與時刻表相差在五分鐘內. 2,876 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 here4 places within 5 min · nearest: Racks for 4 bikes, 步行 1 分鐘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

  • Washroom nearby
  • Drinking water nearby

表現

服務提供情況 · 證據狀態

Service at ELMVALE

Cancellations at this station

Local count cannot be published

Exact stop-call evidence could not be read for 2026年10月27日 – 2026年11月2日. No zero is assumed.

Dates, source versions and limits

Method: retained-pre-service-exact-trip-stop-call-v1. Cancellation-feed completeness and position coverage are unverified.

The retained timetables were fetched, imported and first activated before the service day. The archive does not prove they remained the active timetables throughout that period. Comparisons between places remain unavailable.

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

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

    Prediction agreement
    82.9% 預測與時刻表相差在五分鐘內. 2,876 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.

    82.9% of final provider predictions within 5 minutes of the timetable, from 2,876 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 69%.

    Median predicted difference from the timetable: 2 min 晚點. 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-27 to 2026-11-03. 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: 95.7% of final predictions within five minutes of the timetable, 46 predictions, typically 0.2 min late
    2. 01:00: not enough data
    3. 02:00: not enough data
    4. 03:00: not enough data
    5. 04:00: not enough data
    6. 05:00: 96.4% of final predictions within five minutes of the timetable, 83 predictions, typically 1.7 min late
    7. 06:00: 84.7% of final predictions within five minutes of the timetable, 189 predictions, typically 1.7 min late
    8. 07:00: 91.4% of final predictions within five minutes of the timetable, 210 predictions, typically 1.7 min late
    9. 08:00: 69.5% of final predictions within five minutes of the timetable, 203 predictions, typically 3 min late
    10. 09:00: 84.7% of final predictions within five minutes of the timetable, 170 predictions, typically 1.9 min late
    11. 10:00: 88.8% of final predictions within five minutes of the timetable, 161 predictions, typically 2 min late
    12. 11:00: 85.3% of final predictions within five minutes of the timetable, 163 predictions, typically 2.2 min late
    13. 12:00: 79% of final predictions within five minutes of the timetable, 167 predictions, typically 2 min late
    14. 13:00: 78.5% of final predictions within five minutes of the timetable, 149 predictions, typically 2 min late
    15. 14:00: 77.6% of final predictions within five minutes of the timetable, 174 predictions, typically 2.2 min late
    16. 15:00: 76.6% of final predictions within five minutes of the timetable, 167 predictions, typically 2.5 min late
    17. 16:00: 68.9% of final predictions within five minutes of the timetable, 161 predictions, typically 3.3 min late
    18. 17:00: 75.6% of final predictions within five minutes of the timetable, 193 predictions, typically 2 min late
    19. 18:00: 86.5% of final predictions within five minutes of the timetable, 148 predictions, typically 1.7 min late
    20. 19:00: 88.9% of final predictions within five minutes of the timetable, 108 predictions, typically 1.7 min late
    21. 20:00: 88.3% of final predictions within five minutes of the timetable, 103 predictions, typically 1.7 min late
    22. 21:00: 89.4% of final predictions within five minutes of the timetable, 94 predictions, typically 1.5 min late
    23. 22:00: 92.3% of final predictions within five minutes of the timetable, 78 predictions, typically 1.9 min late
    24. 23:00: 94.6% of final predictions within five minutes of the timetable, 74 predictions, typically 1 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
    ProblemPredictions later than timetable08:003 min lateRunning time on the routes here
    ProblemPredictions later than timetable16:003.3 min lateRunning time on the routes here
    ProblemOne hour has a lower prediction match16:0069%Operations in that hour

    How ELMVALE is doing

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

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

    排班

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

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

    與時刻表接近的預測

    90%

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

    多次預測late的路線時段

    2of 20

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

    有提早預測的路線時數

    0of 20

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

    一般預測延誤

    3.1min

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

    營運: not measurable here

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

    Measurements

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

    Predictions later than timetable · 08:00
    Median delay 3 min
    Measured arrivals 203
    準點 69.5%
    Predictions later than timetable · 16:00
    Median delay 3.3 min
    Measured arrivals 161
    準點 68.9%
    One hour has a lower prediction match · 16:00
    準點 68.9%
    Other hours on time 86.5%
    Measured arrivals 161
    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 2 published platform records in the current four-hour board.
    涵蓋範圍
    14 departures have a published live prediction; 26 are timetable-only.

    來源

    請注意的限制

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

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