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 299 trips cancelled now · 0 did not run in NobyembreCancellations →
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: 3.
Trips needing investigation
1
1 of 50 trips with a usable feed window (2%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
49 with position · 1 to investigate · 0 excluded · 50 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nob 3, 2026, 10:45 PM.
Coverage, exclusions and sources
0 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 49 / 50 (98%). 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 3, 2026, 9:18 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
No comparable percentage published
This service purpose needs a different method. A general percentage could give a misleading picture.
Predictions in the source
3,636
Weekdays with evidence
18
Evidence window
Okt 5, 2026 – Nob 2, 2026
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
Calculated: Nob 4, 2026
2 partial-capture days not counted.
What about time of day?
The general hourly comparison is not suitable for this service purpose. Source records remain available.
Improvement or decline requires comparable periods. This single result cannot establish a trend.
Last 28 days, Oktubre 6, 2026 to Nobyembre 2, 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: Oktubre 8, 2026, Oktubre 15, 2026.
Rush hour sa umaga (6 hanggang 9 a.m.)8%
Mga halaga at paliwanag
8% of back-to-back buses on this route arrived bunched together: 34 of 401 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
42% of pairs (169) 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.
Gawaing kalsada
MANOTICK MAIN between ISLAND VIEW and CURRIER
Ago 31, 2026, 12:00 AM to Nob 16, 2026, 5:00 PM
MANOTICK MAIN off-peak lane reductions in both directions between ISLAND VIEW and CURRIER due to construction, until November 16th. Flagpersons present.
Minarkahan ito ng Lungsod na nakakaapekto sa transit.
about 0 m from the route
City record updated Set 17, 2026, 1:00 PM.
Gawaing kalsada
Ralph Hennessy between Markdale and Earl Armstrong
Okt 6, 2026, 12:00 AM to Nob 6, 2026, 5:00 PM
Ralph Hennessy off-peak lane reductions between Markdale and Earl Armstrong due to construction, from October 6th to November 6th.
Minarkahan ito ng Lungsod na nakakaapekto sa transit.
about 0 m from the route
City record updated Okt 9, 2026, 10:24 AM.
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 ↗
2 scheduled trips with counted cancellation notices from Mar, Okt 6 to Lun, Nob 2.
Not counted: 3 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Mga oras na may pinakamaraming kanseladong biyahe: 7 AM (1), 5 PM (1)
Mga pinakabagong kinanselang biyahe
Miy, Okt 28, scheduled 17:13
Lun, Okt 26, scheduled 07:30
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
Median provider predictions are 4 to 6.1 min later than the timetable in 3 hours of the day.
Predictions near the start are about 2.4 min later than the timetable, with a similar difference near the end. This does not establish the cause.
14:00 has 36% of predictions within five minutes of the timetable, against 65% the rest of the day.
Only 98% of scheduled trips were seen; the rest are not counted as missed.
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, 5 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: not enough data05
06:00: 90% of final predictions within five minutes of the timetable, 360 predictions, typically 0 min late06
07:00: 77.3% of final predictions within five minutes of the timetable, 656 predictions, typically 0.6 min late07
08:00: not enough data08
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: 35.8% of final predictions within five minutes of the timetable, 288 predictions, typically 6.1 min late14
15:00: not enough data15
16:00: not enough data16
17:00: 65.1% of final predictions within five minutes of the timetable, 424 predictions, typically 3.3 min late17
18:00: 54.5% of final predictions within five minutes of the timetable, 290 predictions, typically 4.8 min late18
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
Findings
What
Kailan
Nasukat
Scenario or next investigation
Problem!Predictions later than timetable
14:00 · 17:00 to 19:00
6.1 min late · 4 min late
Recovery time at the terminal
Problem!One hour has a lower prediction match
14:00
36%
Operations, not the timetable
Caveat?Coverage gap
All measured hours
98%
More observation, not a service change
Measurements
Predictions later than timetable · 17:00 to 19:00
Measured arrivals 714
Hours affected 2
Spread 13.1 min
Median delay 4 min
Suggested running time change 4 min
Predictions later than timetable · 14:00
Measured arrivals 288
Hours affected 1
Spread 4.6 min
Median delay 6.1 min
Suggested running time change 6.1 min
One hour has a lower prediction match · 14:00
Oras 14:00
Nasa oras 35.8%
Measured arrivals 288
Shortfall 29.3 pts
Route median on time 65.1%
Coverage gap · All measured hours
Target 99.5%
Trips with a matching position 98%
Mga araw ng serbisyo 5
Trips with a matching position 49
Mga biyaheng nakatakda sa iskedyul 50
14:00 6 → to 1217:00 26 → to 30
Buksan ang kasaysayan, fiabilidad at pagsusuri ng ruta
Pagsusuri ng ruta
How route 299 has been running
Maikling buod ng alam namin. Sinasabi namin kapag hindi namin masagot ang isang tanong.
Pangunahing punto
Kailangan naming malaman kung saan sumasakay ang mga pasahero sa express na rutang ito bago namin ito mabigyan ng rating.
Laki ng sample ng prediksyon: Mas malaking sample
Based on 3,636 eligible provider predictions over 18 measured days, from Okt 5, 2026 to Nob 2, 2026.
Updated Nob 3, 2026, 9:32 PM
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.
Hindi nire-rank ang mga oras na may problema dahil kailangan ng serbisyong ito ng pagsubok na akma sa layunin nito.
2 current notices affect this route
• Limebank Station: Passenger pick-up and drop-off area relocation
• Detour: Routes entering and exiting Limebank Station
Pagkakaiba ng hula ayon sa hintuan
Wala pa kaming sapat na kasaysayan ng ruta bawat hintuan para pangalanan ang paulit-ulit na problemang hintuan. Ginagamit lang na pahiwatig ang mga ulat ng mga sakay, hindi patunay.
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?
Walang live na sagot sa kanselasyonOC Transpo’s live trip-update feed did not answer this check. That is a feed gap. It does not mean zero cancellations, and it is not proof of a cancellation. Open the evidence to see the schedule, retained explicit cancellation notices, and every labelled data gap.
Posibleng hindi sumipot matapos suriin ang mga puwang sa feed?
1 of 50 checked trips need a closer look1 of 50 trips with enough public-feed evidence had no matching position over 7 days. 0 of 50 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.
Hindi po angkop sa layunin ng serbisyo ng rutang ito ang karaniwang pagmamarka ng pagiging on time. Makikita pa rin po ang bilang ng mga takbo ayon sa iskedyul. Hihintayin po muna ang resulta hanggang sa makuha ang mga datos na tugma sa layunin, na inilalarawan sa ibaba.
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: Express / commuter na ruta
Dapat suriin ang pagganap ng papasok na biyahe sa mga lugar ng sakayan. Ang maagang takbo palabas matapos ang mga sakay ay hindi itinuturing na maagang serbisyo gaya ng sa karaniwang ruta.
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
Datos sa likod ng resultang ito
Hindi angkop ang karaniwang marka ng pagiging on time para sa serbisyong ito kung hindi muna susuriin ang layunin nito. Ipinapaliwanag sa pagsusuri ng ruta sa itaas ang kailangang ebidensya tungkol sa pickup, serbisyong pangkomunidad, o event. Maaari pa rin po ninyong tingnan sa ibaba ang mga naitalang biyahe at ang mga kulang na datos.
Saklaw ng ebidensya: Oktubre 5, 2026 to Nobyembre 2, 2026
Nakaiskedyul na bus, ngunit hindi naobserbahan sa real-time
49 / 50 scheduled trips published at least one position across 5 service days (98.0%).
17:001 / 10 trips without a position90.0%
06:000 / 5 trips without a position100.0%
07:000 / 20 trips without a position100.0%
14:000 / 15 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 2, 2026 · 10 trips in the retained timetable · retained notices; capture coverage unverified
In short: 10 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.
06:19– 06:42
Trip 18194020Vehicle position matchedFirst / last feed position: 5:49 a.m. EST / 6:37 a.m. EST; not actual start or end times.
07:12– 07:39
Trip 774020Vehicle position matchedFirst / last feed position: 6:38 a.m. EST / 7:36 a.m. EST; not actual start or end times.
07:26– 07:35
Trip 36751020Vehicle position matchedFirst / last feed position: 7:06 a.m. EST / 7:40 a.m. EST; not actual start or end times.
07:28– 07:37
Trip 18891020Vehicle position matchedFirst / last feed position: 7:08 a.m. EST / 7:39 a.m. EST; not actual start or end times.
07:30– 07:39
Trip 33168020Vehicle position matchedFirst / last feed position: 7:22 a.m. EST / 7:51 a.m. EST; not actual start or end times.
14:17– 14:23
Trip 20991020Vehicle position matchedFirst / last feed position: 1:46 p.m. EST / 2:33 p.m. EST; not actual start or end times.
14:17– 14:23
Trip 28636020Vehicle position matchedFirst / last feed position: 1:59 p.m. EST / 2:32 p.m. EST; not actual start or end times.
14:17– 14:23
Trip 31437020Vehicle position matchedFirst / last feed position: 1:46 p.m. EST / 2:30 p.m. EST; not actual start or end times.
17:13– 17:40
Trip 29353020Explicit notice: CANCELEDVehicle position matchedFirst / last feed position: 4:47 p.m. EST / 6:38 p.m. EST; not actual start or end times.
17:55– 18:19
Trip 15452020Vehicle position matchedFirst / last feed position: 5:55 p.m. EST / 6:27 p.m. EST; not actual start or end times.