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 67 trips cancelled now · 3 did not run in NovemberCancellations →

Previous measure: 90.9% of arrivals were within five minutes of the timetable (52,138 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 67: Fournier/Gréber

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

CENTRE RIDEAU0 min sched.
ALBERT/METCALFE2 min sched.
ALBERT/BANK4 min sched.
KENT / SPARKS5 min sched.
WELLINGTON/LYON6 min sched.
LAVAL/LAURIER11 min sched.
du PORTAGE/de l'HÔTEL-de-VILLE12 min sched.
de l'HÔTEL-de-VILLE/LAURIER13 min sched.
LAURIER/de l'HÔTEL-de-VILLE14 min sched.
MUSÉE DE L'HISTOIRE14 min sched.
LAURIER/des ALLUMETTIÈRES15 min sched.
LAURIER/VERDUN15 min sched.
204, LAURIER16 min sched.
LAURIER/SACRÉ-COEUR16 min sched.
CENTRE LA PIÉTÀ17 min sched.
DUSSAULT/CHAMPLAIN17 min sched.
FOURNIER/HENRI-GAUTHIER18 min sched.
FOURNIER/BÉRIAULT19 min sched.
FOURNIER/du LAC LEAMY2 min sched.
GRÉBER/JACQUES-CARTIER2 min sched.
GRÉBER/SAINT-LOUIS3 min sched.
GRÉBER/SAINT-LOUIS4 min sched.
GRÉBER/LAFORTUNE4 min sched.
GRÉBER/de POINTE-GATINEAU5 min sched.
GRÉBER/LOUIS-RIEL7 min sched.
GRÉBER/LOUIS-RIEL7 min sched.
GRÉBER/de la SAVANE8 min sched.
de la SAVANE/SAINT-ANTOINE9 min sched.
LES PROMENADES10 min sched.
SAINT-JOSAPHAT/LAFERRIÈRE11 min sched.
SAINT-JOSAPHAT/MONSEIGNEUR-FORBES12 min sched.
SAINT-JOSAPHAT/SAINT-GEORGES13 min sched.
de POINTE-GATINEAU/SAINT-ROSAIRE13 min sched.
de POINTE-GATINEAU/SMITH14 min sched.
de POINTE-GATINEAU/ROBERT-SAVOIE15 min sched.
de POINTE-GATINEAU/JOLY16 min sched.
SAINT-LOUIS/de la CITÉ17 min sched.
de la CITÉ/de la FONTENELLE18 min sched.
de la CITÉ/de la SAVANE18 min sched.
de la CITÉ/LAMARCHE19 min sched.
de la CITÉ/LAMARCHE20 min sched.
de la CITÉ/de la GAPPE20 min sched.
de la GAPPE/de la CITÉ0 min sched.
de la GAPPE/de ROUVILLE0 min sched.
QUAI LOCAL de la CITÉ arrivée1 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. Trips with any notice: 1.

Trips needing investigation

4 of 433 trips with a usable feed window (0.9%) had no matching position.

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

429 with position · 4 to investigate · 52 excluded · 485 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nov 4, 2026, 2:17 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.

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

Published position coverage: 429 / 485 (88.5%). 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, 12:49 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

90.9%

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

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

The hours we have evidence for

0088% · 407 predictions · 10 days
0699% · 512 predictions · 10 days
0798% · 660 predictions · 9 days
0896% · 825 predictions · 10 days
0989% · 1,925 predictions · 11 days
1096% · 2,134 predictions · 11 days
1192% · 2,284 predictions · 12 days
1292% · 2,392 predictions · 12 days
1394% · 2,287 predictions · 12 days
1487% · 2,145 predictions · 13 days
1593% · 1,310 predictions · 12 days
1689% · 929 predictions · 13 days
1793% · 1,014 predictions · 12 days
1890% · 1,702 predictions · 11 days
1980% · 1,663 predictions · 11 days
2087% · 1,334 predictions · 10 days
2186% · 1,380 predictions · 10 days
2290% · 1,432 predictions · 10 days
2389% · 1,460 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: 50 of 37,622 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (91) 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,810	0% (0)	0% (0)
Midday (9 a.m. to 3 p.m.)	18,889	0% (35)	0% (41)
Afternoon rush (3 to 6 p.m.)	4,247	0% (3)	0% (1)
Evening (6 to 10 p.m.)	8,072	0% (11)	1% (48)
Night (10 p.m. to 4 a.m.)	4,604	0% (1)	0% (1)

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

Where this route is slowest

Slowest: QUAI LOCAL de la CITÉ #10 to LES PROMENADES, 9.3 km/h actual against 17.5 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
QUAI LOCAL de la CITÉ #10	LES PROMENADES	3.4 km	17.5 km/h	9.3 km/h	542	63%
CENTRE RIDEAU	de l'HÔTEL-de-VILLE/LAURIER	2.8 km	13.3 km/h	10 km/h	542	25%
du PORTAGE/AUBRY	CENTRE RIDEAU	2.8 km	13.9 km/h	14.1 km/h	529	0%
LES PROMENADES	GRÉBER/ SAINT-LOUIS	1.5 km	14.9 km/h	15.7 km/h	574	0%
de l'HÔTEL-de-VILLE/LAURIER	LAURIER/des ALLUMETTIÈRES	690 m	20.7 km/h	16.6 km/h	599	26%
SACRÉ-COEUR/LAURIER	du PORTAGE/AUBRY	1.3 km	21.2 km/h	18 km/h	584	11%
LES PROMENADES	QUAI LOCAL de la CITÉ arrivée	4 km	18.4 km/h	19.1 km/h	536	0%
GRÉBER/SAINT-LOUIS	LES PROMENADES	1.9 km	18.9 km/h	19.4 km/h	596	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.

Oháha: kaio'tén:sera
ALBERT between ELGIN and METCALFE
Oct 29, 2026, 12:00 a.m. to Jan 26, 2027, 5:00 p.m.
ALBERT lane reduction between ELGIN and METCALFE due to construction, from October 29th to January 26th.
The City marks this as affecting transit.
about 0 m from the route
City record updated Nov 2, 2026, 12:44 p.m..
Oháha: kaio'tén:sera
Slater between Bay and Lyon
Oct 30, 2026, 12:00 a.m. to Nov 6, 2026, 5:00 p.m.
Slater lane reduction between Bay and Lyon due to construction, from November 2nd to 6th.
about 0 m from the route
City record updated Oct 30, 2026, 1:28 p.m..
Oháha: kaio'tén:sera
ALBERT at LYON
Dates not published
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 2 m from the route
City record updated Sep 9, 2026, 6:32 p.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 →

6 partial-capture days not counted.

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

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

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

Latest cancelled trips

Mon, Nov 2, scheduled 12:40
Thu, Oct 22, scheduled 18:30

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: 3 of 433 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 15 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats7.1% of 283 trips	Usually seats16.7% of 36 trips	Usually seats14.7% of 34 trips
9 am to 3 pm	Usually seats8.1% of 1,279 trips	Usually seats8.4% of 191 trips	Usually seats1.7% of 172 trips
3 to 6 pm	Usually seats30.8% of 396 trips	Usually seats17.4% of 109 trips	Usually seats5.2% of 115 trips
6 to 10 pm	Usually seats8.8% of 580 trips	Usually seats5.1% of 98 trips	Usually seats1.1% of 90 trips
After 10 pm	Usually seats0.3% of 323 trips	Usually seats5.3% of 38 trips	Usually seats0% of 31 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

90% of predictions are within five minutes of the timetable in a typical sampled hour; the lowest sampled hour is 80%.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 19 hours with samples

00:00: 88.2% of final predictions within five minutes of the timetable, 407 predictions, typically 1.2 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: not enough data
06:00: 99.2% of final predictions within five minutes of the timetable, 512 predictions, typically 1.2 min late
07:00: 97.7% of final predictions within five minutes of the timetable, 660 predictions, typically 1.3 min late
08:00: 96% of final predictions within five minutes of the timetable, 825 predictions, typically 0.6 min late
09:00: 89.4% of final predictions within five minutes of the timetable, 1,925 predictions, typically 1.2 min late
10:00: 95.9% of final predictions within five minutes of the timetable, 2,134 predictions, typically 1.1 min late
11:00: 91.9% of final predictions within five minutes of the timetable, 2,284 predictions, typically 0.7 min late
12:00: 91.6% of final predictions within five minutes of the timetable, 2,392 predictions, typically 1.1 min late
13:00: 94.3% of final predictions within five minutes of the timetable, 2,287 predictions, typically 0.6 min late
14:00: 86.9% of final predictions within five minutes of the timetable, 2,145 predictions, typically 1.4 min late
15:00: 93.3% of final predictions within five minutes of the timetable, 1,310 predictions, typically 1.3 min late
16:00: 88.8% of final predictions within five minutes of the timetable, 929 predictions, typically 2.2 min late
17:00: 93.1% of final predictions within five minutes of the timetable, 1,014 predictions, typically 1.1 min late
18:00: 90.4% of final predictions within five minutes of the timetable, 1,702 predictions, typically 1.2 min late
19:00: 80.4% of final predictions within five minutes of the timetable, 1,663 predictions, typically 2.3 min late
20:00: 86.8% of final predictions within five minutes of the timetable, 1,334 predictions, typically 1.7 min late
21:00: 86% of final predictions within five minutes of the timetable, 1,380 predictions, typically 2.4 min late
22:00: 89.6% of final predictions within five minutes of the timetable, 1,432 predictions, typically 1.8 min late
23:00: 89.1% of final predictions within five minutes of the timetable, 1,460 predictions, typically 2 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
StrengthPredictions consistently close to timetable	00:00, 06:00, 07:00, 08:00, 09:00, 10:00, 11:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00, 20:00, 21:00, 22:00, 23:00	90%	Keep what works

Measurements

Predictions consistently close to timetable · 00:00, 06:00, 07:00, 08:00, 09:00, 10:00, 11:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00, 20:00, 21:00, 22:00, 23:00: Measured arrivals 27,795; Hours measured 19; Worst hour on time 80.4%; Median hour on time 90.4%

Open history, reliability and route analysis

Route check

How route 67 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 in this dated sample.

91 in 100 eligible predictions were within 5 minutes of the timetable · 52,138 predictions checked

Prediction sample size: Larger sample

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

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

No repeated prediction-difference period has cleared the evidence threshold yet.

No current official notice matches this route.

Prediction differences by stop

QUAI LOCAL de la CITÉ #10
64 in 100 eligible predictions differed from the timetable by more than 5 minutes (666 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?: 4 of 433 checked trips need a closer look4 of 433 trips with enough public-feed evidence had no matching position over 7 days. 52 of 485 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.1 min (positive means later; negative means earlier)91 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: 75
Distinct scheduled stops: 82
Distinct published paths: 2
Kahiatónhsera: tsi niió:re ne kà:sere: 06:00–00:33 next day

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 28,912 arrivals over 13 days; after has 4,047 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: 90.9%
Eligible predictions checked: 52,138
Weekdays with data: 17
95th-percentile predicted delay: 6.1 min late

Patterns by hour (19)

Patterns by hour (19)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
00:00	88.2%	1.2 min late	5.7 min late	407 · 10 days
06:00	99.2%	1.2 min late	3 min late	512 · 10 days
07:00	97.7%	1.3 min late	4.1 min late	660 · 9 days
08:00	96.0%	0.6 min late	4.8 min late	825 · 10 days
09:00	89.4%	1.2 min late	6.5 min late	1,925 · 11 days
10:00	95.9%	1.1 min late	4.2 min late	2,134 · 11 days
11:00	91.9%	0.7 min late	6 min late	2,284 · 12 days
12:00	91.6%	1.1 min late	5.6 min late	2,392 · 12 days
13:00	94.3%	0.6 min late	4.3 min late	2,287 · 12 days
14:00	86.9%	1.4 min late	7.5 min late	2,145 · 13 days
15:00	93.3%	1.3 min late	5.2 min late	1,310 · 12 days
16:00	88.8%	2.2 min late	6.2 min late	929 · 13 days
17:00	93.1%	1.1 min late	5.5 min late	1,014 · 12 days
18:00	90.4%	1.2 min late	6.5 min late	1,702 · 11 days
19:00	80.4%	2.3 min late	8.9 min late	1,663 · 11 days
20:00	86.8%	1.7 min late	7.3 min late	1,334 · 10 days
21:00	86.0%	2.4 min late	7.6 min late	1,380 · 10 days
22:00	89.6%	1.8 min late	6.1 min late	1,432 · 10 days
23:00	89.1%	2 min late	6.4 min late	1,460 · 10 days

No repeated pattern below 70% is yet established across at least three service days.

Scheduled bus, but not observed in realtime

429 / 485 scheduled trips published at least one position across 5 service days (88.5%).

07:006 / 19 trips without a position68.4%
19:007 / 26 trips without a position73.1%
06:003 / 12 trips without a position75.0%
20:006 / 24 trips without a position75.0%
21:006 / 24 trips without a position75.0%
22:006 / 24 trips without a position75.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 · 75 trips in the retained timetable · retained notices; capture coverage unverified

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

06:00– 06:41
Trip sto:63294709Insufficient coverage or identity; outcome unknown
06:30– 07:11
Trip sto:63290340Insufficient coverage or identity; outcome unknown
07:00– 07:45
Trip sto:63294753Insufficient coverage or identity; outcome unknown
07:22– 08:05
Trip sto:63295122Insufficient coverage or identity; outcome unknown
07:43– 08:26
Trip sto:63294570Insufficient coverage or identity; outcome unknown
08:01– 08:44
Trip sto:63295697Insufficient coverage or identity; outcome unknown
08:30– 09:13
Trip sto:63294925Insufficient coverage or identity; outcome unknown
09:00– 09:40
Trip sto:63295300Vehicle position matchedFirst / last feed position: 9:22 a.m. EST / 9:49 a.m. EST; not actual start or end times.
09:00– 09:44
Trip sto:63295698Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 9:44 a.m. EST; not actual start or end times.
09:20– 10:00
Trip sto:63294880Vehicle position matchedFirst / last feed position: 9:22 a.m. EST / 10:00 a.m. EST; not actual start or end times.
09:20– 10:02
Trip sto:63295110Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 10:01 a.m. EST; not actual start or end times.
09:40– 10:22
Trip sto:63296111Vehicle position matchedFirst / last feed position: 9:28 a.m. EST / 10:24 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).