Limebank Station: Passenger pick-up and drop-off area relocation: December 12 2025 -
At 10:00 am on Thursday, December 18, Town Square Road and the connector road at Limebank Station will re-open to general traffic. As a result, the temporarily-relocated passenger pick-up and drop-off zone will be moved back to its original location, on the north side of Limebank Station.
Customers are reminded to use the designated pedestrian crossing zones when travelling between the O-Train station and the passenger pick-up and drop-off area.
Routes 70, 73, 74, 99, 110, 198, 283, 299 will continue to follow a detour by entering and exiting Limebank Station via Limebank Road.
Detour routing
99 Limebank: From Limebank, right onto Limebank Station Bus Only Roadway, Loop around bus loop, right onto Connector Roadway, continue regular route (and regular service stops within Limebank Station).
99 Barrhaven Centre: From Limebank Station, loop around bus loop, right onto Connector Roadway, left onto Limebank, continue regular route.
110 Limebank: From Earl Armstrong, right onto Limebank, right onto Limebank Station Bus Only Roadway, Loop around bus loop, right onto Connector Roadway, continue regular route (and regular service stops within Limebank Station).
110 Innovation: No detour required.
70, 73, 74, 198, 283, 299 Limebank: From Earl Armstrong, right onto Limebank, right onto Limebank Station Bus Only Roadway, Loop around bus loop, right onto Connector Roadway, continue regular route (and regular service stops within Limebank Station).
70, 73, 74, 198, 283, 299 Outbound trips: From Limebank Station, loop around bus loop, right onto Connector Roadway, left onto Limebank, left onto Earl Armstrong, continue regular route.
Maps (effective December 18)+1 more notice
No 110 trips cancelled now · 5 did not run in ਨਵੰਬਰCancellations →
Previous measure: 71.6% of arrivals were within five minutes of the timetable (1,13,377 arrivals over 27 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
Trips in the published timetable marked cancelled without qualifying later matching vehicle observations in our archive. This does not prove the trip did not operate. Not counted: 5 trips with qualifying later matching vehicle observations. Trips with any notice: 6.
Trips needing investigation
6
6 of 346 trips with a usable feed window (1.7%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
340 with position · 6 to investigate · 0 excluded · 346 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 5 ਨਵੰ 2026, 12:46 AM.
Coverage, exclusions and sources
0 of 2 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
0 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 340 / 346 (98.3%). This is not a delivered-service rate. 7 service days in this source.
Timetables retained before the service day: 7 / 7 requested days · 0 missing days.
Historical calculation: 5 ਨਵੰ 2026, 12:09 AM
Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.
What does the evidence show?
Predictions against the timetable
71.6%
of eligible provider predictions were within five minutes of the timetable.
Within five minutesOutside
Predictions in the source
1,13,377
Weekdays with evidence
19
Evidence window
6 ਅਕਤੂ 2026 – 3 ਨਵੰ 2026
The hours we have evidence for
0478% · 493 predictions · 15 days
0575% · 3,556 predictions · 15 days
0687% · 4,223 predictions · 15 days
0781% · 4,894 predictions · 15 days
0868% · 4,055 predictions · 15 days
0972% · 4,431 predictions · 11 days
1078% · 4,298 predictions · 11 days
1172% · 3,979 predictions · 11 days
1273% · 4,103 predictions · 11 days
1374% · 4,193 predictions · 11 days
1475% · 3,747 predictions · 11 days
1558% · 3,267 predictions · 11 days
1656% · 3,782 predictions · 14 days
1757% · 4,736 predictions · 15 days
1863% · 5,005 predictions · 15 days
1981% · 4,705 predictions · 15 days
2076% · 3,816 predictions · 11 days
2174% · 970 predictions · 11 days
Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
Calculated: 5 ਨਵੰ 2026
2 partial-capture days not counted.
What about time of day?
18 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.
Improvement or decline requires comparable periods. This single result cannot establish a trend.
Last 28 days, 8 ਅਕਤੂਬਰ 2026 to 4 ਨਵੰਬਰ 2026: 25 days counted.
2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: 8 ਅਕਤੂਬਰ 2026, 15 ਅਕਤੂਬਰ 2026.
ਸਵੇਰ ਦਾ ਤੜਕਾ (ਸਵੇਰੇ 4 ਤੋਂ 6 ਵਜੇ)0%
ਸਵੇਰ ਦੀ ਭੀੜ (ਸਵੇਰੇ 6 ਤੋਂ 9 ਵਜੇ)0%
ਦੁਪਹਿਰ (ਸਵੇਰੇ 9 ਵਜੇ ਤੋਂ ਦੁਪਹਿਰ 3 ਵਜੇ ਤੱਕ)1%
ਬਾਅਦ ਦੁਪਹਿਰ ਦੀ ਭੀੜ (ਦੁਪਹਿਰ 3 ਤੋਂ ਸ਼ਾਮ 6 ਵਜੇ)1%
ਸ਼ਾਮ (ਸ਼ਾਮ 6 ਤੋਂ ਰਾਤ 10 ਵਜੇ ਤੱਕ)0%
ਮੁੱਲ ਅਤੇ ਉਨ੍ਹਾਂ ਦਾ ਮਤਲਬ
0% of back-to-back buses on this route arrived bunched together: 324 of 70,760 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
1% of pairs (413) had a long gap: more than 1.75 times the planned wait between them.
Bank lane reductions in both directions between Riverside westbound and Collins due to construction. Cyclists and pedestrians not affected. From March 25 to December 2026.
Did not come (no bus seen, no notice), last 7 days: 5 of 346 trips we could check.
ਤਰੀਕਾਂ ਵਾਲਾ ਅਨੁਮਾਨ ਵਿਸ਼ਲੇਸ਼ਣ ਖੋਲ੍ਹੋ
ਫ਼ੈਸਲਾ
What this route needs
Median provider predictions are 3.9 min later than the timetable in 3 hours of the day.
The prediction difference from the timetable grows by about 4.9 min along the route.
Provider predictions are about 1.5 min earlier than the timetable, 21:00.
Only 99% of scheduled trips were seen; the rest are not counted as missed.
Scenario: 4 min more running time on 136 trips. The schedule-block model adds no buses; fleet and workforce feasibility are unverified.
Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.
Final provider predictions within five minutes of the timetable, by hour, last 14 days, 18 hours with samples
00:00: not enough data00
01:00: not enough data01
02:00: not enough data02
03:00: not enough data03
04:00: 78.3% of final predictions within five minutes of the timetable, 493 predictions, typically 2.8 min late04
05:00: 74.6% of final predictions within five minutes of the timetable, 3,556 predictions, typically 1.6 min late05
06:00: 87.2% of final predictions within five minutes of the timetable, 4,223 predictions, typically 0.6 min late06
07:00: 81.3% of final predictions within five minutes of the timetable, 4,894 predictions, typically 1.1 min late07
08:00: 68.4% of final predictions within five minutes of the timetable, 4,055 predictions, typically 1.8 min late08
09:00: 72.4% of final predictions within five minutes of the timetable, 4,431 predictions, typically 1.6 min late09
10:00: 77.8% of final predictions within five minutes of the timetable, 4,298 predictions, typically 0.8 min late10
11:00: 72.4% of final predictions within five minutes of the timetable, 3,979 predictions, typically 1.4 min late11
12:00: 72.6% of final predictions within five minutes of the timetable, 4,103 predictions, typically 1.6 min late12
13:00: 73.8% of final predictions within five minutes of the timetable, 4,193 predictions, typically 2.4 min late13
14:00: 74.9% of final predictions within five minutes of the timetable, 3,747 predictions, typically 0.9 min late14
15:00: 58% of final predictions within five minutes of the timetable, 3,267 predictions, typically 3.9 min late15
16:00: 56.3% of final predictions within five minutes of the timetable, 3,782 predictions, typically 4 min late16
17:00: 57.2% of final predictions within five minutes of the timetable, 4,736 predictions, typically 3.1 min late17
18:00: 63.4% of final predictions within five minutes of the timetable, 5,005 predictions, typically 2.5 min late18
19:00: 81.3% of final predictions within five minutes of the timetable, 4,705 predictions, typically 1.3 min late19
20:00: 75.9% of final predictions within five minutes of the timetable, 3,816 predictions, typically 1.6 min late20
21:00: 73.6% of final predictions within five minutes of the timetable, 970 predictions, typically 1.5 min early21
22:00: not enough data22
23:00: not enough data23
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
Problem!Predictions later than timetable
15:00 to 18:00
3.9 min late
More running time
Problem!Predictions earlier than timetable
21:00
1.5 min early
Less running time, or holding points
Caveat?Coverage gap
All measured hours
99%
More observation, not a service change
Measurements
Predictions later than timetable · 15:00 to 18:00
Measured arrivals 11,785
Hours affected 3
Spread 14.5 min
Median delay 3.9 min
Suggested running time change 3.9 min
Predictions earlier than timetable · 21:00
Measured arrivals 970
Hours affected 1
Spread 9.7 min
Median delay -1.5 min
Suggested running time change -1.5 min
Coverage gap · All measured hours
ਟੀਚਾ 99.5%
Trips with a matching position 98.6%
ਸੇਵਾ ਦੇ ਦਿਨ 7
Trips with a matching position 341
ਨਿਰਧਾਰਤ ਸਮੇਂ ਅਨੁਸਾਰ ਸਫ਼ਰ 346
15:00 104 → to 10815:00 103 → to 10716:00 104 → to 10816:00 102 → to 10617:00 97 → to 10117:00 100 → to 104
6 of 346 checked trips need a closer look6 of 346 trips with enough public-feed evidence had no matching position over 7 days. 0 of 346 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position check: the timetable kept before each service day, matched to recorded positions. Exact IDs are preferred; an OC timetable suffix is matched only to one trip on the same route and date with an overlapping time window. Missing timetables, ambiguous matches and feed gaps stay labelled; they are not confirmed no-shows. ਸਰੋਤ ਅਤੇ ਸੀਮਾਵਾਂ.
Dated service
Trips scheduled that day
The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.
November 4, 2026 · 64 trips in the retained timetable · retained notices; capture coverage unverified
In short: 63 with a matched position · 1 with no matching position (to investigate) · 0 with an unknown outcome.
04:45– 05:48
Trip 13596040Vehicle position matchedFirst / last feed position: 4:43 a.m. EST / 6:17 a.m. EST; not actual start or end times.
04:45– 05:37
Trip 4563040Vehicle position matchedFirst / last feed position: 4:20 a.m. EST / 5:48 a.m. EST; not actual start or end times.
05:15– 06:21
Trip 1773040Vehicle position matchedFirst / last feed position: 5:06 a.m. EST / 6:32 a.m. EST; not actual start or end times.
05:15– 06:07
Trip 26285040Vehicle position matchedFirst / last feed position: 4:49 a.m. EST / 6:20 a.m. EST; not actual start or end times.
05:17– 06:32
Trip 16317040Vehicle position matchedFirst / last feed position: 5:00 a.m. EST / 6:43 a.m. EST; not actual start or end times.
05:42– 07:14
Trip 15396040Vehicle position matchedFirst / last feed position: 5:19 a.m. EST / 7:10 a.m. EST; not actual start or end times.
05:51– 07:25
Trip 27204040Vehicle position matchedFirst / last feed position: 5:31 a.m. EST / 7:29 a.m. EST; not actual start or end times.
06:12– 07:44
Trip 32185040Vehicle position matchedFirst / last feed position: 5:49 a.m. EST / 7:55 a.m. EST; not actual start or end times.
06:12– 07:51
Trip 37126040Vehicle position matchedFirst / last feed position: 5:54 a.m. EST / 8:10 a.m. EST; not actual start or end times.
06:42– 08:25
Trip 1181040Vehicle position matchedFirst / last feed position: 6:23 a.m. EST / 8:39 a.m. EST; not actual start or end times.
06:42– 08:14
Trip 18297040Vehicle position matchedFirst / last feed position: 6:34 a.m. EST / 8:18 a.m. EST; not actual start or end times.
07:12– 08:44
Trip 24484040Vehicle position matchedFirst / last feed position: 6:41 a.m. EST / 8:54 a.m. EST; not actual start or end times.