Ward 22 · Ottawa · Councillor: Steve Desroches
Riverside South-Findlay Creek
Riverside South-Findlay Creek: 85.1% of predictions within five minutes.
- Within five minutes
- 85.1%
- Stops in the ward
- 145
- Routes serving it
- 16
- Cancelled trips
- Not available yet
- Not counted per ward yet
Where it is slowest
- 80% and up 5
- 60 to 80% 4
- Under 60% 0
- Too little data 6
Routes serving the ward, by their share of predictions within five minutes. Each route result covers the whole route.
Routes in this ward
| Route | Within 5 min | Cancelled | Crowding |
|---|---|---|---|
| 198 | 65.0% | Not published | Not published |
| 70 | 71.6% | Not published | Not published |
| 110 | 71.6% | Not published | Not published |
| 73 | 75.8% | Not published | Not published |
| 74 | 83.1% | Not published | Not published |
| 99 | 83.5% | Not published | Not published |
| 105 | 88.2% | Not published | Not published |
| 94 | 91.9% | Not published | Not published |
Cancellations and crowding are not published per route yet. 6 routes with too little data or a different service purpose are left out.
All routes and their sourcesOne-page brief
A printable summary of this ward for council and community meetings, with the same numbers, the method in plain words and dated sources.
What can be verified in Riverside South-Findlay Creek?
Arrival predictions, the imported timetable and train notices. Each is shown with its own source.
Provider prediction agreement
85.1%
of eligible predictions within five minutes of schedule
- How this compares
- Rank 1 of 22 · median 78.4%
Service, per the imported timetable
- Scheduled trips at ward stops
- Not available yet
- Routes
- 15
- Train lines
- 1
Current service inside this boundary
The live buses inside this boundary are on the Map tab.
Prediction measure, timetable inventory and methods
Service delivery · evidence state
Cancellations at stops in this ward
Not publishableNo zero or missed trip is inferred when exact stop calls cannot be published.
Predictions at stops inside the ward
85.1% within five minutes of the timetable across 128,887 eligible final provider predictions and 20 weekdays. These are not verified physical arrivals.
Predictions do not prove physical arrival.
Routes to inspect
Oct 28, 2026 – Nov 3, 2026If available, these are route-wide vehicle-position matches for routes serving the ward. They do not locate a missed trip inside this ward or prove a cancellation. Each comparison uses scheduled trips for that same route and window.
- 69724 of 25 scheduled trips had a matched vehicle positionInspect days
- 105662 of 682 scheduled trips had a matched vehicle positionInspect days
- 29949 of 50 scheduled trips had a matched vehicle positionInspect days
Scheduled calls, sources and limits
16 routes · 145 stops. Timetable inventory, not trips delivered.
Cancellations at stops in this ward
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.
Verdict
What would fix transit here
Worked out from the routes that serve this ward. Each item names the route, when it happens, and what would change it.
7 of 9 show repeated provider predictions later than the timetable, consistent with a possible scheduled running-time shortfall. A scheduler should test that scenario against operations; labour, fleet, recovery and transfer impacts are not established here.
Worst here: route 70, predictions later than timetable 15:00 to 19:00, 3.9 min late.
Best here: route 99, observed-position lower bound, 100%.
9 of 9 routes here had something measurable to report.
- 00:00: 90.4% of final predictions within five minutes of the timetable, 2,664 predictions, typically 0.7 min late
- 01:00: 90.3% of final predictions within five minutes of the timetable, 1,608 predictions, typically 1.3 min late
- 02:00: 92.9% of final predictions within five minutes of the timetable, 1,402 predictions, typically 0.7 min late
- 03:00: 89.1% of final predictions within five minutes of the timetable, 1,418 predictions, typically 0.3 min late
- 04:00: 86.1% of final predictions within five minutes of the timetable, 2,939 predictions, typically 1.3 min late
- 05:00: 84.1% of final predictions within five minutes of the timetable, 9,043 predictions, typically 1 min late
- 06:00: 87.5% of final predictions within five minutes of the timetable, 15,523 predictions, typically 1.2 min late
- 07:00: 86.7% of final predictions within five minutes of the timetable, 19,003 predictions, typically 1.1 min late
- 08:00: 78.7% of final predictions within five minutes of the timetable, 17,686 predictions, typically 1.7 min late
- 09:00: 80.7% of final predictions within five minutes of the timetable, 16,051 predictions, typically 1.6 min late
- 10:00: 85.4% of final predictions within five minutes of the timetable, 15,509 predictions, typically 1.1 min late
- 11:00: 80.7% of final predictions within five minutes of the timetable, 15,435 predictions, typically 1.4 min late
- 12:00: 81.7% of final predictions within five minutes of the timetable, 15,546 predictions, typically 1.4 min late
- 13:00: 80.9% of final predictions within five minutes of the timetable, 15,481 predictions, typically 1.9 min late
- 14:00: 80.3% of final predictions within five minutes of the timetable, 15,338 predictions, typically 1.4 min late
- 15:00: 68.9% of final predictions within five minutes of the timetable, 15,667 predictions, typically 3.1 min late
- 16:00: 66.1% of final predictions within five minutes of the timetable, 18,791 predictions, typically 3.1 min late
- 17:00: 63% of final predictions within five minutes of the timetable, 19,853 predictions, typically 3.2 min late
- 18:00: 67.3% of final predictions within five minutes of the timetable, 18,974 predictions, typically 2.9 min late
- 19:00: 83.8% of final predictions within five minutes of the timetable, 15,571 predictions, typically 1.5 min late
- 20:00: 82% of final predictions within five minutes of the timetable, 13,270 predictions, typically 1.7 min late
- 21:00: 79.5% of final predictions within five minutes of the timetable, 10,318 predictions, typically 1.8 min late
- 22:00: 79.8% of final predictions within five minutes of the timetable, 6,375 predictions, typically 2 min late
- 23:00: 86.2% of final predictions within five minutes of the timetable, 4,115 predictions, typically 1.5 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
| What | When | Measured | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable70110747319893997 routes | 15:00 to 19:00 … 23:00 | 3.9 min late … 3.1 min late | More running time |
| ProblemOne hour has a lower prediction match70747393105198947 routes | 15:00 … 17:00 | 52% … 71% | Operations, not the timetable |
| ProblemWide prediction spread1051982 routes | 17:00 · 18:00 | 25.1 min swing · 20.2 min swing | Operations, not the timetable |
| ProblemPredictions earlier than timetable110942 routes | 21:00 · 18:00 | 1.6 min early · 1.3 min early | Less running time, or holding points |
| StrengthObserved-position lower bound999373941985 routes | All measured hours | 100% | Keep what works |
| CaveatCoverage gap10570741104 routes | All measured hours | 97% · 99% | More observation, not a service change |
O-Train evidence
What we know about train service here
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.
Official O-Train alerts could not be read just now, so nothing here can tell you whether a train is delayed. This is about our connection to the notices, not about the trains.
Check all official service alertsRecent 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.
How RIVERSIDE SOUTH-FINDLAY CREEK 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 155 route-hours. 3 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
85.2%
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
21of 155
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
2of 155
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.9min
The typical median predicted delay in flagged route-hours; not a validated amount to add to the timetable.
Operations
Wide variation in arrival predictions calls for an operational review. Traffic, dispatch, boarding and timetable design may contribute; these predictions alone cannot identify the cause or the remedy.
- Who can fix it
- Operations, and often the road itself
- What it costs
- Cost unavailable until the operational cause and remedy are established.
Prediction gap below twenty minutes
98.7%
Route-hours where the 95th-percentile eligible prediction is less than twenty minutes later than the median.
Route-hours with wide prediction gaps
2of 155
Route-hours where the 95th-percentile eligible prediction is at least twenty minutes later than the median. The cause needs investigation.
Typical prediction gap
22.6min
The typical gap between the 95th-percentile eligible prediction and the median in flagged route-hours.
Service, per the imported timetable
Scheduled transit, provider prediction agreement with the timetable, and public services in this ward.
Provider prediction agreement
85.1% of eligible provider predictions were within five minutes of the timetable. 109,648 of 128,887 settled trip-stop predictions at stops inside this ward matched that range across 20 weekdays with feed evidence, from Oct 3, 2026 to Nov 3, 2026. These are provider predictions, not independently observed arrivals.
2 partial-capture days not counted.
- Predictions within five minutes
- 109,648
- Eligible trip-stop predictions
- 128,887
- Observed days
- 20 weekdays
How this compares
Ranked 1 of 22 measured wards. 6.7 points above the city median of 78.4%.
Highest: ward 22 at 85.1%. Lowest: ward 21 at 60.3%.
Only wards whose evidence meets the publication threshold are ranked. Same window and same method for each.
Which routes need closer review
9 of the 15 routes serving this ward have enough provider-prediction evidence to compare. Lowest timetable agreement first.
- 198Open route 65.0%Predictions within five minutes
6,081 eligible predictions across the whole route
- 70Open route 71.6%Predictions within five minutes
150,278 eligible predictions across the whole route
- 110Open route 71.6%Predictions within five minutes
113,377 eligible predictions across the whole route
- 73Open route 75.8%Predictions within five minutes
39,126 eligible predictions across the whole route
- 74Open route 83.1%Predictions within five minutes
83,010 eligible predictions across the whole route
- 99Open route 83.5%Predictions within five minutes
41,425 eligible predictions across the whole route
- 105Open route 88.2%Predictions within five minutes
67,367 eligible predictions across the whole route
- 94Open route 91.9%Predictions within five minutes
2,369 eligible predictions across the whole route
- 93Open route 92.5%Predictions within five minutes
35,681 eligible predictions across the whole route
6 more routes here are not ranked: school, express, shopper or event service, whose schedule result does not compare the same way.
Vehicle visibility to investigate
Vehicle visibility to investigate
The current summary uses seven days. For every route, you can also open yesterday, the last 7 days, or the last 30 days and inspect the day, scheduled trip, excluded feed gaps, and every observed public vehicle ID. An absence does not prove a vehicle fault or operator decision.
| Route | Scheduled trips | With a position | Without a matched position | Coverage | History |
|---|---|---|---|---|---|
| 697 | 25 | 24 | 1 | 96.0% | |
| 105 | 682 | 662 | 20 | 97.1% | |
| 299 | 50 | 49 | 1 | 98.0% | |
| 70 | 623 | 614 | 9 | 98.6% | |
| 110 | 346 | 341 | 5 | 98.6% | |
| 74 | 712 | 703 | 9 | 98.7% | |
| 73 | 335 | 334 | 1 | 99.7% | |
| 99 | 501 | 500 | 1 | 99.8% | |
| 93 | 490 | 490 | 0 | 100.0% | |
| 94 | 60 | 60 | 0 | 100.0% | |
| 198 | 55 | 55 | 0 | 100.0% | |
| 283 | 35 | 35 | 0 | 100.0% | |
| 680 | 35 | 35 | 0 | 100.0% | |
| 676 | 20 | 20 | 0 | 100.0% | |
| 304 | 2 | 2 | 0 | 100.0% |
Routes serving the ward
16 scheduled routesMap & current service
Current service inside this boundary
Scheduled lines, stops, and observed buses share one map. Select a route or vehicle for details.
Evidence & sources
Imported municipal polygon · 46 boundary vertices · City of Ottawa ward boundaries · imported Aug 4, 2026
Public amenity record for this ward
Public washrooms and drinking water
Choose a category to check which location details are available.Public washrooms (City data) 6
The public ward snapshot publishes the count but not the individual locations for this ward. No locations are being invented.
Drinking water (City data) 3
The public ward snapshot publishes the count but not the individual locations for this ward. No locations are being invented.
Prepare an email for City Hall
Choose one current office or enter one other recipient, edit the neutral draft, then review it in your own email app.
Otranspo never sends this message and cannot see whether it was sent, received, or answered.
Send only to the relevant office. Avoid mass email, harassment, report receipts, account details, health information, phone numbers, or an exact personal location. Remove anything you do not want the recipient or email provider to retain.
If no email app opens, copy the draft below and paste it into the email service you choose.
Evidence included with the draft
- Canonical Otranspo evidence link
- https://otranspo.ca/en/city/wards/22
- Sources and time
- Sources and time: open the linked report for its source records and published or imported timestamps.
- Limitations
- Limitations: Otranspo is independent and may show unknown, suppressed, delayed, or corrected values. Confirm urgent or current service matters with the official agency.
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
- Graffiti
- Cleanliness
- Lighting
- Snow or ice
- Washroom unavailable
- Water unavailable
- Accessibility barrier
- Other issue
Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.
Civic evidence brief
The identity, boundary, contacts, service scope and evidence dates behind this ward report, kept together so the page can be cited without losing its qualifications.
- Municipality
- City of Ottawa, Ontario
- Geographic unit
- Official City of Ottawa municipal ward 22: RIVERSIDE SOUTH-FINDLAY CREEK
- Boundary and vintage
- City ward layer · effective not published · imported August 4, 2026
- Official civic contacts
- Steve Desroches · Councillor · source check is older than the publication threshold · source checked August 4, 2026 · official City contact source
- Mark Sutcliffe · Mayor · source check is older than the publication threshold · source checked August 4, 2026 · official City contact source
- Relevant scheduled service
- 16 public route records with a stop inside this boundary · operators: OC Transpo
- Transit evidence vintage
- Timetable import: not published · reliability window: Oct 3, 2026 – Nov 3, 2026
A ward boundary, route inventory, destination list, population count or employment count supplies civic context. None of those values alone measures passenger demand, household trip effects, transfers or daily attendance.
Ottawa wards are municipal wards. They are not Gatineau electoral districts, and results from the two boundary systems are not interchangeable.
Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.
What is being shown
A ward-level inventory of scheduled transit, public washrooms, drinking-water locations, and eligible final OC Transpo provider predictions at stops inside the ward.
How it was produced
Current imported records are assigned by point-in-polygon to the sourced ward boundary. Reliability uses one eligible final provider prediction per trip, stop, and service date in the latest 28 completed service days. Within five minutes is measured against the timetable, not a physical arrival. Publication requires 20 weekdays with prediction evidence and 500 eligible predictions.
Evidence dates
- Imported
- Computed or assembled
- Sample
- 128,887 eligible settled provider predictions across 20 weekdays with prediction evidence support the reliability result.
- Method or data version
- ward-counts-v1 + ward-stop-settled-arrivals-purpose-aware-v3
- Source checksum
- ward-reliability:e2fd407f151a6135a32a2324796619bf848d25b8dc2b1229fc8739e1ebb8531e
Sources
Limits to keep in mind
- Counts describe the published inventory inside the boundary, not service quality or access from every address.
- Reliability covers final OC Transpo provider predictions at geographically assigned stops; physical arrivals are not independently measured. Rail and trips without eligible prediction evidence are not represented.
- An unavailable count remains unavailable. It is not changed to zero.
How we measure this
For each trip, stop and service date at stops inside the ward, we keep the last eligible OC Transpo prediction and compare it with the timetable. It counts as within five minutes when the two are no more than five minutes apart. This is not a physical arrival.
The window is the latest 28 completed service days. A result is published only with 20 weekdays of prediction evidence and 500 eligible predictions. Route results cover each whole route, not only the part inside the ward.
Read the full methodContains information licensed under the Open Government Licence – City of Ottawa.