2 trips cancelled now · 0 did not run in NovemberCancellations →

Previous measure: 92.6% of arrivals were within five minutes of the timetable (35,677 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 93: Rotary ⇄ Leitrim

Tiótkon 30 min

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 28, 2026 – Nov 3, 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: 12 trips with qualifying later matching vehicle observations. Trips with any notice: 12.

Trips needing investigation

0 of 490 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.

490 with position · 0 to investigate · 0 excluded · 490 scheduled trips

Current feed. 2 distinct trips on this route are explicitly marked cancelled or deleted in the current feed. Observed: Nov 4, 2026, 2:14 a.m..

Coverage, exclusions and sources

0 of 4 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: 490 / 490 (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 4, 2026, 1:09 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

92.6%

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

Predictions in the source: 35,677
Weekdays with evidence: 19
Evidence window: Oct 5, 2026 – Nov 2, 2026

The hours we have evidence for

0597% · 493 predictions · 11 days
06100% · 865 predictions · 13 days
0793% · 951 predictions · 14 days
0847% · 901 predictions · 14 days
0982% · 1,087 predictions · 14 days
1090% · 1,118 predictions · 14 days
1196% · 1,106 predictions · 14 days
12100% · 1,079 predictions · 14 days
1396% · 1,086 predictions · 14 days
1492% · 1,174 predictions · 14 days
1587% · 1,053 predictions · 14 days
1697% · 1,048 predictions · 14 days
1788% · 1,099 predictions · 14 days
1888% · 1,078 predictions · 14 days
1997% · 1,086 predictions · 14 days
2099% · 1,050 predictions · 14 days
2194% · 1,022 predictions · 14 days
2295% · 873 predictions · 13 days
23100% · 483 predictions · 13 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?

19 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 7, 2026 to November 3, 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: 40 of 27,241 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (34) 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
Morning rush (6 to 9 a.m.)	1,896	0% (2)	0% (6)
Midday (9 a.m. to 3 p.m.)	11,480	0% (2)	0% (20)
Afternoon rush (3 to 6 p.m.)	5,044	0% (24)	0% (5)
Evening (6 to 10 p.m.)	7,458	0% (12)	0% (3)
Night (10 p.m. to 4 a.m.)	1,363	0% (0)	0% (0)

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

Where this route is slowest

Slowest: LEITRIM B to ALBION / LEITRIM, 19.3 km/h actual against 16.9 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
LEITRIM B	ALBION / LEITRIM	850 m	16.9 km/h	19.3 km/h	833	1%
BANK / ROTARY	KELLY FARM / SHEPODY	1.7 km	20.7 km/h	24.7 km/h	848	1%
ALBION / LEITRIM	KELLY FARM / SHEPODY	2.5 km	24.8 km/h	31.4 km/h	844	1%

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.

The City’s road work list could not be read right now.

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.

5 scheduled trips with counted cancellation notices from Wed, Oct 7 to Tue, Nov 3.

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

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

Latest cancelled trips

Tue, Oct 27, scheduled 17:44
Mon, Oct 26, scheduled 08:12
Mon, Oct 26, scheduled 07:52
Wed, Oct 21, scheduled 18:14
Wed, Oct 21, scheduled 17:54

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

Median provider predictions are 5.4 min later than the timetable in 1 hours of the day.

Predictions near the start are about 5.5 min later than the timetable, with a similar difference near the end. This does not establish the cause.

08:00 has 47% of predictions within five minutes of the timetable, against 95% the rest of the day.

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, 20 hours with samples

00:00: not enough data
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 97.2% of final predictions within five minutes of the timetable, 493 predictions, typically 0.1 min late
06:00: 99.8% of final predictions within five minutes of the timetable, 865 predictions, typically 0.1 min late
07:00: 93.3% of final predictions within five minutes of the timetable, 951 predictions, typically 0.7 min late
08:00: 46.7% of final predictions within five minutes of the timetable, 901 predictions, typically 5.4 min late
09:00: 81.6% of final predictions within five minutes of the timetable, 1,087 predictions, typically 1.6 min late
10:00: 89.7% of final predictions within five minutes of the timetable, 1,118 predictions, typically 0.6 min late
11:00: 95.5% of final predictions within five minutes of the timetable, 1,106 predictions, typically 0.4 min early
12:00: 99.6% of final predictions within five minutes of the timetable, 1,079 predictions, typically 0.2 min late
13:00: 96.2% of final predictions within five minutes of the timetable, 1,086 predictions, typically 0 min late
14:00: 92.1% of final predictions within five minutes of the timetable, 1,174 predictions, typically 0 min late
15:00: 87.2% of final predictions within five minutes of the timetable, 1,053 predictions, typically 0.1 min late
16:00: 96.5% of final predictions within five minutes of the timetable, 1,048 predictions, typically 0.2 min late
17:00: 88% of final predictions within five minutes of the timetable, 1,099 predictions, typically 0.6 min late
18:00: 87.7% of final predictions within five minutes of the timetable, 1,078 predictions, typically 1.1 min late
19:00: 97.3% of final predictions within five minutes of the timetable, 1,086 predictions, typically 0.6 min late
20:00: 98.8% of final predictions within five minutes of the timetable, 1,050 predictions, typically 0.2 min late
21:00: 93.9% of final predictions within five minutes of the timetable, 1,022 predictions, typically 0.2 min late
22:00: 95.3% of final predictions within five minutes of the timetable, 873 predictions, typically 0.6 min late
23:00: 100% of final predictions within five minutes of the timetable, 483 predictions, typically 0.3 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
ProblemPredictions later than timetable	08:00	5.4 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	08:00	47%	Operations, not the timetable

Measurements

Predictions later than timetable · 08:00: Measured arrivals 901; Hours affected 1; Spread 9.3 min; Median delay 5.4 min; Suggested running time change 5.4 min
One hour has a lower prediction match · 08:00: Hour 08:00; Ioiánere tsi nikarì:wes 46.7%; Measured arrivals 901; Shortfall 48.6 pts; Route median on time 95.3%

Open history, reliability and route analysis

Route check

How route 93 has been running

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

Bottom line

Provider predictions were usually close to schedule, but check the problem times below.

93 in 100 eligible predictions were within 5 minutes of the timetable · 35,677 predictions checked

Prediction sample size: Larger sample

Based on 35,677 eligible provider predictions over 27 measured days, from Oct 5, 2026 to Nov 2, 2026.

Updated Nov 4, 2026, 1:43 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.

08–09: 53 in 100 eligible predictions differed from the timetable by more than 5 minutes (901 predictions over 14 days).

No current official notice matches this route.

Prediction differences by stop

We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.

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 4Checks 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 490 checked trips need a closer look0 of 490 trips with enough public-feed evidence had no matching position over 7 days. 0 of 490 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 6.0 min (positive means later; negative means earlier)93 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: 72
Distinct scheduled stops: 40
Distinct published paths: 2
Kahiatónhsera: tsi niió:re ne kà:sere: 05:11–23:57

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: 72
Distinct scheduled stops: 40
Distinct published paths: 2
Kahiatónhsera: tsi niió:re ne kà:sere: 05:11–23:57

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 18,542 arrivals over 14 days; after has 6,729 arrivals over 5 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 5, 2026 to November 2, 2026

Within 5 minutes of schedule: 92.6%
Eligible predictions checked: 35,677
Weekdays with data: 19
95th-percentile predicted delay: 6 min late

Patterns by hour (20)

Patterns by hour (20)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
00:00	100.0%	0.7 min early	1 min late	80 · 4 days
05:00	97.2%	0.1 min late	2.9 min late	493 · 11 days
06:00	99.8%	0.1 min late	3.3 min late	865 · 13 days
07:00	93.3%	0.7 min late	6.9 min late	951 · 14 days
08:00	46.7%	5.4 min late	14.7 min late	901 · 14 days
09:00	81.6%	1.6 min late	10.2 min late	1,087 · 14 days
10:00	89.7%	0.6 min late	6.6 min late	1,118 · 14 days
11:00	95.5%	0.4 min early	3.7 min late	1,106 · 14 days
12:00	99.6%	0.2 min late	3.6 min late	1,079 · 14 days
13:00	96.2%	0 min late	4.5 min late	1,086 · 14 days
14:00	92.1%	0 min late	7.2 min late	1,174 · 14 days
15:00	87.2%	0.1 min late	10.9 min late	1,053 · 14 days
16:00	96.5%	0.2 min late	4.3 min late	1,048 · 14 days
17:00	88.0%	0.6 min late	15.9 min late	1,099 · 14 days
18:00	87.7%	1.1 min late	7.7 min late	1,078 · 14 days
19:00	97.3%	0.6 min late	4.2 min late	1,086 · 14 days
20:00	98.8%	0.2 min late	3.6 min late	1,050 · 14 days
21:00	93.9%	0.2 min late	5.5 min late	1,022 · 14 days
22:00	95.3%	0.6 min late	4.9 min late	873 · 13 days
23:00	100.0%	0.3 min late	3.4 min late	483 · 13 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

490 / 490 scheduled trips published at least one position across 1 service days (100.0%).

05:000 / 15 trips without a position100.0%
06:000 / 22 trips without a position100.0%
07:000 / 24 trips without a position100.0%
08:000 / 25 trips without a position100.0%
09:000 / 28 trips without a position100.0%
10:000 / 30 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 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 72 trips in the retained timetable · retained notices; capture coverage unverified

In short: 72 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.

05:11– 05:28
Trip 34464030Vehicle position matchedFirst / last feed position: 5:15 a.m. EST / 5:30 a.m. EST; not actual start or end times.
05:31– 05:42
Trip 21008030Vehicle position matchedFirst / last feed position: 4:49 a.m. EST / 5:55 a.m. EST; not actual start or end times.
05:54– 06:11
Trip 21614030Vehicle position matchedFirst / last feed position: 5:12 a.m. EST / 6:12 a.m. EST; not actual start or end times.
06:14– 06:25
Trip 6833030Vehicle position matchedFirst / last feed position: 6:13 a.m. EST / 6:55 a.m. EST; not actual start or end times.
06:24– 06:41
Trip 18572030Vehicle position matchedFirst / last feed position: 6:23 a.m. EST / 6:46 a.m. EST; not actual start or end times.
06:44– 06:55
Trip 32316030Vehicle position matchedFirst / last feed position: 6:47 a.m. EST / 7:23 a.m. EST; not actual start or end times.
06:54– 07:11
Trip 4326030Vehicle position matchedFirst / last feed position: 6:56 a.m. EST / 7:12 a.m. EST; not actual start or end times.
07:14– 07:25
Trip 7198030Vehicle position matchedFirst / last feed position: 7:13 a.m. EST / 7:27 a.m. EST; not actual start or end times.
07:24– 07:43
Trip 14371030Vehicle position matchedFirst / last feed position: 7:24 a.m. EST / 7:43 a.m. EST; not actual start or end times.
07:44– 07:56
Trip 29375030Vehicle position matchedFirst / last feed position: 7:44 a.m. EST / 8:00 a.m. EST; not actual start or end times.
07:52– 08:12
Trip 18338030Vehicle position matchedFirst / last feed position: 7:25 a.m. EST / 8:15 a.m. EST; not actual start or end times.
08:12– 08:24
Trip 14253030Vehicle position matchedFirst / last feed position: 7:40 a.m. EST / 8:30 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).