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 NoofeembarCancellations →
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.
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: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 1.
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: 05-Nof-2026 ee 1:01 GH.
Coverage, exclusions and sources
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: 05-Nof-2026 ee 12:09 GH
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
06-Okt-2026 – 03-Nof-2026
The hours we have evidence for
05100% · 33 predictions · 11 days
0684% · 704 predictions · 11 days
0791% · 627 predictions · 11 days
0895% · 407 predictions · 11 days
1521% · 248 predictions · 11 days
1650% · 532 predictions · 11 days
1736% · 660 predictions · 11 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: 05-Nof-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.
4% of back-to-back buses on this route arrived bunched together: 17 of 482 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.
Shaqada waddooyinka iyo xidhitaannada waddooyinka ee dhacdooyinka oo Magaalada Ottawa daabacday, lagana qiyaasay inay u dhow yihiin jidka waddadan. U dhow ma aha caddeyn in baska jid kale loo weeciyay. Taas ka eeg digniinaha hawlwadaha laftiisa.
Liiska shaqooyinka waddooyinka ee Magaalada hadda lama akhrin karo.
A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.
Isha: Dhacdooyinka taraafikada ee Magaalada Ottawa (shaqada waddooyinka iyo xidhitaannada). Waxay ka kooban tahay macluumaad lagu shatiyeeyay Open Government Licence, City of Ottawa. Magaaladu waxay sheegtaa in liiskan yahay dadaal ugu fiican oo laga yaabo inuusan dhammaystirnayn. Khariidadda taraafikada Magaalada Ottawa ↗
1 scheduled trips with counted cancellation notices from Khms, Okt 8 to Arbc, Nof 4.
Not counted: 7 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Saacadaha ugu badan ee safarro la joojiyay: 3 GD (1)
Safarrada ugu dambeeyay ee la joojiyay
Arbc, Okt 21, scheduled 15:37
OC Transpo sabab uma bixiso safarrada gaarka ah, sidaas darteed midna lama muujin.
Ma iman (basku lama arkin, ogeysiis ma jirin), 7-dii maalmood ee la soo dhaafay: mid ka mid ah safarrada aan hubin karnay ma jiro.
Fur falanqaynta saadaalinta ee taariikhaysan
Go'aan
What this route needs
Median provider predictions are 6.2 min later than the timetable in 4 hours of the day.
Predictions near the start are about 4.9 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 21% of predictions within five minutes of the timetable, against 68% 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, 33 predictions, typically 1.3 min late05
06:00: 83.5% of final predictions within five minutes of the timetable, 704 predictions, typically 2.3 min late06
07:00: 91.1% of final predictions within five minutes of the timetable, 627 predictions, typically 1.7 min late07
08:00: 95.1% of final predictions within five minutes of the timetable, 407 predictions, typically 0.3 min late08
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: 21% of final predictions within five minutes of the timetable, 248 predictions, typically 11.3 min late15
16:00: 50.2% of final predictions within five minutes of the timetable, 532 predictions, typically 5 min late16
17:00: 35.5% of final predictions within five minutes of the timetable, 660 predictions, typically 7.5 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
Goorma
La cabbiray
Scenario or next investigation
Problem!Predictions later than timetable
15:00 to 19:00
6.2 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
21%
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,860
Hours affected 4
Spread 13.1 min
Median delay 6.2 min
Suggested running time change 6.2 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
Saacad 15:00
Waqtigii 21%
Measured arrivals 248
Shortfall 47.1 pts
Route median on time 68.1%
Observed-position lower bound · All measured hours
Yool 99.5%
Trips with a matching position 100%
Maalmaha adeegga 5
Trips with a matching position 55
Safarrada jadwalka ku qoran 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
64 in 100 eligible predictions differed from the timetable by more than 5 minutes (117 predictions over 20 days).
Fur joogsigan
Kuwani waa saadaalyo khad gaar ah oo bixiyaha laga helay, la barbar dhigay jadwalka. Waxay muujiyaan farqi saadaal oo soo noqnoqda goob iyo waqti gaar ah. Ma aha imaatin la cabbiray, mana muujiyaan sababta.
Hubi safar kasta iyo taariikh kasta
Fur muddo waqti ah si aad u aragto maalin kasta oo adeeg, safar kasta oo jadwalka ku qoran, daldaloolka xogta, aqoonsiga gaariga dadweynaha ee la arkay, iyo tirooyinka saxda ah ee ka dambeeya soo koobiddan.
Suurtagal in aan la iman marka la hubiyo daldaloolada xogta?
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.
Sidee bay u kala duwanaayeen saadaalinta bixiyaha iyo jadwalka?
Weli natiijo heer waddo ah ma gaarin xadka caddaymaha. Tani micnaheedu maaha in kala go'yaal adeeg aysan dhicin.
Hubinta isbeddelka jadwalka
Jadwalka la daabacay: ka hor iyo ka dib
Tani waxay isbarbar dhigaysaa jadwalka rasmiga ah ee hadda la haysto iyo nuqulkii hore ee la haystay. Isbeddellada jadwalka waa xaqiiqooyin ku saabsan wixii la qorsheeyay. Ma caddaynayaan in safar la socday.
Current published schedule began Oktoobar 30, 2026
Maalinta adeegga la doortay ee jadwal kasta oo la daabacay
Waxaan eegnaa Isniintii ugu horreysay ee ka dambaysay bilowga jadwalka cusub iyo Isniintii toddobaad ka horreysay. Tiro kasta waxay ka timaadaa noocyada rasmiga ah ee GTFS ee la hayo, ee hoos lagu magacaabay.
Ugu yaraan hal taariikh oo la doortay waxay isticmaalaysaa adeeg taariikh gaar ah oo la daray ama la saaray. U fiirso tan inay tahay xaalad fasax ama adeeg gaar ah, ma aha kordhin caadi ah oo maalmaha shaqada ah.
Waxaan isbarbar dhigi doonaa imaatinnada la xaqiijiyay ee 14-ka maalmood ee ka horreeya iyo ka dambeeya isbeddelka. Isbarbardhigga waxaan daabacaynaa kaliya marka labada dhinac mid walba leeyahay ugu yaraan 7 maalmood oo adeeg ah iyo 200 imaatin.
Still collecting: before has 3,284 arrivals over 10 days; after has 1,331 arrivals over 4 days. No improvement or decline is claimed yet.
Lambarrada hubinta waxay u saamaxaan qof kasta inuu hubiyo jadwalka la xajiyay ee soo saaray tirada. Tiro isbeddelay ma muujinayso sabab, joojin, go'aanka hawlgalaha, ama saameyn ku yimid rakaabka.
Waxaan isbarbardhignaa saadaashii ugu dambaysay ee bixiyaha ee u qalma imaatin kasta oo jadwalka ku jirta iyo jadwalka rasmiga ah. Kuwani ma aha imaatinno si madaxbannaan loo cabbiray. Natiijadu waxay u baahan tahay ugu yaraan 200 saadaal oo u qalma. Gudaha 5 daqiiqo waa bartilmaameedka rakaabku arki karaan ee halkan loo isticmaalay.
Waxa xogtani caddayn karin
Xogta tooska ah ee dadweynaha ma bixiso tirada rakaabka ee la isku halayn karo, ama dhacdooyinka rakaab laga dhaafay. Booska oo ka maqan keligiis ma caddeeyo joojin, safar aan la imaan, safar la gaabiyay, ama sabab.
Isha rasmiga ah ee hadda: joojinta si cad loo sheegay, boosas la boodey iyo ogeysiisyo shaqeynaya.
Indha-indheyn is waafaqday: meelaha gawaarida iyo saadaalin la xaqiijiyay oo ku xiran jadwalka rasmiga ah.
Jadwalka rasmiga ah: waxa la qorsheeyay, oo ka gaar ah waxa la arkay.
Warbixinnada rakaabka iyo shirkadda: tilmaamo ku saabsan wadooyin, wakhtiyo iyo meelo la baaro, maaha caddayn tiro ah keligood.
Natiijooyin ku meel gaar ah, caddayn la daabacay
Sidee bay saadaalintu ula barbar dhigmeen jadwalka?
Saacad kasta waxay is barbar dhigtaa saadaashii ugu dambaysay ee la aqbali karay ee bixiyaha ee imaatin jadwal ku xusan iyo jadwalka. “Gudaha 5 daqiiqo” waxay qeexaysaa farqiga saadaashaas. Ma aha imaatin la cabbiray ama caddayn ah in bas ordey.
Muddada caddaynta: Oktoobar 6, 2026 to Noofeembar 3, 2026
4 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
Bas jadwal leh, laakiin aan waqtiga dhabta ah lagu arkin
55 / 55 scheduled trips published at least one position across 5 service days (100.0%).
05:000 / 5 trips without a position100.0%
06:000 / 10 trips without a position100.0%
07:000 / 10 trips without a position100.0%
15:000 / 5 trips without a position100.0%
16:000 / 10 trips without a position100.0%
17:000 / 10 trips without a position100.0%
Tani ma aha ka-maqnaansho la xaqiijiyay. Goob maqan waxay la macno noqon kartaa bas la joojiyay ama la seegay, laakiin waxay kaloo la macno noqon kartaa aqoonsi safar aan loo qoondeynin ama farqi ku jira xogta shirkadda. Otranspo waxay daabacaysaa farqigan sababtoo ah wuxuu muhiim u yahay rakaabka, iyadoo gabagabada ka dhigaysa mid daacad ah.
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. Ilaha iyo xadadka.
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 · 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 12749040Vehicle position matchedFirst / last feed position: 5:27 a.m. EST / 6:48 a.m. EST; not actual start or end times.
06:44– 07:13
Trip 7831040Vehicle position matchedFirst / last feed position: 6:30 a.m. EST / 7:42 a.m. EST; not actual start or end times.
06:48– 07:13
Trip 12264040Vehicle position matchedFirst / last feed position: 6:49 a.m. EST / 7:29 a.m. EST; not actual start or end times.
07:43– 08:16
Trip 28012040Vehicle position matchedFirst / last feed position: 7:34 a.m. EST / 8:25 a.m. EST; not actual start or end times.
07:48– 08:20
Trip 15143040Vehicle 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 34447040Vehicle position matchedFirst / last feed position: 3:25 p.m. EST / 4:24 p.m. EST; not actual start or end times.
16:06– 16:38
Trip 11881040Vehicle position matchedFirst / last feed position: 3:43 p.m. EST / 4:41 p.m. EST; not actual start or end times.
16:44– 17:17
Trip 6054040Vehicle position matchedFirst / last feed position: 4:19 p.m. EST / 5:28 p.m. EST; not actual start or end times.
17:08– 17:40
Trip 36020040Vehicle position matchedFirst / last feed position: 4:48 p.m. EST / 5:40 p.m. EST; not actual start or end times.
17:45– 18:17
Trip 10364040Vehicle position matchedFirst / last feed position: 5:18 p.m. EST / 6:18 p.m. EST; not actual start or end times.
18:24– 18:56
Trip 35953040Vehicle position matchedFirst / last feed position: 6:19 p.m. EST / 6:52 p.m. EST; not actual start or end times.