Stop impacts: #4036 -- Holly Acres (south-side) / Ramp temporary relocation: October 30 2026 - From 11:00 pm on Monday, November 2, until 11:00 pm on Friday, December 4, stop #4036 -- Holly Acres (south-side) / Ramp will be temporarily relocated 120 metres closer to Richmond Road due to construction work near the Highway 417 off-ramp. There will be no detours, but the routes below will be impacted by the stop relocation: 57 Carling Campus ~ Complexe Carling 60 Terry Fox / Tunney's Pasture 61 Tunney's Pasture & N Rideau 62 Tunney's Pasture 63 Tunney's Pasture 66 Tunneys Pasture 67 Terry Fox / Tunney's Pasture 88 Hurdman 261 Tunney's Pasture 262 Tunney's Pasture 263 Tunney's Pasture 265 Tunney's Pasture 266 Tunney's Pasture+1 more notice

No 66 trips cancelled now · 1 did not run in NovemberCancellations →

Previous measure: 84.6% of arrivals were within five minutes of the timetable (44,863 arrivals over 22 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.

STO route 66: Mont-Luc/Du Barry

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

Quai local de la GAPPE #416 min sched.
des FLANDRES/de PIEDMONT18 min sched.
des FLANDRES/de PICARDIE18 min sched.
des FLANDRES/de TOURS19 min sched.
des FLANDRES/de NANTES20 min sched.
des FLANDRES/d'AUVERGNE20 min sched.
de TOURAINE/d'AUVERGNE21 min sched.
Av. GATINEAU/de TOURAINE22 min sched.
Av. GATINEAU/de BERNAY22 min sched.
Av. GATINEAU/de BOURGOGNE22 min sched.
Av. GATINEAU/de ROCHEFORT23 min sched.
la VÉRENDRYE OUEST/Av. GATINEAU24 min sched.
de CANNES/la VÉRENDRYE OUEST25 min sched.
de CANNES/de RAYOL26 min sched.
de CANNES/de SALERNES26 min sched.
de CANNES/de SANARY27 min sched.
de CANNES/de MOUGINS28 min sched.
de CANNES/de CONTES28 min sched.
de CANNES/de MONTÉ-CARLO29 min sched.
de CANNES/de CASTILLOU29 min sched.
de CANNES/de VENCE30 min sched.
École secondaire de L'ÉRABLIÈRE31 min sched.
de CANNES/OSTER31 min sched.
LEBAUDY/de CANNES32 min sched.
LEBAUDY/le LOUTRE32 min sched.
CENTRE COMMUNAUTAIRE LIMBOUR33 min sched.
le GALLOIS/RATIER34 min sched.
le GALLOIS/MAJOR34 min sched.
le GALLOIS/JOBIN34 min sched.
le GALLOIS/de la PLAINE35 min sched.
de CANNES/de la PLAINE36 min sched.
de CANNES/STÉPHANE37 min sched.
de CANNES/COLETTE37 min sched.
de CANNES/de SAINT-VALLIER38 min sched.
la VÉRENDRYE OUEST/Av. GATINEAU40 min sched.
du BARRY/DRAPEAU41 min sched.
du BARRY/de BOURASSA42 min sched.
du BARRY/de MATANE42 min sched.
du BARRY/d'OLIER43 min sched.
du BARRY/le BARON43 min sched.
du BARRY/MATAPÉDIA44 min sched.
du BARRY/GRÉBER45 min sched.
de la GAPPE/de L'ALLIANCE46 min sched.
STATION LOCALE LES PROMENADES47 min sched.

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: 4 trips with qualifying later matching vehicle observations. Trips with any notice: 5.

Trips needing investigation

2 of 334 trips with a usable feed window (0.6%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

332 with position · 2 to investigate · 66 excluded · 400 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 2:37 p.m..

Coverage, exclusions and sources

0 of 12 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

66 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 332 / 400 (83%). 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:38 p.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

84.6%

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

Predictions in the source: 44,863
Weekdays with evidence: 17
Evidence window: Oct 6, 2026 – Nov 3, 2026

The hours we have evidence for

0596% · 361 predictions · 7 days
0693% · 1,520 predictions · 10 days
0784% · 1,441 predictions · 9 days
0878% · 1,674 predictions · 10 days
0964% · 1,424 predictions · 11 days
1086% · 884 predictions · 11 days
1184% · 923 predictions · 12 days
1277% · 926 predictions · 12 days
1354% · 954 predictions · 12 days
1485% · 973 predictions · 13 days
1576% · 2,089 predictions · 12 days
1663% · 1,980 predictions · 13 days
1791% · 2,198 predictions · 12 days
1891% · 2,018 predictions · 11 days
1985% · 925 predictions · 11 days
2095% · 833 predictions · 10 days
2197% · 905 predictions · 10 days
2298% · 793 predictions · 10 days
2399% · 638 predictions · 10 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

6 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: 21 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 12, 2026.

Values and interpretation

0% of back-to-back buses on this route arrived bunched together: 56 of 19,359 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (43) 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.)	106	0% (0)	1% (1)
Morning rush (6 to 9 a.m.)	6,562	0% (4)	0% (5)
Midday (9 a.m. to 3 p.m.)	1,672	0% (2)	0% (1)
Afternoon rush (3 to 6 p.m.)	7,889	1% (50)	0% (14)
Evening (6 to 10 p.m.)	3,130	0% (0)	1% (22)

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

Where this route is slowest

Slowest: STATION LES PROMENADES to du BARRY/le BARON, 10.6 km/h actual against 14.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
STATION LES PROMENADES	du BARRY/le BARON	1.2 km	14.9 km/h	10.6 km/h	415	31%
du BARRY/le BARON	STATION LOCALE LES PROMENADES	1 km	16.2 km/h	15.2 km/h	433	5%
du BARRY/le BARON	la VÉRENDRYE OUEST/Av. GATINEAU	1.4 km	22.1 km/h	17.7 km/h	447	15%
de CANNES/de SAINT-VALLIER	la VÉRENDRYE OUEST/Av. GATINEAU	500 m	16.5 km/h	18.3 km/h	456	6%
la VÉRENDRYE OUEST/Av. GATINEAU	de CANNES/de CAVAILLON	460 m	19.3 km/h	19.2 km/h	468	11%
la VÉRENDRYE OUEST/Av. GATINEAU	du BARRY/le BARON	1.4 km	27.8 km/h	21.2 km/h	449	15%
la VÉRENDRYE OUEST/Av. GATINEAU	LEBAUDY/de CANNES	2.9 km	22.3 km/h	22.6 km/h	441	1%
de CANNES/de CAVAILLON	de CANNES/de la PLAINE	800 m	24 km/h	23.7 km/h	469	4%

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

Tsi ní:ioht →

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

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

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

Hours with the most cancellations: 1 p.m. (1), 5 p.m. (1)

Latest cancelled trips

Tue, Nov 3, scheduled 17:13
Fri, Oct 23, scheduled 13:28

A cause is shown only when STO’s own alert for that trip gives one.

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

When this route is usually busy

From the load level STO’s buses report, over the last eight weeks. A time is marked usually busy when at least half of the trips with a reading reached standing room or fuller.

No time of day was usually busy in the last eight weeks.

When this route is usually busy	Wísk niwenhniserá:ke	Entákta	Awentatokentì:ke
Before 6 am	Usually seats0% of 121 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats0.7% of 594 trips	Usually seats0% of 42 trips	Usually seats0% of 33 trips
9 am to 3 pm	Usually seats0% of 563 trips	Usually seats0% of 100 trips	Usually seats0% of 96 trips
3 to 6 pm	Usually seats0.8% of 626 trips	Usually seats0% of 52 trips	Usually seats0% of 45 trips
6 to 10 pm	Usually seats0% of 397 trips	Usually seats2.9% of 70 trips	Usually seats3% of 67 trips
After 10 pm	Usually seats0% of 130 trips	Usually seats0% of 30 trips	Usually seats0% of 32 trips

Based on 56 computed days.

Source: the occupancy status in STO’s public real-time vehicle feed, which STO sets from each bus’s load sensor (seats available under 60% full, standing room under 90%, full above 90%).
Each trip counts once per time of day, at the highest load it reported.
Reports of an empty bus are left out, because older records could not tell an empty bus from one with no sensor.
A time of day needs at least 12 trips on at least 4 different days before anything is shown. Holidays are counted with their day of the week.

Open the dated prediction analysis

Ka' nikarihò:ten

What this route needs

Median provider predictions are 3.5 to 4.8 min later than the timetable in 3 hours of the day.

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

13:00 has 54% of predictions within five minutes of the timetable, against 85% 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, 19 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: 96.4% of final predictions within five minutes of the timetable, 361 predictions, typically 0.1 min late
06:00: 93.4% of final predictions within five minutes of the timetable, 1,520 predictions, typically 0.9 min late
07:00: 84.1% of final predictions within five minutes of the timetable, 1,441 predictions, typically 1.9 min late
08:00: 78% of final predictions within five minutes of the timetable, 1,674 predictions, typically 2.7 min late
09:00: 63.5% of final predictions within five minutes of the timetable, 1,424 predictions, typically 3.5 min late
10:00: 85.5% of final predictions within five minutes of the timetable, 884 predictions, typically 2.4 min late
11:00: 83.9% of final predictions within five minutes of the timetable, 923 predictions, typically 1.7 min late
12:00: 77.2% of final predictions within five minutes of the timetable, 926 predictions, typically 1.9 min late
13:00: 53.6% of final predictions within five minutes of the timetable, 954 predictions, typically 4.8 min late
14:00: 84.9% of final predictions within five minutes of the timetable, 973 predictions, typically 1.4 min late
15:00: 75.6% of final predictions within five minutes of the timetable, 2,089 predictions, typically 2.6 min late
16:00: 63.2% of final predictions within five minutes of the timetable, 1,980 predictions, typically 3.7 min late
17:00: 90.5% of final predictions within five minutes of the timetable, 2,198 predictions, typically 1.8 min late
18:00: 90.5% of final predictions within five minutes of the timetable, 2,018 predictions, typically 1.1 min late
19:00: 84.8% of final predictions within five minutes of the timetable, 925 predictions, typically 2.2 min late
20:00: 94.8% of final predictions within five minutes of the timetable, 833 predictions, typically 1.3 min late
21:00: 96.6% of final predictions within five minutes of the timetable, 905 predictions, typically 1.7 min late
22:00: 98.4% of final predictions within five minutes of the timetable, 793 predictions, typically 0.9 min late
23:00: 98.9% of final predictions within five minutes of the timetable, 638 predictions, typically 1.6 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	09:00 · 13:00 · 16:00	3.5 min late … 3.7 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	13:00	54%	Operations, not the timetable

Measurements

Predictions later than timetable · 16:00: Measured arrivals 1,980; Hours affected 1; Spread 7.9 min; Median delay 3.7 min; Suggested running time change 3.7 min
Predictions later than timetable · 09:00: Measured arrivals 1,424; Hours affected 1; Spread 7.9 min; Median delay 3.5 min; Suggested running time change 3.5 min
Predictions later than timetable · 13:00: Measured arrivals 954; Hours affected 1; Spread 7.2 min; Median delay 4.8 min; Suggested running time change 4.8 min
One hour has a lower prediction match · 13:00: Hour 13:00; Ioiánere tsi nikarì:wes 53.6%; Measured arrivals 954; Shortfall 31.3 pts; Route median on time 84.9%

Open history, reliability and route analysis

Route check

How route 66 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.

85 in 100 eligible predictions were within 5 minutes of the timetable · 44,863 predictions checked

Prediction sample size: Larger sample

Based on 44,863 eligible provider predictions over 22 measured days, from Oct 6, 2026 to Nov 3, 2026.

Updated Nov 4, 2026, 2:32 p.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.

13–14: 46 in 100 eligible predictions differed from the timetable by more than 5 minutes (954 predictions over 12 days).
16–17: 37 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,980 predictions over 13 days).
09–10: 37 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,424 predictions over 11 days).

No current official notice matches this route.

Prediction differences by stop

Quai local de la GAPPE #4
49 in 100 eligible predictions differed from the timetable by more than 5 minutes (500 predictions over 24 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?: 2 of 334 checked trips need a closer look2 of 334 trips with enough public-feed evidence had no matching position over 7 days. 66 of 400 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 7.9 min (positive means later; negative means earlier)85 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 November 2, 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: 0
Distinct scheduled stops: 0
Distinct published paths: 0
Kahiatónhsera: tsi niió:re ne kà:sere: —–—

Kahiatónhsera: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

New schedule

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

Schedule trips: 66
Distinct scheduled stops: 90
Distinct published paths: 2
Kahiatónhsera: tsi niió:re ne kà:sere: 05:30–23:41

Operator calendar-date records: 1 added · 0 removed

Kahiatónhsera: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

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 24,717 arrivals over 13 days; after has 3,225 arrivals over 2 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: 84.6%
Eligible predictions checked: 44,863
Weekdays with data: 17
95th-percentile predicted delay: 7.9 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.2 min late	0.7 min late	28 · 2 days
05:00	96.4%	0.1 min late	2.7 min late	361 · 7 days
06:00	93.4%	0.9 min late	5.2 min late	1,520 · 10 days
07:00	84.1%	1.9 min late	7.8 min late	1,441 · 9 days
08:00	78.0%	2.7 min late	13.3 min late	1,674 · 10 days
09:00	63.5%	3.5 min late	11.4 min late	1,424 · 11 days
10:00	85.5%	2.4 min late	6.2 min late	884 · 11 days
11:00	83.9%	1.7 min late	8.8 min late	923 · 12 days
12:00	77.2%	1.9 min late	11.1 min late	926 · 12 days
13:00	53.6%	4.8 min late	12 min late	954 · 12 days
14:00	84.9%	1.4 min late	8.7 min late	973 · 13 days
15:00	75.6%	2.6 min late	9.9 min late	2,089 · 12 days
16:00	63.2%	3.7 min late	11.6 min late	1,980 · 13 days
17:00	90.5%	1.8 min late	6 min late	2,198 · 12 days
18:00	90.5%	1.1 min late	5.9 min late	2,018 · 11 days
19:00	84.8%	2.2 min late	8.6 min late	925 · 11 days
20:00	94.8%	1.3 min late	4.7 min late	833 · 10 days
21:00	96.6%	1.7 min late	4.4 min late	905 · 10 days
22:00	98.4%	0.9 min late	3.8 min late	793 · 10 days
23:00	98.9%	1.6 min late	3.7 min late	638 · 10 days

3 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

332 / 400 scheduled trips published at least one position across 5 service days (83.0%).

07:0014 / 39 trips without a position64.1%
22:005 / 14 trips without a position64.3%
23:003 / 9 trips without a position66.7%
06:008 / 27 trips without a position70.4%
19:004 / 14 trips without a position71.4%
20:004 / 14 trips without a position71.4%

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 · 66 trips in the retained timetable · retained notices; capture coverage unverified

In short: 45 with a matched position · 1 with no matching position (to investigate) · 20 with an unknown outcome.

05:30– 05:59
Trip sto:63294918Insufficient coverage or identity; outcome unknown
05:50– 06:19
Trip sto:63290346Insufficient coverage or identity; outcome unknown
05:57– 06:27
Trip sto:63295249Insufficient coverage or identity; outcome unknown
06:08– 06:37
Trip sto:63295250Insufficient coverage or identity; outcome unknown
06:17– 06:47
Trip sto:63295302Insufficient coverage or identity; outcome unknown
06:29– 06:58
Trip sto:63295297Insufficient coverage or identity; outcome unknown
06:37– 07:07
Trip sto:63295252Insufficient coverage or identity; outcome unknown
06:49– 07:18
Trip sto:63295253Insufficient coverage or identity; outcome unknown
07:00– 07:30
Trip sto:63290347Insufficient coverage or identity; outcome unknown
07:10– 07:39
Trip sto:63290348Insufficient coverage or identity; outcome unknown
07:19– 07:49
Trip sto:63295299Insufficient coverage or identity; outcome unknown
07:33– 08:02
Trip sto:63295291Insufficient coverage or identity; outcome unknown

· 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).