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 NovemberCancellations →

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.

Oháha 99: Barrhaven Centre ⇄ Limebank

Every 29 to 32 min

Toward Barrhaven Centre1 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 29, 2026 – Nov 4, 2026

Scheduled trips with cancellation notices

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 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: Nov 5, 2026, 5:41 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: 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: Nov 5, 2026, 4:38 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

83.5%

of eligible provider predictions were within five minutes of the timetable.

Predictions in the source: 41,425
Weekdays with evidence: 19
Evidence window: Oct 6, 2026 – Nov 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: Nov 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.

Explore the dated evidence Source of this result

Buses arriving bunched

Last 28 days, October 8, 2026 to November 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: October 8, 2026, October 15, 2026.

Values and interpretation

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.

Buses arriving bunched
Tó: nikahwistá:ke	Pairs checked	Bunched	Long gap
Early morning (4 to 6 a.m.)	96	0% (0)	0% (0)
Morning rush (6 to 9 a.m.)	2,632	1% (18)	0% (13)
Midday (9 a.m. to 3 p.m.)	11,884	0% (4)	0% (0)
Afternoon rush (3 to 6 p.m.)	3,659	0% (0)	0% (11)
Evening (6 to 10 p.m.)	7,073	0% (9)	0% (3)
Night (10 p.m. to 4 a.m.)	1,017	0% (0)	0% (0)

Tsi ní:ioht →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: BARRHAVEN CENTRE B to NEPEAN WOODS A, 21.4 km/h actual against 17.4 km/h planned.

Where this route is slowest
Tsi nón:we	Tsi nón:we	Tsi niió:re (distance)	Planned speed	Actual speed	Trips measured	Slow trips
BARRHAVEN CENTRE B	NEPEAN WOODS A	2.7 km	17.4 km/h	21.4 km/h	837	2%
SPRATT / CANYON WALK	NEPEAN WOODS B	4.7 km	24.3 km/h	22.2 km/h	828	2%
NEPEAN WOODS A	BORBRIDGE / STARGAZER	2.2 km	19.7 km/h	23.1 km/h	844	2%
LIMEBANK F	SPRATT / CANYON WALK	2.6 km	33.4 km/h	24 km/h	825	32%
BORBRIDGE / STARGAZER	SPRATT / CANYON WALK	3.1 km	27.2 km/h	25.9 km/h	845	3%

A slow trip took at least 1.5 times the planned time.

Tsi ní:ioht →

City road work, kí:ken route

Road work tánon event road closures, City of Ottawa published. Measured near ne route. Near iah proof tsi bus detoured. Check ne operator alerts.

Oháha: kaio'tén:sera
SPRATT between CANYON WALK / GOLDENEYE and HOLLOW TRAIL
Oct 6, 2026, 12:00 a.m. to Nov 6, 2026, 5:00 p.m.
SPRATT off-peak lane reductions between CANYON WALK / GOLDENEYE and HOLLOW TRAIL due to construction, from October 6th to November 6th.
The City marks this as affecting transit.
about 0 m from the route
City record updated Oct 9, 2026, 10:16 a.m..

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.

Source: City of Ottawa traffic events (road work and closures). Contains information licensed under the Open Government Licence, City of Ottawa. The City says this list is best effort and may be incomplete. City of Ottawa traffic map ↗

Cancellations on this route

What these words mean →

2 partial-capture days not counted.

7 scheduled trips with counted cancellation notices from Thu, Oct 8 to Wed, Nov 4.

Not counted: 12 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.

Hours with the most cancellations: 4 p.m. (2), 8 a.m. (1), 9 a.m. (1)

Latest cancelled trips

Wed, Oct 28, scheduled 19:56
Thu, Oct 22, scheduled 16:36
Thu, Oct 22, scheduled 15:54
Tue, Oct 20, scheduled 16:06
Mon, Oct 19, scheduled 09:35

OC Transpo gives no reason for single trips, so none is shown.

Did not come (no bus seen, no notice), last 7 days: none of the trips we could check.

Open the dated prediction analysis

Ka' nikarihò:ten

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 late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 82.4% of final predictions within five minutes of the timetable, 539 predictions, typically 0.8 min early
06:00: 88.2% of final predictions within five minutes of the timetable, 1,148 predictions, typically 2.1 min late
07:00: 87.8% of final predictions within five minutes of the timetable, 1,288 predictions, typically 1.8 min late
08:00: 86.2% of final predictions within five minutes of the timetable, 1,219 predictions, typically 1.3 min late
09:00: 87.3% of final predictions within five minutes of the timetable, 1,267 predictions, typically 1.5 min late
10:00: 86.7% of final predictions within five minutes of the timetable, 1,328 predictions, typically 1.9 min late
11:00: 87.2% of final predictions within five minutes of the timetable, 1,347 predictions, typically 2.2 min late
12:00: 90.2% of final predictions within five minutes of the timetable, 1,341 predictions, typically 0.6 min late
13:00: 90.3% of final predictions within five minutes of the timetable, 1,305 predictions, typically 2.1 min late
14:00: 78% of final predictions within five minutes of the timetable, 1,500 predictions, typically 2.2 min late
15:00: 76.9% of final predictions within five minutes of the timetable, 1,278 predictions, typically 2.4 min late
16:00: 78.3% of final predictions within five minutes of the timetable, 1,246 predictions, typically 2 min late
17:00: 85.1% of final predictions within five minutes of the timetable, 1,291 predictions, typically 2 min late
18:00: 87% of final predictions within five minutes of the timetable, 1,314 predictions, typically 2.4 min late
19:00: 88.3% of final predictions within five minutes of the timetable, 1,301 predictions, typically 1.7 min late
20:00: 77.8% of final predictions within five minutes of the timetable, 1,237 predictions, typically 1.4 min late
21:00: 78.7% of final predictions within five minutes of the timetable, 1,246 predictions, typically 2 min late
22:00: 77.3% of final predictions within five minutes of the timetable, 898 predictions, typically 2.2 min late
23:00: 67.1% of final predictions within five minutes of the timetable, 477 predictions, typically 2.9 min late

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	Ó:nen	Tewaterièn:tare	Scenario or next investigation
StrengthObserved-position lower bound	All measured hours	100%	Keep what works

Measurements

Observed-position lower bound · All measured hours: Tsi niió:re 99.5%; Trips with a matching position 100%; Wenhniserá:tens tsi ioió'te 6; Trips with a matching position 501; Schedule trips 501

Open history, reliability and route analysis

Route check

How route 99 has been running

A short summary of what we know. We say so when we cannot answer a question.

Bottom line

Dated result, not live service

This prediction-to-timetable result describes the dated period, not service right now. It was last calculated 3 hours ago. Current vehicle positions and official notices are checked separately.

84 in 100 eligible predictions were within 5 minutes of the timetable · 41,425 predictions checked

Prediction sample size: Larger sample

Based on 41,425 eligible provider predictions over 27 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 5, 2026, 2: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.

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

Prediction differences by stop

BEATRICE B
33 in 100 eligible predictions differed from the timetable by more than 5 minutes (960 predictions over 29 days).
Open this stop
MARKETPLACE / RIOCAN
33 in 100 eligible predictions differed from the timetable by more than 5 minutes (986 predictions over 29 days).
Open this stop
NEPEAN WOODS B
31 in 100 eligible predictions differed from the timetable by more than 5 minutes (960 predictions over 29 days).
Open this stop
MARKETPLACE / LONGFIELDS
30 in 100 eligible predictions differed from the timetable by more than 5 minutes (986 predictions over 29 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.

Check every trip and date

Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.

What riders want to know

Is any trip cancelled right now?: 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?: 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.
How did provider predictions differ from the timetable?: At the 95th percentile, the predicted difference was 8.3 min (positive means later; negative means earlier)84 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.

Schedule change check

Published schedule: before and after

This compares the current retained official schedule with the prior retained version. Schedule changes are facts about what was planned. They do not prove that a trip ran.

Current published schedule began October 30, 2026

Selected service day from each published schedule

We check ne first Monday after ne á:se schedule began, tánon ne Monday one week earlier. Akwé:kon figures, official GTFS versions named below.

At least one selected date uses added or removed calendar-date service. Treat this as holiday or special-service context, not ordinary weekday growth.

Ohén:ton

Wenhniserá:te wahatkáhtho: October 26, 2026

Schedule trips: 76
Distinct scheduled stops: 54
Distinct published paths: 4
Kahiatónhsera: tsi niió:re ne kà:sere: 05:26–00:52 next day

Operator calendar-date records: 0 added · 2 removed

Kahiatónhsera: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

New schedule

Wenhniserá:te wahatkáhtho: November 2, 2026

Schedule trips: 76
Distinct scheduled stops: 54
Distinct published paths: 4
Kahiatónhsera: tsi niió:re ne kà:sere: 05:26–00:52 next day

Operator calendar-date records: 0 added · 2 removed

Kahiatónhsera: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

Did service improve after the change?

Enkwatkáhtho' ne arrivals 14 wenhniserá:tens tsi niió:re aorí:wa ne change tánon' ohnà:ken. Ne tsi enkwatkáhtho' entewahró:ri' tsi nikarì:wes ne 7 wenhniserá:tens tánon' 200 arrivals iá:ken'.

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.

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.

See the definitions, thresholds and evidence order

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

Within 5 minutes of schedule: 83.5%
Eligible predictions checked: 41,425
Weekdays with data: 19
95th-percentile predicted delay: 8.3 min late

Patterns by hour (20)

Patterns by hour (20)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
00:00	92.5%	0.9 min late	2.9 min late	504 · 12 days
05:00	82.4%	0.8 min early	7.4 min late	539 · 11 days
06:00	88.2%	2.1 min late	6.3 min late	1,148 · 15 days
07:00	87.8%	1.8 min late	6.7 min late	1,288 · 15 days
08:00	86.2%	1.3 min late	9.6 min late	1,219 · 15 days
09:00	87.3%	1.5 min late	6.4 min late	1,267 · 15 days
10:00	86.7%	1.9 min late	6.2 min late	1,328 · 15 days
11:00	87.2%	2.2 min late	7 min late	1,347 · 15 days
12:00	90.2%	0.6 min late	6.2 min late	1,341 · 15 days
13:00	90.3%	2.1 min late	5.8 min late	1,305 · 15 days
14:00	78.0%	2.2 min late	10.5 min late	1,500 · 15 days
15:00	76.9%	2.4 min late	10.1 min late	1,278 · 15 days
16:00	78.3%	2 min late	11.2 min late	1,246 · 15 days
17:00	85.1%	2 min late	8.4 min late	1,291 · 15 days
18:00	87.0%	2.4 min late	6.8 min late	1,314 · 15 days
19:00	88.3%	1.7 min late	6.3 min late	1,301 · 15 days
20:00	77.8%	1.4 min late	11.3 min late	1,237 · 15 days
21:00	78.7%	2 min late	8.9 min late	1,246 · 15 days
22:00	77.3%	2.2 min late	10.6 min late	898 · 15 days
23:00	67.1%	2.9 min late	10 min late	477 · 14 days

1 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

Scheduled bus, but not observed in realtime

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%

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.

Service day

November 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

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.

· Open all evidence for this day

Draft

This translation is a draft.

Help improve it

About 23% of this site is translated so far. The rest is shown in English.

Read this page in English

This page is a machine draft in Mohawk (Kanien’kéha), the language of the Kanien’kehá:ka (Mohawk) communities. It was prepared without review by its speakers, and is waiting for one. Speakers and the community are invited to correct it. We will replace it with their words. Ottawa is on the unceded territory of the Anishinabe Algonquin Nation.

Cette page est une ébauche automatique en mohawk (kanien’kéha), la langue des communautés kanien’kehá:ka (mohawks). Elle a été préparée sans révision par ses locuteurs, et attend l’un d’eux. Les locuteurs et la communauté sont invités à la corriger. Nous la remplacerons par leurs mots. Ottawa se trouve sur le territoire non cédé de la Nation algonquine anishinabe (Anishinabe Algonquin Nation).