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 99 trips cancelled now · 0 did not run in NobyembreCancellations →
Previous measure: 83.5% of arrivals were within five minutes of the timetable (41,425 arrivals over 27 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
99
Ruta 99: Barrhaven Centre ⇄ Limebank
Bawat 29 hanggang 32 min
Papuntang Barrhaven Centre1 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: 1 trips with qualifying later matching vehicle observations. Trips with any notice: 2.
Trips needing investigation
0
0 of 501 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.
501 with position · 0 to investigate · 0 excluded · 501 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nob 5, 2026, 7:22 AM.
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: 501 / 501 (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: Nob 5, 2026, 6:10 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
83.5%
of eligible provider predictions were within five minutes of the timetable.
Within five minutesOutside
Predictions in the source
41,425
Weekdays with evidence
19
Evidence window
Okt 6, 2026 – Nob 3, 2026
The hours we have evidence for
0093% · 504 predictions · 12 days
0582% · 539 predictions · 11 days
0688% · 1,148 predictions · 15 days
0788% · 1,288 predictions · 15 days
0886% · 1,219 predictions · 15 days
0987% · 1,267 predictions · 15 days
1087% · 1,328 predictions · 15 days
1187% · 1,347 predictions · 15 days
1290% · 1,341 predictions · 15 days
1390% · 1,305 predictions · 15 days
1478% · 1,500 predictions · 15 days
1577% · 1,278 predictions · 15 days
1678% · 1,246 predictions · 15 days
1785% · 1,291 predictions · 15 days
1887% · 1,314 predictions · 15 days
1988% · 1,301 predictions · 15 days
2078% · 1,237 predictions · 15 days
2179% · 1,246 predictions · 15 days
2277% · 898 predictions · 15 days
2367% · 477 predictions · 14 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: Nob 5, 2026
2 partial-capture days not counted.
What about time of day?
20 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, Oktubre 8, 2026 to Nobyembre 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: Oktubre 8, 2026, Oktubre 15, 2026.
Madaling-araw (4 hanggang 6 a.m.)0%
Rush hour sa umaga (6 hanggang 9 a.m.)1%
Tanghali (9 a.m. hanggang 3 p.m.)0%
Rush hour sa hapon (3 hanggang 6 p.m.)0%
Gabi (6 hanggang 10 p.m.)0%
Gabi (10 p.m. hanggang 4 a.m.)0%
Mga halaga at paliwanag
0% of back-to-back buses on this route arrived bunched together: 31 of 26,361 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
0% of pairs (27) had a long gap: more than 1.75 times the planned wait between them.
Mga gawaing kalsada at pagsasara ng kalsada para sa event na inilathala ng City of Ottawa, na sinukat bilang malapit sa daanan ng rutang ito. Ang malapit ay hindi patunay na iniiba ang daan ng bus. Tingnan po ang sariling abiso ng tagapagpatakbo para doon.
Hindi po mabasa ngayon ang listahan ng lungsod ng mga gawaing pangkalsada.
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.
Pinagmulan: mga traffic event ng City of Ottawa (road work at mga pagsasara ng daan). May impormasyong lisensyado sa ilalim ng Open Government Licence, City of Ottawa. Ayon sa Lungsod, pinagsikapan lamang ang listahang ito at maaaring hindi kumpleto. Mapa ng trapiko ng Lungsod ng Ottawa ↗
8 scheduled trips with counted cancellation notices from Huw, Okt 8 to Miy, Nob 4.
Not counted: 12 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Mga oras na may pinakamaraming kanseladong biyahe: 4 PM (2), 7 PM (2), 8 AM (1)
Mga pinakabagong kinanselang biyahe
Miy, Nob 4, scheduled 19:26
Miy, Okt 28, scheduled 19:56
Huw, Okt 22, scheduled 16:36
Huw, Okt 22, scheduled 15:54
Mar, Okt 20, scheduled 16:06
Hindi nagbibigay ang OC Transpo ng dahilan para sa isang biyahe, kaya walang ipinapakita.
Hindi dumating (walang nakitang bus, walang abiso), huling 7 araw: wala sa mga biyaheng nasuri namin.
Buksan ang may petsang pagsusuri ng hula
Hatol
What this route needs
Matched public positions cover 100% of scheduled trips. This is a lower bound on operated service, not an audited delivery result.
Final provider predictions within five minutes of the timetable, by hour, last 14 days, 20 hours with samples
00:00: 92.5% of final predictions within five minutes of the timetable, 504 predictions, typically 0.9 min late00
01:00: not enough data01
02:00: not enough data02
03:00: not enough data03
04:00: not enough data04
05:00: 82.4% of final predictions within five minutes of the timetable, 539 predictions, typically 0.8 min early05
06:00: 88.2% of final predictions within five minutes of the timetable, 1,148 predictions, typically 2.1 min late06
07:00: 87.8% of final predictions within five minutes of the timetable, 1,288 predictions, typically 1.8 min late07
08:00: 86.2% of final predictions within five minutes of the timetable, 1,219 predictions, typically 1.3 min late08
09:00: 87.3% of final predictions within five minutes of the timetable, 1,267 predictions, typically 1.5 min late09
10:00: 86.7% of final predictions within five minutes of the timetable, 1,328 predictions, typically 1.9 min late10
11:00: 87.2% of final predictions within five minutes of the timetable, 1,347 predictions, typically 2.2 min late11
12:00: 90.2% of final predictions within five minutes of the timetable, 1,341 predictions, typically 0.6 min late12
13:00: 90.3% of final predictions within five minutes of the timetable, 1,305 predictions, typically 2.1 min late13
14:00: 78% of final predictions within five minutes of the timetable, 1,500 predictions, typically 2.2 min late14
15:00: 76.9% of final predictions within five minutes of the timetable, 1,278 predictions, typically 2.4 min late15
16:00: 78.3% of final predictions within five minutes of the timetable, 1,246 predictions, typically 2 min late16
17:00: 85.1% of final predictions within five minutes of the timetable, 1,291 predictions, typically 2 min late17
18:00: 87% of final predictions within five minutes of the timetable, 1,314 predictions, typically 2.4 min late18
19:00: 88.3% of final predictions within five minutes of the timetable, 1,301 predictions, typically 1.7 min late19
20:00: 77.8% of final predictions within five minutes of the timetable, 1,237 predictions, typically 1.4 min late20
21:00: 78.7% of final predictions within five minutes of the timetable, 1,246 predictions, typically 2 min late21
22:00: 77.3% of final predictions within five minutes of the timetable, 898 predictions, typically 2.2 min late22
23:00: 67.1% of final predictions within five minutes of the timetable, 477 predictions, typically 2.9 min late23
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
Kailan
Nasukat
Scenario or next investigation
Strength+Observed-position lower bound
All measured hours
100%
Keep what works
Measurements
Observed-position lower bound · All measured hours
Target 99.5%
Trips with a matching position 100%
Mga araw ng serbisyo 6
Trips with a matching position 501
Mga biyaheng nakatakda sa iskedyul 501
Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta
Pagsusuri ng ruta
How route 99 has been running
Maikling buod ng alam namin. Sinasabi namin kapag hindi namin masagot ang isang tanong.
Pangunahing punto
Resultang may petsa, hindi live na serbisyo
This prediction-to-timetable result describes the dated period, not service right now. It was last calculated 5 hours ago. Current vehicle positions and official notices are checked separately.
Based on 41,425 eligible provider predictions over 27 measured days, from Okt 6, 2026 to Nob 3, 2026.
Updated Nob 5, 2026, 2:32 AM
Saan at kailan paulit-ulit na nagkaiba ang mga hula?
Ito ay mga paulit-ulit na pagkakaiba ng hula at ng iskedyul, hindi mga pagkabigo sa serbisyo na sinukat nang hiwalay. Ginagamit nito ang parehong karapat-dapat na mga hula gaya ng resulta sa itaas, pero pinagsasama-sama ayon sa hintuan, hindi ayon sa oras. Kaya maaaring hindi magkapareho ang mga listahan sa bawat linya.
23–00: 33 in 100 eligible predictions differed from the timetable by more than 5 minutes (477 predictions over 14 days).
2 current notices affect this route
• Limebank Station: Passenger pick-up and drop-off area relocation
• Detour: Routes entering and exiting Limebank Station
30 in 100 eligible predictions differed from the timetable by more than 5 minutes (986 predictions over 29 days).
Buksan ang hintuang ito
Ito ay mga hula ng provider para sa partikular na ruta, na inihambing sa iskedyul. Ipinapakita nito ang paulit-ulit na pagkakaiba ng hula sa isang lugar at oras. Hindi ito nasukat na pagdating at hindi nito sinasabi ang dahilan.
Suriin ang bawat biyahe at petsa
Magbukas ng yugto ng panahon para makita ang bawat araw ng serbisyo, nakatakdang biyahe, puwang sa feed, naobserbahang pampublikong ID ng sasakyan, at ang eksaktong bilang sa likod ng buod na ito.
Ang gustong malaman ng mga pasahero
May kanseladong biyahe ba ngayon?
0 of 12Sinusuri ang mga biyaheng magsisimula sa dulo ng ruta sa susunod na 4 na oras. Hindi ito makasaysayang bilang ng pagkansela.
Posibleng hindi sumipot matapos suriin ang mga puwang sa feed?
0 of 501 checked trips need a closer look0 of 501 trips with enough public-feed evidence had no matching position over 7 days. 0 of 501 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
Paano naiba ang mga hula ng tagapagbigay ng serbisyo sa iskedyul?
Gaano katagal na paghihintay ang ipinahiwatig ng mga tinatayang oras ng operator?
Wala pang resulta sa antas ng ruta na umaabot sa pamantayan ng evidence. Hindi po ibig sabihin nito na walang nangyaring puwang sa serbisyo.
Pagsusuri ng pagbabago sa iskedyul
Nailathalang iskedyul: bago at pagkatapos
Ikinukumpara po nito ang kasalukuyang opisyal na iskedyul na iniingatan sa naunang bersyon na iniingatan. Ang mga pagbabago sa iskedyul ay mga katotohanan tungkol sa kung ano ang binalak. Hindi po nito pinatutunayan na naganap ang isang biyahe.
Current published schedule began Oktubre 30, 2026
Piniling araw ng serbisyo mula sa bawat inilathalang iskedyul
Sinusuri po namin ang unang Lunes pagkatapos magsimula ang bagong iskedyul at ang Lunes isang linggo bago nito. Ang bawat bilang ay galing sa mga opisyal na bersyon ng GTFS na itinabi at nakasaad sa ibaba.
Hindi bababa sa isa sa mga napiling petsa ang may idinagdag o inalis na serbisyo sa petsa ng kalendaryo. Ituring po ito bilang konteksto ng holiday o espesyal na serbisyo, hindi karaniwang paglago tuwing karaniwang araw.
Fingerprint ng feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
Gumanda po ba ang serbisyo pagkatapos ng pagbabago?
Ihahambing po namin ang mga natapos na dating ng sasakyan sa loob ng 14 na araw bago at pagkatapos ng pagbabago. Ilalathala lamang po namin ang paghahambing kapag may hindi bababa sa 7 araw ng serbisyo at 200 dating ang magkabilang panig.
Still collecting: before has 21,431 arrivals over 14 days; after has 9,396 arrivals over 6 days. No improvement or decline is claimed yet.
Sa checksum, maaaring tiyakin ng sinuman kung aling iskedyul na itinabi ang pinagmulan ng mga bilang. Ang pagbabago sa bilang ay hindi nagpapakita ng dahilan, pagkansela, desisyon ng operator, o epekto sa mga pasahero.
Paano hinuhusgahan ang rutang ito: Regular na ruta na humihinto sa lahat ng hintuan
Inihahambing namin ang huling karapat-dapat na hula ng provider para sa bawat nakaiskedyul na pagdating sa opisyal na iskedyul. Hindi ito mga pagdating na sinukat nang hiwalay. Kailangan ng hindi bababa sa 200 karapat-dapat na hula para magkaroon ng resulta. Ang loob ng 5 minuto ang target para sa mga sakay na ginagamit dito.
Ang hindi mapatutunayan ng datos na ito
Ang public feed po ay hindi nagbibigay ng maaasahang bilang ng pasahero o ng mga pagkakataong nilampasan ang mga naghihintay na pasahero. Ang kawalan ng posisyon ay hindi nangangahulugang patunay ng pagkansela, hindi pagdating, maikling biyahe o sanhi nito.
Tingnan ang mga kahulugan, hangganan at pagkakasunod-sunod ng ebidensya
Opisyal na kasalukuyang feed: mga tahasang pagkansela, mga nilaktawang hintuan, at mga aktibong abiso.
Mga tugmang obserbasyon: mga posisyon ng sasakyan at mga pinal na prediksyon na iniugnay sa opisyal na iskedyul.
Opisyal na iskedyul: ang plano, hiwalay sa naobserbahan.
Mga ulat ng pasahero at operator: mga lead tungkol sa ruta, oras, at lugar na dapat imbestigahan. Hindi ito sapat na patunay na numerikal sa sarili nito.
Pansamantalang resulta, inilathalang ebidensya
Paano ikinumpara ang mga hula sa iskedyul?
Sa bawat oras, inihahambing ang huling karapat-dapat na predicted na dating mula sa provider para sa isang scheduled na pagdating sa timetable. Ang "Within 5 minutes" ay naglalarawan ng pagkakaiba ng prediksyon, hindi ng nasukat na pagdating o patunay na bumiyahe ang bus.
Saklaw ng ebidensya: Oktubre 6, 2026 to Nobyembre 3, 2026
1 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
Nakaiskedyul na bus, ngunit hindi naobserbahan sa real-time
501 / 501 scheduled trips published at least one position across 6 service days (100.0%).
00:000 / 12 trips without a position100.0%
05:000 / 15 trips without a position100.0%
06:000 / 24 trips without a position100.0%
07:000 / 29 trips without a position100.0%
08:000 / 26 trips without a position100.0%
09:000 / 28 trips without a position100.0%
Hindi ito kumpirmadong hindi pagsipot. Ang nawawalang posisyon ay maaaring mangahulugang kinansela o nalagpasang bus, pero maaari rin itong mangahulugang walang nakatalagang ID ng biyahe o may puwang sa feed ng operator. Inilalathala ng Otranspo ang puwang dahil mahalaga ito sa mga sakay, habang nananatiling tapat ang konklusyon.
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. Mga pinagmulan at limitasyon.
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 · 76 trips in the retained timetable · retained notices; capture coverage unverified
In short: 76 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.
05:26– 05:55
Trip 16646040Vehicle position matchedFirst / last feed position: 4:57 a.m. EST / 5:58 a.m. EST; not actual start or end times.
05:31– 05:51
Trip 26587040Vehicle position matchedFirst / last feed position: 5:26 a.m. EST / 5:49 a.m. EST; not actual start or end times.
05:51– 06:20
Trip 4618040Vehicle position matchedFirst / last feed position: 5:11 a.m. EST / 6:29 a.m. EST; not actual start or end times.
06:01– 06:24
Trip 23693040Vehicle position matchedFirst / last feed position: 5:16 a.m. EST / 6:29 a.m. EST; not actual start or end times.
06:26– 06:57
Trip 36624040Vehicle position matchedFirst / last feed position: 6:30 a.m. EST / 6:55 a.m. EST; not actual start or end times.
06:35– 06:58
Trip 19717040Vehicle position matchedFirst / last feed position: 6:30 a.m. EST / 7:02 a.m. EST; not actual start or end times.
06:56– 07:27
Trip 13447040Vehicle position matchedFirst / last feed position: 6:41 a.m. EST / 7:27 a.m. EST; not actual start or end times.
07:01– 07:26
Trip 24298040Vehicle position matchedFirst / last feed position: 6:56 a.m. EST / 7:27 a.m. EST; not actual start or end times.
07:28– 08:03
Trip 27483040Vehicle position matchedFirst / last feed position: 7:28 a.m. EST / 8:01 a.m. EST; not actual start or end times.
07:29– 07:40
Trip 19877040Vehicle position matchedFirst / last feed position: 7:10 a.m. EST / 7:39 a.m. EST; not actual start or end times.
07:33– 08:00
Trip 31624040Vehicle position matchedFirst / last feed position: 6:48 a.m. EST / 8:05 a.m. EST; not actual start or end times.
07:56– 08:31
Trip 13418040Vehicle position matchedFirst / last feed position: 7:40 a.m. EST / 8:29 a.m. EST; not actual start or end times.