Skip to main content
Otranspo
FR

IRIS

Ottawa · OC Transpo · Departures · All platforms at this station · 3 Platforms · #3016

Board updated

1A2 routes2A2 routes
  1. 1A75Barrhaven CentreOperator: OC Transpo1min01:34 p.m. · 2 min earlyLive
  2. 2A75Tunney's PastureOperator: OC Transpo9min01:42 p.m. · 8 min lateLive
  3. 2A74Tunney's PastureOperator: OC Transpo12min01:46 p.m. · 9 min lateLive
  4. 2A75Tunney's PastureOperator: OC Transpo15min01:48 p.m. · 2 min earlyLive
  5. 1A74LimebankOperator: OC Transpo17min01:50 p.m. · 4 min lateLive
  6. 1A75CambrianOperator: OC Transpo21min01:54 p.m. · 3 min lateLive
  7. 1A75Barrhaven CentreOperator: OC Transpo32min02:06 p.m.Live
  8. 2A74Tunney's PastureOperator: OC Transpo33min02:06 p.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

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

Find your way through this station

Start with what the current sources can confirm. Open any row for the complete platform, transfer, accessibility, or amenity evidence.

The operator may publish a station map or guide outside its machine-readable transit feed.

Open OC Transpo 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.

Lines served (2)
Platforms and wayfinding (3)

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.

This feed version contains no published station path or transfer rule that can support a platform-to-platform guide.

A published path is not a verified accessible path. It does not prove that elevators are operating, every entrance is represented, or the route is suitable for a particular rider.

Source details

What this feed version includes

Imported source observed 2026-09-18, 5:00:16 a.m.

Station levels
The operator omitted this optional file from the feed
Indoor paths
The operator omitted this optional file from the feed
Transfer rules
The operator omitted this optional file from the feed
Feed version
99de510d-89b0-4652-9d93-217659284cf2
Parser version
2026-08-25.4
Combined source checksum
6ea0e1f6e32a67268ea7a89ce4fa64d15c914ac4d54208cbe0421c242cb8ce40
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.

Published station accessibility
Unverified. The imported station record does not confirm a complete accessible route.
Current operating condition
Unknown. Current alerts cannot be matched completely to every entrance, elevator, pathway, and platform.

No verified accessible alternative is available in current data.

Accessibility chain

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

All 8 links are unverified. Review the element list before relying on this station for an accessible trip.

Source: Current imported agency GTFS; detailed station accessibility assets are not published · Observed: 2026-09-19, 5:34:26 p.m.

Review 8 unverified links
  1. Path to the stationUnknown
  2. Station entranceUnknown
  3. Fare gate or paid-area entryUnknown
  4. Path to the platformUnknown
  5. Required elevatorsUnknown
  6. Boarding at 3 platform(s)Unknown
  7. Transfer linksUnknown
  8. Destination-side exitUnknown
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…

Verdict

When this station runs late

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

80.3% of arrivals within 5 minutes, from 2,047 arrivals over 5 weekdays. The worst hour is 12:00 at 67%.

Half the arrivals are 2 min late. The worst 5% are 10 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. 5 weekdays observed, 2026-09-12 to 2026-09-19. On time means no more than five minutes early or late.

Arrivals within five minutes, by hour of day, 5 weekdays
  1. 00:00: 100% of arrivals on time, 33 arrivals, typically 0 min early
  2. 01:00: 96.8% of arrivals on time, 31 arrivals, typically 0.6 min late
  3. 02:00: not enough data
  4. 03:00: not enough data
  5. 04:00: 93.8% of arrivals on time, 32 arrivals, typically 0.4 min late
  6. 05:00: 100% of arrivals on time, 37 arrivals, typically 0 min late
  7. 06:00: 91.9% of arrivals on time, 86 arrivals, typically 1 min late
  8. 07:00: 69.8% of arrivals on time, 126 arrivals, typically 2.5 min late
  9. 08:00: 87.9% of arrivals on time, 124 arrivals, typically 1.3 min late
  10. 09:00: 74.4% of arrivals on time, 121 arrivals, typically 1.4 min late
  11. 10:00: 86.1% of arrivals on time, 115 arrivals, typically 1.9 min late
  12. 11:00: 77.4% of arrivals on time, 115 arrivals, typically 1.4 min late
  13. 12:00: 67% of arrivals on time, 115 arrivals, typically 3.5 min late
  14. 13:00: 76.6% of arrivals on time, 107 arrivals, typically 2.2 min late
  15. 14:00: 70.6% of arrivals on time, 102 arrivals, typically 2.5 min late
  16. 15:00: 69.4% of arrivals on time, 121 arrivals, typically 3.7 min late
  17. 16:00: 71.9% of arrivals on time, 139 arrivals, typically 2.9 min late
  18. 17:00: 71.5% of arrivals on time, 130 arrivals, typically 2 min late
  19. 18:00: 75% of arrivals on time, 120 arrivals, typically 1.9 min late
  20. 19:00: 90.7% of arrivals on time, 86 arrivals, typically 1.3 min late
  21. 20:00: 92.2% of arrivals on time, 77 arrivals, typically 1.2 min late
  22. 21:00: 89.9% of arrivals on time, 79 arrivals, typically 1.3 min late
  23. 22:00: 93.1% of arrivals on time, 58 arrivals, typically 0.6 min late
  24. 23:00: 100% of arrivals on time, 36 arrivals, typically 0.4 min early
  • 90% or more on time
  • 80 to 90% on time
  • under 80% on time
  • not enough data
WhatWhenMeasuredScenario or next investigation
ProblemArrivals run late12:003.5 min lateRunning time on the routes here
ProblemArrivals run late15:003.7 min lateRunning time on the routes here
ProblemOne hour collapses12:0067%Operations in that hour

How IRIS 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 22 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
Cost unavailable until fleet, labour, recovery and transfer effects are tested.

Timetable matches the trip

90.9%

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

Route-hours where the timetable is short

2of 22

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

Route-hours running early

0of 22

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

Running time a short hour needs

3.6min

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 late · 12:00
medianDelaySeconds 212
observations 115
onTimePct 67
Arrivals run late · 15:00
medianDelaySeconds 221
observations 121
onTimePct 69.4
One hour collapses · 12:00
onTimePct 67
otherHoursOnTimePct 87.9
observations 115
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 3 published platform records in the current four-hour board.
Coverage
9 departures have a published live prediction; 31 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.