Skip to main content
Otranspo
FR

STATION LORRAIN

Gatineau · STO · Departures · 4 Platforms · #4000

Board updated

·5 routes·8 routes·3 routes·1 route
  1. ·100TerrassesOperator: STOSTATION LORRAIN3min08:13 a.m.Live
  2. ·79LorrainOperator: STOSTATION LORRAIN arrêt d'arrivée3min08:13 a.m.Live
  3. ·72LorrainOperator: STOSTATION LORRAIN5min08:15 a.m.Timetable
  4. ·68Cégep GRoyOperator: STOSTATION LORRAIN6min08:16 a.m.Timetable
  5. ·800Pob AllumOperator: STOSTATION LORRAIN6min08:16 a.m.Live
  6. ·800LorrainOperator: STOSTATION LORRAIN arrêt d'arrivée6min08:16 a.m.Live
  7. ·200OttawaOperator: STOSTATION LORRAIN7min08:17 a.m.Timetable
  8. ·400LorrainOperator: STOSTATION LORRAIN arrêt d'arrivée7min08:17 a.m.Timetable

What the labels mean

Live
a vehicle is being tracked and this is its predicted time
Timetable
the agency published no prediction for this trip yet

Station guide

Jump straight to the information you need.

Rider essentials

More station information

Station actions

Report an issue
Share this page

Share this page

Use the permanent public link to this page and its sources.

Download evidence image

Only the canonical public link is shared. Panel state, location, receipts, and other browser-only details are left out. Email and social services apply their own privacy terms.

Opens your device’s print dialog. Choose Save as PDF when available.

Verdict

When this station runs late

Early evidence: 6 of 20 weekdays. This updates hourly. Results become more certain as more trips are observed.

65.9% of arrivals within 5 minutes, from 2,657 arrivals over 6 weekdays. The worst hour is 22:00 at 54%.

Half the arrivals are 10 s early. The worst 5% are 7 min late.

Conventional bus arrivals at OC Transpo and STO stations. 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 observed, 2026-09-02 to 2026-09-09. On time means no more than five minutes early or late.

Arrivals within five minutes, by hour of day, 6 weekdays
  1. 00:00: 58.3% of arrivals on time, 36 arrivals, typically 0 min late
  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: 74.5% of arrivals on time, 102 arrivals, typically 1 min early
  7. 06:00: 68.1% of arrivals on time, 270 arrivals, typically 1.4 min early
  8. 07:00: 69.7% of arrivals on time, 287 arrivals, typically 0 min late
  9. 08:00: 67.6% of arrivals on time, 170 arrivals, typically 0 min late
  10. 09:00: 64% of arrivals on time, 125 arrivals, typically 0.4 min early
  11. 10:00: 69.2% of arrivals on time, 120 arrivals, typically 0.1 min early
  12. 11:00: 69.1% of arrivals on time, 123 arrivals, typically 1.2 min early
  13. 12:00: 64.3% of arrivals on time, 126 arrivals, typically 0.5 min early
  14. 13:00: 68.1% of arrivals on time, 119 arrivals, typically 0.4 min early
  15. 14:00: 68.7% of arrivals on time, 131 arrivals, typically 0 min late
  16. 15:00: 67.4% of arrivals on time, 144 arrivals, typically 0.4 min late
  17. 16:00: 61.7% of arrivals on time, 154 arrivals, typically 0.9 min late
  18. 17:00: 63.1% of arrivals on time, 160 arrivals, typically 0 min late
  19. 18:00: 65.5% of arrivals on time, 139 arrivals, typically 0 min late
  20. 19:00: 64.7% of arrivals on time, 102 arrivals, typically 0.2 min early
  21. 20:00: 58.8% of arrivals on time, 85 arrivals, typically 0 min late
  22. 21:00: 54.9% of arrivals on time, 82 arrivals, typically 0 min late
  23. 22:00: 54.4% of arrivals on time, 90 arrivals, typically 1 min early
  24. 23:00: 63% of arrivals on time, 73 arrivals, typically 0.4 min early
  • 90% or more on time
  • 80 to 90% on time
  • under 80% on time
  • not enough data
WhatWhenMeasuredFix
ProblemArrivals run early05:00 to 07:001.3 min earlyHolding points on the routes here
ProblemArrivals run early11:001.2 min earlyHolding points on the routes here
ProblemArrivals run early22:001 min earlyHolding points on the routes here

How STATION LORRAIN is doing

Two different failures hide inside one on-time percentage, and they have opposite fixes. These separate them. Each figure is a share of the route-hours this site measured well enough to speak for, and the count it is out of is shown beside it.

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

Scheduling

Whether the timetable describes the trip that is actually made. A route late by the same amount every day is not unreliable, it is mis-scheduled, and every operator is driving a schedule nobody can keep.

Who can fix it
A service planner
What it costs
An afternoon of work, and no extra buses.

Timetable matches the trip

80%

Hours where the middle arrival is within three minutes late and one minute early of the timetable.

Route-hours where the timetable is short

0of 20

Hours where the middle arrival is three minutes late or worse. Each is a candidate for a running-time rewrite.

Route-hours running early

4of 20

Hours where buses typically leave early. Riders who arrive on time can still watch one go.

Running time a short hour needs

Not enough evidence this month to publish this indicator.

For a typical short hour, the minutes a planner would add.

Operations: not measurable here

This site records a median delay for each hour at a stop, and no percentile, so the gap between a normal trip and a bad one cannot be worked out. That is a limit of our own measurement, not a finding about this place.

Measurements

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

Arrivals run early · 05:00 to 07:00
medianDelaySeconds -77
observations 372
onTimePct 71.3
Arrivals run early · 11:00
medianDelaySeconds -73
observations 123
onTimePct 69.1
Arrivals run early · 22:00
medianDelaySeconds -61
observations 90
onTimePct 54.4
Lines served (12)
Platforms and wayfinding (4)

Each row is an individual platform stop. Open it for departures from that platform; use the station board above for every platform together.

The imported transit source does not publish station entrances, indoor pathways, step-free routes, or bay-to-entrance instructions. We do not invent a “get me there” route without that geometry.

The platform list above is the structured text alternative to the station-centre map link. It includes every linked platform record that the current imported feed provides.

Open the station centre in OpenStreetMap
Transfers and paths

Official station-path evidence

Otranspo reads the optional GTFS station files separately from the timetable. A linked platform does not prove that a physical path exists, is open, or is step-free.

The operator’s feed has no station record for this place, so there are no internal paths to describe. The departure board is unaffected.

Accessibility

OC Transpo publishes no accessibility data for its stops, so we show none. An absent value is not a confirmation, and a guess here could send someone to a platform they cannot use.

No verified accessible alternative is available in current data.

Accessibility chain

Unknown. Available sources do not confirm a complete accessible trip.

  1. Path to the stationSource: Current imported agency GTFS; detailed station accessibility assets are not published · Observed: 2026-09-09, 12:10:08 p.m.Unknown
  2. Station entranceSource: Current imported agency GTFS; detailed station accessibility assets are not published · Observed: 2026-09-09, 12:10:08 p.m.Unknown
  3. Fare gate or paid-area entrySource: Current imported agency GTFS; detailed station accessibility assets are not published · Observed: 2026-09-09, 12:10:08 p.m.Unknown
  4. Path to the platformSource: Current imported agency GTFS; detailed station accessibility assets are not published · Observed: 2026-09-09, 12:10:08 p.m.Unknown
  5. Required elevatorsSource: Current imported agency GTFS; detailed station accessibility assets are not published · Observed: 2026-09-09, 12:10:08 p.m.Unknown
  6. Boarding at 4 platform(s)Source: Current imported agency GTFS; detailed station accessibility assets are not published · Observed: 2026-09-09, 12:10:08 p.m.Unknown
  7. Transfer linksSource: Current imported agency GTFS; detailed station accessibility assets are not published · Observed: 2026-09-09, 12:10:08 p.m.Unknown
  8. Destination-side exitSource: Current imported agency GTFS; detailed station accessibility assets are not published · Observed: 2026-09-09, 12:10:08 p.m.Unknown

Alerts and disruptions

Station-specific matching unavailable

The current combined alert sources do not provide a complete, verified station-to-feature match for entrances, elevators, pathways, and platforms. This page therefore does not claim that there are no disruptions. Check network alerts and official rider help before relying on an accessible path.

Check network alertsOfficial rider help
Nearby amenities

Nearby municipal washrooms and drinking fountains are shown separately from station-owned amenities. The source does not establish that they are inside the station, open now, or reachable by a step-free path.

Nearby amenities

Loading after departures…

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
Sample
40 departures across 4 published platform records in the current four-hour board.
Coverage
15 departures have a published live prediction; 25 are timetable-only.

Sources

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.