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

ᐱᔨᑦᑎᕐᓂᖅ

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

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 20 · Ottawa · Councillor: Isabelle Skalski

Osgoode

ᓄᓇᓕᐅᑉ ᐃᓚᖓᓄᑦ ᐱᓕᕆᓗᑎᑦ

Osgoode: prediction accuracy is not published for this ward yet.

ᑕᓪᓕᒪ ᒥᓂᑦ ᐃᓗᐊᓂ
ᓱᓕ ᐱᔭᐅᔪᓐᓇᙱᑦᑐᖅ
ᓂᕈᐊᕐᕕᖕᒥ ᓄᖅᑲᖅᑕᕐᕖᑦ
104
ᐊᖅᑯᑏᑦ ᐅᕗᖓ ᑎᑭᑦᑐᑦ
6
Cancelled trips
ᓱᓕ ᐱᔭᐅᔪᓐᓇᙱᑦᑐᖅ
ᓱᓕ ᓈᓴᐅᑎᓕᐅᕐᓯᒪᖏᑦᑐᖅ ᓂᕈᐊᕐᓂᕐᒧᑦ ᐊᕕᒃᓯᒪᓂᖏᓐᓂ.

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

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

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

Routes in this ward

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

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

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

One-page brief

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

ᐅᓂᒃᑳᓕᐊᖅ ᓇᐃᑦᑐᖅ ᐅᒃᑯᐃᓗᒍᐊᔾᔨᒌᙱᓐᓂᖏᑦ ᑕᑯᓗᒋᑦ ᐊᓯᐊᓂ ᓂᕈᐊᕐᕕᖕᒥ

What can be verified in Osgoode?

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

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

ᓱᓕ ᐱᔭᐅᔪᓐᓇᙱᑦᑐᖅ

96 eligible settled provider predictions are available at stops inside this ward across 20 weekdays with feed evidence. A percentage remains unavailable until the evidence reaches 500 eligible predictions and 20 such weekdays.

ᐊᓯᖏᓐᓄᑦ ᓇᓚᐅᑦᑖᖅᑕᐅᓂᖓ
ᓈᓴᐅᑎᖃᖅᑎᑕᐅᓚᐅᖅᓯᒪᙱᓚᖅ

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

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

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

ᓄᓇᙳᐊᖅ ᒫᓐᓇᐅᔪᖅ ᐅᒃᑯᐃᓗᒍ

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

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

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

96 eligible final provider predictions across 20 weekdays. The local percentage is withheld until its publication threshold is met.

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

6 routes · 104 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.

    1 of 2 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 110, predictions later than timetable 15:00 to 18:00, 3.8 min late.

    2 of 2 routes here had something measurable to report.

    Arrivals within five minutes, by hour of day, across the 2 routes graded here, last 14 days
    1. 00:00: 87.2% of final predictions within five minutes of the timetable, 1,697 predictions, typically 1 min late
    2. 01:00: 90.3% of final predictions within five minutes of the timetable, 1,608 predictions, typically 1.3 min late
    3. 02:00: 92.9% of final predictions within five minutes of the timetable, 1,402 predictions, typically 0.7 min late
    4. 03:00: 89.1% of final predictions within five minutes of the timetable, 1,418 predictions, typically 0.3 min late
    5. 04:00: 87% of final predictions within five minutes of the timetable, 2,117 predictions, typically 1.3 min late
    6. 05:00: 79.4% of final predictions within five minutes of the timetable, 4,926 predictions, typically 1.5 min late
    7. 06:00: 85.7% of final predictions within five minutes of the timetable, 5,399 predictions, typically 0.8 min late
    8. 07:00: 83.5% of final predictions within five minutes of the timetable, 5,938 predictions, typically 1.1 min late
    9. 08:00: 75.5% of final predictions within five minutes of the timetable, 5,161 predictions, typically 1.5 min late
    10. 09:00: 77.9% of final predictions within five minutes of the timetable, 5,349 predictions, typically 1.3 min late
    11. 10:00: 82.1% of final predictions within five minutes of the timetable, 5,200 predictions, typically 0.6 min late
    12. 11:00: 74.8% of final predictions within five minutes of the timetable, 5,017 predictions, typically 1.4 min late
    13. 12:00: 75.2% of final predictions within five minutes of the timetable, 5,153 predictions, typically 1.4 min late
    14. 13:00: 78.8% of final predictions within five minutes of the timetable, 5,218 predictions, typically 1.9 min late
    15. 14:00: 79.4% of final predictions within five minutes of the timetable, 4,832 predictions, typically 0.9 min late
    16. 15:00: 70.6% of final predictions within five minutes of the timetable, 4,551 predictions, typically 2.8 min late
    17. 16:00: 64.5% of final predictions within five minutes of the timetable, 4,937 predictions, typically 3 min late
    18. 17:00: 60% of final predictions within five minutes of the timetable, 5,752 predictions, typically 2.8 min late
    19. 18:00: 67.2% of final predictions within five minutes of the timetable, 5,913 predictions, typically 2.3 min late
    20. 19:00: 84.6% of final predictions within five minutes of the timetable, 5,739 predictions, typically 1.1 min late
    21. 20:00: 82.2% of final predictions within five minutes of the timetable, 4,838 predictions, typically 1.3 min late
    22. 21:00: 85.1% of final predictions within five minutes of the timetable, 2,287 predictions, typically 0 min late
    23. 22:00: 92.8% of final predictions within five minutes of the timetable, 1,381 predictions, typically 0.8 min late
    24. 23:00: 90.5% of final predictions within five minutes of the timetable, 1,322 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 timetable1101 routes15:00 to 18:003.8 min lateMore running time
    ProblemWide prediction spread1051 routes17:0025.1 min swingOperations, not the timetable
    ProblemPredictions earlier than timetable1101 routes21:001.6 min earlyLess running time, or holding points
    ProblemOne hour has a lower prediction match1051 routes17:0068%Operations, not the timetable
    CaveatCoverage gap1051102 routesAll measured hours97% · 99%More observation, not a service change

    O-Train evidence

    What we know about train service here

    Open the train observation report

    Trains are not in the public data feed

    The bus punctuality reports compare archived arrival predictions with published schedules. They do not count independently measured physical arrivals. Otranspo has no comparable public train-position dataset for these reports, so those bus figures cannot show where a train is or whether Lines 1, 2 and 4 run on time.

    Publishing train positions, their timestamps, and the measurement method would help build a separate, verifiable record of rail service. The missing dataset does not establish how the trains performed.

    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 observedCheck all official service alertsOpen train research and history

    How OSGOODE is doing

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

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

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

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

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

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

    90.5%

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

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

    3of 42

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

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

    1of 42

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

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

    3.8min

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

    ᐊᐅᓚᑦᑎᓂᖅ

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

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

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

    97.6%

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

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

    1of 42

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

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

    25.1min

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

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

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

    6
    ᐊᖁᑏᑦ
    104
    ᓄᖃᕐᕕᐃᑦ
    13
    Washrooms
    3
    ᐃᒥᕐᕕᐅᔪᑦ
    Provider-prediction measureᑐᓴᖅᑎᑕᐅᓚᐅᖏᑦᑐᖅprovider prediction within five minutes of the timetable

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

    96 eligible settled provider predictions are available at stops inside this ward across 20 weekdays with feed evidence. A percentage remains unavailable until the evidence reaches 500 eligible predictions and 20 such weekdays.

    2 partial-capture days not counted.

    Predictions within five minutes
    65
    Eligible trip-stop predictions
    96
    Observed days
    20 weekdays

    Which routes need closer review

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

    1. 110Open route
      71.6%Predictions within five minutes

      113,377 eligible predictions across the whole route

    2. 105Open route
      88.2%Predictions within five minutes

      67,367 eligible predictions across the whole route

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

    Vehicle visibility to investigate
    ᐊᖁᑎᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦWith a positionWithout a matched positionᐃᓚᐅᔪᑦᐊᓂᒍᖅᓯᒪᔪᑦ
    1056826622097.1%
    2995049198.0%
    110346341598.6%
    22230300100.0%
    304220100.0%

    Routes serving the ward

    6 scheduled routes

    Bus routes · 5

    Train lines · 1

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

    ━ 5 bus routes═ 1 train lines● 104 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) 13

    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.

    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 20: OSGOODE
    Boundary and vintage
    City ward layer · effective ᑐᓴᖅᑎᑕᐅᓚᐅᖏᑦᑐᖅ · imported August 4, 2026
    Official civic contacts
    • Isabelle Skalski · 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
    6 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.

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

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

    ᓇᑭᑦ ᑐᓴᒐᒃᓴᐃᑦ

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

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