Detour Route 34 South: Route 34 diverted from Laval to Station Lyon.

No 34 trips cancelled now · 2 did not run in NovemberCancellations →

Previous measure: 79.5% of arrivals were within five minutes of the timetable (69,224 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 34: Plateau/Des Trembles

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

CENTRE RIDEAU3 min sched.
ALBERT/METCALFE5 min sched.
ALBERT/BANK7 min sched.
KENT / SPARKS8 min sched.
WELLINGTON/LYON9 min sched.
du PORTAGE/AUBRY15 min sched.
du PORTAGE/LAVAL16 min sched.
LAURIER/EDDY17 min sched.
ALEXANDRE-TACHÉ/MILLAR19 min sched.
ALEXANDRE-TACHÉ/SAINT-JOSEPH20 min sched.
ALEXANDRE-TACHÉ/CHÂTEAUBRIAND21 min sched.
ALEXANDRE-TACHÉ/HORMIDAS-DUPUIS22 min sched.
ALEXANDRE-TACHÉ/BÉGIN23 min sched.
ALEXANDRE-TACHÉ/BOUDRIA24 min sched.
ALEXANDRE-TACHÉ/SAINTE-THÉRÈSE24 min sched.
ALEXANDRE-TACHÉ/SAINT-DOMINIQUE25 min sched.
ALEXANDRE-TACHÉ/SAINT-RAYMOND26 min sched.
SAINT-RAYMOND/des CAPUCINES27 min sched.
SAINT-RAYMOND/des JONQUILLES28 min sched.
SAINT-RAYMOND/des TREMBLES28 min sched.
des TREMBLES/SAINT-RAYMOND29 min sched.
des TREMBLES/BOYER0 min sched.
des TREMBLES/de la SITELLE0 min sched.
des TREMBLES/de L'ÉPERVIER1 min sched.
des TREMBLES/des PERDRIX2 min sched.
des TREMBLES/des TOURTERELLES2 min sched.
LOUISE-CAMPAGNA/du MARTIN-PÊCHEUR3 min sched.
LOUISE-CAMPAGNA/du BRUANT4 min sched.
LOUISE-CAMPAGNA/des MIGRATEURS4 min sched.
SAINT-RAYMOND/LOUISE-CAMPAGNA5 min sched.
du PLATEAU/SAINT-RAYMOND7 min sched.
du PLATEAU/des CÈDRES8 min sched.
de l'ATMOSPHÈRE/du PLATEAU9 min sched.
de l'ATMOSPHÈRE/de l'ASTROLABE9 min sched.
de l'ATMOSPHÈRE/de la SAPINIÈRE10 min sched.
de l'ATMOSPHÈRE/de L'ÉCLIPSE10 min sched.
de l'ATMOSPHÈRE/de l'ÉQUATEUR12 min sched.
de l'ATMOSPHÈRE/du FIRMAMENT12 min sched.
des GRIVES/de l'ATMOSPHERE13 min sched.
des GRIVES/du STRATUS14 min sched.
du PLATEAU/des GRIVES15 min sched.
du PLATEAU/du CUMULUS16 min sched.
du PLATEAU/de l'AUTOMNE17 min sched.
du PLATEAU/de BRUXELLES17 min sched.
AGORA18 min sched.
PLATEAU/EUROPE19 min sched.
du PLATEAU/du PRADO20 min sched.
du PLATEAU/de l'AMÉRIQUE-FRANÇAISE21 min sched.
du PLATEAU/d'AMSTERDAM23 min sched.
du PLATEAU/de LIVERPOOL24 min sched.
du PLATEAU/du MARIGOT26 min sched.
du PLATEAU/du MARIGOT27 min sched.
KATIMAVIK/DU PLATEAU27 min sched.
de SÉTO/KATIMAVIK28 min sched.
des ALLUMETTIÈRES/SAMUEL-EDEY33 min sched.
des ALLUMETTIÈRES/WILFRID-LAVIGNE34 min sched.
des ALLUMETTIÈRES/des CHAMPIGNONS0 min sched.
des ALLUMETTIÈRES/KLOCK1 min sched.
des ALLUMETTIÈRES/FRONT2 min sched.
PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée4 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: 2 trips with qualifying later matching vehicle observations. Trips with any notice: 2.

Trips needing investigation

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

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

387 with position · 2 to investigate · 53 excluded · 442 scheduled trips

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

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

Published position coverage: 387 / 442 (87.6%). 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:48 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

79.5%

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

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

The hours we have evidence for

0081% · 719 predictions · 10 days
0690% · 652 predictions · 10 days
0789% · 803 predictions · 9 days
0887% · 1,249 predictions · 10 days
0986% · 2,286 predictions · 11 days
1087% · 2,363 predictions · 11 days
1186% · 2,410 predictions · 12 days
1274% · 2,523 predictions · 12 days
1384% · 2,624 predictions · 12 days
1475% · 2,421 predictions · 13 days
1565% · 2,307 predictions · 12 days
1675% · 1,524 predictions · 13 days
1755% · 1,551 predictions · 12 days
1869% · 2,373 predictions · 11 days
1983% · 2,249 predictions · 11 days
2083% · 2,214 predictions · 10 days
2182% · 2,236 predictions · 10 days
2288% · 2,317 predictions · 10 days
2390% · 2,085 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: 143 of 48,089 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

0% of pairs (221) 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,590	0% (2)	0% (0)
Midday (9 a.m. to 3 p.m.)	18,956	0% (38)	0% (42)
Afternoon rush (3 to 6 p.m.)	6,464	0% (32)	1% (82)
Evening (6 to 10 p.m.)	12,632	1% (70)	1% (81)
Night (10 p.m. to 4 a.m.)	8,447	0% (1)	0% (16)

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

Where this route is slowest

Slowest: CENTRE RIDEAU to KENT / SPARKS, 8.5 km/h actual against 14.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
CENTRE RIDEAU	KENT / SPARKS	1.2 km	14.5 km/h	8.5 km/h	485	41%
KENT / SPARKS	du PORTAGE/AUBRY	1.2 km	12.8 km/h	9.8 km/h	515	33%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	14.1 km/h	12 km/h	521	20%
PARC-O-BUS ALLUMETTIÈRES	VANIER/du PLATEAU	5.1 km	26.8 km/h	13 km/h	430	67%
du PORTAGE/AUBRY	LAURIER/EDDY	470 m	11.6 km/h	13.7 km/h	543	3%
de l'HÔTEL-de-VILLE/LAURIER	CENTRE RIDEAU	2.5 km	12.3 km/h	16.3 km/h	424	0%
SAINT-RAYMOND/LOUISE-CAMPAGNA	du PLATEAU/des CÈDRES	1 km	20 km/h	19.7 km/h	539	4%
VANIER/du PLATEAU	PLATEAU/EUROPE	2.2 km	21.6 km/h	19.9 km/h	509	6%

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 →

6 partial-capture days not counted.

No counted cancellations on this route in the last four weeks. Notices we could not check would be listed below.

Did not come (no bus seen, no notice), last 7 days: 2 of 389 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.

When this route is usually busy	Wísk niwenhniserá:ke	Entákta	Awentatokentì:ke
Before 6 am	Usually seats0% of 27 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats0.4% of 256 trips	Usually seats25.4% of 59 trips	Usually seats10.2% of 49 trips
9 am to 3 pm	Usually seats15.4% of 908 trips	Usually seats24.3% of 218 trips	Usually seats19.8% of 197 trips
3 to 6 pm	Usually seats22.6% of 380 trips	Usually busy50.4% of 127 trips	Usually seats15.4% of 136 trips
6 to 10 pm	Usually seats9.9% of 659 trips	Usually seats31.6% of 152 trips	Usually seats12.9% of 139 trips
After 10 pm	Usually seats3.1% of 358 trips	Usually seats3.8% of 79 trips	Usually seats0% of 63 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.6 min later than the timetable in 1 hours of the day.

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

17:00 has 55% of predictions within five minutes of the timetable, against 83% 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: 81.4% of final predictions within five minutes of the timetable, 719 predictions, typically 2.3 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: 90.3% of final predictions within five minutes of the timetable, 652 predictions, typically 1.4 min late
07:00: 89% of final predictions within five minutes of the timetable, 803 predictions, typically 1.2 min late
08:00: 86.7% of final predictions within five minutes of the timetable, 1,249 predictions, typically 1.8 min late
09:00: 86% of final predictions within five minutes of the timetable, 2,286 predictions, typically 1.5 min late
10:00: 87.2% of final predictions within five minutes of the timetable, 2,363 predictions, typically 1.1 min late
11:00: 85.6% of final predictions within five minutes of the timetable, 2,410 predictions, typically 1.7 min late
12:00: 74.2% of final predictions within five minutes of the timetable, 2,523 predictions, typically 2.2 min late
13:00: 83.5% of final predictions within five minutes of the timetable, 2,624 predictions, typically 2 min late
14:00: 74.9% of final predictions within five minutes of the timetable, 2,421 predictions, typically 2.4 min late
15:00: 65.4% of final predictions within five minutes of the timetable, 2,307 predictions, typically 2.8 min late
16:00: 74.8% of final predictions within five minutes of the timetable, 1,524 predictions, typically 2 min late
17:00: 54.7% of final predictions within five minutes of the timetable, 1,551 predictions, typically 3.6 min late
18:00: 68.8% of final predictions within five minutes of the timetable, 2,373 predictions, typically 2.7 min late
19:00: 82.6% of final predictions within five minutes of the timetable, 2,249 predictions, typically 2.1 min late
20:00: 83.2% of final predictions within five minutes of the timetable, 2,214 predictions, typically 2 min late
21:00: 81.5% of final predictions within five minutes of the timetable, 2,236 predictions, typically 1.3 min late
22:00: 88.3% of final predictions within five minutes of the timetable, 2,317 predictions, typically 1.3 min late
23:00: 90.1% of final predictions within five minutes of the timetable, 2,085 predictions, typically 1.4 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	17:00	3.6 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	17:00	55%	Operations, not the timetable

Measurements

Predictions later than timetable · 17:00: Measured arrivals 1,551; Hours affected 1; Spread 15.2 min; Median delay 3.6 min; Suggested running time change 3.6 min
One hour has a lower prediction match · 17:00: Hour 17:00; Ioiánere tsi nikarì:wes 54.7%; Measured arrivals 1,551; Shortfall 28.5 pts; Route median on time 83.2%

Open history, reliability and route analysis

Route check

How route 34 has been running

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

Bottom line

Provider predictions often differed from the timetable; actual arrivals were not independently measured.

80 in 100 eligible predictions were within 5 minutes of the timetable · 69,224 predictions checked

Prediction sample size: Larger sample

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

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

17–18: 45 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,551 predictions over 12 days).
15–16: 35 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,307 predictions over 12 days).
18–19: 31 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,373 predictions over 11 days).

1 current notice affects this route

• Detour Route 34 South

Prediction differences by stop

PARC-O-BUS ALLUMETTIÈRES
65 in 100 eligible predictions differed from the timetable by more than 5 minutes (580 predictions over 24 days).
Open this stop
du PORTAGE/AUBRY
37 in 100 eligible predictions differed from the timetable by more than 5 minutes (637 predictions over 24 days).
Open this stop
du PORTAGE/LAVAL
32 in 100 eligible predictions differed from the timetable by more than 5 minutes (636 predictions over 24 days).
Open this stop
ALEXANDRE-TACHÉ/SAINTE-THÉRÈSE
31 in 100 eligible predictions differed from the timetable by more than 5 minutes (640 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 389 checked trips need a closer look2 of 389 trips with enough public-feed evidence had no matching position over 7 days. 53 of 442 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 9.4 min (positive means later; negative means earlier)80 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: 62
Distinct scheduled stops: 122
Distinct published paths: 3
Kahiatónhsera: tsi niió:re ne kà:sere: 05:55–00:41 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 38,780 arrivals over 13 days; after has 4,738 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: 79.5%
Eligible predictions checked: 69,224
Weekdays with data: 17
95th-percentile predicted delay: 9.4 min late

Patterns by hour (20)

Patterns by hour (20)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
00:00	81.4%	2.3 min late	10.8 min late	719 · 10 days
05:00	70.0%	0.9 min late	6.1 min late	20 · 7 days
06:00	90.3%	1.4 min late	9.2 min late	652 · 10 days
07:00	89.0%	1.2 min late	7.3 min late	803 · 9 days
08:00	86.7%	1.8 min late	6.3 min late	1,249 · 10 days
09:00	86.0%	1.5 min late	8.5 min late	2,286 · 11 days
10:00	87.2%	1.1 min late	6.6 min late	2,363 · 11 days
11:00	85.6%	1.7 min late	6.7 min late	2,410 · 12 days
12:00	74.2%	2.2 min late	12.9 min late	2,523 · 12 days
13:00	83.5%	2 min late	8.5 min late	2,624 · 12 days
14:00	74.9%	2.4 min late	11 min late	2,421 · 13 days
15:00	65.4%	2.8 min late	12 min late	2,307 · 12 days
16:00	74.8%	2 min late	8.3 min late	1,524 · 13 days
17:00	54.7%	3.6 min late	18.8 min late	1,551 · 12 days
18:00	68.8%	2.7 min late	13.6 min late	2,373 · 11 days
19:00	82.6%	2.1 min late	8 min late	2,249 · 11 days
20:00	83.2%	2 min late	7.7 min late	2,214 · 10 days
21:00	81.5%	1.3 min late	7.8 min late	2,236 · 10 days
22:00	88.3%	1.3 min late	6.1 min late	2,317 · 10 days
23:00	90.1%	1.4 min late	6.3 min late	2,085 · 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

387 / 442 scheduled trips published at least one position across 2 service days (87.6%).

06:004 / 12 trips without a position66.7%
19:008 / 28 trips without a position71.4%
20:008 / 28 trips without a position71.4%
21:008 / 28 trips without a position71.4%
23:006 / 21 trips without a position71.4%
22:007 / 26 trips without a position73.1%

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

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

05:55– 06:55
Trip sto:63295789Insufficient coverage or identity; outcome unknown
06:22– 07:23
Trip sto:63295154Insufficient coverage or identity; outcome unknown
06:53– 07:57
Trip sto:63294858Insufficient coverage or identity; outcome unknown
07:26– 08:33
Trip sto:63294878Insufficient coverage or identity; outcome unknown
07:56– 09:03
Trip sto:63294735Insufficient coverage or identity; outcome unknown
08:26– 09:28
Trip sto:63295448Vehicle position matchedFirst / last feed position: 9:22 a.m. EST / 9:30 a.m. EST; not actual start or end times.
08:40– 09:48
Trip sto:63295699Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 9:47 a.m. EST; not actual start or end times.
08:56– 09:58
Trip sto:63294860Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 9:54 a.m. EST; not actual start or end times.
09:13– 10:16
Trip sto:63294785Vehicle position matchedFirst / last feed position: 9:23 a.m. EST / 10:10 a.m. EST; not actual start or end times.
09:26– 10:26
Trip sto:63290351Vehicle position matchedFirst / last feed position: 9:26 a.m. EST / 11:10 a.m. EST; not actual start or end times.
09:43– 10:46
Trip sto:63294862Vehicle position matchedFirst / last feed position: 9:21 a.m. EST / 10:41 a.m. EST; not actual start or end times.
09:56– 10:56
Trip sto:63294737Vehicle position matchedFirst / last feed position: 10:01 a.m. EST / 11:02 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).