Before
Service date checked: August 31, 2026
- Scheduled trips
- 71
- Distinct scheduled stops
- 83
- Distinct published paths
- 2
- Published service span
- 04:53–23:56
Feed fingerprint: ecc28a3727bcaff4 · 345fd07d-fb05-4eaa-8ec2-3daf8b7fcbe9
Otranspo
Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
Route
112
OC Transpo
Billings Bridge ↔ Baseline
All imported trips are marked accessible.Imported schedule valid through: Oct 4, 2026
Verdict
What this route needs
Unreliable 14:00: a bad trip runs 39 min behind a normal one.
On time 91% in a normal hour, never below 80%.
- 00:00: not enough data
- 01:00: not enough data
- 02:00: not enough data
- 03:00: not enough data
- 04:00: 100% of arrivals on time, 45 arrivals, typically 1.1 min late
- 05:00: 98.3% of arrivals on time, 421 arrivals, typically 0.2 min late
- 06:00: 92.4% of arrivals on time, 844 arrivals, typically 0.5 min late
- 07:00: 89.8% of arrivals on time, 844 arrivals, typically 0.8 min late
- 08:00: 83.6% of arrivals on time, 561 arrivals, typically 1 min late
- 09:00: 86.2% of arrivals on time, 675 arrivals, typically 2.1 min late
- 10:00: 89.9% of arrivals on time, 663 arrivals, typically 0.2 min late
- 11:00: 98.1% of arrivals on time, 830 arrivals, typically 0.6 min late
- 12:00: 97.1% of arrivals on time, 617 arrivals, typically 0.3 min late
- 13:00: 93.4% of arrivals on time, 685 arrivals, typically 0.8 min late
- 14:00: 84.2% of arrivals on time, 777 arrivals, typically 1.4 min late. Unreliable: a bad trip runs far behind a normal one.
- 15:00: 85.7% of arrivals on time, 594 arrivals, typically 1.3 min late
- 16:00: 80% of arrivals on time, 550 arrivals, typically 2.6 min late
- 17:00: 84.9% of arrivals on time, 423 arrivals, typically 2.5 min late
- 18:00: 92.1% of arrivals on time, 541 arrivals, typically 1.8 min late
- 19:00: 93.1% of arrivals on time, 518 arrivals, typically 1.1 min late
- 20:00: 89.5% of arrivals on time, 550 arrivals, typically 0.5 min late
- 21:00: 94.9% of arrivals on time, 506 arrivals, typically 0.1 min late
- 22:00: 100% of arrivals on time, 380 arrivals, typically 0.8 min late
- 23:00: 84.4% of arrivals on time, 211 arrivals, typically 0.4 min early
- 90% or more on time
- 80 to 90% on time
- under 80% on time
- not enough data
- unreliable: a bad trip runs 20 min or more behind a normal one
| What | When | Measured | Fix |
|---|---|---|---|
| StrengthConsistently on time | 04:00 to 00:00 | 91% | Keep what works |
| ProblemUnreliable | 14:00 | 39 min swing | Operations, not the timetable |
Measurements
- Consistently on time · 04:00 to 00:00
- medianHourOnTimePct 91
- worstHourOnTimePct 80
- hoursMeasured 20
- observations 11,235
- Unreliable · 14:00
- medianDelaySeconds 82
- spreadSeconds 2,337
- observations 777
- hoursAffected 1
- suggestedRunningTimeChangeMinutes 1.4
Route check
How route 112 is doing
A plain-language summary of the strongest evidence we have. We say when the data cannot answer a question.
Bottom line
Usually close to schedule in the period we measured.
87 in 100 arrivals were within 5 minutes of schedule · 20,264 arrivals checkedConfidence in this summary: High
Based on 20,264 arrivals over 20 weekdays, from Aug 9, 2026 to Sep 8, 2026.
Updated Sep 8, 2026, 2:32 a.m.
Where and when does it keep going wrong?
These are repeated patterns, not one bad day or an unverified rider report. They are measured the same way as the verdict above, over the same arrivals, but they are counted per stop rather than per hour, so the two lists need not match line for line.
No recurring problem time has cleared our evidence threshold yet.
No current official notice matches this route.
Problem places
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 7
- Possible no-shows after checking feed gaps?
- 244 of 431 checked trips need a closer look
- How late does this route get?
- The slowest 5 in 100 were more than about 8.7 min late
- Do buses bunch or leave long gaps?
- No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.
Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
244 of 431 trips with enough public-feed evidence had no matching position over 7 days. 39 of 470 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
87 in 100 arrivals were within 5 minutes of schedule.
Schedule change check
Fall schedule: before and after
This compares the official schedule that ended with the one that started August 30. Schedule changes are facts about what was planned; they do not prove that a trip ran.
Current published schedule began September 4, 2026
What the official notice says about this route
The City’s public summary did not name this route. The feed comparison below can still show a changed timetable, but it cannot tell us why it changed.
Read the official August 30 service-change notice →One comparable weekday from each published schedule
We use 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.
New schedule
Service date checked: September 7, 2026
- Scheduled trips
- 59
- Distinct scheduled stops
- 83
- Distinct published paths
- 2
- Published service span
- 06:55–23:41
Feed fingerprint: e0b417f2ea03fcf0 · 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad
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 9,599 arrivals over 11 days; after has 2,320 arrivals over 3 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 observed arrivals with the official schedule. A result needs at least 200 arrivals. 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.
Would you count on route 112?
No sign-in needed. A vote from a device that is not signed in counts a little less than one from an account, and a person who rates many routes counts a little less on each, so no one voice outweighs the rest.
Share this page
Use the permanent public link to this page and its sources.
Only the canonical public link is shared. Panel state, location, receipts, and other browser-only details are left out. Email and social services apply their own privacy terms.
Live route map
Where the buses are now
Fresh vehicle positions appear on the route below. A marker stops moving when the evidence runs out. We do not invent movement.
Route and live buses
The line is the official route. Dots show published stops, buses seen now and stops named in current notices.
0 official shapes · 83 stops · 0 vehicle markers
Loading official route geometry · Loading current vehicles
Markers move between GPS fixes using measured progress along the published route. They pause after one measured reporting interval, on a measured standstill, or when evidence becomes stale.
Today’s schedule
Service date September 8, 2026
- Towards Billings Bridge
- 35 scheduled trips
- 4:53 a.m.–11:21 p.m.
- 30 min median scheduled gap
- Towards Baseline
- 36 scheduled trips
- 5:34 a.m.–11:56 p.m.
- 30 min median scheduled gap
Span and median gap are computed from today’s official GTFS stop_times. They are timetable measures, not observed headways or a frequency guarantee.
Next trips from the ends of the route
These are trip starts. For the time at your stop, open that stop’s departure board.
Towards Billings Bridge
Starts at BASELINE 1B
Timetable only. No usable prediction is available for this trip.
Towards Baseline
Starts at BILLINGS BRIDGE 3B
Timetable only. No usable prediction is available for this trip.
Towards Billings Bridge
Starts at BASELINE 1B
Timetable only. No usable prediction is available for this trip.
Towards Baseline
Starts at BILLINGS BRIDGE 3B
Timetable only. No usable prediction is available for this trip.
Showing 4 of 7 trips. Open a stop for its full departure board.
Buses seen now
The current healthy operator position feed contains no vehicle matched to this route.
Official notices
No matching active notice appears in the current healthy operator feed.
Planned changes
No safely matched planned change is recorded for this route.
These are Otranspo register records, separate from operator alerts. A record is attached only when its route label identifies one operator; ambiguous OC Transpo/STO number matches are withheld.
Evidence checked Sep 8, 2:54 a.m.
Provisional results, published evidence
When is this route reliable?
Every hour below is backed by this route’s settled arrivals. “On time” means no more than five minutes early or late, so a bus that leaves very early counts as a failure for the waiting rider.
Evidence window: August 9, 2026 to September 8, 2026
- Within 5 minutes of schedule
- 86.7%
- Arrivals checked
- 20,264
- Weekdays with data
- 20
- How late the worst 5 in 100 were
- 8.7 min late
Patterns by hour (21)
| Hour | On time | Median | Worst 5 in 100 | Evidence |
|---|---|---|---|---|
| 00:00 | 100.0% | 0.9 min late | 2.3 min late | 72 · 1 days |
| 04:00 | 100.0% | 1.1 min late | 1.8 min late | 45 · 5 days |
| 05:00 | 98.3% | 0.2 min late | 3.1 min late | 421 · 6 days |
| 06:00 | 92.4% | 0.5 min late | 7.1 min late | 844 · 6 days |
| 07:00 | 89.8% | 0.8 min late | 5.8 min late | 844 · 6 days |
| 08:00 | 83.6% | 1 min late | 11.8 min late | 561 · 6 days |
| 09:00 | 86.2% | 2.1 min late | 8.5 min late | 675 · 6 days |
| 10:00 | 89.9% | 0.2 min late | 6.1 min late | 663 · 7 days |
| 11:00 | 98.1% | 0.6 min late | 4.5 min late | 830 · 8 days |
| 12:00 | 97.1% | 0.3 min late | 3.6 min late | 617 · 7 days |
| 13:00 | 93.4% | 0.8 min late | 5.7 min late | 685 · 9 days |
| 14:00 | 84.2% | 1.4 min late | 40.3 min late | 777 · 8 days |
| 15:00 | 85.7% | 1.3 min late | 11 min late | 594 · 7 days |
| 16:00 | 80.0% | 2.6 min late | 7.1 min late | 550 · 6 days |
| 17:00 | 84.9% | 2.5 min late | 6.4 min late | 423 · 5 days |
| 18:00 | 92.1% | 1.8 min late | 4.9 min late | 541 · 7 days |
| 19:00 | 93.1% | 1.1 min late | 5.3 min late | 518 · 7 days |
| 20:00 | 89.5% | 0.5 min late | 6.7 min late | 550 · 7 days |
| 21:00 | 94.9% | 0.1 min late | 5.4 min late | 506 · 6 days |
| 22:00 | 100.0% | 0.8 min late | 3.2 min late | 380 · 7 days |
| 23:00 | 84.4% | 0.4 min early | 7.9 min late | 211 · 7 days |
No repeated pattern below 70% is yet established across at least three service days.
Scheduled bus, but not observed in realtime
187 / 470 scheduled trips published at least one position across 1 service days (39.8%).
- 14:0023 / 28 trips without a position17.9%
- 23:006 / 8 trips without a position25.0%
- 09:0019 / 28 trips without a position32.1%
- 16:0019 / 28 trips without a position32.1%
- 17:0019 / 28 trips without a position32.1%
- 10:0018 / 28 trips without a position35.7%
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.
Arrival check: the last prediction within ten minutes of arrival, counted once per trip, stop and service date. Trip 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.
See all stops and route patterns
Stops and stations
2 official stop patterns
Each row below is one exact stop order published in the official schedule. Short turns and alternate destinations stay separate.
- View stops and calendar →
Towards Billings Bridge: BASELINE 1B to BILLINGS BRIDGE 4B
41 stops · 391 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
12 official service records
3 added dates and 23 removed dates
- View stops and calendar →
Towards Baseline: BILLINGS BRIDGE 3B to BASELINE 2A
42 stops · 395 imported trips
Scheduled from Sep 4, 2026 to Oct 4, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
12 official service records
3 added dates and 23 removed dates
Official feed version 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad
Source checksum e0b417f2ea03fcf035ed795c07b47461157b81b0c43d43639094105ed66b0a4a
Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.
What is being shown
The current public route group, its published schedule variants and stop patterns, current operations, and matching observed reliability where available.
How it was produced
1 current GTFS route record variants are grouped by operator and public route number. Stop patterns remain tied to their published variant; aggregated reliability records are not merged into an invented percentile.
Evidence dates
- Collected or observed
- Computed or assembled
- Sample
- 20,264 settled arrivals across 1 matching reliability records.
- Coverage
- 2 published stop patterns containing 83 stop calls are available on this page.
- Method or data version
- last-prediction-within-ten-minutes-v1; 37ff8dfc-21cc-48c3-9eba-fc0d2e50b2ad; e0b417f2ea03fcf035ed795c07b47461157b81b0c43d43639094105ed66b0a4a
Sources
Limits to keep in mind
- Schedule variants can apply on different dates. A grouped route is not a claim that every pattern operates today.
- Accessibility fields report only what the operator publishes; an unknown value is not confirmation of access.
Rider evidence
Community reports
Signals below are moderated community aggregates, not official operator notices or reliability scores.
You can report without signing in. Anonymous reports count a little less when we calculate public patterns. You can add an account after submitting.
Report a specific problem
Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.
Source: currently imported OC Transpo GTFS. Check the Alerts panel for current official notices and each stop page for observed departures.