ᐱᓗᐊᖅᑐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᒧᑦ ᐊᐅᓪᓚᕐᓗᑎᑦ

ᐱᔨᑦᑎᕐᓂᖅ

ᐊᔪᕐᓇᖅᑐᖅ ᐅᖃᐅᑎᒋᓗᒍ

This page is not about one stop, route, station or vehicle. Open one to have the report name it, or use the full report.

ᖃᓄᐃᓕᖓᓯᒪᕙ?
Full report No account needed

Ward 3 · Ottawa · Councillor: David Hill

Barrhaven West

Barrhaven West: 79.8% of predictions within five minutes.

Partial data · 2 days partly captured
ᑕᓪᓕᒪ ᒥᓂᑦ ᐃᓗᐊᓂ
79.8%
ᓂᕈᐊᕐᕕᖕᒥ ᓄᖅᑲᖅᑕᕐᕖᑦ
205
ᐊᖅᑯᑏᑦ ᐅᕗᖓ ᑎᑭᑦᑐᑦ
16
Cancelled trips
ᓱᓕ ᐱᔭᐅᔪᓐᓇᙱᑦᑐᖅ
ᓱᓕ ᓈᓴᐅᑎᓕᐅᕐᓯᒪᖏᑦᑐᖅ ᓂᕈᐊᕐᓂᕐᒧᑦ ᐊᕕᒃᓯᒪᓂᖏᓐᓂ.

ᓇᐅᓂ ᓱᑲᐃᓂᖅᐹᖑᔪᖅ

  • 80% ᐅᖓᑖᓄᓪᓗ 3
  • 60 ᐊᒻᒪ 80% ᐊᑯᓐᖓᓂ 3
  • 60%-ᒥᑦ ᒥᑭᓐᓂᖅᓴᖅ 0
  • ᑐᓴᒐᒃᓴᑦ ᐊᒥᓲᙱᑦᑐᑦ 10

ᐊᖁᑏᑦ ᓄᓇᓕᐅᑉ ᐃᓚᖓᓂ ᐃᖏᕐᕋᔪᑦ, ᑕᓪᓕᒪᓂ ᒥᓂᑦᓯᓂ ᐃᓗᐊᓂ ᐱᕕᒃᓴᖓᓂ ᑎᑭᑦᑐᑦ ᖃᔅᓰᓐᓂᖏᑦ ᒪᓕᒡᓗᒋᑦ. ᐊᖁᑦ ᐊᑐᓂ ᐊᖁᑎᒥ ᑕᒪᐃᓐᓂ ᓈᓴᐅᑎᖃᖅᐳᖅ.

Routes in this ward

ᐃᖏᕐᕋᕝᕕᐅᔪᑦ ᐅᕙᓂ ᓂᕈᐊᕐᕕᒃᑯᑦ ᐃᓚᖓᓂ. ᑭᖑᕙᖅᐸᓪᓕᐊᓂᐹᑦ ᓯᕗᓪᓕᐅᓪᓗᑎᒃ.
ᐊᖁᑎ5 ᒥᓂᑦ ᐃᓗᐊᓂCancelledᐃᓄᒋᓐᓂᖓ
7071.6%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
11071.6%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
8074.2%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
9983.5%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
7587.8%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
17393.5%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ

Cancellations and crowding are not published per route yet. 10 routes with too little data or a different service purpose are left out.

ᐊᖅᑯᑏᑦ ᑕᒪᐃᓐᓂ ᐊᒻᒪ ᓇᑭᙶᕐᓂᖏᑦ

One-page brief

ᓇᐃᑦᑐᒥᒃ ᑎᑎᕋᖅᓯᒪᔪᖅ ᓇᖏᖅᑎᑕᐅᔪᓐᓇᖅᑐᖅ ᐅᓇ ᓂᕈᐊᕐᓂᕐᒧᑦ ᐊᕕᒃᑐᖅᓯᒪᔪᒧᑦ, ᑲᑎᒪᔨᑦ ᓄᓇᓕᓪᓗ ᑲᑎᒪᓂᖏᓐᓄᑦ. ᐊᔾᔨᒋᔭᐅᔪᑦ ᓈᓴᐅᑏᑦ, ᖃᓄᖅ ᐱᓕᕆᓯᒪᓂᖅ ᐅᖃᐅᓯᕐᓂ ᐱᑐᙱᑦᑐᓂ, ᓇᑭᙶᕐᓂᖏᓪᓗ ᐅᓪᓗᖃᖅᑐᑦ.

What can be verified in Barrhaven West?

ᑎᑭᕐᕕᒃᓴᖏᑦ ᐃᓱᒪᒋᔭᐅᔪᑦ, ᐊᐅᓪᓚᕐᕕᒃᓴᐃᑦ ᐊᑐᐊᒐᖏᑦ, ᐊᒻᒪ ᑐᕇᓐ ᐱᓗᒍ ᑐᓴᖅᑎᑦᑎᔾᔪᑎᑦ. ᐊᑐᓂ ᓴᖅᑭᑕᐅᔪᑦ ᓇᑭᓐᖓᐅᓂᖏᓐᓂᒃ.

ᐱᔨᑦᑎᔨᐅᑉ ᓇᓚᐅᑦᑖᖅᑕᖏᑦ ᐊᖏᖃᑎᒌᖕᓂᖏᑦ

79.8%

of eligible predictions within five minutes of schedule

ᐊᓯᖏᓐᓄᑦ ᓇᓚᐅᑦᑖᖅᑕᐅᓂᖓ
Rank 8 of 22 · median 78.4%

ᐱᔨᑦᑎᕋᐅᑎ, ᐱᕕᒃᓴᐃᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ ᐃᓕᔭᐅᓯᒪᔪᑦ ᒪᓕᒡᓗᒋᑦ

Scheduled trips at ward stops
ᓱᓕ ᐱᔭᐅᔪᓐᓇᙱᑦᑐᖅ
ᐊᖁᑏᑦ
16
ᑐᕇᓐ ᐊᖅᑯᑎᖏᑦ
0

ᒫᓐᓇ ᐱᔨᑦᑎᕋᐅᑦ ᑭᒡᓕᐅᑉ ᐃᓗᐊᓂ

ᒫᓐᓇ ᐃᖏᕐᕋᔪᑦ ᐳᓯᑦ ᑖᔅᓱᒪ ᑭᒡᓕᐅᑉ ᐃᓗᐊᓂ ᑕᑯᔭᐅᔪᓐᓇᖅᑐᑦ ᓄᓇᙳᐊᖅ ᒪᒃᐱᒐᖓᓂ.

ᓂᕆᐅᒋᔭᐅᔪᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕐᓂᖏᑦ, ᐃᓕᓯᒪᔪᑦ ᐱᕕᒃᓴᐃᑦ, ᐊᒻᒪ ᐱᓕᕆᔾᔪᑏᑦ

Service delivery · evidence state

Oct 28, 2026 – Nov 3, 2026

Cancellations at stops in this ward

Not publishable

No zero or missed trip is inferred when exact stop calls cannot be published.

Predictions at stops inside the ward

79.8% within five minutes of the timetable across 213,134 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, 2026

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

Scheduled calls, sources and limits

16 routes · 205 stops. Timetable inventory, not trips delivered.

Cancellations at stops in this ward

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.

ᐃᓱᓕᑦᑎᓂᖅ

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 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 173, predictions consistently close to timetable, 96%.

6 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: 94.7% of final predictions within five minutes of the timetable, 3,342 predictions, typically 0.1 min late
  2. 01:00: 92.8% of final predictions within five minutes of the timetable, 1,782 predictions, typically 0.8 min late
  3. 02:00: 81.5% of final predictions within five minutes of the timetable, 1,626 predictions, typically 0.7 min late
  4. 03:00: 90% of final predictions within five minutes of the timetable, 1,726 predictions, typically 0.4 min late
  5. 04:00: 90.3% of final predictions within five minutes of the timetable, 3,989 predictions, typically 1.1 min late
  6. 05:00: 86.3% of final predictions within five minutes of the timetable, 11,019 predictions, typically 1 min late
  7. 06:00: 87.4% of final predictions within five minutes of the timetable, 18,187 predictions, typically 1.2 min late
  8. 07:00: 81.4% of final predictions within five minutes of the timetable, 23,367 predictions, typically 1.5 min late
  9. 08:00: 76% of final predictions within five minutes of the timetable, 21,694 predictions, typically 1.8 min late
  10. 09:00: 82.9% of final predictions within five minutes of the timetable, 20,255 predictions, typically 1.3 min late
  11. 10:00: 83.7% of final predictions within five minutes of the timetable, 20,386 predictions, typically 1 min late
  12. 11:00: 80.6% of final predictions within five minutes of the timetable, 20,302 predictions, typically 1.5 min late
  13. 12:00: 82% of final predictions within five minutes of the timetable, 20,486 predictions, typically 1.5 min late
  14. 13:00: 79% of final predictions within five minutes of the timetable, 19,885 predictions, typically 1.9 min late
  15. 14:00: 76.9% of final predictions within five minutes of the timetable, 19,655 predictions, typically 1.7 min late
  16. 15:00: 66.1% of final predictions within five minutes of the timetable, 19,613 predictions, typically 3.2 min late
  17. 16:00: 67.1% of final predictions within five minutes of the timetable, 22,950 predictions, typically 3 min late
  18. 17:00: 69% of final predictions within five minutes of the timetable, 24,162 predictions, typically 2.6 min late
  19. 18:00: 68.8% of final predictions within five minutes of the timetable, 23,887 predictions, typically 2.7 min late
  20. 19:00: 80.3% of final predictions within five minutes of the timetable, 19,320 predictions, typically 1.7 min late
  21. 20:00: 79.3% of final predictions within five minutes of the timetable, 16,412 predictions, typically 1.9 min late
  22. 21:00: 79.6% of final predictions within five minutes of the timetable, 13,320 predictions, typically 1.9 min late
  23. 22:00: 79.1% of final predictions within five minutes of the timetable, 9,814 predictions, typically 2 min late
  24. 23:00: 88.7% of final predictions within five minutes of the timetable, 7,641 predictions, typically 1 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
Findings
WhatᖃᖓᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅScenario or next investigation
ProblemPredictions later than timetable7011080994 routes15:00 to 19:00 … 23:003.9 min late … 3.1 min lateMore running time
StrengthPredictions consistently close to timetable1731 routes04:00 to 00:0096%Keep what works
ProblemOne hour has a lower prediction match701 routes15:0052%Operations, not the timetable
ProblemPredictions earlier than timetable1101 routes21:001.6 min earlyLess running time, or holding points
ProblemWide prediction spread801 routes04:0033 min swingOvernight operations
StrengthObserved-position lower bound75991733 routesAll measured hours100%Keep what works
CaveatCoverage gap70110803 routesAll measured hours99% · 100%More observation, not a service change

How BARRHAVEN WEST is doing

ᑖᒃᑯᐊ ᓇᓗᓇᐃᒃᑯᑕᐃᑦ ᐊᕕᒃᑐᐃᔪᑦ ᐅᑎᖅᑕᖅᐸᒃᑐᒥᒃ ᑭᖑᕙᕐᓂᕐᒥᒃ ᐊᒻᒪ ᐱᓕᕆᕝᕕᐅᑉ ᑎᑭᓐᓂᐊᕐᓂᖏᑦ ᐃᓱᒪᒋᔭᖏᑦ ᐊᓯᔾᔨᖅᐸᓐᓂᖏᓐᓂᒃ. ᐊᐱᖁᑎᓂᒃ ᐃᓱᒪᒋᐊᖅᑎᑦᑎᔪᑦ ᐸᕐᓇᐃᔨᓄᑦ ᐊᒻᒪ ᐱᓕᕆᔨᓄᑦ. ᐱᔾᔪᑎᖓ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ. ᐱᐊᓯᑦ ᖃᖓ ᑎᑭᒻᒪᖔᑕ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ. ᓈᓴᐅᑎ ᑕᒪᐃᓐᓂ ᑕᑯᒃᓴᐅᑎᑦᑎᔪᖅ ᖃᑦᓯᓂᒃ ᐃᖏᕐᕋᕝᕕᒃ-ᐃᑲᕐᕋᓂᒃ ᐊᑐᖅᓯᒪᒻᒪᖔᑦ.

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

ᐃᑲᕐᕋᓄᑦ ᐋᖅᑭᒃᓯᓂᖅ

ᐊᑯᓂ ᑭᖑᕙᕐᓂᖏᑦ ᓂᕆᐅᒋᔭᐅᔪᑦ ᑕᑯᑎᑦᑎᔪᓐᓇᖅᑐᑦ ᐃᑲᕐᕋᓕᐊᖑᔪᖅ ᕿᒥᕐᕈᔭᐅᒃᓴᐅᓂᖓᓂᒃ. ᕿᒥᕐᕈᓗᒋᑦ ᑎᑭᑦᑐᑦ ᐃᑲᕐᕋᖏᑦ ᐊᒻᒪ ᐊᐅᓪᓚᑎᑦᑎᓂᕐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ. ᑕᐃᒪ ᐃᓱᒪᓕᐅᕐᓗᑎᑦ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐱᕕᒃ ᐊᓯᔾᔨᕆᐊᖃᕐᒪᖔᑦ.

ᑭᓇ ᐋᖅᑭᒃᓯᔪᓐᓇᖅᐸ
ᐃᖏᕐᕋᓂᕐᒧᑦ ᐸᕐᓇᐃᔨ
ᖃᓄᖅ ᐊᑭᖃᖅᐸ
ᐊᑭᖏᑦ ᓇᓗᓇᖅᐳᑦ ᓱᓕ. ᖃᐅᔨᓴᖅᑕᐅᔭᕆᐊᖃᖅᐳᑦ ᐊᖅᑲᐅᑏᑦ, ᐃᖅᑲᓇᐃᔭᖅᑏᑦ, ᐊᑭᓕᖅᑕᐅᓂᖏᑦ ᐊᒻᒪ ᐊᓯᔾᔨᖅᓯᓂᖏᑦ.

ᓇᓚᐅᑦᑖᖅᑕᐅᓯᒪᔪᑦ ᐃᑲᕐᕋᐃᑦ ᐊᓪᓚᓯᒪᔪᓂᒃ ᖃᓂᒋᔭᖃᖅᑐᑦ

87.9%

Route-hours where the median eligible arrival prediction is less than one minute early and less than three minutes late.

ᐊᖅᑯᑎᐅᑉ ᐃᑲᕐᕋᖏᑦ ᑭᖑᕙᕆᐊᖃᑦᑕᕐᓂᐊᖅᑐᖅ ᐅᖃᐅᓯᐅᖃᑦᑕᖅᑐᑦ

14of 124

ᐃᖏᕐᕋᕝᕕᐅᑉ ᐃᑲᕐᕋᖏᑦ, ᑎᑭᓂᐊᕐᓂᖏᑦ ᓂᕆᐅᒋᔭᐅᔪᑦ ᐊᑯᓐᓂᐊᓂ ᐱᖓᓱᓂᒃ ᒥᓂᑦᓂᒃ ᐅᖓᑖᓄᓪᓘᓐᓃᑦ ᑭᖑᕙᖅᑐᑦ. ᐃᖏᕐᕋᓂᖓᑕ ᐊᑯᓐᓂᖓ ᖃᐅᔨᓴᕐᓗᒍ ᐃᖏᕐᕋᓂᕐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᓂᒃ ᓴᓂᐊᓂᒃ.

ᐃᖏᕐᕋᕝᕕᐃᑦ ᐃᑲᕐᕋᖏᑦ, ᐸᔅ ᓯᕗᓪᓕᐅᕐᓂᐊᕐᓂᖓᓂᒃ ᓇᓚᐅᑦᑖᖅᑕᐅᑎᓪᓗᒍ

1of 124

ᐊᖁᑎ ᐃᑲᕐᕋᖏᑦ, ᑕᐃᑦᓱᒪᓂ ᑎᑭᓐᓂᐊᕐᓂᖓᓄᑦ ᓇᓚᐅᑦᑖᕐᓂᖅ ᐊᑯᓐᓂᐊᓂ ᓯᕗᓪᓕᐅᕐᓂᐊᖅᑐᖅ ᐊᑕᐅᓯᕐᒥᒃ ᒥᓂᑦᒥᒃ ᐅᖓᑖᓄᓪᓘᓃᑦ. ᐅᓇ ᓇᓗᓇᐃᖅᓯᙱᑦᑐᖅ ᐸᓯᑦ ᓯᕗᓪᓕᐅᖅᖢᑎᒃ ᐊᐅᓪᓚᓚᐅᖅᓯᒪᓂᖏᓐᓂᒃ.

ᑭᖑᕙᕆᐊᕐᓂᖅ ᓂᕆᐅᒋᔭᐅᑦᑕᐃᓐᓇᖅᑐᖅ

3.7min

ᑭᖑᕙᕆᐊᖃᕐᓂᖅ ᐊᑐᐃᓐᓇᐅᓂᖅᐹᖅ ᓂᕆᐅᒋᔭᐅᔪᖅ ᐃᖏᕐᕋᕝᕕᓐᓂ ᓇᓗᓇᐃᖅᑕᐅᓯᒪᔪᓂ. ᐅᓇ ᓇᓗᓇᐃᖅᑕᐅᑦᑎᐊᖏᑦᑐᖅ ᐃᓚᓗᒍ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐱᕕᒃᓴᓄᑦ.

ᐊᐅᓚᑦᑎᓂᖅ

ᑎᑭᑉᐸᓐᓂᖏᑦ ᓇᓚᐅᑦᑖᖅᑕᐅᔪᑦ ᐊᔾᔨᒌᙱᑦᑐᐊᓘᒐᐃ, ᐱᓕᕆᓂᖅ ᕿᒥᕐᕈᐊᖅᑕᐅᑦᑎᐊᕆᐊᖃᖅᐳᖅ. ᐊᖅᑯᑎᒥ ᐅᓄᖅᑐᑦ ᐃᖏᕐᕋᔪᑦ, ᐊᐅᓪᓚᑦᑎᓂᖅ, ᐃᑭᓂᖅ ᐊᒻᒪ ᐱᓇᓱᐊᕈᓯᐅᑉ ᐋᖅᑭᒃᓯᒪᓂᖓ ᐱᔾᔪᑎᐅᒍᓐᓇᖅᑐᑦ. ᑖᒃᑯᐊ ᓇᓚᐅᑦᑖᖅᑕᐅᔪᑦ ᑭᓯᐊᓂ ᓇᓗᓇᐃᖅᓯᒍᓐᓇᙱᑦᑐᑦ ᐱᔾᔪᑎᒥᒃ ᐋᖅᑭᒋᐊᕈᑎᒥᒡᓘᓐᓃᑦ.

ᑭᓇ ᐋᖅᑭᒃᓯᔪᓐᓇᖅᐸ
ᐊᐅᓚᑦᑎᔨᑦ. ᐊᒥᓲᓂᖏᓐᓂ ᐊᖅᑯᓯᓂᖅ ᓇᒻᒥᓂᖅ.
ᖃᓄᖅ ᐊᑭᖃᖅᐸ
ᐊᑭᖓ ᒫᓐᓇ ᓇᓗᓇᖅᑐᖅ. ᐱᔾᔪᑎᖓ ᐋᖅᑭᒋᐊᕈᑎᖓᓗ ᓇᓗᓇᐃᖅᑕᐅᓚᐅᖅᐸᑦ, ᐊᑭᖓ ᓇᓗᓇᐃᖅᑕᐅᓂᐊᖅᑐᖅ.

ᓂᕆᐅᒋᔭᐅᔪᖅ ᐊᑯᓐᓂᖓ ᑐᐌᓐᑎ-ᒥᓂᑦ ᐊᑖᓂ

99.2%

ᐊᖁᑎ-ᐃᑲᕐᕋᐃᑦ ᐅᑯᐊ: 95-ᐳᓴᓐᑎ ᓇᓚᐅᑦᑖᖅᑕᐅᔪᑦ ᐊᑐᕐᑕᐅᔪᓐᓇᖅᑐᑦ ᑐᐃᓐᑎ ᒥᓂᑦ ᐅᖓᑖᓄᑦ ᑭᖑᕙᖏᑦᑐᑦ ᕿᑎᐊᓃᑦᑐᒥᑦ.

ᐃᖏᕐᕋᕝᕕᐅᑉ ᐃᑲᕐᕋᖏᑦ ᓇᓚᐅᑦᓯᓂᖅ ᐊᔾᔨᒌᙱᑦᑑᓗᐊᖅᑎᓪᓗᒍ

1of 124

ᐊᖁᑦ-ᐃᑲᕐᕋᐃᑦ, 95-ᐳᓴᓐᑎᐊᓪ ᓂᕆᐅᒋᔭᐅᔪᖅ ᑭᖑᕙᖅᑐᖅ ᐊᑯᓐᓂᖓᓂᑦ ᑐᐃᓐᑎ ᒥᓂᑦ ᐅᖓᑖᓄᓪᓗ. ᐱᔾᔪᑎᖓ ᖃᐅᔨᓴᕐᑕᐅᔭᕆᐊᖃᖅᑐᖅ.

ᓂᕆᐅᒋᔭᐅᔪᒥᑦ ᐊᔾᔨᒌᙱᓐᓂᖓ ᑕᐃᒪᐃᖃᑦᑕᖅᑐᖅ

33min

ᐊᑯᓐᓂᖓ 95-ᒥ ᐳᓴᓐᑎᒥ ᑕᑯᓐᓇᐅᑎᐅᑉ ᖃᑎᒻᒥᓗ, ᓇᓗᓇᐃᖅᑕᐅᓯᒪᔪᓂ ᐃᖏᕐᕋᕝᕕᓂ ᐃᑲᕐᕋᓂ.

ᐱᔨᑦᑎᕋᐅᑎ, ᐱᕕᒃᓴᐃᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ ᐃᓕᔭᐅᓯᒪᔪᑦ ᒪᓕᒡᓗᒋᑦ

Scheduled transit, provider prediction agreement with the timetable, and public services in this ward.

ᐱᔨᑦᑎᔨᐅᑉ ᓇᓚᐅᑦᑖᖅᑕᖏᑦ ᐊᖏᖃᑎᒌᖕᓂᖏᑦ

79.8% of eligible provider predictions were within five minutes of the timetable. 170,131 of 213,134 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
170,131
Eligible trip-stop predictions
213,134
Observed days
20 weekdays

ᐊᓯᖏᓐᓄᑦ ᓇᓚᐅᑦᑖᖅᑕᐅᓂᖓ

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

6 of the 16 routes serving this ward have enough provider-prediction evidence to compare. Lowest timetable agreement first.

  1. 70Open route
    71.6%Predictions within five minutes

    150,278 eligible predictions across the whole route

  2. 110Open route
    71.6%Predictions within five minutes

    113,377 eligible predictions across the whole route

  3. 80Open route
    74.2%Predictions within five minutes

    181,776 eligible predictions across the whole route

  4. 99Open route
    83.5%Predictions within five minutes

    41,425 eligible predictions across the whole route

  5. 75Open route
    87.8%Predictions within five minutes

    147,656 eligible predictions across the whole route

  6. 173Open route
    93.5%Predictions within five minutes

    49,389 eligible predictions across the whole route

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

Routes serving the ward

16 scheduled routes

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

━ 16 bus routes● 205 stops
Loading live feed

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

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 ᑐᓴᖅᑎᑕᐅᓚᐅᖏᑦᑐᖅ · 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 · ᒪᐃᔭ · 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: ᑐᓴᖅᑎᑕᐅᓚᐅᖏᑦᑐᖅ · 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.

ᑖᑦᓱᒪ ᒪᑉᐱᒐᐅᑉ ᓇᓗᓇᐃᖅᓯᒍᑎᖏᑦᐅᒃᑯᐃᓗᒍ ᑐᑭᖓ, ᖃᓄᖅ ᐱᓕᕆᓯᒪᓂᖅ, ᓇᑭᙶᕐᓂᖏᑦ, ᐅᓪᓗᖏᑦ, ᓇᒧᑦ ᐊᐅᓚᓂᖏᑦ, ᐊᒻᒪ ᑭᒡᓕᖏᑦ ᖃᐅᔨᒪᔭᐅᔪᑦ.

ᓴᖅᑭᑎᑕᐅᔪᑦ

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.

ᓇᓗᓇᐃᖅᓯᒍᑏᑦ ᐅᓪᓗᖏᑦ

ᐃᓯᖅᑎᑕᐅᓯᒪᔪᖅ
ᓈᓴᐅᑎᓕᐅᖅᑕᐅᔪᖅ ᐅᕝᕙᓘᓐᓃᑦ ᑲᑐᔾᔨᖅᑕᐅᔪᖅ
ᐆᒃᑐᕋᐅᑎ
213,134 eligible settled provider predictions across 20 weekdays with prediction evidence support the reliability result.
ᐱᓕᕆᓯᐊ ᐅᕝᕙᓘᓐᓃᑦ ᑎᑎᖅᑲᑦ ᓄᑖᓕᐊᖏᑦ
ward-counts-v1 + ward-stop-settled-arrivals-purpose-aware-v3
ᓇᑭᙶᕐᓂᖓᑕ ᓇᓗᓇᐃᒃᑯᑕᖓ
ward-reliability:6b10d085eb86bf78c2676b6552814eff63f045f3e7950d97593c82718dc73164

ᓇᑭᑦ ᑐᓴᒐᒃᓴᐃᑦ

ᑭᒡᓕᖏᑦ ᐃᖅᑲᐅᒪᔭᐅᑎᐊᕆᐊᓖᑦ

  • ᓈᓴᐅᑏᑦ ᓇᓗᓇᐃᖅᓯᔪᑦ ᑎᑎᕋᖅᓯᒪᔪᓂᒃ ᑭᒡᓕᐅᑉ ᐃᓗᐊᓂ. ᓇᓗᓇᐃᖅᓯᙱᑦᑐᑦ ᐱᔨᑦᑎᕋᐅᑎᐅᑉ ᐱᐅᓂᖓᓂᒃ. ᐊᒻᒪ ᓇᓗᓇᐃᖅᓯᙱᑦᑐᑦ ᐃᓪᓗᓂ ᑕᒪᐃᓐᓂᑦ ᐊᑐᕈᓐᓇᕐᓂᖓᓂᒃ.
  • ᐱᕕᒃᓴᖓᓂ ᑎᑭᑦᑕᕐᓂᖓ ᐃᓗᓕᖃᖅᐳᖅ OC Transpo ᓂᕆᐅᒋᔭᖏᓐᓂᒃ ᑭᖑᓪᓕᖅᐹᖑᔪᓂᒃ. ᑖᒃᑯᐊ ᓄᖃᖅᑕᕐᕕᓐᓂ ᐱᖃᑕᐅᔪᑦ ᓄᓇᒥ ᐃᓂᖏᑦ ᒪᓕᑦᑐᒋᑦ. ᑎᑭᑦᑕᕐᓂᖏᑦ ᓱᓕᔪᑦ ᐊᓯᐊᒍᑦ ᓇᓗᓇᐃᖅᑕᐅᙱᑦᑐᑦ. O-Train ᐃᓗᓕᐅᙱᑦᑐᖅ. ᐃᖏᕐᕋᓂᐅᔪᑦ ᓂᕆᐅᒋᔭᐅᔪᓂᒃ ᐊᑐᐃᓐᓇᐅᔪᓂᒃ ᐱᑕᖃᙱᑦᑐᑦ ᐃᓗᓕᐅᙱᑦᑐᑦ ᐊᒻᒪ.
  • An unavailable count remains unavailable. It is not changed to zero.
ᓱᓕᔪᒥᒃ ᐋᖅᑭᒋᐊᕐᓂᕐᒥᒃ ᐊᑐᓕᖁᔨᓗᑎᑦ
ᖃᓄᖅ ᓈᓴᐃᕙᒻᒪᖔᑦᑕ

ᐃᖏᕐᕋᓂᕐᒧᑦ ᐊᑐᓂ, ᓄᖅᑲᖓᕝᕕᒧᑦ ᐊᑐᓂ ᐊᒻᒪ ᐅᓪᓗᒧᑦ ᐊᑐᓂ, ᓄᖅᑲᖓᕝᕕᓂ ᓂᕈᐊᕐᓂᕐᒧᑦ ᐊᕕᒃᑐᖅᓯᒪᓂᐅᑉ ᐃᓗᐊᓂ, ᑐᖓᓕᖅᐹᖅ OC Transpo-ᑯᑦ ᓇᓚᐅᑦᑖᖅᑕᖏᑦ ᑎᑭᓂᐊᕐᓂᖓᓂᒃ ᐱᑦᑎᐊᖅᑕᕗᑦ. ᑕᑭᒋᐊᖅᑕᕗᑦ ᐊᐅᓚᓂᕐᒧᑦ ᐸᕐᓇᐅᑎᒥᒃ. ᑕᓪᓕᒪ ᒥᓂᑦ ᐃᓗᐊᓂ ᐱᔪᖅ ᐅᑯᐊ ᒪᕐᕉᒃ ᑕᓪᓕᒪ ᒥᓂᑦ ᐅᖓᑖᓂ ᐊᔾᔨᒌᙱᑦᑐᓐᓂᐅᙱᑉᐸᑕ. ᑕᒪᓐᓇ ᑎᑭᑦᑐᓐᓃᑦᑐᖅ ᑕᑯᔭᐅᓯᒪᔪᐃᑦ ᐅᙱᑦᑐᖅ.

ᐱᕝᕕᒃ ᑭᖑᓪᓕᖅᐹᑦ 28 ᐅᓪᓗᐃᑦ ᐃᖏᕐᕋᓂᖅ ᐱᐊᓂᒃᑕᐅᓚᐅᖅᑐᑦ. ᐱᐊᓂᒃᓯᓂᖅ ᓴᖅᑭᑕᐅᖃᑦᑕᖅᑐᖅ 20 ᐱᓇᓱᐊᕐᕕᐅᔪᑦ ᐅᓪᓗᑦ ᑐᓴᒐᒃᓴᖃᕈᓂ, 500-ᓗ ᓯᕗᓂᒃᓴᒧᑦ ᓇᓚᐅᑦᑖᕆᓂᕐᓂᒃ ᐊᑐᕐᓂᖃᖅᑐᓂᒃ. ᐊᖅᑯᑎᓄᑦ ᐱᐊᓂᒃᓯᓂᐅᔪᑦ ᐊᖅᑯᑎ ᐃᓘᓐᓇᖓ ᐱᔭᐅᕗᖅ. ᓂᕈᐊᕐᓂᕐᒧᑦ ᐃᓂᐅᑉ ᐃᓗᐊᓂ ᐃᓚᖓ ᑭᓯᐊᓂ ᐱᔭᐅᓐᖏᑦᑐᖅ.

Read the full method

Contains information licensed under the Open Government Licence – City of Ottawa.