Detour: Route 20 Rideau due to closure of Alfred and lanes on Montfort: October 01 2026 - From 10:00 am on Monday, October 5, until 6:00 pm on Friday, December 4, a closure of Alfred Street and lanes of Montfort Street for the Montfort, Alfred, and Granville Integrated Renewal Project, will require route 20 Rideau to detour. Route 20 Rideau will detour along Montreal and Ste-Anne before continuing on its regular route. Please allow extra time for your travels. Affected stops Bus Stop (560#) not in use · Routes · Alternate Stop #8749 -- Alfred (east-side) / Montreal · · 20 Rideau · #1543 -- Montreal (north-side) / Granville #7046 -- Montfort (north-side) / Alfred · · 20 Rideau · #1543 -- Montreal (north-side) / Granville #8745 -- Montfort (north-side) / Ste-Anne · · 20 Rideau · TEMP -- Ste-Anne (east-side) / Montfort Detour routing 20 Rideau: From Montreal at Alfred, continue on Montreal, turn right onto Ste-Anne, left onto Montfort, continue to regular route. Detour map

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

Previous measure: 65.5% of arrivals were within five minutes of the timetable (89,846 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 20: Rideau ⇄ St-Laurent

Every 29 to 35 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: 8 trips with qualifying later matching vehicle observations. Trips with any notice: 12.

Trips needing investigation

3 of 448 trips with a usable feed window (0.7%) had no matching position.

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

445 with position · 3 to investigate · 0 excluded · 448 scheduled trips

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

Coverage, exclusions and sources

0 of 8 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: 445 / 448 (99.3%). 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, 2:17 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

65.5%

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

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

The hours we have evidence for

0051% · 496 predictions · 11 days
0598% · 1,070 predictions · 10 days
0679% · 1,576 predictions · 12 days
0777% · 2,031 predictions · 12 days
0863% · 2,474 predictions · 14 days
0976% · 2,948 predictions · 14 days
1076% · 2,970 predictions · 14 days
1171% · 2,986 predictions · 14 days
1274% · 2,987 predictions · 14 days
1370% · 2,991 predictions · 14 days
1464% · 2,786 predictions · 14 days
1552% · 2,403 predictions · 14 days
1634% · 2,343 predictions · 14 days
1733% · 2,520 predictions · 14 days
1836% · 2,645 predictions · 14 days
1955% · 3,105 predictions · 14 days
2065% · 2,843 predictions · 14 days
2163% · 2,613 predictions · 14 days
2269% · 2,181 predictions · 14 days
2373% · 1,388 predictions · 14 days

Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.

These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.

Calculated: Nov 4, 2026

2 partial-capture days not counted.

What about time of day?

20 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.

Improvement or decline requires comparable periods. This single result cannot establish a trend.

Explore the dated evidence Source of this result

Buses arriving bunched

Last 28 days, October 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

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

1% of pairs (295) 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,507	0% (0)	0% (0)
Midday (9 a.m. to 3 p.m.)	22,560	0% (64)	0% (60)
Afternoon rush (3 to 6 p.m.)	7,573	7% (504)	2% (173)
Evening (6 to 10 p.m.)	16,856	1% (136)	0% (60)
Night (10 p.m. to 4 a.m.)	2,114	0% (1)	0% (2)

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

Where this route is slowest

Slowest: MONTFORT HOSPITAL to BRITTANY / MONTRÉAL, 9.4 km/h actual against 13.3 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
MONTFORT HOSPITAL	BRITTANY / MONTRÉAL	450 m	13.3 km/h	9.4 km/h	779	35%
RIDEAU B	ST PATRICK / COBOURG	1.7 km	13.3 km/h	11.2 km/h	756	13%
BRITTANY / MONTRÉAL	MONTFORT HOSPITAL	610 m	11 km/h	12.5 km/h	751	4%
MONTRÉAL / GRANVILLE	300 DES PÈRES BLANCS	1.4 km	15.9 km/h	15.2 km/h	741	2%
ST-LAURENT D	MONTFORT HOSPITAL	3.7 km	16.6 km/h	15.8 km/h	776	2%
Stop name not found	300 DES PÈRES BLANCS	1.5 km	16.5 km/h	15.8 km/h	32	3%
300 DES PÈRES BLANCS	BRITTANY / MONTRÉAL	3.5 km	20.1 km/h	16.9 km/h	763	8%
300 DES PÈRES BLANCS	BEECHWOOD / MACKAY	1.6 km	17.5 km/h	17.3 km/h	769	2%

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
Marquette between Beechwood and Des Pères Blancs
Apr 13, 2026, 6:00 a.m. to Nov 30, 2026, 6:00 p.m.
Marquette closed between Beechwood and Des Pères Blancs due to construction, April 13th to December 20th. Access for local traffic maintained.
about 1 m from the route
City record updated Sep 22, 2026, 3:37 p.m..
Oháha: kaio'tén:sera
Longpré between des Pères Blancs and Marier [PC]
May 18, 2026, 7:00 a.m. to Dec 30, 2026, 5:00 p.m.
Longpré closed between des Pères Blancs and Marier due to construction, May 18th to December 30th . Access for local traffic maintained.
about 7 m from the route
City record updated Sep 4, 2026, 9:08 a.m..
Oháha: kaio'tén:sera
Crichton between Beechwood and Vaughan
Oct 6, 2026, 12:00 a.m. to Nov 6, 2026, 5:00 p.m.
Crichton off-peak lane reduction between Beechwood and Vaughan due to construction, from October 6th to November 6th.
The City marks this as affecting transit.
about 0 m from the route
City record updated Oct 13, 2026, 10:44 a.m..
Oháha: kaio'tén:sera
YORK between DALHOUSIE and CUMBERLAND
Oct 30, 2026, 7:00 a.m. to Nov 13, 2026, 5:00 p.m.
YORK closed between DALHOUSIE and CUMBERLAND due to construction, from November 2nd to 13th. Access for local traffic maintained.
about 0 m from the route
City record updated Oct 30, 2026, 6:56 a.m..

A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.

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

Cancellations on this route

What these words mean →

2 partial-capture days not counted.

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

Not counted: 23 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. (3), 5 p.m. (3), 4 p.m. (2)

Latest cancelled trips

Mon, Nov 2, scheduled 15:52
Thu, Oct 29, scheduled 17:01
Wed, Oct 28, scheduled 17:01
Tue, Oct 27, scheduled 20:10
Wed, Oct 21, scheduled 23:10

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

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

Open the dated prediction analysis

Ka' nikarihò:ten

What this route needs

Median provider predictions are 3.1 to 4.6 min later than the timetable in 12 hours of the day.

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

Wide prediction spread 16:00 to 18:00: the 95th percentile is 28.2 min later than the median.

17:00 has 33% of predictions within five minutes of the timetable, against 67% 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: 51% of final predictions within five minutes of the timetable, 496 predictions, typically 4.6 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 98.4% of final predictions within five minutes of the timetable, 1,070 predictions, typically 0.8 min late
06:00: 79.3% of final predictions within five minutes of the timetable, 1,576 predictions, typically 3.5 min late
07:00: 77.1% of final predictions within five minutes of the timetable, 2,031 predictions, typically 2.5 min late
08:00: 62.5% of final predictions within five minutes of the timetable, 2,474 predictions, typically 3.3 min late
09:00: 76.2% of final predictions within five minutes of the timetable, 2,948 predictions, typically 1.9 min late
10:00: 76.3% of final predictions within five minutes of the timetable, 2,970 predictions, typically 2.5 min late
11:00: 70.9% of final predictions within five minutes of the timetable, 2,986 predictions, typically 3.1 min late
12:00: 74.3% of final predictions within five minutes of the timetable, 2,987 predictions, typically 2.2 min late
13:00: 70% of final predictions within five minutes of the timetable, 2,991 predictions, typically 2.6 min late
14:00: 64.4% of final predictions within five minutes of the timetable, 2,786 predictions, typically 3.1 min late
15:00: 52.2% of final predictions within five minutes of the timetable, 2,403 predictions, typically 4.4 min late
16:00: 33.8% of final predictions within five minutes of the timetable, 2,343 predictions, typically 6.9 min late. Provider predictions have a wide spread.
17:00: 33% of final predictions within five minutes of the timetable, 2,520 predictions, typically 7.2 min late. Provider predictions have a wide spread.
18:00: 35.6% of final predictions within five minutes of the timetable, 2,645 predictions, typically 6.4 min late
19:00: 54.7% of final predictions within five minutes of the timetable, 3,105 predictions, typically 4.5 min late
20:00: 65.1% of final predictions within five minutes of the timetable, 2,843 predictions, typically 3.5 min late
21:00: 62.6% of final predictions within five minutes of the timetable, 2,613 predictions, typically 4.2 min late
22:00: 69.2% of final predictions within five minutes of the timetable, 2,181 predictions, typically 2.9 min late
23:00: 73.3% of final predictions within five minutes of the timetable, 1,388 predictions, typically 2.5 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
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	Ó:nen	Tewaterièn:tare	Scenario or next investigation
ProblemPredictions later than timetable	00:00 · 06:00 · 08:00 · 11:00 · 14:00 to 22:00	4.6 min late … 4.4 min late	Recovery time at the terminal
ProblemWide prediction spread	16:00 to 18:00	28.2 min swing	Operations, not the timetable
ProblemOne hour has a lower prediction match	17:00	33%	Operations, not the timetable

Measurements

Predictions later than timetable · 14:00 to 22:00: Measured arrivals 21,258; Hours affected 8; Spread 13.9 min; Median delay 4.4 min; Suggested running time change 4.4 min
Wide prediction spread · 16:00 to 18:00: Measured arrivals 4,863; Hours affected 2; Spread 28.2 min; Median delay 7.1 min; Suggested running time change 7.1 min
Predictions later than timetable · 11:00: Measured arrivals 2,986; Hours affected 1; Spread 6.7 min; Median delay 3.1 min; Suggested running time change 3.1 min
Predictions later than timetable · 08:00: Measured arrivals 2,474; Hours affected 1; Spread 10.7 min; Median delay 3.3 min; Suggested running time change 3.3 min
Predictions later than timetable · 06:00: Measured arrivals 1,576; Hours affected 1; Spread 3 min; Median delay 3.5 min; Suggested running time change 3.5 min
Predictions later than timetable · 00:00: Measured arrivals 496; Hours affected 1; Spread 16.8 min; Median delay 4.6 min; Suggested running time change 4.6 min
One hour has a lower prediction match · 17:00: Hour 17:00; Ioiánere tsi nikarì:wes 33%; Measured arrivals 2,520; Shortfall 34.2 pts; Route median on time 67.2%

Open history, reliability and route analysis

Route check

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

66 in 100 eligible predictions were within 5 minutes of the timetable · 89,846 predictions checked

Prediction sample size: Larger sample

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

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

17–18: 67 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,520 predictions over 14 days).
16–17: 66 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,343 predictions over 14 days).
18–19: 64 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,645 predictions over 14 days).
00–01: 49 in 100 eligible predictions differed from the timetable by more than 5 minutes (496 predictions over 11 days).

1 current notice affects this route

• Detour: Route 20 Rideau due to closure of Alfred and lanes on Montfort

Prediction differences by stop

MONTRÉAL / CUMMINGS
52 in 100 eligible predictions differed from the timetable by more than 5 minutes (887 predictions over 29 days).
Open this stop
ST-LAURENT / BRITTANY
51 in 100 eligible predictions differed from the timetable by more than 5 minutes (888 predictions over 29 days).
Open this stop
BRITTANY / COLEFORD
51 in 100 eligible predictions differed from the timetable by more than 5 minutes (888 predictions over 29 days).
Open this stop
ST-LAURENT / AD. 505
51 in 100 eligible predictions differed from the timetable by more than 5 minutes (888 predictions over 29 days).
Open this stop

These are route-specific provider predictions compared with the timetable. They identify repeated prediction differences at a place and time, not measured arrivals or their cause.

Check every trip and date

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

What riders want to know

Is any trip cancelled right now?: 0 of 8Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 3 of 448 checked trips need a closer look3 of 448 trips with enough public-feed evidence had no matching position over 7 days. 0 of 448 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 14.3 min (positive means later; negative means earlier)66 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: 67
Distinct scheduled stops: 100
Distinct published paths: 2
Kahiatónhsera: tsi niió:re ne kà:sere: 05:10–00:22 next day

Operator calendar-date records: 0 added · 2 removed

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

New schedule

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

Schedule trips: 67
Distinct scheduled stops: 100
Distinct published paths: 2
Kahiatónhsera: tsi niió:re ne kà:sere: 05:10–00:22 next day

Operator calendar-date records: 0 added · 2 removed

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

Did service improve after the change?

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

Still collecting: before has 46,768 arrivals over 14 days; after has 16,721 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: 65.5%
Eligible predictions checked: 89,846
Weekdays with data: 19
95th-percentile predicted delay: 14.3 min late

Patterns by hour (20)

Patterns by hour (20)
Hour	Ioiánere tsi nikarì:wes	Median	95th percentile	Tsi tó:kenske
00:00	51.0%	4.6 min late	21.4 min late	496 · 11 days
05:00	98.4%	0.8 min late	4.5 min late	1,070 · 10 days
06:00	79.3%	3.5 min late	6.5 min late	1,576 · 12 days
07:00	77.1%	2.5 min late	9.6 min late	2,031 · 12 days
08:00	62.5%	3.3 min late	14 min late	2,474 · 14 days
09:00	76.2%	1.9 min late	12.3 min late	2,948 · 14 days
10:00	76.3%	2.5 min late	9.8 min late	2,970 · 14 days
11:00	70.9%	3.1 min late	9.8 min late	2,986 · 14 days
12:00	74.3%	2.2 min late	10.4 min late	2,987 · 14 days
13:00	70.0%	2.6 min late	11.2 min late	2,991 · 14 days
14:00	64.4%	3.1 min late	11.8 min late	2,786 · 14 days
15:00	52.2%	4.4 min late	20.9 min late	2,403 · 14 days
16:00	33.8%	6.9 min late	32 min late	2,343 · 14 days
17:00	33.0%	7.2 min late	38.6 min late	2,520 · 14 days
18:00	35.6%	6.4 min late	23.6 min late	2,645 · 14 days
19:00	54.7%	4.5 min late	15.8 min late	3,105 · 14 days
20:00	65.1%	3.5 min late	11.4 min late	2,843 · 14 days
21:00	62.6%	4.2 min late	11.8 min late	2,613 · 14 days
22:00	69.2%	2.9 min late	11.7 min late	2,181 · 14 days
23:00	73.3%	2.5 min late	21.6 min late	1,388 · 14 days

11 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

445 / 448 scheduled trips published at least one position across 1 service days (99.3%).

06:001 / 21 trips without a position95.2%
15:001 / 23 trips without a position95.7%
17:001 / 28 trips without a position96.4%
05:000 / 10 trips without a position100.0%
07:000 / 21 trips without a position100.0%
08:000 / 25 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 · 67 trips in the retained timetable · retained notices; capture coverage unverified

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

05:10– 05:45
Trip 9093030Vehicle position matchedFirst / last feed position: 4:53 a.m. EST / 6:14 a.m. EST; not actual start or end times.
05:20– 05:58
Trip 9678030Vehicle position matchedFirst / last feed position: 5:11 a.m. EST / 5:56 a.m. EST; not actual start or end times.
06:08– 06:49
Trip 31020030Vehicle position matchedFirst / last feed position: 5:57 a.m. EST / 6:57 a.m. EST; not actual start or end times.
06:20– 06:58
Trip 32243030Vehicle position matchedFirst / last feed position: 6:09 a.m. EST / 6:55 a.m. EST; not actual start or end times.
06:40– 07:27
Trip 4697030Vehicle position matchedFirst / last feed position: 6:14 a.m. EST / 7:35 a.m. EST; not actual start or end times.
06:50– 07:36
Trip 33635030Vehicle position matchedFirst / last feed position: 6:39 a.m. EST / 7:34 a.m. EST; not actual start or end times.
07:10– 07:58
Trip 32555030Vehicle position matchedFirst / last feed position: 6:56 a.m. EST / 8:04 a.m. EST; not actual start or end times.
07:20– 08:09
Trip 28588030Vehicle position matchedFirst / last feed position: 7:08 a.m. EST / 8:11 a.m. EST; not actual start or end times.
07:45– 08:33
Trip 7417030Vehicle position matchedFirst / last feed position: 7:32 a.m. EST / 8:37 a.m. EST; not actual start or end times.
07:50– 08:41
Trip 7103030Vehicle position matchedFirst / last feed position: 7:45 a.m. EST / 8:51 a.m. EST; not actual start or end times.
08:18– 09:06
Trip 15044030Vehicle position matchedFirst / last feed position: 8:12 a.m. EST / 9:16 a.m. EST; not actual start or end times.
08:20– 09:11
Trip 5895030Vehicle position matchedFirst / last feed position: 8:05 a.m. EST / 9:05 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).