Wà:s ne kahiatónhsera

Bus ohnà:ken

Sahró:ri tsi nahò:ten iah tekaié:ri

Oh nahò:ten iahà:wen
Full report No account needed

Buses now:Kwah tsi nikahwistà:kelateyou

STO station · 5112

Station Lyon

Buses at Station Lyon · timetableupdated 30 s ago
Every 17 to 23 min · sched. then 2:20
31
31Ottawa · platform STATION LYON · every 17 to 23 min
Shé:kon iah tetewatahsónteren
2:00
sched. then 2:20
Every 10 to 11 min · sched. then 2:11
400
400Ottawa · platform STATION LYON · every 10 to 11 min
Shé:kon iah tetewatahsónteren
2:01
sched. then 2:11
Every 19 to 21 min · sched. then 2:22
38
38Ottawa · platform STATION LYON · every 19 to 21 min
Shé:kon iah tetewatahsónteren
2:02
sched. then 2:22
Tiótkon 30 min · sched. then 2:37
33
33Ottawa · platform STATION LYON · every 30 to 30 min
Shé:kon iah tetewatahsónteren
2:07
sched. then 2:37
Tiótkon 32 min · sched. then 2:40
34
34Ottawa · platform STATION LYON · every 32 to 32 min
Shé:kon iah tetewatahsónteren
2:08
sched. then 2:40
Tiótkon 30 min · sched. then 2:38
59
59Ottawa · platform STATION LYON · every 30 to 30 min
Shé:kon iah tetewatahsónteren
2:08
sched. then 2:38
36
36Ottawa
platform STATION LYON
Shé:kon iah tetewatahsónteren
2:10
from the timetable
Tiótkon 30 min · sched. then 2:44
32
32Ottawa · platform STATION LYON · every 30 to 30 min
Shé:kon iah tetewatahsónteren
2:14
sched. then 2:44
Tiótkon 20 min · sched. then 2:34
67
67Ottawa · platform STATION LYON · every 20 to 20 min
Shé:kon iah tetewatahsónteren
2:14
sched. then 2:34
Tiótkon 30 min · sched. then 2:53
55
55Ottawa · platform STATION LYON · every 30 to 30 min
Shé:kon iah tetewatahsónteren
2:23
sched. then 2:53
Tiótkon 15 min · sched. then 2:44
95
95Buckingham · platform STATION LYON · every 15 to 15 min
Shé:kon iah tetewatahsónteren
2:29
sched. then 2:44
371
371Ottawa
platform STATION LYON
Shé:kon iah tetewatahsónteren
2:31
from the timetable
45
45Gal.Aylmer
platform STATION LYON
Shé:kon iah tetewatahsónteren
2:46
from the timetable
93
93M-Angers
platform STATION LYON
Shé:kon iah tetewatahsónteren
2:49
from the timetable
37
37Ottawa
platform STATION LYON
Shé:kon iah tetewatahsónteren
2:53
from the timetable
40
40Front/Allum.
platform STATION LYON
Shé:kon iah tetewatahsónteren
2:57
from the timetable
47
47Gal.Aylmer
platform STATION LYON
Shé:kon iah tetewatahsónteren
3:02
from the timetable
25
25Amérique-Française
platform STATION LYON
Shé:kon iah tetewatahsónteren
3:02
from the timetable
41
41Pob Allum
platform STATION LYON
Shé:kon iah tetewatahsónteren
3:07
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

88% predicted within five minutes of schedule. 2,806 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
Plan from here
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
Iah JavaScriptBoards and departures still show without JavaScript

Station details

Step-free route

Iah teiotòn:'on aonsakheweiénhste' ó:nen. Kahiatónhsera kèn:'en iah tewakaterièn:tare tó: nikahá:wi tánon ka nón:we tkawé:non. Satkáhtho OC Transpo tóka' STO ohén:ton tsi enhsátiake ohahà:ke.

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 LYON

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

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

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

    Ka' nikarihò:ten

    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.

    88% of final provider predictions within 5 minutes of the timetable, from 2,806 predictions over 6 weekdays. The lowest sampled hour is 08:00 at 75%.

    Median predicted difference from the timetable: 5 s late. At the 95th percentile: 7 min late.

    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: 89.7% of final predictions within five minutes of the timetable, 39 predictions, typically 0.4 min early
    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: 98% of final predictions within five minutes of the timetable, 51 predictions, typically 0 min late
    7. 06:00: 93.7% of final predictions within five minutes of the timetable, 190 predictions, typically 0.1 min late
    8. 07:00: 85.8% of final predictions within five minutes of the timetable, 246 predictions, typically 0.1 min late
    9. 08:00: 74.9% of final predictions within five minutes of the timetable, 303 predictions, typically 0.7 min late
    10. 09:00: 90.1% of final predictions within five minutes of the timetable, 202 predictions, typically 0.2 min early
    11. 10:00: 94.2% of final predictions within five minutes of the timetable, 156 predictions, typically 0.4 min early
    12. 11:00: 92.8% of final predictions within five minutes of the timetable, 167 predictions, typically 0.4 min early
    13. 12:00: 93.6% of final predictions within five minutes of the timetable, 141 predictions, typically 0.2 min early
    14. 13:00: 89.2% of final predictions within five minutes of the timetable, 148 predictions, typically 0.4 min early
    15. 14:00: 94.2% of final predictions within five minutes of the timetable, 137 predictions, typically 0.1 min late
    16. 15:00: 84.6% of final predictions within five minutes of the timetable, 169 predictions, typically 0.6 min late
    17. 16:00: 76.7% of final predictions within five minutes of the timetable, 159 predictions, typically 1.1 min late
    18. 17:00: 81.4% of final predictions within five minutes of the timetable, 161 predictions, typically 0.4 min late
    19. 18:00: 89.3% of final predictions within five minutes of the timetable, 112 predictions, typically 0.1 min late
    20. 19:00: 89% of final predictions within five minutes of the timetable, 91 predictions, typically 0.3 min late
    21. 20:00: 95.6% of final predictions within five minutes of the timetable, 91 predictions, typically 0.6 min late
    22. 21:00: 92.7% of final predictions within five minutes of the timetable, 82 predictions, typically 0.1 min late
    23. 22:00: 95.3% of final predictions within five minutes of the timetable, 86 predictions, typically 0 min early
    24. 23:00: 92% of final predictions within five minutes of the timetable, 75 predictions, typically 0.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
    Findings
    WhatÓ:nenTewaterièn:tareScenario or next investigation
    ProblemOne hour has a lower prediction match08:0075%Operations in that hour

    How STATION LYON is doing

    These indicators separate repeated delay from changes in the operator's arrival predictions. They suggest questions for planners and operations staff. They do not show the cause. They do not prove when buses arrived. Each figure shows its route-hour sample.

    Measured over 20 route-hours. 0 more were observed too thinly to count, and are excluded rather than assumed good.

    Scheduling

    Repeated late predictions can point to a timetable worth reviewing. Check actual arrival and dispatch records before deciding whether running time needs to change.

    Who can fix it
    A service planner
    What it costs
    Iah tewaterièn:tare tó: nikaná:ien tsi niió:re ahontkáhtho ne ká'sere, ne raotiio'te tánon ne ò:ia.

    Tsi ní:ioht kahiatónhsera tánon tsi nihawen:'en iah teiotsén:ion

    100%

    Route-hours: median arrival prediction iáh énska minute early, iáh áhsen minutes late.

    Route-hours with repeated late predictions

    0of 20

    Route-hours where the median eligible arrival prediction is at least three minutes late. Review running time against actual operating records.

    Route hours with early predictions

    0of 20

    Route-hours where the median eligible arrival prediction is at least one minute early. This does not show that buses left early.

    Typical predicted delay

    Not enough evidence this month to publish this indicator.

    The typical median predicted delay in flagged route-hours. It is not a validated amount to add to the timetable.

    Operations: not measurable here

    This site records a median delay for each hour at a stop. It does not record a percentile. So we cannot work out the gap between a normal trip and a bad one. That is a limit of our own measurement. It is not a finding about this place.

    Measurements

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

    One hour has a lower prediction match · 08:00
    Ioiánere tsi nikarì:wes 74.9%
    Other hours on time 92%
    Measured arrivals 303
    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.

    Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.

    What is being shown

    A current station board assembled from the imported timetable and any usable operator prediction for each trip.

    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.

    Evidence dates

    Computed or assembled
    Kén:k nikón
    40 departures across 4 published platform records in the current four-hour board.
    Coverage
    0 departures have a published live prediction; 40 are timetable-only.

    Tsi nón: ionkwaién:ta'

    Limits to keep in mind

    • OC Transpo does not publish live rail positions or predictions in the feed used here, so rail times are timetable-only.
    • The stop source does not publish a complete station accessibility chain, entrances, or indoor paths.
    Suggest a factual correction

    Contains information licensed under the Open Government Licence – City of Ottawa.