Skip to main content

Next bus

FR

Report a problem

What happened
Full report No account needed

Buses now:on timelateyou

1O-Train Line 1 · station 3022

Lees

Trains · timetableon timelateno reading
Every 6 min · sched. then 11:10
1
1Tunney's Pasture · platform 1
Not measured yet
11:05
sched. then 11:10
Every 6 min · sched. then 11:13
1
1Blair · platform 2
Not measured yet
11:07
sched. then 11:13
Buses at Lees · liveupdated 30 s ago
Every 30 min · then 37 · 67 sched.
10
10Hurdman · platform B · every 30 to 30 min
Not measured yet
7minlive
then 37 · 67 sched.
Every 15 to 16 min · then 24 · 40 sched.
85
85Bayshore · platform A · every 15 to 16 min
Not measured yet
9minlive
then 24 · 40 sched.
Every 30 min · then 39 · 69 sched.
10
10Main · platform A · every 30 to 30 min
Not measured yet
9minlive
then 39 · 69 sched.
Every 15 to 17 min · then 30 · 38 sched.
85
85Lees · platform B · every 15 to 17 min
Not measured yet
12minlive
then 30 · 38 sched.
Entrances and elevators

We cannot confirm elevator status right now.

79.9% predicted within five minutes of schedule. 1,919 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 here11 places within 5 min · nearest: Racks for 8 bikes, 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 LEES

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

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

Prediction agreement
79.9% predicted within five minutes of schedule. 1,919 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.

79.9% of final provider predictions within 5 minutes of the timetable, from 1,919 predictions over 6 weekdays. The lowest sampled hour is 15:00 at 62%.

Median predicted difference from the timetable: 42 s late. At the 95th percentile: 11 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: 71.8% of final predictions within five minutes of the timetable, 39 predictions, typically 3.7 min late
  3. 02:00: 68.3% of final predictions within five minutes of the timetable, 41 predictions, typically 2.6 min late
  4. 03:00: 80% of final predictions within five minutes of the timetable, 45 predictions, typically 1.6 min late
  5. 04:00: 83.8% of final predictions within five minutes of the timetable, 68 predictions, typically 1.6 min late
  6. 05:00: 84.1% of final predictions within five minutes of the timetable, 44 predictions, typically 1.1 min late
  7. 06:00: 85.6% of final predictions within five minutes of the timetable, 104 predictions, typically 0.1 min early
  8. 07:00: 87.9% of final predictions within five minutes of the timetable, 107 predictions, typically 0.3 min late
  9. 08:00: 72.7% of final predictions within five minutes of the timetable, 128 predictions, typically 0.9 min late
  10. 09:00: 83.1% of final predictions within five minutes of the timetable, 124 predictions, typically 0 min early
  11. 10:00: 86.6% of final predictions within five minutes of the timetable, 112 predictions, typically 0 min early
  12. 11:00: 86.4% of final predictions within five minutes of the timetable, 81 predictions, typically 0.2 min early
  13. 12:00: 76.7% of final predictions within five minutes of the timetable, 86 predictions, typically 0 min late
  14. 13:00: 88.5% of final predictions within five minutes of the timetable, 87 predictions, typically 0.9 min late
  15. 14:00: 75% of final predictions within five minutes of the timetable, 116 predictions, typically 1.7 min late
  16. 15:00: 61.9% of final predictions within five minutes of the timetable, 97 predictions, typically 2.9 min late
  17. 16:00: 69.9% of final predictions within five minutes of the timetable, 113 predictions, typically 1.7 min late
  18. 17:00: 76.7% of final predictions within five minutes of the timetable, 103 predictions, typically 1.4 min late
  19. 18:00: 81.4% of final predictions within five minutes of the timetable, 113 predictions, typically 0.4 min late
  20. 19:00: 82% of final predictions within five minutes of the timetable, 61 predictions, typically 0.1 min early
  21. 20:00: 80.4% of final predictions within five minutes of the timetable, 56 predictions, typically 0.1 min late
  22. 21:00: 86% of final predictions within five minutes of the timetable, 57 predictions, typically 0.1 min early
  23. 22:00: 87.3% of final predictions within five minutes of the timetable, 55 predictions, typically 0.7 min early
  24. 23:00: 83% of final predictions within five minutes of the timetable, 53 predictions, typically 0.4 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
WhatWhenMeasuredScenario or next investigation
ProblemPredictions later than timetable01:003.7 min lateRunning time on the routes here
ProblemOne hour has a lower prediction match15:0062%Operations in that hour

How LEES 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 23 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

95.7%

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

1of 23

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 23

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

3.7min

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 later than timetable · 01:00
Median delay 3.7 min
Measured arrivals 39
On time 71.8%
One hour has a lower prediction match · 15:00
On time 61.9%
Other hours on time 82.5%
Measured arrivals 97

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