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

ᑐᓪᓕᐊ ᐸᓯ

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

Filled in: ᓄᖅᑲᖓᕝᕕᒃ · 5:26 a.m. · pick one

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

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

STO station · 8500

Station LABROSSE

Buses at Station LABROSSE · liveupdated 30 s ago
4 ᐊᒻᒪ 10 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 10 · 15 sched.
400
400Ottawa · platform Station LABROSSE #1 · every 4 to 10 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
ᒫᓐᓇᒫᓐᓇᐅᔪᖅ
then 10 · 15 sched.
28 ᐊᒻᒪ 30 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 6:14
800
800Pob Allum · platform Station LABROSSE #3 · every 28 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5:46
sched. then 6:14
18 ᐊᒻᒪ 20 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 6:22
68
68Cégep GRoy · platform Station LABROSSE #3 · every 18 to 20 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:02
sched. then 6:22
ᑕᒪᑦ 45 ᒥᓂᑦᓂ · sched. then 6:47
18
18Pré Tunney · platform Station LABROSSE #3 · every 45 to 45 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:02
sched. then 6:47
9 ᐊᒻᒪ 10 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 6:13
100
100Terrasses · platform Station LABROSSE #2 · every 9 to 10 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:03
sched. then 6:13
2 ᐊᒻᒪ 9 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 6:10
200
200Ottawa · platform Station LABROSSE #1 · every 2 to 9 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:04
sched. then 6:10
14 ᐊᒻᒪ 15 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 6:20
400
400Lorrain · platform Station LABROSSE #04 · every 14 to 15 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:05
sched. then 6:20
13 ᐊᒻᒪ 15 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 6:28
95
95Ottawa · platform Station LABROSSE #1 · every 13 to 15 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:13
sched. then 6:28
ᑕᒪᑦ 20 ᒥᓂᑦᓂ · sched. then 6:40
93
93Ottawa · platform Station LABROSSE #1 · every 20 to 20 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:20
sched. then 6:40
68
68Lorrain
platform Station LABROSSE #04
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:26
from the timetable
800
800Lorrain
platform Station LABROSSE #04
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:34
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

88.1% predicted within five minutes of schedule. 1,911 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 Station LABROSSE

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

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

    Prediction agreement
    88.1% predicted within five minutes of schedule. 1,911 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.

    88.1% of final provider predictions within 5 minutes of the timetable, from 1,911 predictions over 5 weekdays. The lowest sampled hour is 16:00 at 71%.

    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.

    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: not enough data
    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: 100% of final predictions within five minutes of the timetable, 36 predictions, typically 0.7 min late
    7. 06:00: 94.4% of final predictions within five minutes of the timetable, 126 predictions, typically 0.4 min late
    8. 07:00: 85.1% of final predictions within five minutes of the timetable, 141 predictions, typically 0.4 min late
    9. 08:00: 85.2% of final predictions within five minutes of the timetable, 108 predictions, typically 1.3 min late
    10. 09:00: 88.1% of final predictions within five minutes of the timetable, 126 predictions, typically 0.9 min late
    11. 10:00: 95.6% of final predictions within five minutes of the timetable, 114 predictions, typically 0.4 min late
    12. 11:00: 98.3% of final predictions within five minutes of the timetable, 116 predictions, typically 0 min late
    13. 12:00: 92.6% of final predictions within five minutes of the timetable, 95 predictions, typically 0.5 min late
    14. 13:00: 88.5% of final predictions within five minutes of the timetable, 113 predictions, typically 1.1 min late
    15. 14:00: 91.3% of final predictions within five minutes of the timetable, 92 predictions, typically 0.8 min late
    16. 15:00: 87.5% of final predictions within five minutes of the timetable, 128 predictions, typically 1.2 min late
    17. 16:00: 71.3% of final predictions within five minutes of the timetable, 136 predictions, typically 2.7 min late
    18. 17:00: 83.1% of final predictions within five minutes of the timetable, 166 predictions, typically 1.8 min late
    19. 18:00: 90.4% of final predictions within five minutes of the timetable, 114 predictions, typically 0.8 min late
    20. 19:00: 84.9% of final predictions within five minutes of the timetable, 73 predictions, typically 1.8 min late
    21. 20:00: 85.2% of final predictions within five minutes of the timetable, 61 predictions, typically 1.6 min late
    22. 21:00: 90.7% of final predictions within five minutes of the timetable, 54 predictions, typically 1.7 min late
    23. 22:00: 85.4% of final predictions within five minutes of the timetable, 48 predictions, typically 1.6 min late
    24. 23:00: 83.8% of final predictions within five minutes of the timetable, 37 predictions, typically 2.3 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:0071%Operations in that hour

    How Station LABROSSE is doing

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

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

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

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

    0of 19

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

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

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

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

    ᐊᐅᓚᑦᑎᓂᖅ: not measurable here

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

    Measurements

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

    One hour has a lower prediction match · 16:00
    ᐱᕕᒃᓴᖓᓂ 71.3%
    Other hours on time 88.3%
    Measured arrivals 136
    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 4 published platform records in the current four-hour board.
    ᐃᓚᐅᔪᑦ
    2 departures have a published live prediction; 38 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.