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.

Platforms and wayfinding (7)

Each row is an individual platform stop. Open it for departures from that platform; use Departures for every platform together.

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 OpenStreetMap

Transfers 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: 0dd440979a2d1f47af79a157130a722288616e1851472bc35b40a99e97d2c910

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 information

Accessibility

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 1: Wheelchair boarding is not specified for this platform.
Tsi nón:we 2: Wheelchair boarding is not specified for this platform.
Tsi nón:we A: Wheelchair boarding is not specified for this platform.
Tsi nón:we B: Wheelchair boarding is not specified for this platform.
Tsi nón:we C: Wheelchair boarding is not specified for this platform.
Tsi nón:we D: Wheelchair boarding is not specified for this platform.
Tsi nón:we E: 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

Path to the stationTóka'
Station entranceTóka'
Fare gate or paid-area entryTóka'
Path to the platformTóka'
Required elevatorsTóka'
Boarding at 7 platform(s)Tóka'
Transfer linksTóka'
Destination-side exitTóka'

Elevators and escalators

Ó:nen: evidence: Nov 4, 2026, 2:00 p.m.

Iah teiotòn:'on ó:nen ahshiatkáthon tsi iorihwà:ke.

OC Transpo and STO do not publish a live elevator feed. They only post some outages as alerts. No alert does not prove an elevator or escalator works.

Akwé:kon station

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 · 14 live provider predictions
Prediction agreement: 89.5% predicted within five minutes of schedule. 4,711 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.5% of final provider predictions within 5 minutes of the timetable, from 4,711 predictions over 6 weekdays, with no sampled hour far below the rest.

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-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

00:00: 93.4% of final predictions within five minutes of the timetable, 76 predictions, typically 0.5 min late
01:00: 97.2% of final predictions within five minutes of the timetable, 71 predictions, typically 0.9 min late
02:00: 86.7% of final predictions within five minutes of the timetable, 60 predictions, typically 0.6 min late
03:00: 81.5% of final predictions within five minutes of the timetable, 65 predictions, typically 0.4 min late
04:00: 93.3% of final predictions within five minutes of the timetable, 90 predictions, typically 0.1 min early
05:00: 93.7% of final predictions within five minutes of the timetable, 111 predictions, typically 0.2 min late
06:00: 91.1% of final predictions within five minutes of the timetable, 235 predictions, typically 1.6 min late
07:00: 90.8% of final predictions within five minutes of the timetable, 284 predictions, typically 0 min late
08:00: 82.6% of final predictions within five minutes of the timetable, 288 predictions, typically 1.6 min late
09:00: 89.6% of final predictions within five minutes of the timetable, 268 predictions, typically 0.9 min late
10:00: 91.7% of final predictions within five minutes of the timetable, 266 predictions, typically 0.7 min late
11:00: 94.4% of final predictions within five minutes of the timetable, 270 predictions, typically 0 min late
12:00: 92.4% of final predictions within five minutes of the timetable, 277 predictions, typically 0 min late
13:00: 91.1% of final predictions within five minutes of the timetable, 236 predictions, typically 0.1 min late
14:00: 89.9% of final predictions within five minutes of the timetable, 257 predictions, typically 0 min late
15:00: 90.8% of final predictions within five minutes of the timetable, 295 predictions, typically 0.9 min late
16:00: 80.3% of final predictions within five minutes of the timetable, 279 predictions, typically 1.7 min late
17:00: 80.8% of final predictions within five minutes of the timetable, 265 predictions, typically 2.1 min late
18:00: 91.3% of final predictions within five minutes of the timetable, 240 predictions, typically 0.9 min late
19:00: 89.7% of final predictions within five minutes of the timetable, 194 predictions, typically 0.3 min late
20:00: 94.9% of final predictions within five minutes of the timetable, 178 predictions, typically 1.4 min late
21:00: 90.7% of final predictions within five minutes of the timetable, 151 predictions, typically 0 min late
22:00: 91.9% of final predictions within five minutes of the timetable, 135 predictions, typically 1.4 min late
23:00: 85.8% of final predictions within five minutes of the timetable, 120 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

Findings
What	Ó:nen	Tewaterièn:tare	Scenario or next investigation
StrengthPredictions consistently close to timetable	00:00 to 00:00	80%	Keep what works

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: 2026-11-04T18:03:14.152Z · Method: settled-arrivals-oc-sto-conventional-v5

Predictions consistently close to timetable · 00:00 to 00:00: Worst hour on time 80.3%; Median hour on time 90.9%; Hours measured 24

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 observed Check all official service alerts Open train research and history

Official timetable

OC Transpo does not publish O-Train positions or arrival predictions in the public feed Otranspo receives. Schedules, official alerts, and rider observations are shown separately so one source cannot impersonate another.

Ask for this data

Turn this gap into a public-data request

OC Transpo does not publish live O-Train positions in the public feed Otranspo can use. You can ask the City to publish them in a stable, reusable format.

This is your message. Edit it before opening your own email app. Otranspo does not send it, track delivery, or speak for you. Write to one relevant recipient; do not use this tool for mass email, harassment, or personal or sensitive information.

How do you want to address this draft?

Choose an official recipientEnter another recipient email

Subject

Message

Choose an official recipient or enter one valid other email address to open an email draft.

Check the official councillor directory Send through OC Transpo’s official feedback form Official contact sources

Lines served (19)

OC Transpo does not publish live train positions or predictions for O-Train lines. Train times shown here therefore come from the timetable.

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.

Shelter and bench

The City publishes 7 records with stop code 3023. None is attached here because choosing one would be a guess.

Method and limitations

Nearby public washrooms

The City publishes 209 locations; none is within 400 m.

Drinking water nearby

The City publishes 133 locations with drinking water across Ottawa; none is within 400 m of here.

Nearby amenities

Loading after departures…

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.

Computed or assembled: November 4, 2026 at 1:57 p.m.
Kén:k nikón: 40 departures across 7 published platform records in the current four-hour board.
Coverage: 14 departures have a published live prediction; 26 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.

Draft

This translation is a draft.

Help improve it

About 23% of this site is translated so far. The rest is shown in English.

Read this page in English

This page is a machine draft in Mohawk (Kanien’kéha), the language of the Kanien’kehá:ka (Mohawk) communities. It was prepared without review by its speakers, and is waiting for one. Speakers and the community are invited to correct it. We will replace it with their words. Ottawa is on the unceded territory of the Anishinabe Algonquin Nation.

Cette page est une ébauche automatique en mohawk (kanien’kéha), la langue des communautés kanien’kehá:ka (mohawks). Elle a été préparée sans révision par ses locuteurs, et attend l’un d’eux. Les locuteurs et la communauté sont invités à la corriger. Nous la remplacerons par leurs mots. Ottawa se trouve sur le territoire non cédé de la Nation algonquine anishinabe (Anishinabe Algonquin Nation).

Hurdman

More at this station

Station details

Step-free route

Buses from here

In the station

Transfers and paths

What this feed version includes

Find your way through this station

Published entrances and exits

Accessibility

Boarding kahiatónhsera

Elevators and escalators

Performance

Service at HURDMAN

Bus prediction reliability at this station

How HURDMAN is doing

Scheduling

Operations: not measurable here

What we know about train service here

Recent shared train observations

Station information

Shelter and bench

Nearby public washrooms

Drinking water nearby

Nearby amenities

Community reports

What is being shown

How it was produced

Evidence dates

Tsi nón: ionkwaién:ta'

Limits to keep in mind

Elevators and escalators

Shelter and bench

Nearby public washrooms

Drinking water nearby