Skip to main content

Next bus

FR

Report a problem

What happened
Full report No account needed

Buses now:on timelateyou

1O-Train Line 1 · station 3009

Rideau

Trains · timetableon timelateno reading
Every 4 to 5 min · sched. then 6:02
1
1Blair · platform 2
Not measured yet
6:00
sched. then 6:02
Every 4 to 8 min · sched. then 6:04
1
1Tunney's Pasture · platform 1
Not measured yet
6:00
sched. then 6:04
Buses at Rideau · liveupdated 30 s ago
Every 27 min
15
15Parliament ~ Parlement · platform A · every 27 to 27 min
Not measured yet
Nowlive
Every 15 min · then 17 sched.
5
5Elmvale · platform A · every 15 to 15 min
Not measured yet
Nowlive
then 17 sched.
Every 13 min · then 14 sched.
15
15Blair · platform B · every 13 to 13 min
Not measured yet
1minlive
then 14 sched.
Every 13 min · then 16 sched.
5
5Waller · platform B · every 13 to 13 min
Not measured yet
2minlive
then 16 sched.
Every 12 min · then 11 sched.
14
14St-Laurent · platform B · every 12 to 12 min
Not measured yet
6minlive
then 11 sched.
12
12Blair
platform B
Not measured yet
7minlive
6
6Rockcliffe
platform B
Not measured yet
13minlive
12
12Tunney's Pasture
platform A
Not measured yet
13minlive
Every 1 to 14 min · then 16 · 24 sched.
6
6Greenboro · platform D · every 1 to 14 min
Not measured yet
14minlive
then 16 · 24 sched.
7
7St-Laurent
platform B
Not measured yet
15minlive
6
6Billings Bridge
platform A
Not measured yet
18minlive
9
9Rideau
platform D
Not measured yet
20minlive
18
18St-Laurent
platform B
Not measured yet
21minlive
18
18Billings Bridge
platform A
Not measured yet
23minlive
9
9Hurdman
platform C
Not measured yet
24minlive
Every 13 min · then 25 sched.
14
14Tunney's Pasture · platform A · every 13 to 13 min
Not measured yet
24minlive
then 25 sched.
7
7Carleton
platform A
Not measured yet
Cancelled
from the timetable
12
12Parliament ~ Parlement
platform A
Not measured yet
Cancelled
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

72.6% predicted within five minutes of schedule. 7,164 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 here50 places within 5 min · nearest: Bike parking, 1 min walkBike parking: OpenStreetMap, data as of Jun 1, 2026. 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
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

  • Washroom nearby
  • Drinking water nearby

Performance

Service delivery · evidence state

Service at RIDEAU

Cancellations at this station

Local count cannot be published

Exact stop-call evidence could not be read for Oct 28, 2026 – Nov 3, 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 · 23 live provider predictions

    Server snapshot assembled Nov 4, 2026, 6:00 p.m.; open Departures for a refreshed board. This is not a cancellation count.

    Prediction agreement
    72.6% predicted within five minutes of schedule. 7,164 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.

    72.6% of final provider predictions within 5 minutes of the timetable, from 7,164 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 51%.

    Median predicted difference from the timetable: 2 min late. At the 95th percentile: 12 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-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: 83.3% of final predictions within five minutes of the timetable, 120 predictions, typically 2 min late
    2. 01:00: 83.3% of final predictions within five minutes of the timetable, 84 predictions, typically 2.4 min late
    3. 02:00: 78.3% of final predictions within five minutes of the timetable, 69 predictions, typically 3 min late
    4. 03:00: 93.1% of final predictions within five minutes of the timetable, 58 predictions, typically 1.5 min late
    5. 04:00: 86.2% of final predictions within five minutes of the timetable, 87 predictions, typically 2.1 min late
    6. 05:00: 93.3% of final predictions within five minutes of the timetable, 105 predictions, typically 1.7 min late
    7. 06:00: 91.7% of final predictions within five minutes of the timetable, 290 predictions, typically 1.4 min late
    8. 07:00: 85.2% of final predictions within five minutes of the timetable, 411 predictions, typically 1.8 min late
    9. 08:00: 65.5% of final predictions within five minutes of the timetable, 458 predictions, typically 3 min late
    10. 09:00: 75.3% of final predictions within five minutes of the timetable, 461 predictions, typically 2 min late
    11. 10:00: 79.2% of final predictions within five minutes of the timetable, 424 predictions, typically 1.9 min late
    12. 11:00: 73.5% of final predictions within five minutes of the timetable, 419 predictions, typically 2.5 min late
    13. 12:00: 68.8% of final predictions within five minutes of the timetable, 398 predictions, typically 3 min late
    14. 13:00: 75.3% of final predictions within five minutes of the timetable, 430 predictions, typically 2 min late
    15. 14:00: 73.5% of final predictions within five minutes of the timetable, 411 predictions, typically 2.2 min late
    16. 15:00: 57.3% of final predictions within five minutes of the timetable, 384 predictions, typically 3.8 min late
    17. 16:00: 51.4% of final predictions within five minutes of the timetable, 444 predictions, typically 4.8 min late
    18. 17:00: 62.9% of final predictions within five minutes of the timetable, 455 predictions, typically 3.6 min late
    19. 18:00: 69% of final predictions within five minutes of the timetable, 394 predictions, typically 2.8 min late
    20. 19:00: 72.8% of final predictions within five minutes of the timetable, 312 predictions, typically 2.4 min late
    21. 20:00: 73.6% of final predictions within five minutes of the timetable, 277 predictions, typically 1.9 min late
    22. 21:00: 74.3% of final predictions within five minutes of the timetable, 245 predictions, typically 2.7 min late
    23. 22:00: 74.7% of final predictions within five minutes of the timetable, 233 predictions, typically 2.8 min late
    24. 23:00: 75.9% of final predictions within five minutes of the timetable, 195 predictions, typically 2.3 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
    ProblemPredictions later than timetable02:003 min lateRunning time on the routes here
    ProblemPredictions later than timetable15:00 to 18:004.1 min lateRunning time on the routes here
    ProblemOne hour has a lower prediction match16:0051%Operations in that hour

    How RIDEAU 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 24 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

    83.3%

    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

    4of 24

    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 24

    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

    3.7min

    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

    Predictions later than timetable · 02:00
    Median delay 3 min
    Measured arrivals 69
    On time 78.3%
    Predictions later than timetable · 15:00 to 18:00
    Median delay 4.1 min
    Measured arrivals 1,283
    On time 57.3%
    One hour has a lower prediction match · 16:00
    On time 51.4%
    Other hours on time 75.3%
    Measured arrivals 444

    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 6 published platform records in the current four-hour board.
    Coverage
    23 departures have a published live prediction; 17 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.