Skip to main content

Next bus

FR

Report a problem

What happened
Full report No account needed

Buses now:on timelateyou

2O-Train Line 2 · station 3068

Limebank

Trains · timetableon timelateno reading
Every 12 min · sched. then 4:41
2
2Limebank · platform LIMEBANK O-TRAIN
Not measured yet
4:29
sched. then 4:41
Every 12 min · sched. then 4:46
2
2Bayview · platform LIMEBANK O-TRAIN NORTH / NORD
Not measured yet
4:34
sched. then 4:46
Buses at Limebank · liveupdated 30 s ago
Every 14 to 16 min · sched. then 4:43
70
70Limebank · platform C · every 14 to 16 min
Not measured yet
4:29
sched. then 4:43
Every 31 min · sched. then 5:00
99
99Limebank · platform C · every 31 to 31 min
Not measured yet
4:29
sched. then 5:00
Every 31 min · then 35 sched.
99
99Barrhaven Centre · platform F · every 31 to 31 min
Not measured yet
4minlive
then 35 sched.
Every 12 to 16 min · sched. then 4:48
74
74Limebank · platform C · every 12 to 16 min
Not measured yet
4:36
sched. then 4:48
Every 15 min · then 24 · 38 sched.
70
70Fallowfield · platform I · every 15 to 15 min
Not measured yet
9minlive
then 24 · 38 sched.
Every 15 min · then 24 · 39 sched.
74
74Tunney's Pasture · platform H · every 15 to 15 min
Not measured yet
9minlive
then 24 · 39 sched.
Every 28 min · then 39 sched.
110
110Innovation · platform F · every 28 to 28 min
Not measured yet
11minlive
then 39 sched.
Every 30 min · sched. then 5:12
73
73Limebank · platform C · every 30 to 30 min
Not measured yet
4:42
sched. then 5:12
Every 30 min · then 48 sched.
73
73Tunney's Pasture · platform G · every 30 to 30 min
Not measured yet
18minlive
then 48 sched.
110
110Limebank
platform A
Not measured yet
4:51
from the timetable
283
283Munster Hamlet
platform A
Not measured yet
25minlive
198
198Greenboro
platform A
Not measured yet
5:05
from the timetable
299
299Manotick
platform A
Not measured yet
5:10
from the timetable
198
198Limebank
platform C
Not measured yet
5:14
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

94% predicted within five minutes of schedule. 1,406 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 walkBike 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
Without JavaScriptBoards and departures still show without JavaScript

Station details

Step-free route

Current notice coverage cannot be confirmed. Retained notices below may have unconfirmed timing or source evidence. Check the operator before you travel.

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 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 4, 2026, 4:29 p.m.; open Departures for a refreshed board. This is not a cancellation count.

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

Verdict

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% of final provider predictions within 5 minutes of the timetable, from 1,406 predictions over 6 weekdays, with no sampled hour far below the rest.

Median predicted difference from the timetable: 3 s late. 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. 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: 85.7% of final predictions within five minutes of the timetable, 56 predictions, typically 0 min late
  7. 06:00: 97.1% of final predictions within five minutes of the timetable, 104 predictions, typically 0 min late
  8. 07:00: 99% of final predictions within five minutes of the timetable, 96 predictions, typically 0 min late
  9. 08:00: 97.6% of final predictions within five minutes of the timetable, 85 predictions, typically 0 min late
  10. 09:00: 91% of final predictions within five minutes of the timetable, 78 predictions, typically 0.3 min late
  11. 10:00: 100% of final predictions within five minutes of the timetable, 86 predictions, typically 0 min late
  12. 11:00: 97.6% of final predictions within five minutes of the timetable, 85 predictions, typically 0 min late
  13. 12:00: 95.3% of final predictions within five minutes of the timetable, 85 predictions, typically 0.3 min late
  14. 13:00: 100% of final predictions within five minutes of the timetable, 80 predictions, typically 0.6 min late
  15. 14:00: 95.2% of final predictions within five minutes of the timetable, 83 predictions, typically 0.3 min late
  16. 15:00: 85.1% of final predictions within five minutes of the timetable, 94 predictions, typically 0.5 min late
  17. 16:00: 83.9% of final predictions within five minutes of the timetable, 93 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
WhatWhenMeasuredScenario 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 variation in the operator’s arrival predictions. They suggest questions for planners and operations staff; they do not establish the cause or 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
Cost unavailable until fleet, labour, recovery and transfer effects are tested.

Predictions close to the timetable

100%

Route-hours where the median eligible arrival prediction is less than one minute early and less than three 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 establish that buses departed early.

Typical predicted delay

Not enough evidence this month to publish this indicator.

The typical median predicted delay in flagged route-hours; 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, and no percentile, so the gap between a normal trip and a bad one cannot be worked out. That is a limit of our own measurement, 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 83.9%
Median hour on time 95.3%
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
Sample
40 departures across 8 published platform records in the current four-hour board.
Coverage
11 departures have a published live prediction; 29 are timetable-only.

Sources

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.