Buses now:Kwah tsi nikahwistà:kelateyou
We cannot confirm elevator status right now.
More at this station
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 networkBuses from here
Tap a route for live buses and how full they are.
In the station
No published source lists amenities here yet.
Transfers and paths
Platforms and wayfinding (9)→
Each row is an individual platform stop. Open it for departures from that platform; use Departures for every platform together.
- Platform 1ABILLINGS BRIDGE 1A (A)→
- Platform 2ABILLINGS BRIDGE 2A (B)→
- Platform 3ABILLINGS BRIDGE 3A→
- Platform 3BBILLINGS BRIDGE 3B→
- Platform 3CBILLINGS BRIDGE 3C→
- Platform 4BBILLINGS BRIDGE 4B→
- Platform 4CBILLINGS BRIDGE 4C→
- Platform 4DBILLINGS BRIDGE 4D→
- BILLINGS BRIDGE / BANK→
Station sources can include entrances and indoor paths. Check Transfers and paths for what this station’s source actually contains. A published path does not verify an entrance is open, a step-free route is usable, or how to reach a bay from the street.
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 OpenStreetMapTransfers and paths→
Official paths inside the station
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.
No step-by-step guide for this station yet. 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-10-30, 1:00:32 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
- 6ee8491d-8f94-4122-a67b-ef228d9e0945
- Parser version
- 2026-09-30.1
- Combined source checksum
- 44beccfc80480bcb5f6084066f2aa70a08abb7e234cb0bbc90f550e65ea08188
Find your way through this station
Start with what we know for sure. Open any row for platforms, transfers, accessibility and nearby services.
Published entrances and exits
No entrance record is published. Approach routes and exits remain unknown.
The operator may publish a station map or guide outside its machine-readable transit feed.
Open OC Transpo station informationAccessibility
→
Imported boarding information is shown separately when available. It does not verify a complete accessible route or current operating condition. Missing information is not a confirmation.
- Complete accessible route
- 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.
Boarding kahiatónhsera
These are static wheelchair-boarding facts from the imported GTFS schedule. They do not confirm current elevator operation, an open path, or an available vehicle.
Iah tekarihwahní:rats ne tsi nón:we tkaié:ri ne kahiatónhsera tánon tsi nahò:ten wahskerhatié:ten.
- Published station record
- The station record does not specify wheelchair boarding.
Iah tetewaterièn:tare akwé:kon tsi nón:we.
- Tsi nón:we 1A
- Wheelchair boarding is not specified for this platform.
- Tsi nón:we 2A
- Wheelchair boarding is not specified for this platform.
- Tsi nón:we 3A
- Wheelchair boarding is not specified for this platform.
- Tsi nón:we 3B
- Wheelchair boarding is not specified for this platform.
- Tsi nón:we 3C
- Wheelchair boarding is not specified for this platform.
- Tsi nón:we 4B
- Wheelchair boarding is not specified for this platform.
- Tsi nón:we 4C
- Wheelchair boarding is not specified for this platform.
- Tsi nón:we 4D
- Wheelchair boarding is not specified for this platform.
- Tsi nón:we BILLINGS BRIDGE / BANK
- Wheelchair boarding is not specified for this platform.
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.
Tsi nón: tká:ien: Current imported agency GTFS; detailed station accessibility has not been verified from this imported schedule
Review 8 unverified links
- 01Path to the stationTóka'
- 02Station entranceTóka'
- 03Fare gate or paid-area entryTóka'
- 04Path to the platformTóka'
- 05Required elevatorsTóka'
- 06Boarding at 9 platform(s)Tóka'
- 07Transfer linksTóka'
- 08Destination-side exitTóka'
Performance
Service delivery · evidence state
Service at BILLINGS BRIDGE
Cancellations at this station
Local count cannot be published
Exact stop-call evidence could not be read for Oct 27, 2026 – Nov 2, 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 · 31 live provider predictions
- Prediction agreement
- 81.1% predicted within five minutes of schedule. 10,333 eligible provider predictions; arrivals not independently measured
Server snapshot assembled Nov 3, 2026, 9:41 p.m.; open Departures for a refreshed board. This is not a cancellation count.
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.
81.1% of final provider predictions within 5 minutes of the timetable, from 10,333 predictions over 6 weekdays. The lowest sampled hour is 17:00 at 70%.
Median predicted difference from the timetable: 2 min late. At the 95th percentile: 9 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-27 to 2026-11-03. Within five minutes means the final prediction differs from the schedule by no more than five minutes.
- 00:00: 87.4% of final predictions within five minutes of the timetable, 143 predictions, typically 0.7 min late00
- 01:00: 81.1% of final predictions within five minutes of the timetable, 74 predictions, typically 2.3 min late01
- 02:00: 93.5% of final predictions within five minutes of the timetable, 31 predictions, typically 0.5 min late02
- 03:00: not enough data03
- 04:00: 96.7% of final predictions within five minutes of the timetable, 92 predictions, typically 0.7 min late04
- 05:00: 87.6% of final predictions within five minutes of the timetable, 249 predictions, typically 1.2 min late05
- 06:00: 86.5% of final predictions within five minutes of the timetable, 468 predictions, typically 1.4 min late06
- 07:00: 86.1% of final predictions within five minutes of the timetable, 646 predictions, typically 1.5 min late07
- 08:00: 80.5% of final predictions within five minutes of the timetable, 665 predictions, typically 2.1 min late08
- 09:00: 82.5% of final predictions within five minutes of the timetable, 634 predictions, typically 1.7 min late09
- 10:00: 82.5% of final predictions within five minutes of the timetable, 588 predictions, typically 1.4 min late10
- 11:00: 81.6% of final predictions within five minutes of the timetable, 597 predictions, typically 1.4 min late11
- 12:00: 80.5% of final predictions within five minutes of the timetable, 585 predictions, typically 1.9 min late12
- 13:00: 79.2% of final predictions within five minutes of the timetable, 596 predictions, typically 1.8 min late13
- 14:00: 83.6% of final predictions within five minutes of the timetable, 568 predictions, typically 1.6 min late14
- 15:00: 75.4% of final predictions within five minutes of the timetable, 633 predictions, typically 2 min late15
- 16:00: 76% of final predictions within five minutes of the timetable, 638 predictions, typically 2.2 min late16
- 17:00: 69.6% of final predictions within five minutes of the timetable, 672 predictions, typically 2.3 min late17
- 18:00: 78.3% of final predictions within five minutes of the timetable, 621 predictions, typically 1.7 min late18
- 19:00: 81.2% of final predictions within five minutes of the timetable, 467 predictions, typically 1.3 min late19
- 20:00: 84.3% of final predictions within five minutes of the timetable, 426 predictions, typically 0.8 min late20
- 21:00: 83.7% of final predictions within five minutes of the timetable, 356 predictions, typically 1.5 min late21
- 22:00: 85% of final predictions within five minutes of the timetable, 306 predictions, typically 1.2 min late22
- 23:00: 84.2% of final predictions within five minutes of the timetable, 260 predictions, typically 1 min late23
- 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
How BILLINGS BRIDGE 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 23 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 23
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 23
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
Station information
Lines served (12)→
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…
Station evidence and sources
Print view prepared from the station record shown on this page. https://otranspo.ca/moh/stations/3034_stn
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
- Elevator unavailable →
- Accessibility barrier →
- Washroom unavailable →
- Cleanliness →
- Graffiti →
- Damage →
- Lighting →
- Snow or ice →
- Safety →
- Other issue →
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 9 published platform records in the current four-hour board.
- Coverage
- 31 departures have a published live prediction; 9 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.
Contains information licensed under the Open Government Licence – City of Ottawa.