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

OC Transpo station · 3049

Beatrice

Buses at Beatrice · liveupdated 30 s ago
Every 28 to 33 min · then 31 · 58 sched.
99
99Limebank · platform A · every 28 to 33 min
Shé:kon iah tetewatahsónteren
Ó:nenò:nen
then 31 · 58 sched.
Every 27 to 34 min · then 48 · 82 sched.
99
99Barrhaven Centre · platform B · every 27 to 34 min
Shé:kon iah tetewatahsónteren
15minitò:nen
then 48 · 82 sched.
Every 27 to 30 min · then 54 · 84 sched.
110
110Innovation · platform B · every 27 to 30 min
Shé:kon iah tetewatahsónteren
23minitò:nen
then 54 · 84 sched.
Every 25 to 37 min · then 56 · 86 sched.
110
110Limebank · platform A · every 25 to 37 min
Shé:kon iah tetewatahsónteren
31minitò:nen
then 56 · 86 sched.
Entrances and elevators

We cannot confirm elevator status right now.

79.7% predicted within five minutes of schedule. 812 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 here2 places within 5 min · nearest: Racks for 30 bikes, 1 min ohsitá:keBike parking: OpenStreetMap, data as of Jun 1, 2026. The walk is an estimate.
Details →
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 BEATRICE

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
32 listed departures · 5 live provider predictions

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

Prediction agreement
79.7% predicted within five minutes of schedule. 812 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.

79.7% of final provider predictions within 5 minutes of the timetable, from 812 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 45%.

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-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: 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: not enough data
  7. 06:00: 77.8% of final predictions within five minutes of the timetable, 45 predictions, typically 1.3 min late
  8. 07:00: 85.1% of final predictions within five minutes of the timetable, 47 predictions, typically 1.9 min late
  9. 08:00: 71.7% of final predictions within five minutes of the timetable, 46 predictions, typically 2.5 min late
  10. 09:00: 93.6% of final predictions within five minutes of the timetable, 47 predictions, typically 1.5 min late
  11. 10:00: 87.5% of final predictions within five minutes of the timetable, 48 predictions, typically 1.4 min late
  12. 11:00: 87.5% of final predictions within five minutes of the timetable, 48 predictions, typically 1.7 min late
  13. 12:00: 89.4% of final predictions within five minutes of the timetable, 47 predictions, typically 0.7 min late
  14. 13:00: 81.3% of final predictions within five minutes of the timetable, 48 predictions, typically 2 min late
  15. 14:00: 79.1% of final predictions within five minutes of the timetable, 43 predictions, typically 2.4 min late
  16. 15:00: 77.1% of final predictions within five minutes of the timetable, 48 predictions, typically 3.2 min late
  17. 16:00: 45.2% of final predictions within five minutes of the timetable, 42 predictions, typically 5.4 min late
  18. 17:00: 68.4% of final predictions within five minutes of the timetable, 57 predictions, typically 3.8 min late
  19. 18:00: 76.5% of final predictions within five minutes of the timetable, 51 predictions, typically 2.5 min late
  20. 19:00: 94% of final predictions within five minutes of the timetable, 50 predictions, typically 1.2 min late
  21. 20:00: 75% of final predictions within five minutes of the timetable, 40 predictions, typically 2.2 min late
  22. 21:00: 71% of final predictions within five minutes of the timetable, 31 predictions, typically 1.8 min late
  23. 22:00: not enough data
  24. 23:00: not enough data
  • 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 later than timetable15:00 to 18:004.1 min lateRunning time on the routes here
ProblemOne hour has a lower prediction match16:0045%Operations in that hour

How BEATRICE 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 16 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

81.3%

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

Route-hours with repeated late predictions

3of 16

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 16

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

3.8min

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 later than timetable · 15:00 to 18:00
Median delay 4.1 min
Measured arrivals 147
Ioiánere tsi nikarì:wes 68.4%
One hour has a lower prediction match · 16:00
Ioiánere tsi nikarì:wes 45.2%
Other hours on time 79.1%
Measured arrivals 42
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
32 departures across 2 published platform records in the current four-hour board.
Coverage
5 departures have a published live prediction; 27 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.