Wà:s ne kahiatónhsera

Bus ohnà:ken

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

Filled in: tsi teiontkahrhatsténhtha 3068 · 2:31 a.m. · pick one

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

Buses now:Kwah tsi nikahwistà:kelateyou

2O-Train Line 2 · station 3068

Limebank

Trains · timetableKwah tsi nikahwistà:kelateIah thé:nen
Every 12 to 13 min · sched. then 6:10
2
2Bayview · platform LIMEBANK O-TRAIN NORTH / NORD
Shé:kon iah tetewatahsónteren
5:57
sched. then 6:10
Tiótkon 10 min · sched. then 6:27
2
2Limebank · platform LIMEBANK O-TRAIN
Shé:kon iah tetewatahsónteren
6:17
sched. then 6:27
Buses at Limebank · timetableupdated 30 s ago
Tiótkon 28 min · sched. then 5:25
105
105St-Laurent · platform A · every 28 to 28 min
Shé:kon iah tetewatahsónteren
4:57
sched. then 5:25
Tiótkon 30 min · sched. then 5:31
110
110Hurdman · platform A · every 30 to 30 min
Shé:kon iah tetewatahsónteren
5:01
sched. then 5:31
Tiótkon 60 min · sched. then 6:12
73
73Fallowfield · platform G · every 60 to 60 min
Shé:kon iah tetewatahsónteren
5:12
sched. then 6:12
Tiótkon 28 min · sched. then 5:49
70
70Limebank · platform C · every 28 to 28 min
Shé:kon iah tetewatahsónteren
5:21
sched. then 5:49
Every 12 to 36 min · sched. then 6:00
70
70Fallowfield · platform I · every 12 to 36 min
Shé:kon iah tetewatahsónteren
5:24
sched. then 6:00
Tiótkon 30 min · sched. then 5:58
99
99Barrhaven Centre · platform F · every 30 to 30 min
Shé:kon iah tetewatahsónteren
5:28
sched. then 5:58
Every 14 to 24 min · sched. then 6:06
74
74Tunney's Pasture · platform H · every 14 to 24 min
Shé:kon iah tetewatahsónteren
5:42
sched. then 6:06
73
73Limebank
platform C
Shé:kon iah tetewatahsónteren
5:43
from the timetable
Tiótkon 21 min · sched. then 6:09
110
110Innovation · platform F · every 21 to 21 min
Shé:kon iah tetewatahsónteren
5:48
sched. then 6:09
Tiótkon 25 min · sched. then 6:17
99
99Limebank · platform C · every 25 to 25 min
Shé:kon iah tetewatahsónteren
5:52
sched. then 6:17
283
283Limebank
platform C
Shé:kon iah tetewatahsónteren
5:54
from the timetable
74
74Limebank
platform C
Shé:kon iah tetewatahsónteren
6:05
from the timetable
198
198Limebank
platform C
Shé:kon iah tetewatahsónteren
6:17
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

94% predicted within five minutes of schedule. 1,264 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: Bike parking, 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 LIMEBANK

Cancellations at this station

Local count cannot be published

Exact stop-call evidence could not be read for Oct 28, 2026 – Nov 3, 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
    30 listed departures · 0 live provider predictions

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

    Prediction agreement
    94% predicted within five minutes of schedule. 1,264 eligible provider predictions; arrivals not independently measured
    Bus prediction reliability at this station

    Ka' nikarihò:ten

    Bus prediction reliability at this station

    Early evidence: 5 of 20 weekdays with eligible final provider predictions. This updates hourly; more records will make the estimate steadier.

    94% of final provider predictions within 5 minutes of the timetable, from 1,264 predictions over 5 weekdays, with no sampled hour far below the rest.

    Median predicted difference from the timetable: on the minute. At the 95th percentile: 6 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. 5 weekdays with eligible predictions, 2026-10-28 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, 5 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: 87.2% of final predictions within five minutes of the timetable, 47 predictions, typically 0.1 min late
    7. 06:00: 96.6% of final predictions within five minutes of the timetable, 88 predictions, typically 0 min late
    8. 07:00: 98.8% of final predictions within five minutes of the timetable, 81 predictions, typically 0 min late
    9. 08:00: 97.3% of final predictions within five minutes of the timetable, 73 predictions, typically 0 min late
    10. 09:00: 95.5% of final predictions within five minutes of the timetable, 66 predictions, typically 0.2 min late
    11. 10:00: 100% of final predictions within five minutes of the timetable, 73 predictions, typically 0 min late
    12. 11:00: 97.3% of final predictions within five minutes of the timetable, 73 predictions, typically 0 min late
    13. 12:00: 94.5% of final predictions within five minutes of the timetable, 73 predictions, typically 0.5 min late
    14. 13:00: 100% of final predictions within five minutes of the timetable, 69 predictions, typically 0.5 min late
    15. 14:00: 95.8% of final predictions within five minutes of the timetable, 71 predictions, typically 0.2 min late
    16. 15:00: 84% of final predictions within five minutes of the timetable, 81 predictions, typically 0.3 min late
    17. 16:00: 84.1% of final predictions within five minutes of the timetable, 88 predictions, typically 0.9 min late
    18. 17:00: 87.2% of final predictions within five minutes of the timetable, 94 predictions, typically 0.5 min late
    19. 18:00: 94.7% of final predictions within five minutes of the timetable, 76 predictions, typically 0 min late
    20. 19:00: 98.4% of final predictions within five minutes of the timetable, 62 predictions, typically 0 min late
    21. 20:00: 100% of final predictions within five minutes of the timetable, 56 predictions, typically 0 min late
    22. 21:00: 87.5% of final predictions within five minutes of the timetable, 48 predictions, typically 0 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
    StrengthPredictions consistently close to timetable05:00 to 22:0084%Keep what works

    How LIMEBANK 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 17 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 17

    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 17

    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

    Predictions consistently close to timetable · 05:00 to 22:00
    Worst hour on time 84%
    Median hour on time 95.8%
    Hours measured 17

    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
    30 departures across 8 published platform records in the current four-hour board.
    Coverage
    0 departures have a published live prediction; 30 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.