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

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

STO ᐊᖁᑎᖓ 79: Bellevue

ᑐᕌᖓᔪᖅLabrosse1 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

STATION LORRAIN0 min sched.
LORRAIN/SAINT-RENÉ EST1 min sched.
LORRAIN/VINCENT-LEGRIS EST1 min sched.
LORRAIN/MARLENE-GOYET2 min sched.
LORRAIN/AUGUSTE-RENOIR3 min sched.
LORRAIN/des FLEURS3 min sched.
LORRAIN/des POMMETIERS6 min sched.
LORRAIN/JEAN-MARC6 min sched.
LORRAIN/CROTEAU7 min sched.
LORRAIN/THÉRÈSE8 min sched.
de CHAMBORD/de ROBERVAL9 min sched.
de SAINTE-MONIQUE/DE CHAMBORD10 min sched.
SAINT-THOMAS/de SAINTE-MONIQUE11 min sched.
SAINT-THOMAS/d'ARVIDA11 min sched.
SAINT-THOMAS/d'ALMA12 min sched.
SAINT-THOMAS/ELZÉAR13 min sched.
ELZÉAR/IRÈNE14 min sched.
ELZÉAR/de CHAMBORD15 min sched.
des AFFAIRES/LABROSSE17 min sched.
des AFFAIRES/des ENTREPRISES19 min sched.
des AFFAIRES/LABROSSE20 min sched.
LABROSSE/DAVIDSON22 min sched.
LABROSSE/A.-GIBEAULT22 min sched.
LABROSSE/DOCTEUR J.-COUSINEAU23 min sched.
LABROSSE/de CANDIAC24 min sched.
LABROSSE/MARQUETTE25 min sched.
LABROSSE/SAINT-RENÉ EST25 min sched.
Terminus Labrosse26 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

—

No retained notice returned; this does not prove zero cancellations.

Trips needing investigation

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

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

67 with position · 2 to investigate · 16 excluded · 85 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 67 / 85 (78.8%). 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:09 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

95.7%

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

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

The hours we have evidence for

05100% · 145 predictions · 7 days
0699% · 138 predictions · 7 days
0793% · 228 predictions · 6 days
0898% · 354 predictions · 7 days
1295% · 271 predictions · 9 days
1397% · 204 predictions · 8 days
1490% · 30 predictions · 5 days
1595% · 392 predictions · 9 days
1694% · 319 predictions · 9 days
1794% · 314 predictions · 9 days
1896% · 262 predictions · 8 days
1996% · 158 predictions · 8 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?

12 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

No bunched buses were measured on this route in the last 28 days (1,449 pairs checked at stops).

0% of pairs (0) had a long gap: more than 1.75 times the planned wait between them.

Buses arriving bunched
ᐅᓪᓗᒥ ᐃᑲᕐᕋᖅ	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	477	0% (0)	0% (0)
Midday (9 a.m. to 3 p.m.)	46	0% (0)	0% (0)
Afternoon rush (3 to 6 p.m.)	926	0% (0)	0% (0)

ᖃᓄᖅ ᐅᒃᑐᖅᑕᐅᒻᒪᖔᑦ →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: STATION LORRAIN to LORRAIN/des FLEURS, 7.5 km/h actual against 19.8 km/h planned.

Where this route is slowest
ᐱᒋᐊᕐᕕᒃ	ᑐᕌᕐᕕᒃ	ᐅᖓᓯᒋᓂᖓ	Planned speed	Actual speed	Trips measured	Slow trips
STATION LORRAIN	LORRAIN/des FLEURS	1.2 km	19.8 km/h	7.5 km/h	124	72%
Quai local LABROSSE #6	des AFFAIRES/des ENTREPRISES	3.4 km	24.3 km/h	12.4 km/h	58	69%
LORRAIN/SAINT-RENÉ EST	STATION LORRAIN arrêt d'arrivée	400 m	13 km/h	13.3 km/h	55	2%
des AFFAIRES/des ENTREPRISES	Terminus Labrosse	3.4 km	23.3 km/h	23.5 km/h	109	1%
LORRAIN/THÉRÈSE	des AFFAIRES/des ENTREPRISES	4.8 km	24.5 km/h	25.8 km/h	123	0%
des AFFAIRES/des ENTREPRISES	LORRAIN/SAINT-RENÉ EST	8 km	25.9 km/h	27.3 km/h	56	0%
LORRAIN/des FLEURS	LORRAIN/THÉRÈSE	2.4 km	31.6 km/h	34 km/h	126	1%

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

ᖃᓄᖅ ᐅᒃᑐᖅᑕᐅᒻᒪᖔᑦ →

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 69 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	ᐱᓇᓱᐊᕈᓰᑦ	ᓈᑦᓰᓈᕐᕕᒃᑯᑦ	ᓈᑦᑏᖑᔭᕐᓂ
Before 6 am	Usually seats0% of 32 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats0% of 188 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats0.7% of 146 trips	Not enough readings	Not enough readings
3 to 6 pm	Usually seats3.2% of 216 trips	Not enough readings	Not enough readings
6 to 10 pm	Usually seats1.7% of 58 trips	Not enough readings	Not enough readings
After 10 pm	Not enough readings	Not enough readings	Not enough readings

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

ᐃᓱᓕᑦᑎᓂᖅ

What this route needs

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

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 12 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: 100% of final predictions within five minutes of the timetable, 145 predictions, typically 0.2 min late
06:00: 98.6% of final predictions within five minutes of the timetable, 138 predictions, typically 1.4 min late
07:00: 93.4% of final predictions within five minutes of the timetable, 228 predictions, typically 3 min late
08:00: 97.7% of final predictions within five minutes of the timetable, 354 predictions, typically 1 min late
09:00: not enough data
10:00: not enough data
11:00: not enough data
12:00: 95.2% of final predictions within five minutes of the timetable, 271 predictions, typically 0.2 min late
13:00: 96.6% of final predictions within five minutes of the timetable, 204 predictions, typically 0.5 min late
14:00: 90% of final predictions within five minutes of the timetable, 30 predictions, typically 0.3 min early
15:00: 94.6% of final predictions within five minutes of the timetable, 392 predictions, typically 0.1 min early
16:00: 93.7% of final predictions within five minutes of the timetable, 319 predictions, typically 0.5 min late
17:00: 94.3% of final predictions within five minutes of the timetable, 314 predictions, typically 0.2 min early
18:00: 95.8% of final predictions within five minutes of the timetable, 262 predictions, typically 0.9 min late
19:00: 95.6% of final predictions within five minutes of the timetable, 158 predictions, typically 1.4 min late
20:00: not enough data
21:00: not enough data
22:00: not enough data
23:00: not enough data

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	ᖃᖓ	ᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅ	Scenario or next investigation
StrengthPredictions consistently close to timetable	05:00, 06:00, 07:00, 08:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00	95%	Keep what works

Measurements

Predictions consistently close to timetable · 05:00, 06:00, 07:00, 08:00, 12:00, 13:00, 14:00, 15:00, 16:00, 17:00, 18:00, 19:00: Measured arrivals 2,815; Hours measured 12; Worst hour on time 90%; Median hour on time 95.4%

Open history, reliability and route analysis

Route check

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

96 in 100 eligible predictions were within 5 minutes of the timetable · 5,765 predictions checked

Prediction sample size: Larger sample

Based on 5,765 eligible provider predictions over 17 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.

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

No current official notice matches this route.

Prediction differences by stop

STATION LORRAIN
46 in 100 eligible predictions differed from the timetable by more than 5 minutes (145 predictions over 18 days).
Open this stop
Quai local LABROSSE #6
46 in 100 eligible predictions differed from the timetable by more than 5 minutes (76 predictions over 15 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 6Checks 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 69 checked trips need a closer look2 of 69 trips with enough public-feed evidence had no matching position over 7 days. 16 of 85 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 4.5 min (positive means later; negative means earlier)96 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.

ᐊᐅᓪᓚᖅᑕᕐᕕᐅᓂᖏᑦ ᐊᓯᔾᔨᕐᓂᖏᓐᓂᒃ ᕿᒥᕐᕈᓂᖅ

ᓴᖅᑭᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᖏᑦ ᐅᓪᓗᖏᑦ: ᓯᕗᓂᐊᓂ ᑭᖑᓂᐊᓂᓗ

ᐅᓇ ᒫᓐᓇ ᐊᐅᓚᓂᕐᒧᑦ ᐸᕐᓇᐅᑎ ᓇᓪᓕᐅᓇᐃᓪᓗᒍ ᓯᕗᓪᓕᐅᔪᒧᑦ ᐸᕐᓇᐅᑎᒧᑦ. ᐸᕐᓇᐅᑎᒥ ᐊᓯᔾᔨᕐᓂᑦ ᐸᕐᓇᓯᒪᔪᓂᒃ ᓇᓗᓇᐃᖅᓯᔪᑦ. ᐃᖏᕐᕋᓂᖅ ᐊᐅᓚᓚᐅᕐᓂᖓᓂᒃ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ.

Current published schedule began November 2, 2026

ᐅᓪᓗᖅ ᓂᕈᐊᖅᑕᐅᓯᒪᔪᖅ ᐊᑐᓂ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐅᓪᓗᓂ ᐃᑲᕐᕋᓂᓪᓗ ᓴᖅᑭᑕᐅᓯᒪᔪᓂᑦ

ᑕᑯᓐᓇᕈᑦᑕᖅᐳᒍᑦ ᓯᕗᓪᓕᖅᐹᖅ ᓇᒡᒐᔾᔭᐅ ᓄᑖᑦ ᐊᐅᓚᓂᕐᒧᑦ ᐸᕐᓇᐅᑎᑦ ᐱᒋᐊᓚᐅᖅᑎᓪᓗᒋᑦ. ᐊᒻᒪ ᓇᒡᒐᔾᔭᐅ ᐱᓇᓱᐊᕈᓯᕐᒥᒃ ᓯᕗᓂᐊᒍᑦ. ᓈᓴᐅᑎᑦ ᑕᒪᕐᒥᒃ ᐱᔭᐅᔪᑦ ᐱᑕᖃᕐᓂᐊᖅᑐᓂᑦ ᒐᕙᒪᐅᑉ GTFS ᑐᓴᒐᒃᓴᖏᓐᓂᑦ. ᐊᑎᖏᑦ ᐊᑖᓂ ᐃᓗᓕᖃᖅᑐᑦ.

ᐅᓪᓗᑦ ᓂᕈᐊᖅᓯᒪᔭᑎᑦ ᐊᑕᐅᓯᖅ ᐅᖓᑖᓄᓪᓗ ᐊᐅᓚᓂᖓ ᐊᓯᔾᔨᖅᑕᐅᓯᒪᔪᖅ. ᐅᓇ ᖁᕕᐊᓱᐊᕐᕕᐅᓂᖓᓄᑦ ᐅᕝᕙᓘᓐᓃᑦ ᐊᔾᔨᐅᙱᑦᑐᒥᒃ ᐊᐅᓚᓂᖃᕐᓂᖓᓄᑦ ᐱᔾᔪᑎᖃᖅᑐᖅ. ᐱᓇᓱᐊᕐᕕᐅᔪᓂ ᐅᓪᓗᓂ ᐊᐅᓚᓂᖓ ᐅᒃᓱᓂᖓᓂᒃ ᑐᑭᖃᙱᑦᑐᖅ.

ᓯᕗᓂᐊᓂ

ᐱᔨᑦᑎᕋᐅᑎᐅᑉ ᐅᓪᓗᖓ ᕿᒥᕐᕈᐊᖅᑕᐅᔪᖅ: October 26, 2026

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 0
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 0
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 0
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: —–—

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

ᓄᑖᖅ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐸᕐᓇᐅᑎ

ᐱᔨᑦᑎᕋᐅᑎᐅᑉ ᐅᓪᓗᖓ ᕿᒥᕐᕈᐊᖅᑕᐅᔪᖅ: November 2, 2026

ᐸᕐᓇᒃᑕᐅᓯᒪᔪᑦ ᐃᖏᕐᕋᓂᐅᔪᑦ: 17
ᐊᔾᔨᒌᙱᑦᑐᑦ ᓄᖃᖅᑕᕝᕕᑦ ᐸᕐᓇᐅᑎᒥ: 56
ᐊᔾᔨᒌᙱᑦᑐᑦ ᐊᖁᑎᑦ ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 3
ᐱᔨᑦᑎᕋᖅᑐᑦ ᐃᑲᕐᕋᖏᑦ, ᓴᖅᑭᑕᐅᓯᒪᔪᑦ: 05:38–19:22

Operator calendar-date records: 1 added · 0 removed

ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᓯᒋᐊᕈᑎᖓ: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

ᐱᔨᑦᑎᕋᐅᑎᑦ ᐱᐅᓯᕚᓕᓚᐅᖅᐸᑦ ᐊᓯᔾᔨᕐᓂᐅᑉ ᑭᖑᓂᐊᒍᑦ?

ᑎᑭᓐᓂᖏᑦ ᓇᓗᓇᐃᖅᓯᒪᔪᑦ ᐊᔾᔨᒌᙱᓐᓂᖏᑦ ᖃᐅᔨᓴᕐᓂᐊᖅᐸᕗᑦ. 14 ᐅᓪᓗᓂ ᐊᓯᔾᔨᕐᓂᖓᑕ ᓯᕗᓂᖓᓂ ᑭᖑᓂᖓᓂᓗ. ᓴᖅᑭᑎᑦᑎᓂᐊᖅᐳᒍᑦ ᒪᕐᕉᒃ ᐱᑕᖃᓕᕋᐃᒐᒃ ᐱᔨᑦᑎᕐᕕᐅᔪᓂᒃ ᐅᓪᓗᓂᒃ 7 ᐅᖓᑖᓄᓪᓗ, ᑎᑭᓐᓂᕐᓂᓪᓗ 200 ᐅᖓᑖᓄᓪᓗ.

Still collecting: before has 3,117 arrivals over 10 days; after has 453 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: 95.7%
Eligible predictions checked: 5,765
Weekdays with data: 17
95th-percentile predicted delay: 4.5 min late

Patterns by hour (13)

Patterns by hour (13)
ᐃᑲᕐᕋᖅ	ᐱᕕᒃᓴᖓᓂ	Median	95th percentile	ᓇᓗᓇᐃᖅᓯᔾᔪᑎᑦ
05:00	100.0%	0.2 min late	1.3 min late	145 · 7 days
06:00	98.6%	1.4 min late	3.6 min late	138 · 7 days
07:00	93.4%	3 min late	4.8 min late	228 · 6 days
08:00	97.7%	1 min late	4.4 min late	354 · 7 days
09:00	100.0%	0.5 min late	2.6 min late	28 · 6 days
12:00	95.2%	0.2 min late	4.8 min late	271 · 9 days
13:00	96.6%	0.5 min late	4.6 min late	204 · 8 days
14:00	90.0%	0.3 min early	0.7 min late	30 · 5 days
15:00	94.6%	0.1 min early	4.7 min late	392 · 9 days
16:00	93.7%	0.5 min late	3.8 min late	319 · 9 days
17:00	94.3%	0.2 min early	5.1 min late	314 · 9 days
18:00	95.8%	0.9 min late	4.2 min late	262 · 8 days
19:00	95.6%	1.4 min late	4.8 min late	158 · 8 days

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

Scheduled bus, but not observed in realtime

67 / 85 scheduled trips published at least one position across 5 service days (78.8%).

06:002 / 5 trips without a position60.0%
07:004 / 10 trips without a position60.0%
08:003 / 10 trips without a position70.0%
05:001 / 5 trips without a position80.0%
12:002 / 10 trips without a position80.0%
14:001 / 5 trips without a position80.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 · 17 trips in the retained timetable · retained notices; capture coverage unverified

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

05:38– 06:05
Trip sto:63296824Insufficient coverage or identity; outcome unknown
06:38– 07:06
Trip sto:63296826Insufficient coverage or identity; outcome unknown
07:09– 07:40
Trip sto:63296827Insufficient coverage or identity; outcome unknown
07:42– 08:13
Trip sto:63296823Insufficient coverage or identity; outcome unknown
08:08– 08:36
Trip sto:63296825Insufficient coverage or identity; outcome unknown
08:38– 09:05
Trip sto:63296828Insufficient coverage or identity; outcome unknown
12:10– 12:17
Trip sto:63296814Vehicle position matchedFirst / last feed position: 12:12 p.m. EST / 12:17 p.m. EST; not actual start or end times.
12:24– 12:50
Trip sto:63296817Vehicle position matchedFirst / last feed position: 12:19 p.m. EST / 12:47 p.m. EST; not actual start or end times.
13:24– 13:50
Trip sto:63296818Vehicle position matchedFirst / last feed position: 1:36 p.m. EST / 1:36 p.m. EST; not actual start or end times.
14:54– 15:25
Trip sto:63296815Vehicle position matchedFirst / last feed position: 2:52 p.m. EST / 3:21 p.m. EST; not actual start or end times.
15:24– 15:55
Trip sto:63296816Vehicle position matchedFirst / last feed position: 3:16 p.m. EST / 3:51 p.m. EST; not actual start or end times.
15:56– 16:27
Trip sto:63296819Vehicle position matchedFirst / last feed position: 3:52 p.m. EST / 4:25 p.m. EST; not actual start or end times.

· Open all evidence for this day

ᑐᕌᕝᑦ

ᑖᓐᓇ ᐅᖃᐅᓯᒧᑦ ᐊᓯᔾᔨᖅᓯᒪᔪᖅ ᑐᕌᕝᑦᐅᕗᖅ.

Help improve it

About 48% of this site is translated so far. The rest is shown in English.

Read this page in English

This translation is a draft.

This page is a machine draft in Inuktitut (ᐃᓄᒃᑎᑐᑦ), the language of the Inuit. 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 inuktitut (ᐃᓄᒃᑎᑐᑦ), la langue des Inuits. 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).