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 · 4000

Station Lorrain

Buses at Station Lorrain · liveupdated 30 s ago
Tiótkon 30 min · then 29 sched.
79
79Labrosse · platform STATION LORRAIN · every 30 to 30 min
Shé:kon iah tetewatahsónteren
Ó:nenò:nen
then 29 sched.
Every 12 to 13 min · sched. then 3:08
400
400Ottawa · platform STATION LORRAIN · every 12 to 13 min
Shé:kon iah tetewatahsónteren
2:56
sched. then 3:08
Every 2 to 11 min · then 16 · 18 sched.
400
400Lorrain · platform STATION LORRAIN arrêt d'arrivée · every 2 to 11 min
Shé:kon iah tetewatahsónteren
5minitò:nen
then 16 · 18 sched.
Every 1 to 30 min · then 6 · 36 sched.
78
78Lorrain · platform STATION LORRAIN arrêt d'arrivée · every 1 to 30 min
Shé:kon iah tetewatahsónteren
5minitò:nen
then 6 · 36 sched.
Tiótkon 28 min · then 37 sched.
800
800Lorrain · platform STATION LORRAIN arrêt d'arrivée · every 28 to 28 min
Shé:kon iah tetewatahsónteren
7minitò:nen
then 37 sched.
Every 8 to 22 min · then 21 · 43 sched.
77
77Lorrain · platform STATION LORRAIN arrêt d'arrivée · every 8 to 22 min
Shé:kon iah tetewatahsónteren
10minitò:nen
then 21 · 43 sched.
Tiótkon 32 min · sched. then 3:37
72
72Lorrain · platform STATION LORRAIN · every 32 to 32 min
Shé:kon iah tetewatahsónteren
3:05
sched. then 3:37
97
97Ar Masson
platform STATION LORRAIN
Shé:kon iah tetewatahsónteren
3:07
from the timetable
Tiótkon 30 min · then 47 sched.
75
75Lorrain · platform STATION LORRAIN arrêt d'arrivée · every 30 to 30 min
Shé:kon iah tetewatahsónteren
16minitò:nen
then 47 sched.
Tiótkon 18 min · then 36 sched.
68
68Lorrain · platform STATION LORRAIN arrêt d'arrivée · every 18 to 18 min
Shé:kon iah tetewatahsónteren
17minitò:nen
then 36 sched.
Tiótkon 17 min · sched. then 3:27
800
800Pob Allum · platform STATION LORRAIN · every 17 to 17 min
Shé:kon iah tetewatahsónteren
3:10
sched. then 3:27
75
75La Cité
platform STATION LORRAIN
Shé:kon iah tetewatahsónteren
3:12
from the timetable
97
97Lorrain
platform STATION LORRAIN arrêt d'arrivée
Shé:kon iah tetewatahsónteren
22minitò:nen
68
68Cégep GRoy
platform STATION LORRAIN
Shé:kon iah tetewatahsónteren
3:15
from the timetable
200
200Lorrain
platform STATION LORRAIN arrêt d'arrivée
Shé:kon iah tetewatahsónteren
3:43
from the timetable
100
100Lorrain
platform STATION LORRAIN arrêt d'arrivée
Shé:kon iah tetewatahsónteren
3:44
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

69.4% predicted within five minutes of schedule. 2,809 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 LORRAIN

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

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

Prediction agreement
69.4% predicted within five minutes of schedule. 2,809 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.

69.4% of final provider predictions within 5 minutes of the timetable, from 2,809 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 53%.

Median predicted difference from the timetable: 10 s early. 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-29 to 2026-11-05. 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: 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: 65.3% of final predictions within five minutes of the timetable, 95 predictions, typically 0.9 min early
  7. 06:00: 77.7% of final predictions within five minutes of the timetable, 215 predictions, typically 1 min early
  8. 07:00: 76.5% of final predictions within five minutes of the timetable, 217 predictions, typically 0.1 min early
  9. 08:00: 69.5% of final predictions within five minutes of the timetable, 190 predictions, typically 0 min late
  10. 09:00: 68.3% of final predictions within five minutes of the timetable, 180 predictions, typically 0 min late
  11. 10:00: 72.1% of final predictions within five minutes of the timetable, 154 predictions, typically 0.3 min early
  12. 11:00: 66.7% of final predictions within five minutes of the timetable, 192 predictions, typically 1.9 min early
  13. 12:00: 74.7% of final predictions within five minutes of the timetable, 162 predictions, typically 0.4 min early
  14. 13:00: 77.3% of final predictions within five minutes of the timetable, 154 predictions, typically 0.3 min early
  15. 14:00: 76.3% of final predictions within five minutes of the timetable, 156 predictions, typically 0.2 min early
  16. 15:00: 69.2% of final predictions within five minutes of the timetable, 172 predictions, typically 0 min late
  17. 16:00: 52.9% of final predictions within five minutes of the timetable, 172 predictions, typically 1 min late
  18. 17:00: 64.7% of final predictions within five minutes of the timetable, 190 predictions, typically 0.6 min late
  19. 18:00: 70.1% of final predictions within five minutes of the timetable, 154 predictions, typically 0.2 min early
  20. 19:00: 60.9% of final predictions within five minutes of the timetable, 87 predictions, typically 0 min late
  21. 20:00: 65.3% of final predictions within five minutes of the timetable, 75 predictions, typically 0.4 min early
  22. 21:00: 65.7% of final predictions within five minutes of the timetable, 70 predictions, typically 0 min late
  23. 22:00: 62.5% of final predictions within five minutes of the timetable, 72 predictions, typically 1.1 min early
  24. 23:00: 61.8% of final predictions within five minutes of the timetable, 55 predictions, typically 0.8 min early
  • 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
ProblemPredictions earlier than timetable06:001 min earlyHolding points on the routes here
ProblemPredictions earlier than timetable11:001.9 min earlyHolding points on the routes here
ProblemPredictions earlier than timetable22:001.1 min earlyHolding points on the routes here
ProblemOne hour has a lower prediction match16:0053%Operations in that hour

How STATION LORRAIN 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 19 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

84.2%

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

Route-hours with repeated late predictions

0of 19

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

3of 19

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

Predictions earlier than timetable · 06:00
Median delay -1 min
Measured arrivals 215
Ioiánere tsi nikarì:wes 77.7%
Predictions earlier than timetable · 11:00
Median delay -1.9 min
Measured arrivals 192
Ioiánere tsi nikarì:wes 66.7%
Predictions earlier than timetable · 22:00
Median delay -1.1 min
Measured arrivals 72
Ioiánere tsi nikarì:wes 62.5%
One hour has a lower prediction match · 16:00
Ioiánere tsi nikarì:wes 52.9%
Other hours on time 68.8%
Measured arrivals 172
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
17 departures have a published live prediction; 23 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.