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

No 33 trips cancelled now · 5 did not run in NovemberCancellations →

Previous measure: 79.5% of arrivals were within five minutes of the timetable (59,796 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 33: Freeman/G-Roy/Ottawa

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

CENTRE RIDEAU51 min sched.
ALBERT/METCALFE53 min sched.
ALBERT/BANK54 min sched.
KENT / SPARKS55 min sched.
WELLINGTON/LYON56 min sched.
du PORTAGE/AUBRY62 min sched.
du PORTAGE/LAVAL0 min sched.
EDDY/WELLINGTON1 min sched.
EDDY/WRIGHT2 min sched.
EDDY/FRONTENAC2 min sched.
EDDY/PAPINEAU3 min sched.
des ALLUMETTIÈRES/SAINT-RÉDEMPTEUR4 min sched.
SAINT-RÉDEMPTEUR/SAINT-ÉTIENNE5 min sched.
SAINT-RÉDEMPTEUR/SACRÉ-CŒUR6 min sched.
SAINT-RÉDEMPTEUR/ADÉLARD-BEAUCHAMP7 min sched.
MONTCLAIR/DUCHARME10 min sched.
SAINT-JOSEPH/SAINTE-MARIE11 min sched.
GAMELIN/SAINT-JOSEPH11 min sched.
GAMELIN/JOFFRE12 min sched.
GAMELIN/RICHELIEU12 min sched.
GAMELIN/MOUSSETTE13 min sched.
LIONEL-ÉMOND/GAMELIN14 min sched.
SAINT-RAYMOND/LIONEL-ÉMOND15 min sched.
de la CITÉ-DES-JEUNES/SAINT-RAYMOND16 min sched.
de la CITÉ-DES-JEUNES/BÉDARD17 min sched.
de la CITÉ-DES-JEUNES18 min sched.
de la CITÉ-DES-JEUNES/THÉRIEN19 min sched.
de la CITÉ-DES-JEUNES/PERRAS20 min sched.
de la CITÉ-DES-JEUNES/PERRAS21 min sched.
CEGEP GABRIELLE-ROY22 min sched.
de la CITÉ-DES-JEUNES/du MONT-BLEU22 min sched.
de la CITÉ-DES-JEUNES/TALBOT23 min sched.
de la CITÉ-DES-JEUNES/RIEL24 min sched.
de la CITÉ-DES-JEUNES/de l'AVIRON24 min sched.
de la CITÉ-DES-JEUNES/de l'AVIRON25 min sched.
de la CITÉ-DES-JEUNES/du PLEIN-AIR26 min sched.
des HAUTES-PLAINES/de la CITÉ-DES-JEUNES26 min sched.
des HAUTES-PLAINES/du TERROIR28 min sched.
des HAUTES-PLAINES/de la FALAISE28 min sched.
des HAUTES-PLAINES/de la FONDRIÈRE29 min sched.
des HAUTES-PLAINES/du VAL-PERCHÉ29 min sched.
des HAUTES-PLAINES/du PARCOURS30 min sched.
des HAUTES-PLAINES/FREEMAN31 min sched.
des HAUTES-PLAINES/FREEMAN31 min sched.
FREEMAN/ALPHONSE-LUSIGNAN32 min sched.
FREEMAN/du DÔME33 min sched.
FREEMAN/du TALUS33 min sched.
TERMINUS Parc-o-bus FREEMAN40 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: 3.

Trips needing investigation

6 of 411 trips with a usable feed window (1.5%) had no matching position.

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

405 with position · 6 to investigate · 76 excluded · 487 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 405 / 487 (83.2%). 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, 10:47 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: 59,796
Weekdays with evidence: 17
Evidence window: Oct 6, 2026 – Nov 3, 2026

The hours we have evidence for

12 a.m.89% · 609 predictions · 10 days
1 a.m.100% · 248 predictions · 9 days
5 a.m.95% · 83 predictions · 6 days
6 a.m.94% · 1,428 predictions · 8 days
7 a.m.93% · 2,042 predictions · 10 days
8 a.m.87% · 2,585 predictions · 11 days
9 a.m.91% · 1,711 predictions · 12 days
10 a.m.90% · 1,528 predictions · 12 days
11 a.m.89% · 2,215 predictions · 13 days
12 p.m.82% · 2,553 predictions · 12 days
1 p.m.80% · 1,928 predictions · 12 days
2 p.m.84% · 1,856 predictions · 13 days
3 p.m.71% · 2,394 predictions · 12 days
4 p.m.60% · 2,131 predictions · 13 days
5 p.m.64% · 1,915 predictions · 12 days
6 p.m.84% · 2,049 predictions · 11 days
7 p.m.90% · 1,204 predictions · 11 days
8 p.m.87% · 1,074 predictions · 10 days
9 p.m.88% · 806 predictions · 10 days
10 p.m.90% · 911 predictions · 10 days
11 p.m.90% · 910 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 5, 2026

6 partial-capture days not counted.

What about time of day?

21 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

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

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

Buses arriving bunched
Time of day	Pairs checked	Bunched	Long gap
Morning rush (6 to 9 a.m.)	7,421	1% (98)	0% (23)
Midday (9 a.m. to 3 p.m.)	13,380	0% (54)	0% (46)
Afternoon rush (3 to 6 p.m.)	8,356	2% (132)	3% (267)
Evening (6 to 10 p.m.)	2,728	3% (75)	2% (41)

How this is measured →How we got this numberBunching and slow spots on every route →

Where this route is slowest

Slowest: CENTRE RIDEAU to EDDY/WELLINGTON, 9.3 km/h actual against 11.8 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
CENTRE RIDEAU	EDDY/WELLINGTON	2.8 km	11.8 km/h	9.3 km/h	514	20%
CEGEP GABRIELLE-ROY	de la CITÉ-DES-JEUNES/PERRAS	370 m	16.3 km/h	11.2 km/h	572	46%
EDDY/WELLINGTON	SAINT-RÉDEMPTEUR/SAINT-ÉTIENNE	910 m	13.2 km/h	11.6 km/h	575	11%
SAINT-RÉDEMPTEUR/MARIE-LE FRANC	de l'HÔTEL-de-VILLE/LAURIER	1.7 km	12.8 km/h	11.8 km/h	555	4%
de la CITÉ-DES-JEUNES/BÉDARD	LIONEL-ÉMOND/SAINT-RAYMOND	560 m	9.4 km/h	11.9 km/h	568	1%
LIONEL-ÉMOND/GAMELIN	de la CITÉ-DES-JEUNES/BÉDARD	740 m	12.9 km/h	13.8 km/h	588	2%
TERMINUS FREEMAN	CEGEP GABRIELLE-ROY	5 km	23.1 km/h	14.5 km/h	497	39%
de l'HÔTEL-de-VILLE/LAURIER	CENTRE RIDEAU	2.5 km	12 km/h	15.2 km/h	508	0%

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

How this is measured →

City road work near this route

Road work and event road closures the City of Ottawa has published, measured as near this route’s path. Near is not proof that the bus is detoured: check the operator’s own alerts for that.

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.

3 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: 2 p.m. (1), 3 p.m. (1), 4 p.m. (1)

Latest cancelled trips

Tue, Nov 3, scheduled 16:52
Fri, Oct 30, scheduled 15:33
Fri, Oct 30, scheduled 14:25

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: 5 of 411 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	Weekdays	Saturdays	Sundays
Before 6 am	Usually seats0% of 29 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats15.8% of 685 trips	Usually seats0% of 30 trips	Usually seats0% of 26 trips
9 am to 3 pm	Usually seats3.2% of 1,094 trips	Usually seats7.8% of 90 trips	Usually seats3.3% of 90 trips
3 to 6 pm	Usually seats20.7% of 702 trips	Usually seats27.3% of 55 trips	Usually seats9.4% of 53 trips
6 to 10 pm	Usually seats3.5% of 460 trips	Usually seats4.1% of 73 trips	Usually seats0% of 64 trips
After 10 pm	Usually seats0% of 192 trips	Usually seats0% of 55 trips	Usually seats0% of 40 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

Verdict

What this route needs

Median provider predictions are 3.5 min later than the timetable in 2 hours of the day.

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

16:00 has 60% of predictions within five minutes of the timetable, against 89% 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, 21 hours with samples

00:00: 88.8% of final predictions within five minutes of the timetable, 609 predictions, typically 1.5 min late
01:00: 100% of final predictions within five minutes of the timetable, 248 predictions, typically 0.1 min late
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 95.2% of final predictions within five minutes of the timetable, 83 predictions, typically 2.6 min late
06:00: 94.3% of final predictions within five minutes of the timetable, 1,428 predictions, typically 1.3 min late
07:00: 93.2% of final predictions within five minutes of the timetable, 2,042 predictions, typically 1 min late
08:00: 86.5% of final predictions within five minutes of the timetable, 2,585 predictions, typically 1.5 min late
09:00: 90.8% of final predictions within five minutes of the timetable, 1,711 predictions, typically 0.6 min late
10:00: 89.9% of final predictions within five minutes of the timetable, 1,528 predictions, typically 1.6 min late
11:00: 89% of final predictions within five minutes of the timetable, 2,215 predictions, typically 1.8 min late
12:00: 82.4% of final predictions within five minutes of the timetable, 2,553 predictions, typically 2.5 min late
13:00: 80.2% of final predictions within five minutes of the timetable, 1,928 predictions, typically 2.5 min late
14:00: 83.8% of final predictions within five minutes of the timetable, 1,856 predictions, typically 2 min late
15:00: 70.7% of final predictions within five minutes of the timetable, 2,394 predictions, typically 2.9 min late
16:00: 59.8% of final predictions within five minutes of the timetable, 2,131 predictions, typically 3.5 min late
17:00: 63.6% of final predictions within five minutes of the timetable, 1,915 predictions, typically 3.6 min late
18:00: 83.5% of final predictions within five minutes of the timetable, 2,049 predictions, typically 1.9 min late
19:00: 90.2% of final predictions within five minutes of the timetable, 1,204 predictions, typically 1 min late
20:00: 87.4% of final predictions within five minutes of the timetable, 1,074 predictions, typically 1.4 min late
21:00: 87.5% of final predictions within five minutes of the timetable, 806 predictions, typically 1.8 min late
22:00: 89.8% of final predictions within five minutes of the timetable, 911 predictions, typically 1.9 min late
23:00: 89.8% of final predictions within five minutes of the timetable, 910 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	When	Measured	Scenario or next investigation
ProblemPredictions later than timetable	16:00 to 18:00	3.5 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	16:00	60%	Operations, not the timetable

Measurements

Predictions later than timetable · 16:00 to 18:00: Measured arrivals 4,046; Hours affected 2; Spread 13.2 min; Median delay 3.5 min; Suggested running time change 3.5 min
One hour has a lower prediction match · 16:00: Hour 16:00; On time 59.8%; Measured arrivals 2,131; Shortfall 29 pts; Route median on time 88.8%

Open history, reliability and route analysis

Route check

How route 33 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 · 59,796 predictions checked

Prediction sample size: Larger sample

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

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

4 p.m.–5 p.m.: 40 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,131 predictions over 13 days).
5 p.m.–6 p.m.: 36 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,915 predictions over 12 days).

1 current notice affects this route

• Detour Route 33 South

Prediction differences by stop

TERMINUS FREEMAN
40 in 100 eligible predictions differed from the timetable by more than 5 minutes (614 predictions over 24 days).
Open this stop
des ALLUMETTIÈRES/SAINT-RÉDEMPTEUR
38 in 100 eligible predictions differed from the timetable by more than 5 minutes (692 predictions over 24 days).
Open this stop
GAMELIN/JOFFRE
38 in 100 eligible predictions differed from the timetable by more than 5 minutes (689 predictions over 24 days).
Open this stop
SAINT-RÉDEMPTEUR/SAINT-ÉTIENNE
37 in 100 eligible predictions differed from the timetable by more than 5 minutes (690 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 1Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 6 of 411 checked trips need a closer look6 of 411 trips with enough public-feed evidence had no matching position over 7 days. 76 of 487 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 11.3 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?: Average predicted extra wait was under 30 seconds at the sampled stop0.5 min beyond the scheduled wait, based on 155 eligible predictions at 5 high-frequency stops over 8 days.

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 the first Monday after the new schedule began and the Monday one week earlier. Every figure comes from the retained 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.

Before

Service date checked: October 26, 2026

Scheduled trips: 0
Distinct scheduled stops: 0
Distinct published paths: 0
Published service span: —–—

Feed fingerprint: 7692f9a7012f44e6 · 68840ddf-afaa-4cf4-9656-22afc030f92f

New schedule

Service date checked: November 2, 2026

Scheduled trips: 83
Distinct scheduled stops: 97
Distinct published paths: 2
Published service span: 5:50 a.m.–1:26 a.m. next day

Operator calendar-date records: 1 added · 0 removed

Feed fingerprint: 540f8e4e98d50320 · 7a8023af-fdc6-4276-bed6-2e3d7bd7bb74

Did service improve after the change?

We will compare settled arrivals for the 14 days before and after the change. We publish the comparison only after both sides have at least 7 service days and 200 arrivals.

Still collecting: before has 33,011 arrivals over 13 days; after has 4,619 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: 59,796
Weekdays with data: 17
95th-percentile predicted delay: 11.3 min late

Patterns by hour (21)

Patterns by hour (21)
Hour	On time	Median	95th percentile	Evidence
00:00	88.8%	1.5 min late	6.1 min late	609 · 10 days
01:00	100.0%	0.1 min late	2.9 min late	248 · 9 days
05:00	95.2%	2.6 min late	4.9 min late	83 · 6 days
06:00	94.3%	1.3 min late	4.9 min late	1,428 · 8 days
07:00	93.2%	1 min late	5.4 min late	2,042 · 10 days
08:00	86.5%	1.5 min late	7.7 min late	2,585 · 11 days
09:00	90.8%	0.6 min late	6.7 min late	1,711 · 12 days
10:00	89.9%	1.6 min late	7.5 min late	1,528 · 12 days
11:00	89.0%	1.8 min late	6.8 min late	2,215 · 13 days
12:00	82.4%	2.5 min late	8.9 min late	2,553 · 12 days
13:00	80.2%	2.5 min late	11.6 min late	1,928 · 12 days
14:00	83.8%	2 min late	9.1 min late	1,856 · 13 days
15:00	70.7%	2.9 min late	14.5 min late	2,394 · 12 days
16:00	59.8%	3.5 min late	17.5 min late	2,131 · 13 days
17:00	63.6%	3.6 min late	16 min late	1,915 · 12 days
18:00	83.5%	1.9 min late	8.5 min late	2,049 · 11 days
19:00	90.2%	1 min late	6.6 min late	1,204 · 11 days
20:00	87.4%	1.4 min late	8.4 min late	1,074 · 10 days
21:00	87.5%	1.8 min late	8.1 min late	806 · 10 days
22:00	89.8%	1.9 min late	5.9 min late	911 · 10 days
23:00	89.8%	1.4 min late	5.9 min late	910 · 10 days

2 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

405 / 487 scheduled trips published at least one position across 7 service days (83.2%).

05:003 / 5 trips without a position40.0%
06:0011 / 30 trips without a position63.3%
21:005 / 14 trips without a position64.3%
07:0015 / 44 trips without a position65.9%
00:003 / 9 trips without a position66.7%
20:006 / 19 trips without a position68.4%

This is not a confirmed no-show. A missing position can mean a cancelled or missed bus, but it can also mean an unassigned trip ID or an operator-feed gap. Otranspo publishes the gap because it matters to riders while keeping the conclusion honest.

Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position check: the timetable kept before each service day, matched to recorded positions. Exact IDs are preferred; an OC timetable suffix is matched only to one trip on the same route and date with an overlapping time window. Missing timetables, ambiguous matches and feed gaps stay labelled; they are not confirmed no-shows. Sources and limitations.

Dated service

Trips scheduled that day

The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.

Service day

November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026 October 28, 2026

November 3, 2026 · 83 trips in the retained timetable · retained notices; capture coverage unverified

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

05:50– 06:39
Trip sto:63295512Insufficient coverage or identity; outcome unknown
06:07– 07:05
Trip sto:63295608Insufficient coverage or identity; outcome unknown
06:10– 06:59
Trip sto:63295803Insufficient coverage or identity; outcome unknown
06:27– 07:25
Trip sto:63295574Insufficient coverage or identity; outcome unknown
06:28– 07:20
Trip sto:63295001Insufficient coverage or identity; outcome unknown
06:42– 07:35
Trip sto:63295746Insufficient coverage or identity; outcome unknown
06:43– 07:45
Trip sto:63295804Insufficient coverage or identity; outcome unknown
07:00– 07:56
Trip sto:63295611Insufficient coverage or identity; outcome unknown
07:10– 08:06
Trip sto:63295373Insufficient coverage or identity; outcome unknown
07:17– 08:19
Trip sto:63294904Insufficient coverage or identity; outcome unknown
07:21– 08:17
Trip sto:63296094Insufficient coverage or identity; outcome unknown
07:30– 08:32
Trip sto:63295358Insufficient coverage or identity; outcome unknown

· Open all evidence for this day