Skip to main content

Next bus

FR

Report a problem

What happened
Full report No account needed

Buses now:on timelateyou

OC Transpo station · 3032

Riverside

Buses at Riverside · liveupdated 30 s ago
Every 7 to 11 min · then 7 · 27 sched.
98
98Hurdman · platform 2A · every 7 to 11 min
Not measured yet
Nowlive
then 7 · 27 sched.
Every 10 to 12 min · then 8 · 19 sched.
88
88Hurdman · platform 2A · every 10 to 12 min
Not measured yet
Nowlive
then 8 · 19 sched.
Every 7 to 13 min · then 16 · 23 sched.
88
88Bayshore · platform 1A · every 7 to 13 min
Not measured yet
Nowlive
then 16 · 23 sched.
Every 27 min · then 31 sched.
10
10Lyon · platform 1A · every 27 to 27 min
Not measured yet
Nowlive
then 31 sched.
Every 31 min · then 35 sched.
49
49Hurdman · platform 2A · every 31 to 31 min
Not measured yet
1minlive
then 35 sched.
Every 30 min · then 39 sched.
98
98Hawthorne · platform 1A · every 30 to 30 min
Not measured yet
2minlive
then 39 sched.
Every 33 min · then 40 sched.
92
92Hurdman · platform 2A · every 33 to 33 min
Not measured yet
5minlive
then 40 sched.
Every 16 to 25 min · then 24 · 41 sched.
90
90Hurdman · platform 2A · every 16 to 25 min
Not measured yet
7minlive
then 24 · 41 sched.
Every 11 to 26 min · then 31 · 42 sched.
10
10Hurdman · platform 2A · every 11 to 26 min
Not measured yet
14minlive
then 31 · 42 sched.
Every 31 min · then 45 sched.
98
98South Keys / Hunt Club Loop ~ South Keys / Boucle Hunt Club · platform 1A · every 31 to 31 min
Not measured yet
14minlive
then 45 sched.
Every 14 to 15 min · then 25 · 41 sched.
90
90Greenboro · platform 1A · every 14 to 15 min
Not measured yet
17minlive
then 25 · 41 sched.
Every 28 min · then 41 sched.
10
10Main · platform 1A · every 28 to 28 min
Not measured yet
22minlive
then 41 sched.
105
105St-Laurent
platform 2A
Not measured yet
24minlive
105
105Uplands
platform 1A
Not measured yet
25minlive
617
617Omer-Deslauriers
platform 1A
Not measured yet
7:55
from the timetable
49
49Elmvale
platform 1A
Not measured yet
8:00
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

84.9% predicted within five minutes of schedule. 4,376 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 here4 places within 5 min · nearest: Racks for 6 bikes, 2 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

No published source lists amenities here yet.

Performance

Service delivery · evidence state

Service at RIVERSIDE

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 · 30 live provider predictions

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

Prediction agreement
84.9% predicted within five minutes of schedule. 4,376 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.

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

Median predicted difference from the timetable: 1 min late. At the 95th percentile: 8 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.

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: 92.7% of final predictions within five minutes of the timetable, 82 predictions, typically 0.9 min late
  2. 01:00: 89.8% of final predictions within five minutes of the timetable, 49 predictions, typically 0.7 min late
  3. 02:00: not enough data
  4. 03:00: not enough data
  5. 04:00: 96.8% of final predictions within five minutes of the timetable, 62 predictions, typically 0.3 min late
  6. 05:00: 91.1% of final predictions within five minutes of the timetable, 112 predictions, typically 1.5 min late
  7. 06:00: 85.2% of final predictions within five minutes of the timetable, 209 predictions, typically 1.7 min late
  8. 07:00: 82% of final predictions within five minutes of the timetable, 266 predictions, typically 1.8 min late
  9. 08:00: 81% of final predictions within five minutes of the timetable, 279 predictions, typically 1.7 min late
  10. 09:00: 82.8% of final predictions within five minutes of the timetable, 244 predictions, typically 1.6 min late
  11. 10:00: 82.7% of final predictions within five minutes of the timetable, 237 predictions, typically 1.5 min late
  12. 11:00: 85.3% of final predictions within five minutes of the timetable, 224 predictions, typically 1.2 min late
  13. 12:00: 90.8% of final predictions within five minutes of the timetable, 240 predictions, typically 1.4 min late
  14. 13:00: 86.1% of final predictions within five minutes of the timetable, 230 predictions, typically 1.3 min late
  15. 14:00: 85.1% of final predictions within five minutes of the timetable, 249 predictions, typically 1.6 min late
  16. 15:00: 86.2% of final predictions within five minutes of the timetable, 304 predictions, typically 1.6 min late
  17. 16:00: 79.7% of final predictions within five minutes of the timetable, 281 predictions, typically 2 min late
  18. 17:00: 80.1% of final predictions within five minutes of the timetable, 286 predictions, typically 2.3 min late
  19. 18:00: 82.8% of final predictions within five minutes of the timetable, 227 predictions, typically 1.5 min late
  20. 19:00: 87.6% of final predictions within five minutes of the timetable, 177 predictions, typically 1.2 min late
  21. 20:00: 84% of final predictions within five minutes of the timetable, 156 predictions, typically 0.7 min late
  22. 21:00: 83.8% of final predictions within five minutes of the timetable, 148 predictions, typically 1.4 min late
  23. 22:00: 89.4% of final predictions within five minutes of the timetable, 151 predictions, typically 1.2 min late
  24. 23:00: 87.3% of final predictions within five minutes of the timetable, 118 predictions, typically 0.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

How RIVERSIDE 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 22 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 22

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 22

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

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