Wà:s ne kahiatónhsera

Bus ohnà:ken

Sahró:ri tsi nahò:ten iah tekaié:ri

Filled in: tsi teiontkahrhatsténhtha 3023 · 11:18 p.m. · pick one

Oh nahò:ten iahà:wen
Full report No account needed

Buses now:Kwah tsi nikahwistà:kelateyou

1O-Train Line 1 · station 3023

Hurdman

Trains · timetableKwah tsi nikahwistà:kelateIah thé:nen
Every 9 to 15 min · sched. then 11:27
1
1Blair · platform 2
Shé:kon iah tetewatahsónteren
11:18
sched. then 11:27
Every 13 to 17 min · sched. then 11:41
1
1Tunney's Pasture · platform 1
Shé:kon iah tetewatahsónteren
11:24
sched. then 11:41
Buses at Hurdman · liveupdated 30 s ago
48
48Billings Bridge
platform D
Shé:kon iah tetewatahsónteren
Ó:nenò:nen
9
9Hurdman
platform B
Shé:kon iah tetewatahsónteren
11:18
from the timetable
48
48Hurdman
platform B
Shé:kon iah tetewatahsónteren
11:19
from the timetable
Tiótkon 33 min · then 37 sched.
98
98Hawthorne · platform C · every 33 to 33 min
Shé:kon iah tetewatahsónteren
4minitò:nen
then 37 sched.
Tiótkon 30 min · sched. then 11:52
44
44Hurdman · platform B · every 30 to 30 min
Shé:kon iah tetewatahsónteren
11:22
sched. then 11:52
Tiótkon 30 min · then 35 sched.
90
90Greenboro · platform D · every 30 to 30 min
Shé:kon iah tetewatahsónteren
5minitò:nen
then 35 sched.
Tiótkon 26 min · sched. then 11:53
88
88Hurdman · platform B · every 26 to 26 min
Shé:kon iah tetewatahsónteren
11:27
sched. then 11:53
Tiótkon 30 min · then 39 sched.
45
45Hospital ~ Hôpital · platform C · every 30 to 30 min
Shé:kon iah tetewatahsónteren
9minitò:nen
then 39 sched.
98
98Hurdman
platform B
Shé:kon iah tetewatahsónteren
11:28
from the timetable
Every 19 to 25 min · sched. then 11:53
10
10Hurdman · platform B · every 19 to 25 min
Shé:kon iah tetewatahsónteren
11:28
sched. then 11:53
Tiótkon 30 min · then 40 sched.
88
88Bayshore · platform C · every 30 to 30 min
Shé:kon iah tetewatahsónteren
10minitò:nen
then 40 sched.
Tiótkon 30 min · then 42 sched.
44
44Billings Bridge · platform D · every 30 to 30 min
Shé:kon iah tetewatahsónteren
13minitò:nen
then 42 sched.
Tiótkon 31 min · then 50 sched.
105
105Uplands · platform C · every 31 to 31 min
Shé:kon iah tetewatahsónteren
19minitò:nen
then 50 sched.
Tiótkon 30 min · sched. then 12:11
45
45Hurdman · platform A · every 30 to 30 min
Shé:kon iah tetewatahsónteren
11:41
sched. then 12:11
Tiótkon 23 min · sched. then 12:06
90
90Hurdman · platform B · every 23 to 23 min
Shé:kon iah tetewatahsónteren
11:43
sched. then 12:06
Tiótkon 26 min · sched. then 12:19
105
105St-Laurent · platform B · every 26 to 26 min
Shé:kon iah tetewatahsónteren
11:53
sched. then 12:19
Entrances and elevators

We cannot confirm elevator status right now.

89.8% predicted within five minutes of schedule. 5,052 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 here6 places within 5 min · nearest: Racks for 10 bikes, covered, 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 HURDMAN

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

Server snapshot assembled Nov 3, 2026, 11:18 p.m.; open Departures for a refreshed board. This is not a cancellation count.

Prediction agreement
89.8% predicted within five minutes of schedule. 5,052 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.

89.8% of final provider predictions within 5 minutes of the timetable, from 5,052 predictions over 6 weekdays. The lowest sampled hour is 17:00 at 80%.

Median predicted difference from the timetable: 42 s late. 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. This station also has 1 O-Train line. This line is not included because OC Transpo does not publish realtime rail data.

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.

Final provider predictions within five minutes of the timetable, by hour, 6 weekdays
  1. 00:00: 93.4% of final predictions within five minutes of the timetable, 76 predictions, typically 0.3 min late
  2. 01:00: 95.8% of final predictions within five minutes of the timetable, 71 predictions, typically 0.9 min late
  3. 02:00: 88.3% of final predictions within five minutes of the timetable, 60 predictions, typically 0.6 min late
  4. 03:00: 84.6% of final predictions within five minutes of the timetable, 65 predictions, typically 0.3 min late
  5. 04:00: 94.4% of final predictions within five minutes of the timetable, 89 predictions, typically 0.1 min early
  6. 05:00: 93.7% of final predictions within five minutes of the timetable, 111 predictions, typically 0.3 min late
  7. 06:00: 91.9% of final predictions within five minutes of the timetable, 234 predictions, typically 1.6 min late
  8. 07:00: 90.8% of final predictions within five minutes of the timetable, 284 predictions, typically 0 min late
  9. 08:00: 84.4% of final predictions within five minutes of the timetable, 288 predictions, typically 1.5 min late
  10. 09:00: 90.9% of final predictions within five minutes of the timetable, 265 predictions, typically 0.9 min late
  11. 10:00: 92.8% of final predictions within five minutes of the timetable, 265 predictions, typically 0.8 min late
  12. 11:00: 94.8% of final predictions within five minutes of the timetable, 271 predictions, typically 0 min late
  13. 12:00: 93.2% of final predictions within five minutes of the timetable, 278 predictions, typically 0 min late
  14. 13:00: 91.3% of final predictions within five minutes of the timetable, 264 predictions, typically 0.1 min late
  15. 14:00: 89.6% of final predictions within five minutes of the timetable, 297 predictions, typically 0 min late
  16. 15:00: 91.3% of final predictions within five minutes of the timetable, 343 predictions, typically 0.9 min late
  17. 16:00: 80.4% of final predictions within five minutes of the timetable, 326 predictions, typically 1.6 min late
  18. 17:00: 79.9% of final predictions within five minutes of the timetable, 308 predictions, typically 2.1 min late
  19. 18:00: 91.7% of final predictions within five minutes of the timetable, 277 predictions, typically 1.5 min late
  20. 19:00: 89.7% of final predictions within five minutes of the timetable, 223 predictions, typically 0.3 min late
  21. 20:00: 95.6% of final predictions within five minutes of the timetable, 203 predictions, typically 1.4 min late
  22. 21:00: 90.2% of final predictions within five minutes of the timetable, 173 predictions, typically 0 min late
  23. 22:00: 91% of final predictions within five minutes of the timetable, 155 predictions, typically 1.3 min late
  24. 23:00: 87.3% of final predictions within five minutes of the timetable, 126 predictions, typically 0.5 min late
  • 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 HURDMAN 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 24 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 24

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 24

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

O-Train evidence

What we know about train service here

Open the train observation report

Trains are not in the public data feed

The bus punctuality reports compare archived arrival predictions with published schedules. They do not count independently measured physical arrivals. Otranspo has no comparable public train-position dataset for these reports, so those bus figures cannot show where a train is or whether Lines 1, 2 and 4 run on time.

Publishing train positions, their timestamps, and the measurement method would help build a separate, verifiable record of rail service. The missing dataset does not establish how the trains performed.

Recent shared train observations

These are rider sightings approved by a moderator. They show a reported time and place. They are not official train positions, a complete train count, or proof of a cause.

No approved rider observation matches this place or line in the last 31 days. That does not mean no train ran or no problem occurred.

Share what you observedCheck all official service alertsOpen train research and history
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 7 published platform records in the current four-hour board.
Coverage
11 departures have a published live prediction; 29 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.