ᐱᓗᐊᖅᑐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᒧᑦ ᐊᐅᓪᓚᕐᓗᑎᑦ

ᑐᓪᓕᐊ ᐸᓯ

ᐊᔪᕐᓇᖅᑐᖅ ᐅᖃᐅᑎᒋᓗᒍ

ᖃᓄᐃᓕᖓᓯᒪᕙ?
Full report No account needed

Buses now:ᐃᑲᕐᕋᖓᓂᑭᖑᕙᖅᑐᖅyou

2O-Train Line 2 · station 3068

Limebank

Trains · timetableᐃᑲᕐᕋᖓᓂᑭᖑᕙᖅᑐᖅᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
ᑕᒪᑦ 12 ᒥᓂᑦᓂ · sched. then 8:58
2
2Bayview · platform LIMEBANK O-TRAIN NORTH / NORD
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
8:46
sched. then 8:58
ᑕᒪᑦ 12 ᒥᓂᑦᓂ · sched. then 9:04
2
2Limebank · platform LIMEBANK O-TRAIN
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
8:52
sched. then 9:04
Buses at Limebank · liveupdated 30 s ago
13 ᐊᒻᒪ 15 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 9:02
74
74Limebank · platform C · every 13 to 15 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
8:47
sched. then 9:02
ᑕᒪᑦ 15 ᒥᓂᑦᓂ · then 20 · 35 sched.
74
74Tunney's Pasture · platform H · every 15 to 15 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
5ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 20 · 35 sched.
ᑕᒪᑦ 15 ᒥᓂᑦᓂ · sched. then 9:10
70
70Limebank · platform C · every 15 to 15 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
8:55
sched. then 9:10
ᑕᒪᑦ 32 ᒥᓂᑦᓂ · then 42 sched.
70
70Fallowfield · platform I · every 32 to 32 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
10ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 42 sched.
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · sched. then 9:28
99
99Limebank · platform C · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
8:58
sched. then 9:28
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · then 46 sched.
99
99Barrhaven Centre · platform F · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
16ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 46 sched.
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · sched. then 9:38
73
73Limebank · platform C · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
9:08
sched. then 9:38
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · then 53 sched.
110
110Innovation · platform F · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
23ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 53 sched.
ᑕᒪᑦ 30 ᒥᓂᑦᓂ · then 56 sched.
73
73Fallowfield · platform G · every 30 to 30 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
26ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 56 sched.
ᑕᒪᑦ 27 ᒥᓂᑦᓂ · sched. then 9:45
110
110Limebank · platform A · every 27 to 27 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
9:18
sched. then 9:45
Entrances and elevators

We cannot confirm elevator status right now.

94.4% predicted within five minutes of schedule. 1,301 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
ᐸᕐᓇᒋᐊᖅ ᐅᕙᓐᖓᑦ
Bike parking here2 places within 5 min · nearest: Bike parking, 1 ᒥᓂᑦ ᐱᓱᖕᓂᖅBike 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
ᔮᕙᔅᑯᕆᑉ ᐊᑐᖅᑕᐅᙱᑦᑐᖅBoards and departures still show without JavaScript

Station details

Step-free route

ᐅᓪᓗᒥ ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᑕᐅᔪᓐᓇᙱᑦᑐᑦ. ᐊᑖᓂ ᑐᓴᒐᒃᓴᐃᑦ ᖃᖓᓂᖓ ᐅᕝᕙᓘᓐᓃᑦ ᓇᖕᒥᑦ ᐱᓂᖏᑦ ᓇᓗᓇᐃᖅᑕᐅᓯᒪᙱᑦᑐᑦ. ᐃᖏᕐᕋᓚᐅᙱᓐᓂᕐᓂ ᐊᐅᓚᑦᑎᔨ ᐊᐱᕆᓗᒍ.

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 29, 2026 – Nov 4, 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 · 7 live provider predictions

    Server snapshot assembled Nov 5, 2026, 8:46 a.m.; open Departures for a refreshed board. This is not a cancellation count.

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

    ᐃᓱᓕᑦᑎᓂᖅ

    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.

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

    Median predicted difference from the timetable: 1 s ᑭᖑᕙᖅᑐᖅ. At the 95th percentile: 6 min ᑭᖑᕙᖅᑐᖅ.

    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-29 to 2026-11-05. 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: 86% of final predictions within five minutes of the timetable, 57 predictions, typically 0.1 min late
    7. 06:00: 98.1% of final predictions within five minutes of the timetable, 105 predictions, typically 0 min late
    8. 07:00: 100% of final predictions within five minutes of the timetable, 96 predictions, typically 0 min late
    9. 08:00: 97.3% of final predictions within five minutes of the timetable, 74 predictions, typically 0 min late
    10. 09:00: 91.2% of final predictions within five minutes of the timetable, 68 predictions, typically 0.3 min late
    11. 10:00: 100% of final predictions within five minutes of the timetable, 74 predictions, typically 0 min late
    12. 11:00: 97.2% of final predictions within five minutes of the timetable, 72 predictions, typically 0 min late
    13. 12:00: 97.3% of final predictions within five minutes of the timetable, 73 predictions, typically 0 min late
    14. 13:00: 100% of final predictions within five minutes of the timetable, 68 predictions, typically 0.6 min late
    15. 14:00: 95.8% of final predictions within five minutes of the timetable, 72 predictions, typically 0.3 min late
    16. 15:00: 86.4% of final predictions within five minutes of the timetable, 81 predictions, typically 0.3 min late
    17. 16:00: 83.9% of final predictions within five minutes of the timetable, 87 predictions, typically 0.9 min late
    18. 17:00: 88.2% of final predictions within five minutes of the timetable, 93 predictions, typically 0.5 min late
    19. 18:00: 96% of final predictions within five minutes of the timetable, 75 predictions, typically 0.3 min late
    20. 19:00: 98.3% of final predictions within five minutes of the timetable, 59 predictions, typically 0 min late
    21. 20:00: 100% of final predictions within five minutes of the timetable, 54 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ᖃᖓᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅScenario or next investigation
    StrengthPredictions consistently close to timetable05:00 to 22:0084%Keep what works

    How LIMEBANK is doing

    ᑖᒃᑯᐊ ᓇᓗᓇᐃᒃᑯᑕᐃᑦ ᐊᕕᒃᑐᐃᔪᑦ ᐅᑎᖅᑕᖅᐸᒃᑐᒥᒃ ᑭᖑᕙᕐᓂᕐᒥᒃ ᐊᒻᒪ ᐱᓕᕆᕝᕕᐅᑉ ᑎᑭᓐᓂᐊᕐᓂᖏᑦ ᐃᓱᒪᒋᔭᖏᑦ ᐊᓯᔾᔨᖅᐸᓐᓂᖏᓐᓂᒃ. ᐊᐱᖁᑎᓂᒃ ᐃᓱᒪᒋᐊᖅᑎᑦᑎᔪᑦ ᐸᕐᓇᐃᔨᓄᑦ ᐊᒻᒪ ᐱᓕᕆᔨᓄᑦ. ᐱᔾᔪᑎᖓ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ. ᐱᐊᓯᑦ ᖃᖓ ᑎᑭᒻᒪᖔᑕ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ. ᓈᓴᐅᑎ ᑕᒪᐃᓐᓂ ᑕᑯᒃᓴᐅᑎᑦᑎᔪᖅ ᖃᑦᓯᓂᒃ ᐃᖏᕐᕋᕝᕕᒃ-ᐃᑲᕐᕋᓂᒃ ᐊᑐᖅᓯᒪᒻᒪᖔᑦ.

    Measured over 17 route-hours. 0 more were observed too thinly to count, and are excluded rather than assumed good.

    ᐃᑲᕐᕋᓄᑦ ᐋᖅᑭᒃᓯᓂᖅ

    ᐊᑯᓂ ᑭᖑᕙᕐᓂᖏᑦ ᓂᕆᐅᒋᔭᐅᔪᑦ ᑕᑯᑎᑦᑎᔪᓐᓇᖅᑐᑦ ᐃᑲᕐᕋᓕᐊᖑᔪᖅ ᕿᒥᕐᕈᔭᐅᒃᓴᐅᓂᖓᓂᒃ. ᕿᒥᕐᕈᓗᒋᑦ ᑎᑭᑦᑐᑦ ᐃᑲᕐᕋᖏᑦ ᐊᒻᒪ ᐊᐅᓪᓚᑎᑦᑎᓂᕐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ. ᑕᐃᒪ ᐃᓱᒪᓕᐅᕐᓗᑎᑦ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐱᕕᒃ ᐊᓯᔾᔨᕆᐊᖃᕐᒪᖔᑦ.

    ᑭᓇ ᐋᖅᑭᒃᓯᔪᓐᓇᖅᐸ
    ᐃᖏᕐᕋᓂᕐᒧᑦ ᐸᕐᓇᐃᔨ
    ᖃᓄᖅ ᐊᑭᖃᖅᐸ
    ᐊᑭᖏᑦ ᓇᓗᓇᖅᐳᑦ ᓱᓕ. ᖃᐅᔨᓴᖅᑕᐅᔭᕆᐊᖃᖅᐳᑦ ᐊᖅᑲᐅᑏᑦ, ᐃᖅᑲᓇᐃᔭᖅᑏᑦ, ᐊᑭᓕᖅᑕᐅᓂᖏᑦ ᐊᒻᒪ ᐊᓯᔾᔨᖅᓯᓂᖏᑦ.

    ᓇᓚᐅᑦᑖᖅᑕᐅᓯᒪᔪᑦ ᐃᑲᕐᕋᐃᑦ ᐊᓪᓚᓯᒪᔪᓂᒃ ᖃᓂᒋᔭᖃᖅᑐᑦ

    100%

    Route-hours where the median eligible arrival prediction is less than one minute early and less than three minutes late.

    ᐊᖅᑯᑎᐅᑉ ᐃᑲᕐᕋᖏᑦ ᑭᖑᕙᕆᐊᖃᑦᑕᕐᓂᐊᖅᑐᖅ ᐅᖃᐅᓯᐅᖃᑦᑕᖅᑐᑦ

    0of 17

    ᐃᖏᕐᕋᕝᕕᐅᑉ ᐃᑲᕐᕋᖏᑦ, ᑎᑭᓂᐊᕐᓂᖏᑦ ᓂᕆᐅᒋᔭᐅᔪᑦ ᐊᑯᓐᓂᐊᓂ ᐱᖓᓱᓂᒃ ᒥᓂᑦᓂᒃ ᐅᖓᑖᓄᓪᓘᓐᓃᑦ ᑭᖑᕙᖅᑐᑦ. ᐃᖏᕐᕋᓂᖓᑕ ᐊᑯᓐᓂᖓ ᖃᐅᔨᓴᕐᓗᒍ ᐃᖏᕐᕋᓂᕐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᓂᒃ ᓴᓂᐊᓂᒃ.

    ᐃᖏᕐᕋᕝᕕᐃᑦ ᐃᑲᕐᕋᖏᑦ, ᐸᔅ ᓯᕗᓪᓕᐅᕐᓂᐊᕐᓂᖓᓂᒃ ᓇᓚᐅᑦᑖᖅᑕᐅᑎᓪᓗᒍ

    0of 17

    ᐊᖁᑎ ᐃᑲᕐᕋᖏᑦ, ᑕᐃᑦᓱᒪᓂ ᑎᑭᓐᓂᐊᕐᓂᖓᓄᑦ ᓇᓚᐅᑦᑖᕐᓂᖅ ᐊᑯᓐᓂᐊᓂ ᓯᕗᓪᓕᐅᕐᓂᐊᖅᑐᖅ ᐊᑕᐅᓯᕐᒥᒃ ᒥᓂᑦᒥᒃ ᐅᖓᑖᓄᓪᓘᓃᑦ. ᐅᓇ ᓇᓗᓇᐃᖅᓯᙱᑦᑐᖅ ᐸᓯᑦ ᓯᕗᓪᓕᐅᖅᖢᑎᒃ ᐊᐅᓪᓚᓚᐅᖅᓯᒪᓂᖏᓐᓂᒃ.

    ᑭᖑᕙᕆᐊᕐᓂᖅ ᓂᕆᐅᒋᔭᐅᑦᑕᐃᓐᓇᖅᑐᖅ

    ᑖᔅᓱᒪ ᑕᖅᑭᐅᑉ ᐃᓗᐊᓂ ᓇᓗᓇᐃᖅᓯᒍᑎᑦ ᓈᒻᒪᙱᑦᑐᑦ ᑖᓐᓇ ᓴᖅᑭᑎᑦᑎᓂᐊᕐᓗᒍ.

    ᑭᖑᕙᕆᐊᖃᕐᓂᖅ ᐊᑐᐃᓐᓇᐅᓂᖅᐹᖅ ᓂᕆᐅᒋᔭᐅᔪᖅ ᐃᖏᕐᕋᕝᕕᓐᓂ ᓇᓗᓇᐃᖅᑕᐅᓯᒪᔪᓂ. ᐅᓇ ᓇᓗᓇᐃᖅᑕᐅᑦᑎᐊᖏᑦᑐᖅ ᐃᓚᓗᒍ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐱᕕᒃᓴᓄᑦ.

    ᐊᐅᓚᑦᑎᓂᖅ: not measurable here

    ᐅᓇ ᐃᑭᐊᖅᑭᕖᒃᑯᑦ ᑐᑭᓯᒋᐊᕐᕕᒃ ᑎᑎᕋᖅᐸᒃᑐᖅ ᑭᖑᕙᕐᓂᐅᔪᒥᒃ ᐊᑯᓐᓂᐅᔪᒥᒃ ᐃᑲᕐᕋᓂ ᑕᒪᐃᓐᓂ ᓄᖅᑲᖓᕝᕕᒻᒥ. ᐊᓯᖏᓐᓂᒃ ᓈᓴᐅᑎᓂᒃ ᑎᑎᕋᖅᐸᙱᑦᑐᖅ. ᑕᐃᒪ ᓇᓗᓇᖅᑐᖅ ᖃᓄᖅ ᐊᔾᔨᒌᙱᓐᓂᖓ ᐃᖏᕐᕋᓂᖅ ᓈᒻᒪᒃᑐᖅ ᐃᖏᕐᕋᓂᕐᓗ ᐱᐅᙱᑦᑐᖅ. ᑖᓐᓇ ᐅᕙᒍᑦ ᖃᐅᔨᓴᕈᓯᑦᑎᓐᓂ ᑭᒡᓕᖃᖅᑐᖅ. ᑕᒪᓐᓇ ᓇᔪᒐᖅ ᐱᓪᓗᒍ ᑐᑭᓯᓂᐊᕐᓂᐅᙱᑦᑐᖅ.

    Measurements

    Calculated: · Method: settled-arrivals-oc-sto-conventional-v5

    Predictions consistently close to timetable · 05:00 to 22:00
    Worst hour on time 83.9%
    Median hour on time 97.2%
    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.

    ᑖᑦᓱᒪ ᒪᑉᐱᒐᐅᑉ ᓇᓗᓇᐃᖅᓯᒍᑎᖏᑦᐅᒃᑯᐃᓗᒍ ᑐᑭᖓ, ᖃᓄᖅ ᐱᓕᕆᓯᒪᓂᖅ, ᓇᑭᙶᕐᓂᖏᑦ, ᐅᓪᓗᖏᑦ, ᓇᒧᑦ ᐊᐅᓚᓂᖏᑦ, ᐊᒻᒪ ᑭᒡᓕᖏᑦ ᖃᐅᔨᒪᔭᐅᔪᑦ.

    ᓴᖅᑭᑎᑕᐅᔪᑦ

    ᐊᖁᑏᑦ ᓄᖑᕐᕕᐊᑕ ᑕᑯᒃᓴᐅᑎᖓ ᒫᓐᓇ. ᐱᕕᒃᓴᖏᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ ᐊᒻᒪ ᐊᐅᓚᑦᑎᔨᐅᑉ ᓇᓚᐅᑦᑖᕈᑎᖓ ᐃᖏᕐᕋᓂᕐᒧᑦ ᑕᒪᐃᓐᓄᑦ.

    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.

    ᓇᓗᓇᐃᖅᓯᒍᑏᑦ ᐅᓪᓗᖏᑦ

    ᓈᓴᐅᑎᓕᐅᖅᑕᐅᔪᖅ ᐅᕝᕙᓘᓐᓃᑦ ᑲᑐᔾᔨᖅᑕᐅᔪᖅ
    ᐆᒃᑐᕋᐅᑎ
    40 departures across 8 published platform records in the current four-hour board.
    ᐃᓚᐅᔪᑦ
    7 departures have a published live prediction; 33 are timetable-only.

    ᓇᑭᑦ ᑐᓴᒐᒃᓴᐃᑦ

    ᑭᒡᓕᖏᑦ ᐃᖅᑲᐅᒪᔭᐅᑎᐊᕆᐊᓖᑦ

    • OC Transpo ᓴᖅᑭᑦᑎᙱᓚᖅ O-Train ᒫᓐᓇ ᓇᐅᓐᓂᖓᓂᒃ ᐅᕝᕙᓘᓐᓃᑦ ᖃᖓ ᑎᑭᓐᓂᐊᕐᓂᖓᓂᒃ ᑐᓴᒐᒃᓴᓂ ᐅᕙᓂ ᐊᑐᖅᑕᐅᔪᓂ. ᑕᐃᒪ O-Train ᐱᕕᖏᑦ ᐸᕐᓇᐅᑎᒥᑦ ᑭᓯᐊᓂ.
    • 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.