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 198 trips cancelled now · 0 did not run in ਨਵੰਬਰCancellations →
Previous measure: 65% of arrivals were within five minutes of the timetable (6,081 arrivals over 18 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
198
ਰੂਟ 198: Limebank ⇄ Greenboro
ਵੱਲLimebank0 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)
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: 2 trips with qualifying later matching vehicle observations. Trips with any notice: 2.
Trips needing investigation
0
0 of 55 trips with a usable feed window (0%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
55 with position · 0 to investigate · 0 excluded · 55 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 4 ਨਵੰ 2026, 2:59 PM.
Coverage, exclusions and sources
0 of 6 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: 55 / 55 (100%). 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: 4 ਨਵੰ 2026, 1:19 PM
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
65%
of eligible provider predictions were within five minutes of the timetable.
Within five minutesOutside
Predictions in the source
6,081
Weekdays with evidence
18
Evidence window
6 ਅਕਤੂ 2026 – 3 ਨਵੰ 2026
The hours we have evidence for
05100% · 30 predictions · 10 days
0682% · 640 predictions · 10 days
0791% · 570 predictions · 10 days
0896% · 370 predictions · 10 days
1523% · 225 predictions · 10 days
1653% · 483 predictions · 10 days
1736% · 615 predictions · 10 days
1853% · 420 predictions · 9 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: 4 ਨਵੰ 2026
2 partial-capture days not counted.
What about time of day?
8 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, 7 ਅਕਤੂਬਰ 2026 to 3 ਨਵੰਬਰ 2026: 26 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.
ਬਾਅਦ ਦੁਪਹਿਰ ਦੀ ਭੀੜ (ਦੁਪਹਿਰ 3 ਤੋਂ ਸ਼ਾਮ 6 ਵਜੇ)3%
ਮੁੱਲ ਅਤੇ ਉਨ੍ਹਾਂ ਦਾ ਮਤਲਬ
3% of back-to-back buses on this route arrived bunched together: 17 of 513 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
0% of pairs (0) had a long gap: more than 1.75 times the planned wait between them.
Median provider predictions are 6 min later than the timetable in 4 hours of the day.
Predictions near the start are about 4.6 min later than the timetable, with a similar difference near the end. This does not establish the cause.
Wide prediction spread 18:00: the 95th percentile is 20.2 min later than the median.
15:00 has 23% of predictions within five minutes of the timetable, against 67% the rest of the day.
Matched public positions cover 100% of scheduled trips. This is a lower bound on operated service, not an audited delivery result.
Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.
Final provider predictions within five minutes of the timetable, by hour, last 14 days, 8 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: not enough data04
05:00: 100% of final predictions within five minutes of the timetable, 30 predictions, typically 1.1 min late05
06:00: 81.9% of final predictions within five minutes of the timetable, 640 predictions, typically 2.7 min late06
07:00: 90.7% of final predictions within five minutes of the timetable, 570 predictions, typically 1.6 min late07
08:00: 95.9% of final predictions within five minutes of the timetable, 370 predictions, typically 0.1 min early08
09:00: not enough data09
10:00: not enough data10
11:00: not enough data11
12:00: not enough data12
13:00: not enough data13
14:00: not enough data14
15:00: 23.1% of final predictions within five minutes of the timetable, 225 predictions, typically 11.2 min late15
16:00: 52.8% of final predictions within five minutes of the timetable, 483 predictions, typically 4.7 min late16
17:00: 36.3% of final predictions within five minutes of the timetable, 615 predictions, typically 7.3 min late17
18:00: 52.6% of final predictions within five minutes of the timetable, 420 predictions, typically 4.6 min late. Provider predictions have a wide spread.18
19:00: not enough data19
20:00: not enough data20
21:00: not enough data21
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
prediction spread of 20 min or more between the 95th percentile and median
Findings
What
ਕਦੋਂ
ਮਾਪਿਆ ਗਿਆ
Scenario or next investigation
Problem!Predictions later than timetable
15:00 to 19:00
6 min late
Recovery time at the terminal
Problem!Wide prediction spread
18:00
20.2 min swing
Operations, not the timetable
Problem!One hour has a lower prediction match
15:00
23%
Operations, not the timetable
Strength+Observed-position lower bound
All measured hours
100%
Keep what works
Measurements
Predictions later than timetable · 15:00 to 19:00
Measured arrivals 1,743
Hours affected 4
Spread 12.5 min
Median delay 6 min
Suggested running time change 6 min
Wide prediction spread · 18:00
Measured arrivals 420
Hours affected 1
Spread 20.2 min
Median delay 4.6 min
Suggested running time change 4.6 min
One hour has a lower prediction match · 15:00
ਘੰਟਾ 15:00
ਸਮੇਂ ਸਿਰ 23.1%
Measured arrivals 225
Shortfall 44.2 pts
Route median on time 67.4%
Observed-position lower bound · All measured hours
ਟੀਚਾ 99.5%
Trips with a matching position 100%
ਸੇਵਾ ਦੇ ਦਿਨ 5
Trips with a matching position 55
ਨਿਰਧਾਰਤ ਸਮੇਂ ਅਨੁਸਾਰ ਸਫ਼ਰ 55
15:00 32 → to 3816:00 33 → to 3916:00 32 → to 3817:00 32 → to 3817:00 32 → to 3818:00 32 → to 38
0 of 55 checked trips need a closer look0 of 55 trips with enough public-feed evidence had no matching position over 7 days. 0 of 55 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 3, 2026 · 11 trips in the retained timetable · retained notices; capture coverage unverified
In short: 11 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.
05:57– 06:20
Trip 12749030Vehicle position matchedFirst / last feed position: 5:43 a.m. EST / 6:46 a.m. EST; not actual start or end times.
06:44– 07:13
Trip 7831030Vehicle position matchedFirst / last feed position: 6:28 a.m. EST / 7:42 a.m. EST; not actual start or end times.
06:48– 07:13
Trip 12264030Vehicle position matchedFirst / last feed position: 6:47 a.m. EST / 7:21 a.m. EST; not actual start or end times.
07:43– 08:16
Trip 28012030Vehicle position matchedFirst / last feed position: 7:33 a.m. EST / 8:18 a.m. EST; not actual start or end times.
07:48– 08:20
Trip 15143030Vehicle position matchedFirst / last feed position: 7:43 a.m. EST / 8:20 a.m. EST; not actual start or end times.
15:37– 16:09
Trip 34447030Vehicle position matchedFirst / last feed position: 3:25 p.m. EST / 4:19 p.m. EST; not actual start or end times.
16:06– 16:38
Trip 11881030Vehicle position matchedFirst / last feed position: 3:44 p.m. EST / 4:37 p.m. EST; not actual start or end times.
16:44– 17:17
Trip 6054030Vehicle position matchedFirst / last feed position: 4:21 p.m. EST / 5:26 p.m. EST; not actual start or end times.
17:08– 17:40
Trip 36020030Vehicle position matchedFirst / last feed position: 4:48 p.m. EST / 5:51 p.m. EST; not actual start or end times.
17:45– 18:17
Trip 10364030Vehicle position matchedFirst / last feed position: 5:13 p.m. EST / 6:22 p.m. EST; not actual start or end times.
18:24– 18:56
Trip 35953030Vehicle position matchedFirst / last feed position: 6:23 p.m. EST / 7:06 p.m. EST; not actual start or end times.