Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.
OC Transpo · Regular service
Billings Bridge · Baseline
All imported trips are marked accessible.
Live route map
Fresh vehicle positions appear on the route below. A marker stops moving when the evidence runs out. We do not invent movement.
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.
Service date September 19, 2026
Span and median gap are computed from today’s official GTFS stop_times. They are timetable measures, not observed headways or a frequency guarantee.
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
Provider prediction · Scheduled 1:45 p.m.
Towards Billings Bridge
Starts at BASELINE 1B
Provider prediction · Scheduled 2:06 p.m.
Towards Baseline
Starts at BILLINGS BRIDGE 3B
Timetable only. No usable prediction is available for this trip.
Showing 4 of 12 trips. Open a stop for its full departure board.
2 current vehicle positions match this route.
The feed identifier is not a verified physical bus or fleet number.
Towards Billings Bridge
Feed vehicle 4634
Updated Sep 19, 1:32 p.m.
Towards Baseline
Feed vehicle 4700
Updated Sep 19, 1:32 p.m.
No matching active notice appears in the current healthy operator feed.
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 19, 1:34 p.m.
2 official stop patterns
Each row below is one exact stop order published in the official schedule. Short turns and alternate destinations stay separate.
41 stops · 471 imported trips
Scheduled from Sep 18, 2026 to Oct 18, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
14 official service records
5 added dates and 31 removed dates
42 stops · 481 imported trips
Scheduled from Sep 18, 2026 to Oct 18, 2026
Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday
14 official service records
5 added dates and 31 removed dates
Official feed version 99de510d-89b0-4652-9d93-217659284cf2
Source checksum 2f30d876ae731cae79cf274d036530bb78b0c14f6e0e994d1ad32ca16291b367
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.
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.
Verdict
Timetable short by 3.6 min in 1 hours of the day.
Buses already leave about 4.1 min late and hold it to the end. The running time is right; the terminal is the problem.
17:00 drops to 61% on time, against 92% the rest of the day.
Next investigation: test terminal recovery and the preceding trip. The arrival pattern alone does not establish the cause.
| What | When | Measured | Scenario or next investigation |
|---|---|---|---|
| ProblemLate by the timetable | 17:00 | 3.6 min late | Recovery time at the terminal |
| ProblemOne hour collapses | 17:00 | 61% | Operations, not the timetable |
Route check
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, but check the problem times below.
89 in 100 arrivals were within 5 minutes of schedule · 42,649 arrivals checkedConfidence in this summary: High
Based on 42,649 arrivals over 20 weekdays, from Aug 20, 2026 to Sep 19, 2026.
Updated Sep 19, 2026, 1:32 p.m.
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 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.
Open a time period to see each service day, scheduled trip, feed gap, observed public vehicle ID, and the exact counts behind this summary.
Schedule change check
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 September 18, 2026
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.
Service date checked: September 14, 2026
Operator calendar-date records: 0 added · 3 removed
Feed fingerprint: d6d50360bb16d494 · 151dbfc4-6745-4fbd-9eef-6885ecb708f4
Service date checked: September 21, 2026
Operator calendar-date records: 0 added · 2 removed
Feed fingerprint: 2f30d876ae731cae · 99de510d-89b0-4652-9d93-217659284cf2
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 30,225 arrivals over 13 days; after has 2,825 arrivals over 1 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.
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.
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.
Provisional results, published evidence
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 20, 2026 to September 19, 2026
| Hour | On time | Median | Worst 5 in 100 | Evidence |
|---|---|---|---|---|
| 00:00 | 100.0% | 2.5 min late | 4.2 min late | 72 · 1 days |
| 04:00 | 100.0% | 1.1 min late | 2.1 min late | 81 · 9 days |
| 05:00 | 94.7% | 0.4 min late | 5.2 min late | 734 · 10 days |
| 06:00 | 98.6% | 0.4 min late | 3.5 min late | 1,485 · 11 days |
| 07:00 | 96.9% | 0.5 min late | 3.9 min late | 1,479 · 11 days |
| 08:00 | 70.6% | 2.8 min late | 12.5 min late | 1,723 · 11 days |
| 09:00 | 84.6% | 1.4 min late | 9.4 min late | 1,915 · 12 days |
| 10:00 | 95.8% | 0 min late | 4.8 min late | 1,946 · 12 days |
| 11:00 | 99.0% | 0.4 min early | 3.4 min late | 1,930 · 12 days |
| 12:00 | 97.8% | 0.3 min late | 3.7 min late | 1,915 · 12 days |
| 13:00 | 94.5% | 0.1 min late | 5.1 min late | 1,992 · 13 days |
| 14:00 | 91.2% | 0.4 min late | 5.8 min late | 1,894 · 12 days |
| 15:00 | 89.7% | 0.2 min late | 7.2 min late | 1,903 · 12 days |
| 16:00 | 79.8% | 1.4 min late | 9.8 min late | 1,967 · 12 days |
| 17:00 | 61.0% | 3.6 min late | 15.2 min late | 1,896 · 12 days |
| 18:00 | 89.9% | 1.9 min late | 8.1 min late | 1,914 · 12 days |
| 19:00 | 90.9% | 0.9 min late | 6.2 min late | 1,940 · 12 days |
| 20:00 | 88.1% | 0.7 min late | 7.3 min late | 2,051 · 12 days |
| 21:00 | 91.5% | 0.5 min late | 5.8 min late | 1,927 · 12 days |
| 22:00 | 92.2% | 1 min late | 5.8 min late | 1,387 · 12 days |
| 23:00 | 93.9% | 0.2 min late | 6.5 min late | 859 · 12 days |
1 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
410 / 482 scheduled trips published at least one position across 1 service days (85.1%).
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.
The current public route group, its published schedule variants and stop patterns, current operations, and matching observed reliability where available.
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.
Rider evidence
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.
