Buses now:ᐃᑲᕐᕋᖓᓂᑭᖑᕙᖅᑐᖅyou
We cannot confirm elevator status right now.
More at this station
Station details
Step-free route
ᐅᓪᓗᒥ ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᑕᐅᔪᓐᓇᙱᑦᑐᑦ. ᐊᑖᓂ ᑐᓴᒐᒃᓴᐃᑦ ᖃᖓᓂᖓ ᐅᕝᕙᓘᓐᓃᑦ ᓇᖕᒥᑦ ᐱᓂᖏᑦ ᓇᓗᓇᐃᖅᑕᐅᓯᒪᙱᑦᑐᑦ. ᐃᖏᕐᕋᓚᐅᙱᓐᓂᕐᓂ ᐊᐅᓚᑦᑎᔨ ᐊᐱᕆᓗᒍ.
All elevators in the networkBuses from here
Tap a route for live buses and how full they are.
In the station
No published source lists amenities here yet.
Transfers and paths
Platforms and wayfinding (6)→
Each row is an individual platform stop. Open it for departures from that platform; use Departures for every platform together.
- Platform 1ST-LAURENT O-TRAIN WEST / OUEST→
- Platform 2ST-LAURENT O-TRAIN EAST / EST→
- Platform AST-LAURENT A→
- Platform BST-LAURENT B→
- Platform CST-LAURENT C→
- Platform DST-LAURENT D→
Station sources can include entrances and indoor paths. Check Transfers and paths for what this station’s source actually contains. A published path does not verify an entrance is open, a step-free route is usable, or how to reach a bay from the street.
The platform list above is the structured text alternative to the station-centre map link. It includes every linked platform record that the current imported feed provides.
Open the station centre in OpenStreetMapTransfers and paths→
Official paths inside the station
Otranspo reads the optional GTFS station files separately from the timetable. A linked platform does not prove that a physical path exists, is open, or is step-free.
No step-by-step guide for this station yet. This feed version contains no published station path or transfer rule that can support a platform-to-platform guide.
A published path is not a verified accessible path. It does not prove that elevators are operating, every entrance is represented, or the route is suitable for a particular rider.
Source details
What this feed version includes
Imported source observed 2026-10-30, 1:00:32 a.m.
- Station levels
- The operator omitted this optional file from the feed
- Indoor paths
- The operator omitted this optional file from the feed
- Transfer rules
- The operator omitted this optional file from the feed
- Feed version
- 6ee8491d-8f94-4122-a67b-ef228d9e0945
- Parser version
- 2026-09-30.1
- Combined source checksum
- 0dd440979a2d1f47af79a157130a722288616e1851472bc35b40a99e97d2c910
Find your way through this station
Start with what we know for sure. Open any row for platforms, transfers, accessibility and nearby services.
Published entrances and exits
No entrance record is published. Approach routes and exits remain unknown.
The operator may publish a station map or guide outside its machine-readable transit feed.
Open OC Transpo station informationAccessibility
→
Imported boarding information is shown separately when available. It does not verify a complete accessible route or current operating condition. Missing information is not a confirmation.
- Complete accessible route
- Unverified. The imported station record does not confirm a complete accessible route.
- Current operating condition
- Unknown. Current alerts cannot be matched completely to every entrance, elevator, pathway, and platform.
No verified accessible alternative is available in current data.
ᐃᑭᕐᓂᕐᒧᑦ ᑐᓴᒐᒃᓴᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ
These are static wheelchair-boarding facts from the imported GTFS schedule. They do not confirm current elevator operation, an open path, or an available vehicle.
ᑎᑎᖅᑲᐃᑦ ᓴᓇᐅᓯᖏᑦ ᐃᓕᔭᐅᓂᖏᓪᓗ ᖃᖓᓂᑦ ᖃᐅᔨᓴᖅᑕᐅᓚᐅᖅᓯᒪᙱᑦᑐᑦ ᐅᓇ ᑎᑎᖅᑲᒧᑦ.
- ᔅᑌᓴᓐ ᐅᓂᒃᑲᖓ ᓴᖅᑭᑕᐅᓯᒪᔪᖅ
- The station record does not specify wheelchair boarding.
ᐃᑎᕐᓂᕐᒧᑦ ᐊᑕᐅᓯᕐᒥᒃ ᑭᐅᔾᔪᑎᖃᕈᓐᓇᖏᑦᑐᒍᑦ ᑕᒪᐃᓐᓄᑦ ᐃᑎᕐᕕᖕᓄᑦ.
- ᐅᑕᖅᑭᕝᕕᒃ 1
- Wheelchair boarding is not specified for this platform.
- ᐅᑕᖅᑭᕝᕕᒃ 2
- Wheelchair boarding is not specified for this platform.
- ᐅᑕᖅᑭᕝᕕᒃ A
- Wheelchair boarding is not specified for this platform.
- ᐅᑕᖅᑭᕝᕕᒃ B
- Wheelchair boarding is not specified for this platform.
- ᐅᑕᖅᑭᕝᕕᒃ C
- Wheelchair boarding is not specified for this platform.
- ᐅᑕᖅᑭᕝᕕᒃ D
- Wheelchair boarding is not specified for this platform.
Accessibility chain
Unknown. Available sources do not confirm a complete accessible trip.
All 8 links are unverified. Review the element list before relying on this station for an accessible trip.
ᓴᖅᑭᕝᕕᖓ: Current imported agency GTFS; detailed station accessibility has not been verified from this imported schedule
Review 8 unverified links
- 01Path to the stationᖃᐅᔨᒪᔭᐅᙱᑦᑐᖅ
- 02Station entranceᖃᐅᔨᒪᔭᐅᙱᑦᑐᖅ
- 03Fare gate or paid-area entryᖃᐅᔨᒪᔭᐅᙱᑦᑐᖅ
- 04Path to the platformᖃᐅᔨᒪᔭᐅᙱᑦᑐᖅ
- 05Required elevatorsᖃᐅᔨᒪᔭᐅᙱᑦᑐᖅ
- 06Boarding at 6 platform(s)ᖃᐅᔨᒪᔭᐅᙱᑦᑐᖅ
- 07Transfer linksᖃᐅᔨᒪᔭᐅᙱᑦᑐᖅ
- 08Destination-side exitᖃᐅᔨᒪᔭᐅᙱᑦᑐᖅ
Performance
Service delivery · evidence state
Service at ST-LAURENT
Cancellations at this station
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.
- Departure-board snapshot
- 40 listed departures · 16 live provider predictions
- Prediction agreement
- 82.2% predicted within five minutes of schedule. 3,619 eligible provider predictions; arrivals not independently measured
Server snapshot assembled Nov 4, 2026, 7:04 p.m.; open Departures for a refreshed board. This is not a cancellation count.
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.
82.2% of final provider predictions within 5 minutes of the timetable, from 3,619 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 64%.
Median predicted difference from the timetable: 3 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. 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-28 to 2026-11-04. Within five minutes means the final prediction differs from the schedule by no more than five minutes.
- 00:00: 76.3% of final predictions within five minutes of the timetable, 59 predictions, typically 3.2 min late00
- 01:00: not enough data01
- 02:00: not enough data02
- 03:00: not enough data03
- 04:00: 83.6% of final predictions within five minutes of the timetable, 55 predictions, typically 0.9 min late04
- 05:00: 93.1% of final predictions within five minutes of the timetable, 116 predictions, typically 1.4 min late05
- 06:00: 90.2% of final predictions within five minutes of the timetable, 214 predictions, typically 2.3 min late06
- 07:00: 93.8% of final predictions within five minutes of the timetable, 192 predictions, typically 1.7 min late07
- 08:00: 79.7% of final predictions within five minutes of the timetable, 241 predictions, typically 2.4 min late08
- 09:00: 80.6% of final predictions within five minutes of the timetable, 206 predictions, typically 2.3 min late09
- 10:00: 85.9% of final predictions within five minutes of the timetable, 205 predictions, typically 1.7 min late10
- 11:00: 83.6% of final predictions within five minutes of the timetable, 219 predictions, typically 2.5 min late11
- 12:00: 83.2% of final predictions within five minutes of the timetable, 208 predictions, typically 2.5 min late12
- 13:00: 83.7% of final predictions within five minutes of the timetable, 203 predictions, typically 2.6 min late13
- 14:00: 86.1% of final predictions within five minutes of the timetable, 209 predictions, typically 2.1 min late14
- 15:00: 72.8% of final predictions within five minutes of the timetable, 191 predictions, typically 3.3 min late15
- 16:00: 64.3% of final predictions within five minutes of the timetable, 207 predictions, typically 3.7 min late16
- 17:00: 69.9% of final predictions within five minutes of the timetable, 209 predictions, typically 3.5 min late17
- 18:00: 82.2% of final predictions within five minutes of the timetable, 191 predictions, typically 2.7 min late18
- 19:00: 89.9% of final predictions within five minutes of the timetable, 159 predictions, typically 2.4 min late19
- 20:00: 82% of final predictions within five minutes of the timetable, 139 predictions, typically 2.7 min late20
- 21:00: 85% of final predictions within five minutes of the timetable, 127 predictions, typically 2.8 min late21
- 22:00: 79.8% of final predictions within five minutes of the timetable, 109 predictions, typically 2.9 min late22
- 23:00: 84.5% of final predictions within five minutes of the timetable, 84 predictions, typically 2.6 min late23
- 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
| What | ᖃᖓ | ᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅ | Scenario or next investigation |
|---|---|---|---|
| Problem!Predictions later than timetable | 00:00 | 3.2 min late | Running time on the routes here |
| Problem!Predictions later than timetable | 15:00 to 18:00 | 3.5 min late | Running time on the routes here |
| Problem!One hour has a lower prediction match | 16:00 | 64% | Operations in that hour |
How ST-LAURENT is doing
ᑖᒃᑯᐊ ᓇᓗᓇᐃᒃᑯᑕᐃᑦ ᐊᕕᒃᑐᐃᔪᑦ ᐅᑎᖅᑕᖅᐸᒃᑐᒥᒃ ᑭᖑᕙᕐᓂᕐᒥᒃ ᐊᒻᒪ ᐱᓕᕆᕝᕕᐅᑉ ᑎᑭᓐᓂᐊᕐᓂᖏᑦ ᐃᓱᒪᒋᔭᖏᑦ ᐊᓯᔾᔨᖅᐸᓐᓂᖏᓐᓂᒃ. ᐊᐱᖁᑎᓂᒃ ᐃᓱᒪᒋᐊᖅᑎᑦᑎᔪᑦ ᐸᕐᓇᐃᔨᓄᑦ ᐊᒻᒪ ᐱᓕᕆᔨᓄᑦ. ᐱᔾᔪᑎᖓ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ. ᐱᐊᓯᑦ ᖃᖓ ᑎᑭᒻᒪᖔᑕ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ. ᓈᓴᐅᑎ ᑕᒪᐃᓐᓂ ᑕᑯᒃᓴᐅᑎᑦᑎᔪᖅ ᖃᑦᓯᓂᒃ ᐃᖏᕐᕋᕝᕕᒃ-ᐃᑲᕐᕋᓂᒃ ᐊᑐᖅᓯᒪᒻᒪᖔᑦ.
Measured over 21 route-hours. 0 more were observed too thinly to count, and are excluded rather than assumed good.
ᐃᑲᕐᕋᓄᑦ ᐋᖅᑭᒃᓯᓂᖅ
ᐊᑯᓂ ᑭᖑᕙᕐᓂᖏᑦ ᓂᕆᐅᒋᔭᐅᔪᑦ ᑕᑯᑎᑦᑎᔪᓐᓇᖅᑐᑦ ᐃᑲᕐᕋᓕᐊᖑᔪᖅ ᕿᒥᕐᕈᔭᐅᒃᓴᐅᓂᖓᓂᒃ. ᕿᒥᕐᕈᓗᒋᑦ ᑎᑭᑦᑐᑦ ᐃᑲᕐᕋᖏᑦ ᐊᒻᒪ ᐊᐅᓪᓚᑎᑦᑎᓂᕐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ. ᑕᐃᒪ ᐃᓱᒪᓕᐅᕐᓗᑎᑦ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐱᕕᒃ ᐊᓯᔾᔨᕆᐊᖃᕐᒪᖔᑦ.
- ᑭᓇ ᐋᖅᑭᒃᓯᔪᓐᓇᖅᐸ
- ᐃᖏᕐᕋᓂᕐᒧᑦ ᐸᕐᓇᐃᔨ
- ᖃᓄᖅ ᐊᑭᖃᖅᐸ
- ᐊᑭᖏᑦ ᓇᓗᓇᖅᐳᑦ ᓱᓕ. ᖃᐅᔨᓴᖅᑕᐅᔭᕆᐊᖃᖅᐳᑦ ᐊᖅᑲᐅᑏᑦ, ᐃᖅᑲᓇᐃᔭᖅᑏᑦ, ᐊᑭᓕᖅᑕᐅᓂᖏᑦ ᐊᒻᒪ ᐊᓯᔾᔨᖅᓯᓂᖏᑦ.
ᓇᓚᐅᑦᑖᖅᑕᐅᓯᒪᔪᑦ ᐃᑲᕐᕋᐃᑦ ᐊᓪᓚᓯᒪᔪᓂᒃ ᖃᓂᒋᔭᖃᖅᑐᑦ
81%
Route-hours where the median eligible arrival prediction is less than one minute early and less than three minutes late.
ᐊᖅᑯᑎᐅᑉ ᐃᑲᕐᕋᖏᑦ ᑭᖑᕙᕆᐊᖃᑦᑕᕐᓂᐊᖅᑐᖅ ᐅᖃᐅᓯᐅᖃᑦᑕᖅᑐᑦ
4of 21
ᐃᖏᕐᕋᕝᕕᐅᑉ ᐃᑲᕐᕋᖏᑦ, ᑎᑭᓂᐊᕐᓂᖏᑦ ᓂᕆᐅᒋᔭᐅᔪᑦ ᐊᑯᓐᓂᐊᓂ ᐱᖓᓱᓂᒃ ᒥᓂᑦᓂᒃ ᐅᖓᑖᓄᓪᓘᓐᓃᑦ ᑭᖑᕙᖅᑐᑦ. ᐃᖏᕐᕋᓂᖓᑕ ᐊᑯᓐᓂᖓ ᖃᐅᔨᓴᕐᓗᒍ ᐃᖏᕐᕋᓂᕐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᓂᒃ ᓴᓂᐊᓂᒃ.
ᐃᖏᕐᕋᕝᕕᐃᑦ ᐃᑲᕐᕋᖏᑦ, ᐸᔅ ᓯᕗᓪᓕᐅᕐᓂᐊᕐᓂᖓᓂᒃ ᓇᓚᐅᑦᑖᖅᑕᐅᑎᓪᓗᒍ
0of 21
ᐊᖁᑎ ᐃᑲᕐᕋᖏᑦ, ᑕᐃᑦᓱᒪᓂ ᑎᑭᓐᓂᐊᕐᓂᖓᓄᑦ ᓇᓚᐅᑦᑖᕐᓂᖅ ᐊᑯᓐᓂᐊᓂ ᓯᕗᓪᓕᐅᕐᓂᐊᖅᑐᖅ ᐊᑕᐅᓯᕐᒥᒃ ᒥᓂᑦᒥᒃ ᐅᖓᑖᓄᓪᓘᓃᑦ. ᐅᓇ ᓇᓗᓇᐃᖅᓯᙱᑦᑐᖅ ᐸᓯᑦ ᓯᕗᓪᓕᐅᖅᖢᑎᒃ ᐊᐅᓪᓚᓚᐅᖅᓯᒪᓂᖏᓐᓂᒃ.
ᑭᖑᕙᕆᐊᕐᓂᖅ ᓂᕆᐅᒋᔭᐅᑦᑕᐃᓐᓇᖅᑐᖅ
3.4min
ᑭᖑᕙᕆᐊᖃᕐᓂᖅ ᐊᑐᐃᓐᓇᐅᓂᖅᐹᖅ ᓂᕆᐅᒋᔭᐅᔪᖅ ᐃᖏᕐᕋᕝᕕᓐᓂ ᓇᓗᓇᐃᖅᑕᐅᓯᒪᔪᓂ. ᐅᓇ ᓇᓗᓇᐃᖅᑕᐅᑦᑎᐊᖏᑦᑐᖅ ᐃᓚᓗᒍ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐱᕕᒃᓴᓄᑦ.
ᐊᐅᓚᑦᑎᓂᖅ: not measurable here
ᐅᓇ ᐃᑭᐊᖅᑭᕖᒃᑯᑦ ᑐᑭᓯᒋᐊᕐᕕᒃ ᑎᑎᕋᖅᐸᒃᑐᖅ ᑭᖑᕙᕐᓂᐅᔪᒥᒃ ᐊᑯᓐᓂᐅᔪᒥᒃ ᐃᑲᕐᕋᓂ ᑕᒪᐃᓐᓂ ᓄᖅᑲᖓᕝᕕᒻᒥ. ᐊᓯᖏᓐᓂᒃ ᓈᓴᐅᑎᓂᒃ ᑎᑎᕋᖅᐸᙱᑦᑐᖅ. ᑕᐃᒪ ᓇᓗᓇᖅᑐᖅ ᖃᓄᖅ ᐊᔾᔨᒌᙱᓐᓂᖓ ᐃᖏᕐᕋᓂᖅ ᓈᒻᒪᒃᑐᖅ ᐃᖏᕐᕋᓂᕐᓗ ᐱᐅᙱᑦᑐᖅ. ᑖᓐᓇ ᐅᕙᒍᑦ ᖃᐅᔨᓴᕈᓯᑦᑎᓐᓂ ᑭᒡᓕᖃᖅᑐᖅ. ᑕᒪᓐᓇ ᓇᔪᒐᖅ ᐱᓪᓗᒍ ᑐᑭᓯᓂᐊᕐᓂᐅᙱᑦᑐᖅ.
Measurements
Calculated: · Method: settled-arrivals-oc-sto-conventional-v5
- Predictions later than timetable · 00:00
- Median delay 3.2 min
- Measured arrivals 59
- ᐱᕕᒃᓴᖓᓂ 76.3%
- Predictions later than timetable · 15:00 to 18:00
- Median delay 3.5 min
- Measured arrivals 607
- ᐱᕕᒃᓴᖓᓂ 69.9%
- One hour has a lower prediction match · 16:00
- ᐱᕕᒃᓴᖓᓂ 64.3%
- Other hours on time 83.6%
- Measured arrivals 207
O-Train evidence
What we know about train service here
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.
Official O-Train alerts could not be read just now, so nothing here can tell you whether a train is delayed. This is about our connection to the notices, not about the trains.
Check all official service alertsRecent 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.
Station information
Lines served (10)→
- 1timetable only→
- 7realtime published→
- 14realtime published→
- 18realtime published→
- 19realtime published→
- 20realtime published→
- 24realtime published→
- 40realtime published→
- 41realtime published→
- 105realtime published→
OC Transpo does not publish live train positions or predictions for O-Train lines. Train times shown here therefore come from the timetable.
Nearby amenities→
Nearby municipal washrooms and drinking fountains are shown separately from station-owned amenities. The source does not establish that they are inside the station, open now, or reachable by a step-free path.
Nearby amenities
Loading after departures…
Station evidence and sources
Print view prepared from the station record shown on this page. https://otranspo.ca/iu/stations/3025_stn
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
- Elevator unavailable →
- Accessibility barrier →
- Washroom unavailable →
- Cleanliness →
- Graffiti →
- Damage →
- Lighting →
- Snow or ice →
- Safety →
- Other issue →
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 6 published platform records in the current four-hour board.
- ᐃᓚᐅᔪᑦ
- 16 departures have a published live prediction; 24 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.