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

ᑐᓪᓕᐊ ᐸᓯ

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

Filled in: ᓄᖅᑲᖓᕝᕕᒃ 3034 · 4:06 a.m. · pick one

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

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

OC Transpo station · 3034

Billings Bridge

Buses at Billings Bridge · liveupdated 30 s ago
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · sched. then 4:47
88
88Bayshore · platform 1A · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:17
sched. then 4:47
27 ᐊᒻᒪ 29 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 52 · 81 sched.
105
105Uplands · platform 1A · every 27 to 29 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
25ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 52 · 81 sched.
105
105Rideau
platform 2A
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:32
from the timetable
1 ᐊᒻᒪ 57 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 32 · 89 sched.
48
48Billings Bridge · platform BILLINGS BRIDGE / BANK · every 1 to 57 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
28ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 32 · 89 sched.
ᑕᒪᑦ 60 ᒥᓂᑦᓂ · then 90 sched.
90
90Hurdman · platform 2A · every 60 to 60 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
30ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 90 sched.
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · sched. then 5:07
41
41St-Laurent · platform 4B · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:37
sched. then 5:07
1 ᐊᒻᒪ 30 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 4:43
41
41Billings Bridge · platform BILLINGS BRIDGE / BANK · every 1 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:41
sched. then 4:43
ᑕᒪᑦ 50 ᒥᓂᑦᓂ · then 87 sched.
48
48Hurdman · platform 4B · every 50 to 50 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
36ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 87 sched.
2 ᐊᒻᒪ 29 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 4:45
6
6Rideau · platform BILLINGS BRIDGE / BANK · every 2 to 29 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:43
sched. then 4:45
ᑕᒪᑦ 34 ᒥᓂᑦᓂ · sched. then 5:20
88
88Hurdman · platform 2A · every 34 to 34 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:46
sched. then 5:20
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · sched. then 5:27
44
44Hurdman · platform 3B · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:57
sched. then 5:27
ᑕᒪᑦ 32 ᒥᓂᑦᓂ · sched. then 5:34
105
105St-Laurent · platform 2A · every 32 to 32 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:02
sched. then 5:34
112
112Billings Bridge
platform 4B
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:14
from the timetable
ᑕᒪᑦ 2 ᒥᓂᑦᓂ · sched. then 5:17
6
6Greenboro · platform BILLINGS BRIDGE / BANK · every 2 to 2 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:15
sched. then 5:17
111
111Baseline
platform 3B
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:16
from the timetable
98
98Hurdman
platform 2A
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:19
from the timetable
44
44Billings Bridge
platform 4D
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:21
from the timetable
111
111Billings Bridge
platform 4C
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:25
from the timetable
110
110Hurdman
platform 2A
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:25
from the timetable
10
10Lyon
platform 1A
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:27
from the timetable
112
112Baseline
platform 3B
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:31
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

80.9% predicted within five minutes of schedule. 9,054 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 here16 places within 5 min · nearest: Racks for 4 bikes, covered, 1 ᒥᓂᑦ ᐱᓱᖕᓂᖅBike parking: OpenStreetMap, data as of Jun 1, 2026. The walk is an estimate.
Details →
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 BILLINGS BRIDGE

Cancellations at this station

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.

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

    Server snapshot assembled Nov 4, 2026, 4:05 a.m.; open Departures for a refreshed board. This is not a cancellation count.

    Prediction agreement
    80.9% predicted within five minutes of schedule. 9,054 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.

    80.9% of final provider predictions within 5 minutes of the timetable, from 9,054 predictions over 6 weekdays. The lowest sampled hour is 17:00 at 69%.

    Median predicted difference from the timetable: 2 min ᑭᖑᕙᖅᑐᖅ. At the 95th percentile: 9 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.

    We use the agency’s last prediction within ten minutes of each scheduled arrival. 6 weekdays with eligible predictions, 2026-10-28 to 2026-11-04. 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: 88% of final predictions within five minutes of the timetable, 142 predictions, typically 0.7 min late
    2. 01:00: 81.1% of final predictions within five minutes of the timetable, 74 predictions, typically 2.2 min late
    3. 02:00: 93.5% of final predictions within five minutes of the timetable, 31 predictions, typically 0.5 min late
    4. 03:00: not enough data
    5. 04:00: 96.3% of final predictions within five minutes of the timetable, 80 predictions, typically 0.6 min late
    6. 05:00: 87.9% of final predictions within five minutes of the timetable, 215 predictions, typically 1.4 min late
    7. 06:00: 86.9% of final predictions within five minutes of the timetable, 396 predictions, typically 1.4 min late
    8. 07:00: 86.2% of final predictions within five minutes of the timetable, 549 predictions, typically 1.5 min late
    9. 08:00: 79.7% of final predictions within five minutes of the timetable, 567 predictions, typically 2.1 min late
    10. 09:00: 82.1% of final predictions within five minutes of the timetable, 547 predictions, typically 1.7 min late
    11. 10:00: 82.3% of final predictions within five minutes of the timetable, 509 predictions, typically 1.5 min late
    12. 11:00: 80.5% of final predictions within five minutes of the timetable, 518 predictions, typically 1.4 min late
    13. 12:00: 79.9% of final predictions within five minutes of the timetable, 507 predictions, typically 1.8 min late
    14. 13:00: 78.9% of final predictions within five minutes of the timetable, 516 predictions, typically 1.8 min late
    15. 14:00: 82.7% of final predictions within five minutes of the timetable, 492 predictions, typically 1.7 min late
    16. 15:00: 76.5% of final predictions within five minutes of the timetable, 545 predictions, typically 1.9 min late
    17. 16:00: 75.7% of final predictions within five minutes of the timetable, 548 predictions, typically 2.2 min late
    18. 17:00: 69.1% of final predictions within five minutes of the timetable, 582 predictions, typically 2.4 min late
    19. 18:00: 78.2% of final predictions within five minutes of the timetable, 536 predictions, typically 1.8 min late
    20. 19:00: 80.9% of final predictions within five minutes of the timetable, 404 predictions, typically 1.3 min late
    21. 20:00: 83.6% of final predictions within five minutes of the timetable, 373 predictions, typically 0.9 min late
    22. 21:00: 83.4% of final predictions within five minutes of the timetable, 343 predictions, typically 1.6 min late
    23. 22:00: 85.5% of final predictions within five minutes of the timetable, 304 predictions, typically 1.2 min late
    24. 23:00: 85.7% of final predictions within five minutes of the timetable, 258 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

    How BILLINGS BRIDGE is doing

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

    Measured over 23 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 23

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

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

    0of 23

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

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

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

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

    ᐊᐅᓚᑦᑎᓂᖅ: not measurable here

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

    Measurements

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

    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 9 published platform records in the current four-hour board.
    ᐃᓚᐅᔪᑦ
    4 departures have a published live prediction; 36 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.