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

ᑐᓪᓕᐊ ᐸᓯ

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

Filled in: ᓄᖅᑲᖓᕝᕕᒃ 3063 · 12:53 p.m. · pick one

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

Buses now:ᐃᑲᕐᕋᖓᓂᑭᖑᕙᖅᑐᖅyou

2O-Train Line 2 · station 3063

Mooney's Bay

Trains · timetableᐃᑲᕐᕋᖓᓂᑭᖑᕙᖅᑐᖅᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
ᑕᒪᑦ 12 ᒥᓂᑦᓂ · sched. then 1:04
2
2Limebank · platform MOONEY'S BAY O-TRAIN
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
12:53
sched. then 1:04
ᑕᒪᑦ 12 ᒥᓂᑦᓂ · sched. then 1:10
2
2Bayview · platform MOONEY'S BAY O-TRAIN
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
12:58
sched. then 1:10
Buses at Mooney's Bay · liveupdated 30 s ago
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · then 28 sched.
88
88Bayshore · platform B · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
ᒫᓐᓇᒫᓐᓇᐅᔪᖅ
then 28 sched.
16 ᐊᒻᒪ 17 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 20 · 37 sched.
10
10Hurdman · platform C · every 16 to 17 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
3ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 20 · 37 sched.
14 ᐊᒻᒪ 15 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 24 · 34 sched.
111
111Baseline · platform B · every 14 to 15 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 24 · 34 sched.
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · then 36 sched.
111
111Billings Bridge · platform A · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
11ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 36 sched.
ᑕᒪᑦ 15 ᒥᓂᑦᓂ · then 26 · 41 sched.
90
90Greenboro · platform B · every 15 to 15 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
11ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 26 · 41 sched.
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · then 41 sched.
112
112Baseline · platform B · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
11ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 41 sched.
ᑕᒪᑦ 15 ᒥᓂᑦᓂ · then 27 · 42 sched.
90
90Hurdman · platform A · every 15 to 15 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
12ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 27 · 42 sched.
ᑕᒪᑦ 15 ᒥᓂᑦᓂ · then 27 · 43 sched.
88
88Hurdman · platform A · every 15 to 15 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
13ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 27 · 43 sched.
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · then 43 sched.
88
88Baseline · platform B · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
13ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 43 sched.
ᑕᒪᑦ 29 ᒥᓂᑦᓂ · then 40 sched.
10
10Main · platform D · every 29 to 29 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
15ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 40 sched.
111
111Carleton
platform A
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
25ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
112
112Billings Bridge
platform A
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
1:21
from the timetable
10
10Lyon
platform D
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
30ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
Entrances and elevators

We cannot confirm elevator status right now.

84.7% predicted within five minutes of schedule. 4,029 eligible provider predictions; arrivals not independently measured
Why →

More at this station

Save, plan, shareSave the station, plan a trip from it, or share it
ᐸᕐᓇᒋᐊᖅ ᐅᕙᓐᖓᑦ
Bike parking hereNone recorded within 5 minutes. Not recorded does not mean there is none.Bike parking: OpenStreetMap, data as of Jun 1, 2026. The walk is an estimate.
Add it ↗
Print this stationA print sheet with the page link at the foot
Station dataDownload the station as JSON or CSV
JSON · CSV
Report a station problemSent to our station log and counted on this page
ᔮᕙᔅᑯᕆᑉ ᐊᑐᖅᑕᐅᙱᑦᑐᖅBoards and departures still show without JavaScript

Station details

Step-free route

ᐅᓪᓗᒥ ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᑕᐅᔪᓐᓇᙱᑦᑐᑦ. ᐊᑖᓂ ᑐᓴᒐᒃᓴᐃᑦ ᖃᖓᓂᖓ ᐅᕝᕙᓘᓐᓃᑦ ᓇᖕᒥᑦ ᐱᓂᖏᑦ ᓇᓗᓇᐃᖅᑕᐅᓯᒪᙱᑦᑐᑦ. ᐃᖏᕐᕋᓚᐅᙱᓐᓂᕐᓂ ᐊᐅᓚᑦᑎᔨ ᐊᐱᕆᓗᒍ.

All elevators in the network

Buses from here

Tap a route for live buses and how full they are.

In the station

No published source lists amenities here yet.

Performance

Service delivery · evidence state

Service at MOONEY'S BAY

Cancellations at this station

Local count cannot be published

Exact stop-call evidence could not be read for Oct 27, 2026 – Nov 2, 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.

    Departure-board snapshot
    40 listed departures · 23 live provider predictions

    Server snapshot assembled Nov 3, 2026, 12:53 p.m.; open Departures for a refreshed board. This is not a cancellation count.

    Prediction agreement
    84.7% predicted within five minutes of schedule. 4,029 eligible provider predictions; arrivals not independently measured
    Bus prediction reliability at this station

    ᐃᓱᓕᑦᑎᓂᖅ

    Bus prediction reliability at this station

    Early evidence: 6 of 20 weekdays with eligible final provider predictions. This updates hourly; more records will make the estimate steadier.

    84.7% of final provider predictions within 5 minutes of the timetable, from 4,029 predictions over 6 weekdays. The lowest sampled hour is 17:00 at 80%.

    Median predicted difference from the timetable: 1 min ᑭᖑᕙᖅᑐᖅ. At the 95th percentile: 8 min ᑭᖑᕙᖅᑐᖅ.

    Final provider predictions for conventional bus arrivals at OC Transpo and STO stations; physical arrivals are not independently verified. Express (200/500), shopper/community (300), event (400), and school (600) routes are excluded because each needs a purpose-specific measure. STO routes are included and graded by their own families: Rapibus 100, 200, 400 and 800 count, and STO school journeys numbered 300 and above are excluded the way OC Transpo’s 600s are. Each operator is measured against its own service, never against the other’s. This station also has 1 O-Train line. This line is not included because OC Transpo does not publish realtime rail data.

    We use the agency’s last prediction within ten minutes of each scheduled arrival. 6 weekdays with eligible predictions, 2026-10-27 to 2026-11-03. Within five minutes means the final prediction differs from the schedule by no more than five minutes.

    Final provider predictions within five minutes of the timetable, by hour, 6 weekdays
    1. 00:00: 96.8% of final predictions within five minutes of the timetable, 63 predictions, typically 0.5 min late
    2. 01:00: not enough data
    3. 02:00: not enough data
    4. 03:00: not enough data
    5. 04:00: not enough data
    6. 05:00: 89.5% of final predictions within five minutes of the timetable, 76 predictions, typically 1.9 min late
    7. 06:00: 86.2% of final predictions within five minutes of the timetable, 189 predictions, typically 2.1 min late
    8. 07:00: 85.9% of final predictions within five minutes of the timetable, 263 predictions, typically 1.3 min late
    9. 08:00: 80.6% of final predictions within five minutes of the timetable, 263 predictions, typically 1.9 min late
    10. 09:00: 82.4% of final predictions within five minutes of the timetable, 261 predictions, typically 1.4 min late
    11. 10:00: 84.8% of final predictions within five minutes of the timetable, 250 predictions, typically 1.3 min late
    12. 11:00: 88% of final predictions within five minutes of the timetable, 258 predictions, typically 1 min late
    13. 12:00: 88.1% of final predictions within five minutes of the timetable, 226 predictions, typically 1.2 min late
    14. 13:00: 84.3% of final predictions within five minutes of the timetable, 230 predictions, typically 1.1 min late
    15. 14:00: 84.7% of final predictions within five minutes of the timetable, 235 predictions, typically 1.1 min late
    16. 15:00: 82.1% of final predictions within five minutes of the timetable, 234 predictions, typically 0.4 min late
    17. 16:00: 85.6% of final predictions within five minutes of the timetable, 243 predictions, typically 0.9 min late
    18. 17:00: 79.5% of final predictions within five minutes of the timetable, 219 predictions, typically 1.2 min late
    19. 18:00: 82.1% of final predictions within five minutes of the timetable, 201 predictions, typically 0.5 min late
    20. 19:00: 81.1% of final predictions within five minutes of the timetable, 175 predictions, typically 1.3 min late
    21. 20:00: 87% of final predictions within five minutes of the timetable, 185 predictions, typically 1.2 min late
    22. 21:00: 83.8% of final predictions within five minutes of the timetable, 167 predictions, typically 1.4 min late
    23. 22:00: 86.7% of final predictions within five minutes of the timetable, 143 predictions, typically 1.3 min late
    24. 23:00: 86.5% of final predictions within five minutes of the timetable, 111 predictions, typically 0.5 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

    How MOONEY'S BAY is doing

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

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

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

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

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

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

    100%

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

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

    0of 20

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

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

    0of 20

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

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

    ᑖᔅᓱᒪ ᑕᖅᑭᐅᑉ ᐃᓗᐊᓂ ᓇᓗᓇᐃᖅᓯᒍᑎᑦ ᓈᒻᒪᙱᑦᑐᑦ ᑖᓐᓇ ᓴᖅᑭᑎᑦᑎᓂᐊᕐᓗᒍ.

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

    ᐊᐅᓚᑦᑎᓂᖅ: not measurable here

    ᐅᓇ ᐃᑭᐊᖅᑭᕖᒃᑯᑦ ᑐᑭᓯᒋᐊᕐᕕᒃ ᑎᑎᕋᖅᐸᒃᑐᖅ ᑭᖑᕙᕐᓂᐅᔪᒥᒃ ᐊᑯᓐᓂᐅᔪᒥᒃ ᐃᑲᕐᕋᓂ ᑕᒪᐃᓐᓂ ᓄᖅᑲᖓᕝᕕᒻᒥ. ᐊᓯᖏᓐᓂᒃ ᓈᓴᐅᑎᓂᒃ ᑎᑎᕋᖅᐸᙱᑦᑐᖅ. ᑕᐃᒪ ᓇᓗᓇᖅᑐᖅ ᖃᓄᖅ ᐊᔾᔨᒌᙱᓐᓂᖓ ᐃᖏᕐᕋᓂᖅ ᓈᒻᒪᒃᑐᖅ ᐃᖏᕐᕋᓂᕐᓗ ᐱᐅᙱᑦᑐᖅ. ᑖᓐᓇ ᐅᕙᒍᑦ ᖃᐅᔨᓴᕈᓯᑦᑎᓐᓂ ᑭᒡᓕᖃᖅᑐᖅ. ᑕᒪᓐᓇ ᓇᔪᒐᖅ ᐱᓪᓗᒍ ᑐᑭᓯᓂᐊᕐᓂᐅᙱᑦᑐᖅ.

    Measurements

    Calculated: · Method: settled-arrivals-oc-sto-conventional-v5

    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
    Station evidence and sources
    Français
    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.

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

    ᓴᖅᑭᑎᑕᐅᔪᑦ

    ᐊᖁᑏᑦ ᓄᖑᕐᕕᐊᑕ ᑕᑯᒃᓴᐅᑎᖓ ᒫᓐᓇ. ᐱᕕᒃᓴᖏᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ ᐊᒻᒪ ᐊᐅᓚᑦᑎᔨᐅᑉ ᓇᓚᐅᑦᑖᕈᑎᖓ ᐃᖏᕐᕋᓂᕐᒧᑦ ᑕᒪᐃᓐᓄᑦ.

    How it was produced

    Platforms sharing the station stop code are grouped, scheduled trips are read from the current GTFS, and a live time is used only when the operator publishes a matching prediction.

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

    ᓈᓴᐅᑎᓕᐅᖅᑕᐅᔪᖅ ᐅᕝᕙᓘᓐᓃᑦ ᑲᑐᔾᔨᖅᑕᐅᔪᖅ
    ᐆᒃᑐᕋᐅᑎ
    40 departures across 5 published platform records in the current four-hour board.
    ᐃᓚᐅᔪᑦ
    23 departures have a published live prediction; 17 are timetable-only.

    ᓇᑭᑦ ᑐᓴᒐᒃᓴᐃᑦ

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

    • OC Transpo ᓴᖅᑭᑦᑎᙱᓚᖅ O-Train ᒫᓐᓇ ᓇᐅᓐᓂᖓᓂᒃ ᐅᕝᕙᓘᓐᓃᑦ ᖃᖓ ᑎᑭᓐᓂᐊᕐᓂᖓᓂᒃ ᑐᓴᒐᒃᓴᓂ ᐅᕙᓂ ᐊᑐᖅᑕᐅᔪᓂ. ᑕᐃᒪ O-Train ᐱᕕᖏᑦ ᐸᕐᓇᐅᑎᒥᑦ ᑭᓯᐊᓂ.
    • The stop source does not publish a complete station accessibility chain, entrances, or indoor paths.
    ᓱᓕᔪᒥᒃ ᐋᖅᑭᒋᐊᕐᓂᕐᒥᒃ ᐊᑐᓕᖁᔨᓗᑎᑦ

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