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

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

Route 112: Billings Bridge ⇄ Baseline

Every 30 to 31 min

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

Next: 29.3 min after the pair

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 29, 2026 – Nov 4, 2026

Scheduled trips with cancellation notices

Trips in the published timetable marked cancelled without qualifying later matching vehicle observations in our archive. This does not prove the trip did not operate. Not counted: 2 trips with qualifying later matching vehicle observations. Trips with any notice: 2.

Trips needing investigation

2 of 481 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.

479 with position · 2 to investigate · 1 excluded · 482 scheduled trips

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

Coverage, exclusions and sources

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

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

Published position coverage: 479 / 482 (99.4%). 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 5, 2026, 8:39 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

89.7%

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

Predictions in the source: 74,056
Weekdays with evidence: 19
Evidence window: Oct 7, 2026 – Nov 4, 2026

The hours we have evidence for

4 a.m.100% · 98 predictions · 11 days
5 a.m.95% · 921 predictions · 13 days
6 a.m.93% · 1,828 predictions · 15 days
7 a.m.94% · 1,956 predictions · 15 days
8 a.m.83% · 2,294 predictions · 15 days
9 a.m.95% · 2,435 predictions · 15 days
10 a.m.96% · 2,434 predictions · 15 days
11 a.m.91% · 2,411 predictions · 15 days
12 p.m.94% · 2,396 predictions · 15 days
1 p.m.96% · 2,446 predictions · 15 days
2 p.m.93% · 2,365 predictions · 15 days
3 p.m.89% · 2,394 predictions · 15 days
4 p.m.87% · 2,459 predictions · 15 days
5 p.m.69% · 2,428 predictions · 15 days
6 p.m.87% · 2,451 predictions · 15 days
7 p.m.88% · 2,460 predictions · 15 days
8 p.m.90% · 2,541 predictions · 15 days
9 p.m.91% · 2,379 predictions · 15 days
10 p.m.96% · 1,730 predictions · 15 days
11 p.m.97% · 909 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 5, 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 8, 2026 to November 4, 2026: 26 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

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

0% of pairs (44) 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.)	4,892	0% (0)	0% (0)
Midday (9 a.m. to 3 p.m.)	20,894	0% (0)	0% (0)
Afternoon rush (3 to 6 p.m.)	10,703	0% (1)	0% (35)
Evening (6 to 10 p.m.)	16,823	0% (28)	0% (9)
Night (10 p.m. to 4 a.m.)	2,794	0% (0)	0% (0)

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

Where this route is slowest

Slowest: BASELINE 1B to VIEWMOUNT / MERIVALE, 19.3 km/h actual against 17.2 km/h planned.

Where this route is slowest
From	To	Distance	Planned speed	Actual speed	Trips measured	Slow trips
BASELINE 1B	VIEWMOUNT / MERIVALE	3.3 km	17.2 km/h	19.3 km/h	758	3%
VIEWMOUNT / FARMGATE	VIEWMOUNT / MERIVALE	2.3 km	20.5 km/h	20.2 km/h	887	3%
VIEWMOUNT / FARM GATE	PRINCE OF WALES / HOG'S BACK	2.1 km	22.3 km/h	22.2 km/h	874	1%
PRINCE OF WALES / MEADOWLANDS	VIEWMOUNT / FARMGATE	2 km	17.5 km/h	22.5 km/h	888	2%
VIEWMOUNT / MERIVALE	VIEWMOUNT / FARM GATE	2.1 km	22.1 km/h	23.6 km/h	873	2%
BILLINGS BRIDGE 3B	PRINCE OF WALES / MEADOWLANDS	3.8 km	25.5 km/h	26.3 km/h	851	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.

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 →

2 partial-capture days not counted.

1 scheduled trips with counted cancellation notices from Thu, Oct 8 to Wed, Nov 4.

Not counted: 15 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. (1)

Latest cancelled trips

Thu, Oct 22, scheduled 13:04

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

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

Open the dated prediction analysis

Verdict

What this route needs

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

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 21 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: 100% of final predictions within five minutes of the timetable, 98 predictions, typically 1.2 min late
05:00: 94.9% of final predictions within five minutes of the timetable, 921 predictions, typically 0.2 min late
06:00: 93.2% of final predictions within five minutes of the timetable, 1,828 predictions, typically 0.3 min early
07:00: 94% of final predictions within five minutes of the timetable, 1,956 predictions, typically 0.9 min late
08:00: 82.5% of final predictions within five minutes of the timetable, 2,294 predictions, typically 2.1 min late
09:00: 95.2% of final predictions within five minutes of the timetable, 2,435 predictions, typically 0.5 min late
10:00: 96.4% of final predictions within five minutes of the timetable, 2,434 predictions, typically 0.2 min late
11:00: 91% of final predictions within five minutes of the timetable, 2,411 predictions, typically 0.3 min early
12:00: 93.8% of final predictions within five minutes of the timetable, 2,396 predictions, typically 0.3 min late
13:00: 95.9% of final predictions within five minutes of the timetable, 2,446 predictions, typically 0 min early
14:00: 93.2% of final predictions within five minutes of the timetable, 2,365 predictions, typically 0.2 min late
15:00: 89.4% of final predictions within five minutes of the timetable, 2,394 predictions, typically 0.7 min late
16:00: 86.5% of final predictions within five minutes of the timetable, 2,459 predictions, typically 0.9 min late
17:00: 69.4% of final predictions within five minutes of the timetable, 2,428 predictions, typically 2.1 min late
18:00: 86.5% of final predictions within five minutes of the timetable, 2,451 predictions, typically 1 min late
19:00: 88.3% of final predictions within five minutes of the timetable, 2,460 predictions, typically 0.9 min late
20:00: 89.6% of final predictions within five minutes of the timetable, 2,541 predictions, typically 0.4 min late
21:00: 90.5% of final predictions within five minutes of the timetable, 2,379 predictions, typically 0.1 min late
22:00: 96.3% of final predictions within five minutes of the timetable, 1,730 predictions, typically 1 min late
23:00: 96.7% of final predictions within five minutes of the timetable, 909 predictions, typically 0.1 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
ProblemOne hour has a lower prediction match	17:00	69%	Operations, not the timetable

Measurements

One hour has a lower prediction match · 17:00: Hour 17:00; On time 69.4%; Measured arrivals 2,428; Shortfall 23.8 pts; Route median on time 93.2%

Open history, reliability and route analysis

Route check

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

90 in 100 eligible predictions were within 5 minutes of the timetable · 74,056 predictions checked

Prediction sample size: Larger sample

Based on 74,056 eligible provider predictions over 27 measured days, from Oct 7, 2026 to Nov 4, 2026.

Updated Nov 5, 2026, 9:32 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.

5 p.m.–6 p.m.: 31 in 100 eligible predictions differed from the timetable by more than 5 minutes (2,428 predictions over 15 days).

No current official notice matches this route.

Prediction differences by stop

We do not yet have enough route-by-stop history to name a recurring problem stop. Rider reports are used as leads, not proof.

Check every trip and date

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

What riders want to know

Is any trip cancelled right now?: 0 of 12Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 2 of 481 checked trips need a closer look2 of 481 trips with enough public-feed evidence had no matching position over 7 days. 1 of 482 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 6.8 min (positive means later; negative means earlier)90 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 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: 71
Distinct scheduled stops: 83
Distinct published paths: 2
Published service span: 4:53 a.m.–11:56 p.m.

Operator calendar-date records: 0 added · 2 removed

Feed fingerprint: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

New schedule

Service date checked: November 2, 2026

Scheduled trips: 71
Distinct scheduled stops: 83
Distinct published paths: 2
Published service span: 4:53 a.m.–11:56 p.m.

Operator calendar-date records: 0 added · 2 removed

Feed fingerprint: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

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 38,718 arrivals over 14 days; after has 16,553 arrivals over 6 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 7, 2026 to November 4, 2026

Within 5 minutes of schedule: 89.7%
Eligible predictions checked: 74,056
Weekdays with data: 19
95th-percentile predicted delay: 6.8 min late

Patterns by hour (21)

Patterns by hour (21)
Hour	On time	Median	95th percentile	Evidence
00:00	87.5%	2.3 min late	5.4 min late	144 · 2 days
04:00	100.0%	1.2 min late	1.9 min late	98 · 11 days
05:00	94.9%	0.2 min late	5 min late	921 · 13 days
06:00	93.2%	0.3 min early	5.5 min late	1,828 · 15 days
07:00	94.0%	0.9 min late	5.3 min late	1,956 · 15 days
08:00	82.5%	2.1 min late	6.8 min late	2,294 · 15 days
09:00	95.2%	0.5 min late	4.7 min late	2,435 · 15 days
10:00	96.4%	0.2 min late	4.1 min late	2,434 · 15 days
11:00	91.0%	0.3 min early	5.9 min late	2,411 · 15 days
12:00	93.8%	0.3 min late	5.2 min late	2,396 · 15 days
13:00	95.9%	0 min early	4.1 min late	2,446 · 15 days
14:00	93.2%	0.2 min late	5.8 min late	2,365 · 15 days
15:00	89.4%	0.7 min late	5.9 min late	2,394 · 15 days
16:00	86.5%	0.9 min late	11.9 min late	2,459 · 15 days
17:00	69.4%	2.1 min late	13.7 min late	2,428 · 15 days
18:00	86.5%	1 min late	9.5 min late	2,451 · 15 days
19:00	88.3%	0.9 min late	7.2 min late	2,460 · 15 days
20:00	89.6%	0.4 min late	6 min late	2,541 · 15 days
21:00	90.5%	0.1 min late	4.8 min late	2,379 · 15 days
22:00	96.3%	1 min late	4.4 min late	1,730 · 15 days
23:00	96.7%	0.1 min late	4.5 min late	909 · 14 days

1 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

479 / 482 scheduled trips published at least one position across 1 service days (99.4%).

05:001 / 11 trips without a position90.9%
06:001 / 23 trips without a position95.7%
08:001 / 26 trips without a position96.2%
04:000 / 5 trips without a position100.0%
07:000 / 24 trips without a position100.0%
09:000 / 28 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 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

November 4, 2026 · 71 trips in the retained timetable · retained notices; capture coverage unverified

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

04:53– 05:17
Trip 4482040Vehicle position matchedFirst / last feed position: 4:38 a.m. EST / 5:35 a.m. EST; not actual start or end times.
05:34– 06:02
Trip 32696040Vehicle position matchedFirst / last feed position: 5:36 a.m. EST / 6:10 a.m. EST; not actual start or end times.
05:53– 06:23
Trip 34327040Vehicle position matchedFirst / last feed position: 5:58 a.m. EST / 6:28 a.m. EST; not actual start or end times.
06:04– 06:32
Trip 30108040Vehicle position matchedFirst / last feed position: 5:43 a.m. EST / 6:45 a.m. EST; not actual start or end times.
06:23– 06:53
Trip 18335040Vehicle position matchedFirst / last feed position: 5:49 a.m. EST / 7:20 a.m. EST; not actual start or end times.
06:34– 07:04
Trip 35743040Vehicle position matchedFirst / last feed position: 6:29 a.m. EST / 7:02 a.m. EST; not actual start or end times.
06:53– 07:24
Trip 5563040Vehicle position matchedFirst / last feed position: 6:54 a.m. EST / 7:59 a.m. EST; not actual start or end times.
07:04– 07:34
Trip 35134040Vehicle position matchedFirst / last feed position: 6:52 a.m. EST / 7:37 a.m. EST; not actual start or end times.
07:23– 08:00
Trip 37328040Vehicle position matchedFirst / last feed position: 7:24 a.m. EST / 8:05 a.m. EST; not actual start or end times.
07:34– 08:10
Trip 10553040Vehicle position matchedFirst / last feed position: 7:13 a.m. EST / 8:13 a.m. EST; not actual start or end times.
07:53– 08:30
Trip 5439040Vehicle position matchedFirst / last feed position: 7:57 a.m. EST / 8:37 a.m. EST; not actual start or end times.
08:04– 08:40
Trip 15264040Vehicle position matchedFirst / last feed position: 8:06 a.m. EST / 8:55 a.m. EST; not actual start or end times.

· Open all evidence for this day