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

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

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

STO route 37: Cégep G-Roy/St-Joseph

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

CENTRE RIDEAU1 min sched.
ALBERT/METCALFE4 min sched.
ALBERT/BANK6 min sched.
KENT / SPARKS8 min sched.
WELLINGTON/LYON9 min sched.
du PORTAGE/AUBRY15 min sched.
du PORTAGE/LAVAL16 min sched.
LAURIER/EDDY18 min sched.
ALEXANDRE-TACHÉ/MILLAR21 min sched.
ALEXANDRE-TACHÉ/SAINT-JOSEPH23 min sched.
SAINT-JOSEPH/RENÉ-ROGER24 min sched.
SAINT-JOSEPH/DUQUESNE25 min sched.
SAINT-JOSEPH/SAINT-JEAN-BOSCO26 min sched.
SAINT-JOSEPH/MONTCALM28 min sched.
SAINT-JOSEPH/DALPÉ29 min sched.
SAINT-JOSEPH/WìGWÀS30 min sched.
SAINT-JOSEPH/BRODEUR31 min sched.
SAINT-JOSEPH/NICOLET32 min sched.
SAINT-JOSEPH/SAINTE-MARIE33 min sched.
SAINT-JOSEPH/GAMELIN35 min sched.
SAINT-JOSEPH/CHARLES-CHURCH37 min sched.
SAINT-JOSEPH/RENÉ-MARENGÈRE38 min sched.
SAINT-JOSEPH/CURÉ-ROBERT39 min sched.
SAINT-JOSEPH/VALIN40 min sched.
SAINT-JOSEPH/CHARRON41 min sched.
SAINT-JOSEPH/MEUNIER43 min sched.
ISABELLE/RICHARD44 min sched.
ISABELLE/WILFRID-LATOUR44 min sched.
JOLICOEUR/CHOUINARD45 min sched.
PHILIAS-FORTIN/du MONT-BLEU46 min sched.
GEORGES-BILODEAU/LUCIEN-BRAULT46 min sched.
CHARLES-ALBANEL/LE BRETON47 min sched.
CHARLES-ALBANEL/JUMONVILLE48 min sched.
DANIEL-JOHNSON/JUMONVILLE0 min sched.
DANIEL-JOHNSON/LUCIEN-BRAULT0 min sched.
du MONT-BLEU/GEORGES-BILODEAU1 min sched.
du MONT-BLEU/PÈRE-BÉLAND2 min sched.
du MONT-BLEU/JOLICOEUR2 min sched.
du MONT-BLEU/des MAGNOLIAS3 min sched.
du MONT-BLEU/MARCOUX4 min sched.
du MONT-BLEU/de la CITÉ-DES-JEUNES4 min sched.
CEGEP GABRIELLE-ROY/arrivée5 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

1 of 284 trips with a usable feed window (0.4%) had no matching position.

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

283 with position · 1 to investigate · 56 excluded · 340 scheduled trips

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

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

Published position coverage: 283 / 340 (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, 1:38 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

80.7%

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

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

The hours we have evidence for

12 a.m.90% · 514 predictions · 10 days
1 a.m.100% · 100 predictions · 5 days
5 a.m.97% · 418 predictions · 7 days
6 a.m.95% · 662 predictions · 10 days
7 a.m.93% · 1,009 predictions · 9 days
8 a.m.91% · 1,102 predictions · 10 days
9 a.m.96% · 932 predictions · 11 days
10 a.m.92% · 804 predictions · 11 days
11 a.m.89% · 836 predictions · 12 days
12 p.m.90% · 866 predictions · 12 days
1 p.m.81% · 877 predictions · 12 days
2 p.m.88% · 773 predictions · 13 days
3 p.m.71% · 1,345 predictions · 12 days
4 p.m.72% · 1,643 predictions · 13 days
5 p.m.67% · 1,562 predictions · 12 days
6 p.m.79% · 1,337 predictions · 11 days
7 p.m.83% · 1,127 predictions · 11 days
8 p.m.82% · 951 predictions · 10 days
9 p.m.73% · 778 predictions · 10 days
10 p.m.70% · 882 predictions · 10 days
11 p.m.88% · 425 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?

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

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

1% of pairs (75) 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
Early morning (4 to 6 a.m.)	272	0% (0)	0% (0)
Morning rush (6 to 9 a.m.)	1,822	0% (1)	3% (47)
Midday (9 a.m. to 3 p.m.)	251	0% (0)	0% (0)
Afternoon rush (3 to 6 p.m.)	4,049	0% (17)	1% (26)
Evening (6 to 10 p.m.)	2,749	0% (0)	0% (0)
Night (10 p.m. to 4 a.m.)	382	0% (0)	1% (2)

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

Where this route is slowest

Slowest: CENTRE RIDEAU to KENT / SPARKS, 7.4 km/h actual against 12.7 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
CENTRE RIDEAU	KENT / SPARKS	1.2 km	12.7 km/h	7.4 km/h	391	38%
CEGEP GABRIELLE-ROY	DANIEL-JOHNSON/LUCIEN-BRAULT	1.7 km	17.6 km/h	8.3 km/h	337	63%
KENT / SPARKS	du PORTAGE/AUBRY	1.2 km	12 km/h	9.1 km/h	418	35%
TERRASSES de la CHAUDIÈRE	de l'HÔTEL-de-VILLE/LAURIER	750 m	13.1 km/h	11 km/h	368	19%
du PORTAGE/AUBRY	LAURIER/EDDY	470 m	10.6 km/h	12.5 km/h	425	5%
SAINT-JOSEPH/SAINTE-MARIE	SAINT-JOSEPH/NICOLET	410 m	10.8 km/h	12.8 km/h	376	4%
SAINT-JOSEPH/NICOLET	SAINT-JOSEPH/WìGWÀS	490 m	6.8 km/h	13.7 km/h	363	0%
ALEXANDRE-TACHÉ/SAINT-JOSEPH	SAINT-JOSEPH/MONTCALM	850 m	13.2 km/h	14.5 km/h	427	5%

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.

Road work
ALBERT between ELGIN and METCALFE
Oct 29, 2026, 12:00 a.m. to Jan 26, 2027, 5:00 p.m.
ALBERT lane reduction between ELGIN and METCALFE due to construction, from October 29th to January 26th.
The City marks this as affecting transit.
about 0 m from the route
City record updated Nov 2, 2026, 12:44 p.m..
Road work
Slater between Bay and Lyon
Oct 30, 2026, 12:00 a.m. to Nov 6, 2026, 5:00 p.m.
Slater lane reduction between Bay and Lyon due to construction, from November 2nd to 6th.
about 0 m from the route
City record updated Oct 30, 2026, 1:28 p.m..
Road work
ALBERT at LYON
Dates not published
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 2 m from the route
City record updated Sep 9, 2026, 6:32 p.m..

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

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

Cancellations on this route

What these words mean →

6 partial-capture days not counted.

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: 1 of 284 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 seats22.7% of 66 trips	Not enough readings	Not enough readings
6 to 9 am	Usually seats21% of 362 trips	Usually seats5.7% of 35 trips	Usually seats0% of 34 trips
9 am to 3 pm	Usually seats10.9% of 468 trips	Usually seats21.6% of 97 trips	Usually seats14.9% of 87 trips
3 to 6 pm	Usually seats40.2% of 487 trips	Usually seats32.1% of 53 trips	Usually seats13% of 54 trips
6 to 10 pm	Usually seats14.4% of 436 trips	Usually seats14.7% of 75 trips	Usually seats6.7% of 60 trips
After 10 pm	Usually seats1.5% of 205 trips	Usually seats12.1% of 33 trips	Usually seats0% of 23 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.3 min later than the timetable in 1 hours of the day.

The prediction difference from the timetable grows by about 2.1 min along the route.

17:00 has 67% of predictions within five minutes of the timetable, against 88% the rest of the day.

Scenario: 3 min more running time on 16 trips. The schedule-block model adds no buses; fleet and workforce feasibility are unverified.

Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.

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

00:00: 89.9% of final predictions within five minutes of the timetable, 514 predictions, typically 1 min late
01:00: 100% of final predictions within five minutes of the timetable, 100 predictions, typically 0.3 min early
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: 97.4% of final predictions within five minutes of the timetable, 418 predictions, typically 1.5 min late
06:00: 95.3% of final predictions within five minutes of the timetable, 662 predictions, typically 0.8 min late
07:00: 92.8% of final predictions within five minutes of the timetable, 1,009 predictions, typically 1.2 min late
08:00: 90.8% of final predictions within five minutes of the timetable, 1,102 predictions, typically 0.6 min late
09:00: 96% of final predictions within five minutes of the timetable, 932 predictions, typically 1.4 min late
10:00: 91.5% of final predictions within five minutes of the timetable, 804 predictions, typically 0.6 min late
11:00: 88.8% of final predictions within five minutes of the timetable, 836 predictions, typically 1.5 min late
12:00: 89.5% of final predictions within five minutes of the timetable, 866 predictions, typically 0.8 min late
13:00: 81.2% of final predictions within five minutes of the timetable, 877 predictions, typically 1.9 min late
14:00: 88% of final predictions within five minutes of the timetable, 773 predictions, typically 1.5 min late
15:00: 70.9% of final predictions within five minutes of the timetable, 1,345 predictions, typically 2.7 min late
16:00: 71.5% of final predictions within five minutes of the timetable, 1,643 predictions, typically 2.9 min late
17:00: 67.2% of final predictions within five minutes of the timetable, 1,562 predictions, typically 2.9 min late
18:00: 78.7% of final predictions within five minutes of the timetable, 1,337 predictions, typically 1.8 min late
19:00: 83% of final predictions within five minutes of the timetable, 1,127 predictions, typically 1.4 min late
20:00: 81.9% of final predictions within five minutes of the timetable, 951 predictions, typically 2.2 min late
21:00: 72.9% of final predictions within five minutes of the timetable, 778 predictions, typically 2.9 min late
22:00: 69.6% of final predictions within five minutes of the timetable, 882 predictions, typically 3.3 min late
23:00: 88.2% of final predictions within five minutes of the timetable, 425 predictions, typically 2.3 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	22:00	3.3 min late	More running time
ProblemOne hour has a lower prediction match	17:00	67%	Operations, not the timetable

Measurements

Predictions later than timetable · 22:00: Measured arrivals 882; Hours affected 1; Spread 3.9 min; Median delay 3.3 min; Suggested running time change 3.3 min
One hour has a lower prediction match · 17:00: Hour 17:00; On time 67.2%; Measured arrivals 1,562; Shortfall 21 pts; Route median on time 88.2%

Open history, reliability and route analysis

Route check

How route 37 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, but check the problem times below.

81 in 100 eligible predictions were within 5 minutes of the timetable · 36,138 predictions checked

Prediction sample size: Larger sample

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

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

5 p.m.–6 p.m.: 33 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,562 predictions over 12 days).
10 p.m.–11 p.m.: 30 in 100 eligible predictions differed from the timetable by more than 5 minutes (882 predictions over 10 days).

1 current notice affects this route

• Detour Route 37 South

Prediction differences by stop

CEGEP GABRIELLE-ROY
47 in 100 eligible predictions differed from the timetable by more than 5 minutes (407 predictions over 24 days).
Open this stop
du PORTAGE/AUBRY
37 in 100 eligible predictions differed from the timetable by more than 5 minutes (509 predictions over 24 days).
Open this stop
LAURIER/EDDY
34 in 100 eligible predictions differed from the timetable by more than 5 minutes (508 predictions over 24 days).
Open this stop
du PORTAGE/LAVAL
34 in 100 eligible predictions differed from the timetable by more than 5 minutes (508 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?: 1 of 284 checked trips need a closer look1 of 284 trips with enough public-feed evidence had no matching position over 7 days. 56 of 340 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.0 min (positive means later; negative means earlier)81 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 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: 54
Distinct scheduled stops: 85
Distinct published paths: 3
Published service span: 5:08 a.m.–1:13 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 20,028 arrivals over 13 days; after has 2,489 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: 80.7%
Eligible predictions checked: 36,138
Weekdays with data: 17
95th-percentile predicted delay: 9 min late

Patterns by hour (21)

Patterns by hour (21)
Hour	On time	Median	95th percentile	Evidence
00:00	89.9%	1 min late	5.8 min late	514 · 10 days
01:00	100.0%	0.3 min early	1.9 min late	100 · 5 days
05:00	97.4%	1.5 min late	4.3 min late	418 · 7 days
06:00	95.3%	0.8 min late	4.5 min late	662 · 10 days
07:00	92.8%	1.2 min late	5.5 min late	1,009 · 9 days
08:00	90.8%	0.6 min late	5.5 min late	1,102 · 10 days
09:00	96.0%	1.4 min late	4.6 min late	932 · 11 days
10:00	91.5%	0.6 min late	4.5 min late	804 · 11 days
11:00	88.8%	1.5 min late	6.2 min late	836 · 12 days
12:00	89.5%	0.8 min late	5.9 min late	866 · 12 days
13:00	81.2%	1.9 min late	7 min late	877 · 12 days
14:00	88.0%	1.5 min late	5.9 min late	773 · 13 days
15:00	70.9%	2.7 min late	9.4 min late	1,345 · 12 days
16:00	71.5%	2.9 min late	10.6 min late	1,643 · 13 days
17:00	67.2%	2.9 min late	14.3 min late	1,562 · 12 days
18:00	78.7%	1.8 min late	9 min late	1,337 · 11 days
19:00	83.0%	1.4 min late	7.7 min late	1,127 · 11 days
20:00	81.9%	2.2 min late	7.3 min late	951 · 10 days
21:00	72.9%	2.9 min late	7.6 min late	778 · 10 days
22:00	69.6%	3.3 min late	7.1 min late	882 · 10 days
23:00	88.2%	2.3 min late	6.3 min late	425 · 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

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

07:0012 / 29 trips without a position58.6%
22:005 / 14 trips without a position64.3%
00:004 / 12 trips without a position66.7%
05:003 / 10 trips without a position70.0%
06:005 / 17 trips without a position70.6%
20:004 / 14 trips without a position71.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 · 54 trips in the retained timetable · retained notices; capture coverage unverified

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

05:08– 05:50
Trip sto:63295346Insufficient coverage or identity; outcome unknown
05:37– 06:22
Trip sto:63295195Insufficient coverage or identity; outcome unknown
06:12– 06:57
Trip sto:63295474Insufficient coverage or identity; outcome unknown
06:25– 07:10
Trip sto:63295738Insufficient coverage or identity; outcome unknown
06:42– 07:27
Trip sto:63294959Insufficient coverage or identity; outcome unknown
07:06– 07:55
Trip sto:63296352Insufficient coverage or identity; outcome unknown
07:13– 08:05
Trip sto:63296160Insufficient coverage or identity; outcome unknown
07:29– 08:22
Trip sto:63294822Insufficient coverage or identity; outcome unknown
07:39– 08:25
Trip sto:63295653Insufficient coverage or identity; outcome unknown
07:43– 08:36
Trip sto:63296308Insufficient coverage or identity; outcome unknown
08:05– 08:51
Trip sto:63294667Insufficient coverage or identity; outcome unknown
08:12– 09:04
Trip sto:63294945Insufficient coverage or identity; outcome unknown

· Open all evidence for this day