Skip to main content

Next bus

FR

Report a problem

Filled in: station 3036 · 11:19 p.m. · pick one

What happened
Full report No account needed

Buses now:on timelateyou

2O-Train Line 2 · station 3036

Walkley

Trains · timetableon timelateno reading
Every 12 to 24 min · sched. then 11:30
2
2Bayview · platform WALKLEY O-TRAIN
Not measured yet
11:19
sched. then 11:30
Every 12 to 24 min · sched. then 11:31
2
2Limebank · platform WALKLEY O-TRAIN
Not measured yet
11:19
sched. then 11:31
Buses at Walkley · liveupdated 30 s ago
Every 20 to 30 min · then 27 · 55 sched.
105
105Uplands · platform B · every 20 to 30 min
Not measured yet
Nowlive
then 27 · 55 sched.
98
98Hurdman
platform A
Not measured yet
2minlive
Every 0 to 35 min · then 7 · 36 sched.
44
44Billings Bridge · platform E · every 0 to 35 min
Not measured yet
6minlive
then 7 · 36 sched.
Every 33 min · then 43 sched.
98
98Hawthorne · platform B · every 33 to 33 min
Not measured yet
9minlive
then 43 sched.
Every 2 to 37 min · then 13 · 51 sched.
44
44Hurdman · platform B · every 2 to 37 min
Not measured yet
11minlive
then 13 · 51 sched.
Every 17 to 29 min · sched. then 12:07
105
105St-Laurent · platform A · every 17 to 29 min
Not measured yet
11:41
sched. then 12:07
Every 30 to 33 min · sched. then 1:50
105
105Rideau · platform A · every 30 to 33 min
Not measured yet
1:18
sched. then 1:50
Entrances and elevators

We cannot confirm elevator status right now.

86.8% predicted within five minutes of schedule. 3,832 eligible provider predictions; arrivals not independently measured
Why →

More at this station

Save, plan, shareSave the station, plan a trip from it, or share it
Plan from here
Bike parking hereNone recorded within 5 minutes. Not recorded does not mean there is none.Bike parking: OpenStreetMap, data as of Jun 1, 2026. The walk is an estimate.
Add it ↗
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
Without JavaScriptBoards and departures still show without JavaScript

Station details

Step-free route

Current notice coverage cannot be confirmed. Retained notices below may have unconfirmed timing or source evidence. Check the operator before you travel.

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.

Performance

Service delivery · evidence state

Service at WALKLEY

Cancellations at this station

Local count cannot be published

Exact stop-call evidence could not be read for Oct 27, 2026 – Nov 2, 2026. 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 · 10 live provider predictions

    Server snapshot assembled Nov 3, 2026, 11:19 p.m.; open Departures for a refreshed board. This is not a cancellation count.

    Prediction agreement
    86.8% predicted within five minutes of schedule. 3,832 eligible provider predictions; arrivals not independently measured
    Bus prediction reliability at this station

    Verdict

    Bus prediction reliability at this station

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

    86.8% of final provider predictions within 5 minutes of the timetable, from 3,832 predictions over 6 weekdays. The lowest sampled hour is 15:00 at 74%.

    Median predicted difference from the timetable: 50 s late. At the 95th percentile: 9 min late.

    Final provider predictions for conventional bus arrivals at OC Transpo and STO stations; physical arrivals are not independently verified. Express (200/500), shopper/community (300), event (400), and school (600) routes are excluded because each needs a purpose-specific measure. STO routes are included and graded by their own families: Rapibus 100, 200, 400 and 800 count, and STO school journeys numbered 300 and above are excluded the way OC Transpo’s 600s are. Each operator is measured against its own service, never against the other’s. This station also has 1 O-Train line. This line is not included because OC Transpo does not publish realtime rail data.

    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: 100% of final predictions within five minutes of the timetable, 67 predictions, typically 0.2 min early
    2. 01:00: 95.1% of final predictions within five minutes of the timetable, 41 predictions, typically 1.1 min late
    3. 02:00: 96.8% of final predictions within five minutes of the timetable, 31 predictions, typically 0.2 min late
    4. 03:00: not enough data
    5. 04:00: 93.8% of final predictions within five minutes of the timetable, 32 predictions, typically 0 min late
    6. 05:00: 88.1% of final predictions within five minutes of the timetable, 118 predictions, typically 0.3 min late
    7. 06:00: 90.3% of final predictions within five minutes of the timetable, 206 predictions, typically 0.3 min late
    8. 07:00: 91% of final predictions within five minutes of the timetable, 244 predictions, typically 0.8 min late
    9. 08:00: 89.8% of final predictions within five minutes of the timetable, 246 predictions, typically 0.4 min late
    10. 09:00: 88% of final predictions within five minutes of the timetable, 217 predictions, typically 0.3 min late
    11. 10:00: 90.6% of final predictions within five minutes of the timetable, 202 predictions, typically 0.2 min late
    12. 11:00: 83.5% of final predictions within five minutes of the timetable, 200 predictions, typically 0.8 min late
    13. 12:00: 85% of final predictions within five minutes of the timetable, 207 predictions, typically 1 min late
    14. 13:00: 82.2% of final predictions within five minutes of the timetable, 202 predictions, typically 0.8 min late
    15. 14:00: 81.5% of final predictions within five minutes of the timetable, 222 predictions, typically 1.6 min late
    16. 15:00: 73.7% of final predictions within five minutes of the timetable, 236 predictions, typically 1.9 min late
    17. 16:00: 75.3% of final predictions within five minutes of the timetable, 227 predictions, typically 2.1 min late
    18. 17:00: 78.8% of final predictions within five minutes of the timetable, 236 predictions, typically 1.9 min late
    19. 18:00: 91.9% of final predictions within five minutes of the timetable, 221 predictions, typically 1 min late
    20. 19:00: 93.5% of final predictions within five minutes of the timetable, 139 predictions, typically 0.6 min late
    21. 20:00: 90.2% of final predictions within five minutes of the timetable, 133 predictions, typically 0.7 min late
    22. 21:00: 91.1% of final predictions within five minutes of the timetable, 146 predictions, typically 0.7 min late
    23. 22:00: 96.1% of final predictions within five minutes of the timetable, 129 predictions, typically 0.6 min late
    24. 23:00: 94.6% of final predictions within five minutes of the timetable, 111 predictions, typically 0.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
    WhatWhenMeasuredScenario or next investigation
    ProblemOne hour has a lower prediction match15:0074%Operations in that hour

    How WALKLEY is doing

    These indicators separate repeated delay from variation in the operator’s arrival predictions. They suggest questions for planners and operations staff; they do not establish the cause or prove when buses arrived. Each figure shows its route-hour sample.

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

    Scheduling

    Repeated late predictions can point to a timetable worth reviewing. Check actual arrival and dispatch records before deciding whether running time needs to change.

    Who can fix it
    A service planner
    What it costs
    Cost unavailable until fleet, labour, recovery and transfer effects are tested.

    Predictions close to the timetable

    100%

    Route-hours where the median eligible arrival prediction is less than one minute early and less than three minutes late.

    Route-hours with repeated late predictions

    0of 23

    Route-hours where the median eligible arrival prediction is at least three minutes late. Review running time against actual operating records.

    Route-hours with early predictions

    0of 23

    Route-hours where the median eligible arrival prediction is at least one minute early. This does not establish that buses departed early.

    Typical predicted delay

    Not enough evidence this month to publish this indicator.

    The typical median predicted delay in flagged route-hours; not a validated amount to add to the timetable.

    Operations: not measurable here

    This site records a median delay for each hour at a stop, and no percentile, so the gap between a normal trip and a bad one cannot be worked out. That is a limit of our own measurement, not a finding about this place.

    Measurements

    Calculated: · Method: settled-arrivals-oc-sto-conventional-v5

    One hour has a lower prediction match · 15:00
    On time 73.7%
    Other hours on time 90.4%
    Measured arrivals 236

    O-Train evidence

    What we know about train service here

    Open the train observation report

    Trains are not in the public data feed

    The bus punctuality reports compare archived arrival predictions with published schedules. They do not count independently measured physical arrivals. Otranspo has no comparable public train-position dataset for these reports, so those bus figures cannot show where a train is or whether Lines 1, 2 and 4 run on time.

    Publishing train positions, their timestamps, and the measurement method would help build a separate, verifiable record of rail service. The missing dataset does not establish how the trains performed.

    Recent shared train observations

    These are rider sightings approved by a moderator. They show a reported time and place. They are not official train positions, a complete train count, or proof of a cause.

    No approved rider observation matches this place or line in the last 31 days. That does not mean no train ran or no problem occurred.

    Share what you observedCheck all official service alertsOpen train research and history
    Station evidence and sources
    Français
    Rate or report an issue

    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.

    Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.

    What is being shown

    A current station board assembled from the imported timetable and any usable operator prediction for each trip.

    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.

    Evidence dates

    Computed or assembled
    Sample
    40 departures across 7 published platform records in the current four-hour board.
    Coverage
    10 departures have a published live prediction; 30 are timetable-only.

    Sources

    Limits to keep in mind

    • OC Transpo does not publish live rail positions or predictions in the feed used here, so rail times are timetable-only.
    • The stop source does not publish a complete station accessibility chain, entrances, or indoor paths.
    Suggest a factual correction

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