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

ᑐᓪᓕᐊ ᐸᓯ

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

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

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

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

OC Transpo station · 3050

Bayshore

Buses at Bayshore · liveupdated 30 s ago
ᑕᒪᑦ 31 ᒥᓂᑦᓂ · then 33 sched.
61
61Terry Fox · platform B · every 31 to 31 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
3ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 33 sched.
15 ᐊᒻᒪ 30 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 33 · 48 sched.
85
85Lees · platform A · every 15 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 33 · 48 sched.
15 ᐊᒻᒪ 30 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 5:19
88
88Hurdman · platform C · every 15 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:49
sched. then 5:19
15 ᐊᒻᒪ 31 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 5:25
57
57Tunney's Pasture · platform A · every 15 to 31 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:54
sched. then 5:25
30 ᐊᒻᒪ 33 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 5:26
88
88Bayshore · platform B · every 30 to 33 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
4:56
sched. then 5:26
29 ᐊᒻᒪ 49 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 54 · 103 sched.
61
61Tunney's Pasture · platform A · every 29 to 49 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
26ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 54 · 103 sched.
5 ᐊᒻᒪ 35 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 74 · 100 sched.
63
63Innovation · platform B · every 5 to 35 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
38ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 74 · 100 sched.
ᑕᒪᑦ 35 ᒥᓂᑦᓂ · sched. then 5:59
85
85Bayshore · platform B · every 35 to 35 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:24
sched. then 5:59
ᑕᒪᑦ 35 ᒥᓂᑦᓂ · sched. then 6:03
81
81Tunney's Pasture · platform A · every 35 to 35 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:28
sched. then 6:03
ᑕᒪᑦ 31 ᒥᓂᑦᓂ · sched. then 6:19
61
61Stittsville · platform B · every 31 to 31 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:48
sched. then 6:19
ᑕᒪᑦ 28 ᒥᓂᑦᓂ · sched. then 6:16
62
62Stittsville · platform B · every 28 to 28 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:48
sched. then 6:16
ᑕᒪᑦ 25 ᒥᓂᑦᓂ · sched. then 6:18
66
66Innovation · platform B · every 25 to 25 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:53
sched. then 6:18
58
58Carling Campus ~ Complexe Carling
platform C
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:06
from the timetable
ᑕᒪᑦ 10 ᒥᓂᑦᓂ · sched. then 6:26
57
57Carling Campus ~ Complexe Carling · platform C · every 10 to 10 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:16
sched. then 6:26
Entrances and elevators

We cannot confirm elevator status right now.

86.9% predicted within five minutes of schedule. 3,761 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 hereBike racks, covered · 2 ᒥᓂᑦ ᐱᓱᖕᓂᖅ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 BAYSHORE

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

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

Prediction agreement
86.9% predicted within five minutes of schedule. 3,761 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.

86.9% of final provider predictions within 5 minutes of the timetable, from 3,761 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 72%.

Median predicted difference from the timetable: 55 s ᑭᖑᕙᖅᑐᖅ. 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.

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: 90.1% of final predictions within five minutes of the timetable, 71 predictions, typically 0.9 min late
  2. 01:00: 90.2% of final predictions within five minutes of the timetable, 41 predictions, typically 1 min late
  3. 02:00: not enough data
  4. 03:00: not enough data
  5. 04:00: 97.6% of final predictions within five minutes of the timetable, 41 predictions, typically 0.4 min late
  6. 05:00: 92.3% of final predictions within five minutes of the timetable, 91 predictions, typically 0.1 min late
  7. 06:00: 91.8% of final predictions within five minutes of the timetable, 183 predictions, typically 1 min late
  8. 07:00: 89.9% of final predictions within five minutes of the timetable, 227 predictions, typically 1.1 min late
  9. 08:00: 84% of final predictions within five minutes of the timetable, 225 predictions, typically 1.2 min late
  10. 09:00: 87.6% of final predictions within five minutes of the timetable, 210 predictions, typically 0.9 min late
  11. 10:00: 90.5% of final predictions within five minutes of the timetable, 199 predictions, typically 0.5 min late
  12. 11:00: 92.6% of final predictions within five minutes of the timetable, 203 predictions, typically 0.5 min late
  13. 12:00: 90.6% of final predictions within five minutes of the timetable, 191 predictions, typically 0.7 min late
  14. 13:00: 93.9% of final predictions within five minutes of the timetable, 198 predictions, typically 0.7 min late
  15. 14:00: 92.1% of final predictions within five minutes of the timetable, 202 predictions, typically 0.5 min late
  16. 15:00: 82.3% of final predictions within five minutes of the timetable, 220 predictions, typically 1 min late
  17. 16:00: 71.7% of final predictions within five minutes of the timetable, 240 predictions, typically 1.5 min late
  18. 17:00: 75.8% of final predictions within five minutes of the timetable, 223 predictions, typically 1.7 min late
  19. 18:00: 80.7% of final predictions within five minutes of the timetable, 218 predictions, typically 1.3 min late
  20. 19:00: 88% of final predictions within five minutes of the timetable, 167 predictions, typically 1.1 min late
  21. 20:00: 85.5% of final predictions within five minutes of the timetable, 172 predictions, typically 1 min late
  22. 21:00: 91.6% of final predictions within five minutes of the timetable, 154 predictions, typically 1 min late
  23. 22:00: 87.7% of final predictions within five minutes of the timetable, 130 predictions, typically 1.1 min late
  24. 23:00: 91.7% of final predictions within five minutes of the timetable, 121 predictions, typically 1.2 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
ProblemOne hour has a lower prediction match16:0072%Operations in that hour

How BAYSHORE 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

One hour has a lower prediction match · 16:00
ᐱᕕᒃᓴᖓᓂ 71.7%
Other hours on time 90.2%
Measured arrivals 240
Station evidence and sources
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.

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

ᓴᖅᑭᑎᑕᐅᔪᑦ

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

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