Skip to main content
Otranspo

Ward 3 · Ottawa

BARRHAVEN WEST

Councillor: David Hill

17
Routes
205
Stops
79.0%
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 3: BARRHAVEN WEST
Boundary and vintage
City ward layer · effective not published · imported August 4, 2026
Official civic contacts
  • David Hill · 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.

4 of 6 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.

5 of 6 routes here had something measurable to report.

Arrivals within five minutes, by hour of day, across the 6 routes graded here, last 14 days
  1. 00:00: 93.1% of arrivals on time, 3,925 arrivals, typically 0.3 min late
  2. 01:00: 93.1% of arrivals on time, 1,686 arrivals, typically 0.5 min late
  3. 02:00: 80.9% of arrivals on time, 1,667 arrivals, typically 0.9 min late
  4. 03:00: 89.8% of arrivals on time, 1,788 arrivals, typically 0.1 min early
  5. 04:00: 93.6% of arrivals on time, 4,294 arrivals, typically 0.9 min late
  6. 05:00: 91.9% of arrivals on time, 12,012 arrivals, typically 0.9 min late
  7. 06:00: 89.5% of arrivals on time, 19,558 arrivals, typically 1.2 min late
  8. 07:00: 82.2% of arrivals on time, 24,889 arrivals, typically 1.6 min late
  9. 08:00: 72.6% of arrivals on time, 23,472 arrivals, typically 2.3 min late
  10. 09:00: 80% of arrivals on time, 22,160 arrivals, typically 1.8 min late
  11. 10:00: 83.7% of arrivals on time, 22,165 arrivals, typically 1.3 min late
  12. 11:00: 79.7% of arrivals on time, 22,166 arrivals, typically 1.4 min late
  13. 12:00: 79.4% of arrivals on time, 22,130 arrivals, typically 1.7 min late
  14. 13:00: 75.7% of arrivals on time, 20,083 arrivals, typically 1.9 min late
  15. 14:00: 73.5% of arrivals on time, 19,526 arrivals, typically 2.2 min late
  16. 15:00: 63.6% of arrivals on time, 19,434 arrivals, typically 3.1 min late
  17. 16:00: 61.9% of arrivals on time, 22,975 arrivals, typically 3.4 min late
  18. 17:00: 67.8% of arrivals on time, 24,118 arrivals, typically 2.9 min late
  19. 18:00: 73.8% of arrivals on time, 23,865 arrivals, typically 2.3 min late
  20. 19:00: 77.9% of arrivals on time, 18,955 arrivals, typically 1.8 min late
  21. 20:00: 79.5% of arrivals on time, 16,481 arrivals, typically 2.3 min late
  22. 21:00: 79.3% of arrivals on time, 13,672 arrivals, typically 2.1 min late
  23. 22:00: 82.8% of arrivals on time, 9,981 arrivals, typically 1.7 min late
  24. 23:00: 88.1% of arrivals on time, 7,919 arrivals, typically 1 min late
  • 90% or more on time
  • 80 to 90% on time
  • under 80% on time
  • not enough data
WhatWhenMeasuredScenario or next investigation
ProblemLate by the timetable7080110994 routes14:00 to 19:00 … 04:003.9 min late … 3.2 min lateMore running time
ProblemOne hour collapses70110173994 routes15:00 … 14:0051% … 68%Operations, not the timetable
ProblemRunning early801 routes01:001.8 min earlyLess 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 · 34 boundary vertices · City of Ottawa ward boundaries · imported Aug 4, 2026

17 bus routes205 stops
Loading live feed

How BARRHAVEN WEST 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 125 route-hours. 1 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

87.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

15of 125

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 125

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

Running time a short hour needs

3.5min

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

100%

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

Route-hours that are unpredictable

0of 125

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

How far behind a bad trip runs

Not enough evidence this month to publish this indicator.

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.

Named ward measure79.0%within five minutes

Observed reliability

79.0% within five minutes. 106,874 of 135,282 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
106,874
Settled arrivals
135,282
Observed days
20 weekdays

How this compares

Ranked 8 of 22 measured wards. 1.4 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

6 of the 17 routes serving this ward have enough evidence to compare. Least punctual first.

RouteWithin five minutesArrivals checked
7071.6%105,484
11072.4%80,554
8074.0%129,150
9984.5%29,557
7586.2%100,677
17392.2%34,664

11 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

17 scheduled routes
Public washrooms (City data) 8

The public ward snapshot publishes the count but not the individual locations for this ward. No locations are being invented.

Drinking water (City data) 2

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

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.

Evidence dates

Imported
Computed or assembled
Sample
135,282 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:b8b274acddc88181ad7ef6a5194cf336199bb3d41ce5929de3a8e202fd104c84

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.

How do you want to address this draft?

Evidence included with the draft

Canonical Otranspo evidence link
https://otranspo.ca/en/city/wards/3
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.