Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Ward 9 · Ottawa
KNOXDALE-MERIVALE
Councillor: Sean Devine
- 34
- Routes
- 345
- Stops
- 79.0%
- within five minutes
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 9: KNOXDALE-MERIVALE
- Boundary and vintage
- City ward layer · effective not published · imported August 4, 2026
- Official civic contacts
- Sean Devine · 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
- 34 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 22, 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.
11 of 17 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.
13 of 17 routes here had something measurable to report.
- 00:00: 92% of arrivals on time, 11,985 arrivals, typically 0.7 min late
- 01:00: 93.3% of arrivals on time, 3,556 arrivals, typically 0.5 min late
- 02:00: 80.5% of arrivals on time, 1,660 arrivals, typically 0.9 min late
- 03:00: 89.3% of arrivals on time, 1,814 arrivals, typically 0 min early
- 04:00: 95.3% of arrivals on time, 5,315 arrivals, typically 0.5 min late
- 05:00: 93.3% of arrivals on time, 17,917 arrivals, typically 1.1 min late
- 06:00: 91.2% of arrivals on time, 40,730 arrivals, typically 1.2 min late
- 07:00: 83.2% of arrivals on time, 54,492 arrivals, typically 1.8 min late
- 08:00: 69.3% of arrivals on time, 54,021 arrivals, typically 2.8 min late
- 09:00: 75.9% of arrivals on time, 51,025 arrivals, typically 2.3 min late
- 10:00: 82.1% of arrivals on time, 47,647 arrivals, typically 1.6 min late
- 11:00: 80.6% of arrivals on time, 45,491 arrivals, typically 1.6 min late
- 12:00: 79.9% of arrivals on time, 44,482 arrivals, typically 1.9 min late
- 13:00: 79.4% of arrivals on time, 44,234 arrivals, typically 1.6 min late
- 14:00: 78.6% of arrivals on time, 46,281 arrivals, typically 1.9 min late
- 15:00: 69.1% of arrivals on time, 48,471 arrivals, typically 2.8 min late
- 16:00: 63.3% of arrivals on time, 55,166 arrivals, typically 3.3 min late
- 17:00: 65.2% of arrivals on time, 54,490 arrivals, typically 3.2 min late
- 18:00: 72.8% of arrivals on time, 49,915 arrivals, typically 2.5 min late
- 19:00: 76.7% of arrivals on time, 40,406 arrivals, typically 2 min late
- 20:00: 76.4% of arrivals on time, 38,293 arrivals, typically 2.4 min late
- 21:00: 78.3% of arrivals on time, 37,124 arrivals, typically 2.3 min late
- 22:00: 82.3% of arrivals on time, 29,404 arrivals, typically 1.8 min late
- 23:00: 89.4% of arrivals on time, 20,608 arrivals, typically 1 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 timetable7053801118186827311211718711 routes | 14:00 to 19:00 … 18:00 | 3.9 min late … 11.1 min late | More running time |
| ProblemOne hour collapses53111867011282747317318710 routes | 16:00 … 18:00 | 47% … 30% | Operations, not the timetable |
| ProblemUnreliable821172 routes | 16:00 · 15:00 | 32.8 min swing · 30.2 min swing | Operations, not the timetable |
| ProblemRunning early801 routes | 01:00 | 1.5 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 · 36 boundary vertices · City of Ottawa ward boundaries · imported Aug 4, 2026
How KNOXDALE-MERIVALE 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 322 route-hours. 4 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
84.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
50of 322
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 322
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
99.4%
Hours where the worst trips run less than twenty minutes behind the normal one.
Route-hours that are unpredictable
2of 322
Hours where they run twenty minutes or more behind it. Adding running time does not fix these.
How far behind a bad trip runs
31.5min
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.
Observed reliability
79.0% within five minutes. 199,150 of 252,127 settled OC Transpo arrivals at stops inside this ward were on time across 21 observed weekdays, from Aug 24, 2026 to Sep 22, 2026.
- On-time arrivals
- 199,150
- Settled arrivals
- 252,127
- Observed days
- 21 weekdays
How this compares
Ranked 9 of 22 measured wards. 1.3 points above the city median of 77.7%.
Highest: ward 22 at 85.6%. Lowest: ward 21 at 56.6%.
Only wards whose evidence meets the publication threshold are ranked. Same window and same method for each.
Which routes are pulling this ward down
17 of the 34 routes serving this ward have enough evidence to compare. Least punctual first.
| Route | Within five minutes | Arrivals checked |
|---|---|---|
| 53 | 67.9% | 94,713 |
| 70 | 71.6% | 109,074 |
| 81 | 71.7% | 104,860 |
| 111 | 72.1% | 82,877 |
| 80 | 73.8% | 134,445 |
| 73 | 75.7% | 28,655 |
| 187 | 77.5% | 3,181 |
| 82 | 78.6% | 67,603 |
| 88 | 79.4% | 118,701 |
| 86 | 81.7% | 56,680 |
17 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.
Routes serving the ward
34 scheduled routesPublic washrooms (City data) 5
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
- 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.
Share this page
Share this page
Use the permanent public link to this page and its sources.
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.
Evidence dates
- Imported
- Computed or assembled
- Sample
- 252,127 settled arrivals across 21 observed weekdays support the reliability result.
- Method or data version
- ward-counts-v1 + ward-stop-settled-arrivals-purpose-aware-v3
- Source checksum
- ward-reliability:478fabe906786ff4145d6a36a40cb2c9d089843bb3b2984c3f2aff2228860987
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.
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/9
- 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.
Contains information licensed under the Open Government Licence – City of Ottawa.