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

ᐱᔨᑦᑎᕐᓂᖅ

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

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 19 · Ottawa · Councillor: Catherine Kitts

Orléans South-Navan

Orléans South-Navan: 78.6% of predictions within five minutes.

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

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

  • 80% ᐅᖓᑖᓄᓪᓗ 5
  • 60 ᐊᒻᒪ 80% ᐊᑯᓐᖓᓂ 4
  • 60%-ᒥᑦ ᒥᑭᓐᓂᖅᓴᖅ 1
  • ᑐᓴᒐᒃᓴᑦ ᐊᒥᓲᙱᑦᑐᑦ 17

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

Routes in this ward

ᐃᖏᕐᕋᕝᕕᐅᔪᑦ ᐅᕙᓂ ᓂᕈᐊᕐᕕᒃᑯᑦ ᐃᓚᖓᓂ. ᑭᖑᕙᖅᐸᓪᓕᐊᓂᐹᑦ ᓯᕗᓪᓕᐅᓪᓗᑎᒃ.
ᐊᖁᑎ5 ᒥᓂᑦ ᐃᓗᐊᓂCancelledᐃᓄᒋᓐᓂᖓ
3257.8%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
3170.3%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
2471.4%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
2577.0%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
3078.3%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
3980.2%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
3482.0%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ
3382.1%ᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅᓴᖅᑭᑕᐅᓯᒪᙱᑦᑐᖅ

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

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

One-page brief

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

What can be verified in Orléans South-Navan?

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

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

78.6%

of eligible predictions within five minutes of schedule

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

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

Scheduled trips at ward stops
ᓱᓕ ᐱᔭᐅᔪᓐᓇᙱᑦᑐᖅ
ᐊᖁᑏᑦ
27
ᑐᕇᓐ ᐊᖅᑯᑎᖏᑦ
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

78.6% within five minutes of the timetable across 179,505 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

27 routes · 309 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.

    ᐃᓱᓕᑦᑎᓂᖅ

    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.

    9 of 10 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 24, predictions later than timetable 14:00 to 19:00, 4.3 min late.

    Best here: route 30, observed-position lower bound, 100%.

    10 of 10 routes here had something measurable to report.

    Arrivals within five minutes, by hour of day, across the 10 routes graded here, last 14 days
    1. 00:00: 95.6% of final predictions within five minutes of the timetable, 2,613 predictions, typically 0.9 min late
    2. 01:00: 87.5% of final predictions within five minutes of the timetable, 2,073 predictions, typically 0.7 min late
    3. 02:00: 81.5% of final predictions within five minutes of the timetable, 1,766 predictions, typically 1 min late
    4. 03:00: 80.4% of final predictions within five minutes of the timetable, 1,748 predictions, typically 1.4 min late
    5. 04:00: 80.9% of final predictions within five minutes of the timetable, 2,409 predictions, typically 1.6 min late
    6. 05:00: 88.8% of final predictions within five minutes of the timetable, 6,979 predictions, typically 1.3 min late
    7. 06:00: 88.7% of final predictions within five minutes of the timetable, 17,039 predictions, typically 1 min late
    8. 07:00: 75% of final predictions within five minutes of the timetable, 24,528 predictions, typically 2 min late
    9. 08:00: 72.7% of final predictions within five minutes of the timetable, 25,272 predictions, typically 2.5 min late
    10. 09:00: 80.1% of final predictions within five minutes of the timetable, 23,611 predictions, typically 1.7 min late
    11. 10:00: 83.2% of final predictions within five minutes of the timetable, 24,346 predictions, typically 1.6 min late
    12. 11:00: 83.3% of final predictions within five minutes of the timetable, 24,418 predictions, typically 1.6 min late
    13. 12:00: 82.8% of final predictions within five minutes of the timetable, 24,413 predictions, typically 1.9 min late
    14. 13:00: 79.8% of final predictions within five minutes of the timetable, 24,340 predictions, typically 2.1 min late
    15. 14:00: 75.7% of final predictions within five minutes of the timetable, 25,242 predictions, typically 2.3 min late
    16. 15:00: 73.2% of final predictions within five minutes of the timetable, 26,675 predictions, typically 2.5 min late
    17. 16:00: 63% of final predictions within five minutes of the timetable, 25,870 predictions, typically 3.5 min late
    18. 17:00: 65.1% of final predictions within five minutes of the timetable, 27,407 predictions, typically 3 min late
    19. 18:00: 71.2% of final predictions within five minutes of the timetable, 25,209 predictions, typically 2.3 min late
    20. 19:00: 78.3% of final predictions within five minutes of the timetable, 21,136 predictions, typically 2.1 min late
    21. 20:00: 84.7% of final predictions within five minutes of the timetable, 20,133 predictions, typically 1.4 min late
    22. 21:00: 81.7% of final predictions within five minutes of the timetable, 18,263 predictions, typically 1.8 min late
    23. 22:00: 81.6% of final predictions within five minutes of the timetable, 12,128 predictions, typically 2 min late
    24. 23:00: 85.6% of final predictions within five minutes of the timetable, 8,260 predictions, typically 1.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 timetable2431253332393036349 routes14:00 to 19:00 … 05:004.3 min late … 3.8 min lateMore running time
    ProblemWide prediction spread241 routes16:0025.5 min swingOperations, not the timetable
    ProblemOne hour has a lower prediction match24253330343536328 routes16:00 … 19:0042% … 25%Operations, not the timetable
    StrengthObserved-position lower bound303534314 routesAll measured hours100%Keep what works
    CaveatCoverage gap3925363324326 routesAll measured hours98% · 99%More observation, not a service change

    How ORLÉANS SOUTH-NAVAN is doing

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

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

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

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

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

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

    78.3%

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

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

    41of 189

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

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

    0of 189

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

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

    3.5min

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

    ᐊᐅᓚᑦᑎᓂᖅ

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

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

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

    99.5%

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

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

    1of 189

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

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

    25.5min

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

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

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

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

    78.6% of eligible provider predictions were within five minutes of the timetable. 141,082 of 179,505 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
    141,082
    Eligible trip-stop predictions
    179,505
    Observed days
    20 weekdays

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

    Ranked 11 of 22 measured wards. 0.2 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

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

    1. 32Open route
      57.8%Predictions within five minutes

      10,325 eligible predictions across the whole route

    2. 31Open route
      70.3%Predictions within five minutes

      84,248 eligible predictions across the whole route

    3. 24Open route
      71.4%Predictions within five minutes

      129,384 eligible predictions across the whole route

    4. 25Open route
      77.0%Predictions within five minutes

      150,538 eligible predictions across the whole route

    5. 30Open route
      78.3%Predictions within five minutes

      65,667 eligible predictions across the whole route

    6. 39Open route
      80.2%Predictions within five minutes

      87,906 eligible predictions across the whole route

    7. 34Open route
      82.0%Predictions within five minutes

      66,687 eligible predictions across the whole route

    8. 33Open route
      82.1%Predictions within five minutes

      72,386 eligible predictions across the whole route

    9. 36Open route
      86.6%Predictions within five minutes

      58,190 eligible predictions across the whole route

    10. 35Open route
      87.4%Predictions within five minutes

      61,617 eligible predictions across the whole route

    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

    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

    27 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 · 56 boundary vertices · City of Ottawa ward boundaries · imported Aug 4, 2026

    ━ 27 bus routes● 309 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) 4

    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 19: ORLÉANS SOUTH-NAVAN
    Boundary and vintage
    City ward layer · effective ᑐᓴᖅᑎᑕᐅᓚᐅᖏᑦᑐᖅ · imported August 4, 2026
    Official civic contacts
    • Catherine Kitts · 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
    27 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.

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

    ᐃᓯᖅᑎᑕᐅᓯᒪᔪᖅ
    ᓈᓴᐅᑎᓕᐅᖅᑕᐅᔪᖅ ᐅᕝᕙᓘᓐᓃᑦ ᑲᑐᔾᔨᖅᑕᐅᔪᖅ
    ᐆᒃᑐᕋᐅᑎ
    179,505 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:baf34788f72099b4da00e7daccbcbc37ee1fbb8a46f9ba50c403b412d7b07a26

    ᓇᑭᑦ ᑐᓴᒐᒃᓴᐃᑦ

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

    • ᓈᓴᐅᑏᑦ ᓇᓗᓇᐃᖅᓯᔪᑦ ᑎᑎᕋᖅᓯᒪᔪᓂᒃ ᑭᒡᓕᐅᑉ ᐃᓗᐊᓂ. ᓇᓗᓇᐃᖅᓯᙱᑦᑐᑦ ᐱᔨᑦᑎᕋᐅᑎᐅᑉ ᐱᐅᓂᖓᓂᒃ. ᐊᒻᒪ ᓇᓗᓇᐃᖅᓯᙱᑦᑐᑦ ᐃᓪᓗᓂ ᑕᒪᐃᓐᓂᑦ ᐊᑐᕈᓐᓇᕐᓂᖓᓂᒃ.
    • ᐱᕕᒃᓴᖓᓂ ᑎᑭᑦᑕᕐᓂᖓ ᐃᓗᓕᖃᖅᐳᖅ 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.