Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.

Ward 22 · Ottawa

RIVERSIDE SOUTH-FINDLAY CREEK

Councillor: Steve Desroches

17
Routes: 146
Stops: 85.7%
within five minutes

Boundaries: City of Ottawa ward layer; imported August 4, 2026.Prepare an email for City Hall →

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: 17 public route records with a stop inside this boundary · operators: OC Transpo
Transit evidence vintage: Timetable import: not published · reliability window: Aug 24, 2026 – Sep 21, 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.

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.

6 of 9 show a repeated lateness pattern consistent with insufficient scheduled running time. A scheduler should test a running-time scenario; labour, fleet, recovery and transfer impacts are not established here.

Worst here: route 70, late by the timetable 14:00 to 19:00, 3.9 min late.

9 of 9 routes here had something measurable to report.

Arrivals within five minutes, by hour of day, across the 9 routes graded here, last 14 days

00:00: 90% of arrivals on time, 2,925 arrivals, typically 0.7 min late
01:00: 83% of arrivals on time, 1,561 arrivals, typically 1.3 min late
02:00: 82.7% of arrivals on time, 1,475 arrivals, typically 1 min late
03:00: 89.5% of arrivals on time, 1,529 arrivals, typically 0.6 min late
04:00: 92.9% of arrivals on time, 3,156 arrivals, typically 1.2 min late
05:00: 88.6% of arrivals on time, 9,911 arrivals, typically 1.1 min late
06:00: 90% of arrivals on time, 16,825 arrivals, typically 1.4 min late
07:00: 84.6% of arrivals on time, 20,425 arrivals, typically 1.6 min late
08:00: 75.4% of arrivals on time, 19,241 arrivals, typically 2.2 min late
09:00: 80.6% of arrivals on time, 17,553 arrivals, typically 1.9 min late
10:00: 85.5% of arrivals on time, 16,736 arrivals, typically 1.3 min late
11:00: 83.7% of arrivals on time, 15,688 arrivals, typically 1.3 min late
12:00: 80.1% of arrivals on time, 15,664 arrivals, typically 1.6 min late
13:00: 77.9% of arrivals on time, 15,464 arrivals, typically 1.8 min late
14:00: 77.4% of arrivals on time, 15,191 arrivals, typically 1.8 min late
15:00: 66.7% of arrivals on time, 15,804 arrivals, typically 2.9 min late
16:00: 63.4% of arrivals on time, 19,075 arrivals, typically 3.3 min late
17:00: 65.8% of arrivals on time, 19,754 arrivals, typically 3.1 min late
18:00: 70.2% of arrivals on time, 19,107 arrivals, typically 2.5 min late
19:00: 78.8% of arrivals on time, 15,198 arrivals, typically 1.9 min late
20:00: 79.5% of arrivals on time, 13,298 arrivals, typically 2.3 min late
21:00: 78.9% of arrivals on time, 10,370 arrivals, typically 2.1 min late
22:00: 82.2% of arrivals on time, 6,624 arrivals, typically 1.7 min late
23:00: 87.1% of arrivals on time, 4,522 arrivals, typically 1.4 min late

90% or more on time
80 to 90% on time
under 80% on time
not enough data

What	When	Measured	Scenario or next investigation
ProblemLate by the timetable70 110 73 198 99 936 routes	14:00 to 19:00 … 04:00	3.9 min late … 13.7 min late	More running time
ProblemUnreliable198 1052 routes	17:00 to 19:00 · 17:00	31.3 min swing · 30.6 min swing	Operations, not the timetable
ProblemOne hour collapses110 70 74 93 73 99 198 948 routes	16:00 … 14:00	49% … 71%	Operations, not the timetable
ProblemRunning early941 routes	18:00	1.2 min early	Less running time, or holding points

Map & 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

Route

━ 16 bus routes═ 1 train lines● 146 stops

Loading live feed

O-Train evidence

What we know about train service here

Open the train observation report

Trains are not in the public data feed

OC Transpo publishes live positions for its buses, and this site measures them: millions of bus arrivals every month, which is where every bus figure on this site comes from. The same public feed carries no train positions, so this site has never recorded a single train arrival. Nothing here can tell you where a train is, or whether Lines 1, 2 and 4 run on time.

This is a gap in what is published, not a gap in the trains. If train positions were published the way bus positions already are, riders would get the same record for rail that they have for every bus route on this site.

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 observed Check all official service alerts Open train research and history

Official timetable

OC Transpo does not publish O-Train positions or arrival predictions in the public feed Otranspo receives. Schedules, official alerts, and rider observations are shown separately so one source cannot impersonate another.

Ask for this data

Turn this gap into a public-data request

OC Transpo does not publish live O-Train positions in the public feed Otranspo can use. You can ask the City to publish them in a stable, reusable format.

This is your message. Edit it before opening your own email app. Otranspo does not send it, track delivery, or speak for you. Write to one relevant recipient; do not use this tool for mass email, harassment, or personal or sensitive information.

How do you want to address this draft?

Choose an official recipientEnter another recipient email

Subject

Message

Choose an official recipient or enter one valid other email address to open an email draft.

Check the official councillor directory →Send through OC Transpo’s official feedback form →Official contact sources →

How RIVERSIDE SOUTH-FINDLAY CREEK is doing

Two different failures hide inside one on-time percentage, and they have opposite fixes. These separate them. Each figure is a share of the route-hours this site measured well enough to speak for, and the count it is out of is shown beside it.

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

Scheduling

Whether the timetable describes the trip that is actually made. A route late by the same amount every day is not unreliable, it is mis-scheduled, and every operator is driving a schedule nobody can keep.

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

Timetable matches the trip

85.2%

Hours where the middle arrival is within three minutes late and one minute early of the timetable.

Route-hours where the timetable is short

22of 155

Hours where the middle arrival is three minutes late or worse. Each is a candidate for a running-time rewrite.

Route-hours running early

1of 155

Hours where buses typically leave early. Riders who arrive on time can still watch one go.

Running time a short hour needs

3.7min

For a typical short hour, the minutes a planner would add.

Operations

Whether a bad trip is close to a normal one. A route on time on average but wildly variable has a timetable that is right and something else that is not. Padding the schedule here makes every rider’s trip longer while the bad trips stay bad.

Who can fix it: Operations, and often the road itself
What it costs: Cost unavailable until the operational cause and remedy are established.

A bad trip is close to a normal one

98.1%

Hours where the worst trips run less than twenty minutes behind the normal one.

Route-hours that are unpredictable

3of 155

Hours where they run twenty minutes or more behind it. Adding running time does not fix these.

How far behind a bad trip runs

30.6min

For a typical unpredictable hour, how far behind a bad trip runs.

Service, per the imported timetable

A readable view of scheduled transit, observed reliability, and public services in this ward.

17
Routes: 146
Stops: 6
Washrooms: 3
Water locations

Named ward measure85.7%within five minutes

Observed reliability

85.7% within five minutes. 71,010 of 82,901 settled OC Transpo arrivals at stops inside this ward were on time across 20 observed weekdays, from Aug 24, 2026 to Sep 21, 2026.

On-time arrivals: 71,010
Settled arrivals: 82,901
Observed days: 20 weekdays

How this compares

Ranked 1 of 22 measured wards. 8.1 points above the city median of 77.6%.

Highest: ward 22 at 85.7%. Lowest: ward 21 at 56.5%.

Only wards whose evidence meets the publication threshold are ranked. Same window and same method for each.

Which routes are pulling this ward down

9 of the 16 routes serving this ward have enough evidence to compare. Least punctual first.

Route	Within five minutes	Arrivals checked
198	69.8%	4,720
70	71.6%	109,074
110	72.2%	84,521
73	75.7%	28,655
74	83.0%	60,358
99	84.3%	30,494
105	88.4%	48,484
94	89.4%	1,806
93	94.6%	25,690

7 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

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
299	50	39	11	78.0%	Day 7 30
73	335	265	70	79.1%	Day 7 30
94	60	48	12	80.0%	Day 7 30
198	55	44	11	80.0%	Day 7 30
283	35	28	7	80.0%	Day 7 30
680	35	28	7	80.0%	Day 7 30
697	25	20	5	80.0%	Day 7 30
676	20	16	4	80.0%	Day 7 30
110	344	280	64	81.4%	Day 7 30
74	712	585	127	82.2%	Day 7 30
70	621	518	103	83.4%	Day 7 30
99	501	424	77	84.6%	Day 7 30
93	490	415	75	84.7%	Day 7 30
105	678	575	103	84.8%	Day 7 30
304	2	2	0	100.0%	Day 7 30
406	1	1	0	100.0%	Day 7 30

Routes serving the ward

17 scheduled routes

Bus routes · 16

Train lines · 1

2Train

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.

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.

Share this page

Use the permanent public link to this page and its sources.

Download evidence image

Only the canonical public link is shared. Panel state, location, receipts, and other browser-only details are left out. Email and social services apply their own privacy terms.

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 observed OC Transpo bus arrivals 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 settled arrival per trip, stop, and service date in the latest 28 completed service days. On time is within ±5 minutes, with publication thresholds of 20 observed weekdays and 500 arrivals.

Imported: August 4, 2026 at 10:43 a.m.
Computed or assembled: September 23, 2026 at 3:17 a.m.
Sample: 82,901 settled arrivals across 20 observed weekdays support the reliability result.
Method or data version: ward-counts-v1 + ward-stop-settled-arrivals-purpose-aware-v3
Source checksum: ward-reliability:400c26d6a01343f52f40987c797d7a81db04673df60284f96841e593a6aaab5d

Sources

Limits to keep in mind

Counts describe the published inventory inside the boundary, not service quality or access from every address.
Reliability covers observed OC Transpo bus arrivals at geographically assigned stops. Rail and arrivals without settled evidence are not represented.
An unavailable count remains unavailable. It is not changed to zero.

Suggest a factual correction →

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.