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

ᑐᓪᓕᐊ ᐸᓯ

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

Filled in: ᓄᖅᑲᖓᕝᕕᒃ 3038 · 2:15 a.m. · pick one

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

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

2O-Train Line 2 · station 3038

South Keys

Trains · timetableᐃᑲᕐᕋᖓᓂᑭᖑᕙᖅᑐᖅᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
2
2Bayview
platform SOUTH KEYS O-TRAIN NORTH / NORD
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:59
from the timetable
Buses at South Keys · liveupdated 30 s ago
28 ᐊᒻᒪ 39 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 36 · 75 sched.
105
105Rideau · platform A · every 28 to 39 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 36 · 75 sched.
26 ᐊᒻᒪ 34 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 44 · 77 sched.
105
105Uplands · platform D · every 26 to 34 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
14ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 44 · 77 sched.
19 ᐊᒻᒪ 60 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 5:12
90
90Hurdman · platform E · every 19 to 60 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:12
sched. then 5:12
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · sched. then 5:02
6
6Rideau · platform C · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:32
sched. then 5:02
28 ᐊᒻᒪ 30 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 5:28
105
105St-Laurent · platform A · every 28 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:58
sched. then 5:28
7 ᐊᒻᒪ 27 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 5:40
98
98Hurdman · platform A · every 7 to 27 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:13
sched. then 5:40
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · sched. then 5:49
40
40St-Laurent · platform B · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:19
sched. then 5:49
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · sched. then 5:49
110
110Hurdman · platform A · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:19
sched. then 5:49
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · sched. then 5:51
116
116Baseline · platform E · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:21
sched. then 5:51
ᑕᒪᑦ 27 ᒥᓂᑦᓂ · sched. then 5:58
197
197Greenboro · platform E · every 27 to 27 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:31
sched. then 5:58
6
6Greenboro
platform A
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:37
from the timetable
40
40Greenboro
platform A
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:42
from the timetable
6
6Rockcliffe
platform C
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:54
from the timetable
198
198Limebank
platform E
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:56
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

83% predicted within five minutes of schedule. 4,592 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 here3 places within 5 min · nearest: Racks for 14 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 SOUTH KEYS

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 · 3 live provider predictions

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

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

ᐃᓱᓕᑦᑎᓂᖅ

Bus prediction reliability at this station

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

83% of final provider predictions within 5 minutes of the timetable, from 4,592 predictions over 5 weekdays. The lowest sampled hour is 17:00 at 72%.

Median predicted difference from the timetable: 1 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 2 O-Train lines. These lines are 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. 5 weekdays with eligible predictions, 2026-10-28 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, 5 weekdays
  1. 00:00: 82.7% of final predictions within five minutes of the timetable, 81 predictions, typically 1.1 min late
  2. 01:00: 84.8% of final predictions within five minutes of the timetable, 33 predictions, typically 2.4 min late
  3. 02:00: not enough data
  4. 03:00: not enough data
  5. 04:00: 97.4% of final predictions within five minutes of the timetable, 39 predictions, typically 0.5 min late
  6. 05:00: 92.5% of final predictions within five minutes of the timetable, 134 predictions, typically 0.8 min late
  7. 06:00: 88.9% of final predictions within five minutes of the timetable, 225 predictions, typically 0.9 min late
  8. 07:00: 82.5% of final predictions within five minutes of the timetable, 286 predictions, typically 1.1 min late
  9. 08:00: 87.5% of final predictions within five minutes of the timetable, 272 predictions, typically 1.1 min late
  10. 09:00: 83.3% of final predictions within five minutes of the timetable, 258 predictions, typically 1.3 min late
  11. 10:00: 86.5% of final predictions within five minutes of the timetable, 244 predictions, typically 0.4 min late
  12. 11:00: 83.8% of final predictions within five minutes of the timetable, 241 predictions, typically 0.7 min late
  13. 12:00: 87.3% of final predictions within five minutes of the timetable, 251 predictions, typically 1.1 min late
  14. 13:00: 82.3% of final predictions within five minutes of the timetable, 248 predictions, typically 0.6 min late
  15. 14:00: 79.1% of final predictions within five minutes of the timetable, 258 predictions, typically 0.8 min late
  16. 15:00: 77.5% of final predictions within five minutes of the timetable, 276 predictions, typically 1.2 min late
  17. 16:00: 76.6% of final predictions within five minutes of the timetable, 304 predictions, typically 1.6 min late
  18. 17:00: 72.1% of final predictions within five minutes of the timetable, 287 predictions, typically 2.4 min late
  19. 18:00: 82.6% of final predictions within five minutes of the timetable, 264 predictions, typically 1 min late
  20. 19:00: 82.5% of final predictions within five minutes of the timetable, 194 predictions, typically 0.8 min late
  21. 20:00: 87% of final predictions within five minutes of the timetable, 192 predictions, typically 0.7 min late
  22. 21:00: 84.1% of final predictions within five minutes of the timetable, 170 predictions, typically 1 min late
  23. 22:00: 86.6% of final predictions within five minutes of the timetable, 157 predictions, typically 1.1 min late
  24. 23:00: 81.2% of final predictions within five minutes of the timetable, 133 predictions, typically 1.7 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 SOUTH KEYS is doing

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

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

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

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

0of 22

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

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

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

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

ᐊᐅᓚᑦᑎᓂᖅ: 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 7 published platform records in the current four-hour board.
ᐃᓚᐅᔪᑦ
3 departures have a published live prediction; 37 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.