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 73 trips cancelled now · 0 did not run in NovemberCancellations →
Previous measure: 75.8% of arrivals were within five minutes of the timetable (39,126 arrivals over 18 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: 7 trips with qualifying later matching vehicle observations. Trips with any notice: 9.
Trips needing investigation
1
1 of 335 trips with a usable feed window (0.3%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
334 with position · 1 to investigate · 0 excluded · 335 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 10:29 a.m..
Coverage, exclusions and sources
0 of 12 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: 334 / 335 (99.7%). 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: Nov 4, 2026, 8:49 a.m.
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
75.8%
of eligible provider predictions were within five minutes of the timetable.
Within five minutesOutside
Predictions in the source
39,126
Weekdays with evidence
18
Evidence window
Oct 6, 2026 – Nov 3, 2026
The hours we have evidence for
0591% · 628 predictions · 10 days
0682% · 1,414 predictions · 10 days
0783% · 1,460 predictions · 10 days
0884% · 1,608 predictions · 10 days
0981% · 1,446 predictions · 10 days
1089% · 1,221 predictions · 10 days
1179% · 1,093 predictions · 10 days
1269% · 1,090 predictions · 10 days
1372% · 1,052 predictions · 10 days
1487% · 1,025 predictions · 10 days
1582% · 1,376 predictions · 10 days
1673% · 1,545 predictions · 10 days
1753% · 1,563 predictions · 10 days
1847% · 1,614 predictions · 10 days
1980% · 1,377 predictions · 10 days
2095% · 1,090 predictions · 10 days
2184% · 1,080 predictions · 10 days
2291% · 342 predictions · 10 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: Nov 4, 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, October 7, 2026 to November 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: October 8, 2026, October 15, 2026.
Morning rush (6 to 9 a.m.)0%
Midday (9 a.m. to 3 p.m.)0%
Afternoon rush (3 to 6 p.m.)0%
Evening (6 to 10 p.m.)0%
Night (10 p.m. to 4 a.m.)0%
Values and interpretation
0% of back-to-back buses on this route arrived bunched together: 65 of 27,072 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
0% of pairs (36) had a long gap: more than 1.75 times the planned wait between them.
Based on 39,126 eligible provider predictions over 18 measured days, from Oct 6, 2026 to Nov 3, 2026.
Updated Nov 4, 2026, 9:32 a.m.
Where and when did predictions differ repeatedly?
These are repeated prediction-to-timetable differences, not independently measured service failures. They use the same eligible predictions as the result above, but group by stop rather than hour, so the lists need not match line for line.
18–19: 53 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,614 predictions over 10 days).
17–18: 47 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,563 predictions over 10 days).
12–13: 31 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,090 predictions over 10 days).
2 current notices affect this route
• Limebank Station: Passenger pick-up and drop-off area relocation
• Detour: Routes entering and exiting Limebank Station
58 in 100 eligible predictions differed from the timetable by more than 5 minutes (183 predictions over 21 days).
Open this stop
These are route-specific provider predictions compared with the timetable. They identify repeated prediction differences at a place and time, not measured arrivals or their cause.
0 of 12Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?
1 of 335 checked trips need a closer look1 of 335 trips with enough public-feed evidence had no matching position over 7 days. 0 of 335 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Nawaj na gii-mino-izhiwebad gaa-ishkwaa-aanjichigaadeg?
We will compare settled arrivals for the 14 days before and after the change. We publish the comparison only after both sides have at least 7 service days and 200 arrivals.
Still collecting: before has 21,846 arrivals over 10 days; after has 6,640 arrivals over 3 days. No improvement or decline is claimed yet.
Checksums let anyone verify which retained timetable produced the counts. A changed count does not identify a cause, cancellation, operator decision, or passenger impact.
How this route is judged: Regular all-stop route
We compare the last eligible provider prediction for each scheduled arrival with the official schedule. These are not independently measured arrivals. A result needs at least 200 eligible predictions. Within 5 minutes is the rider-facing target used here.
What this data cannot prove
The public feed does not provide dependable passenger counts or passed-up-rider events. A missing position does not by itself prove a cancellation, no-show, short turn or cause.
Official current feed: explicit cancellations, skipped stops and active notices.
Matched observations: vehicle positions and settled predictions tied to the official schedule.
Official timetable: what was planned, kept separate from what was observed.
Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.
Provisional results, published evidence
How did predictions compare with the timetable?
Each hour compares the last eligible provider prediction for a scheduled arrival with the timetable. “Within 5 minutes” describes that prediction difference, not a measured arrival or proof that a bus ran.
Evidence window: October 6, 2026 to November 3, 2026
3 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
Bus scheduled, gaawiin dash gii-waabandanziimin realtime
334 / 335 scheduled trips published at least one position across 5 service days (99.7%).
06:001 / 20 trips without a position95.0%
05:000 / 15 trips without a position100.0%
07:000 / 20 trips without a position100.0%
08:000 / 20 trips without a position100.0%
09:000 / 15 trips without a position100.0%
10:000 / 20 trips without a position100.0%
This is not a confirmed no-show. A missing position can mean a cancelled or missed bus, but it can also mean an unassigned trip ID or an operator-feed gap. Otranspo publishes the gap because it matters to riders while keeping the conclusion honest.
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. Sources and limitations.
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 · 67 trips in the retained timetable · retained notices; capture coverage unverified
In short: 66 with a matched position · 1 with no matching position (to investigate) · 0 with an unknown outcome.
05:15– 05:38
Trip 9736030Vehicle position matchedFirst / last feed position: 4:55 a.m. EST / 5:36 a.m. EST; not actual start or end times.
05:20– 05:46
Trip 35665030Vehicle position matchedFirst / last feed position: 5:02 a.m. EST / 6:09 a.m. EST; not actual start or end times.
05:35– 06:42
Trip 34733030Vehicle position matchedFirst / last feed position: 4:52 a.m. EST / 7:09 a.m. EST; not actual start or end times.
06:05– 07:10
Trip 26724030Vehicle position matchedFirst / last feed position: 5:35 a.m. EST / 7:09 a.m. EST; not actual start or end times.
06:15– 06:44
Trip 22750030Vehicle position matchedFirst / last feed position: 6:10 a.m. EST / 6:44 a.m. EST; not actual start or end times.
06:34– 07:44
Trip 21577030Vehicle position matchedFirst / last feed position: 6:36 a.m. EST / 7:50 a.m. EST; not actual start or end times.
06:46– 07:15
Trip 26081030Explicit notice: CANCELEDNo matching position; investigate, not a confirmed cancellation
07:05– 08:11
Trip 12951030Vehicle position matchedFirst / last feed position: 7:04 a.m. EST / 8:09 a.m. EST; not actual start or end times.
07:15– 07:45
Trip 33387030Vehicle position matchedFirst / last feed position: 7:10 a.m. EST / 7:50 a.m. EST; not actual start or end times.
07:35– 08:41
Trip 19933030Vehicle position matchedFirst / last feed position: 7:00 a.m. EST / 8:47 a.m. EST; not actual start or end times.
07:48– 08:19
Trip 27368030Vehicle position matchedFirst / last feed position: 7:51 a.m. EST / 8:33 a.m. EST; not actual start or end times.
08:05– 09:11
Trip 5495030Vehicle position matchedFirst / last feed position: 8:07 a.m. EST / 9:14 a.m. EST; not actual start or end times.