Skip to main content
Otranspo
FR

OC Transpo · Regular service

Route 111

Billings Bridge · Carleton · Baseline · Merivale

Current service date
Sep 19, 2026
Selected direction
Every published direction
Imported schedule valid through
Oct 18, 2026

All imported trips are marked accessible.

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.

Service date
September 19, 2026
Official notices
2 matching notices
Current buses
2 buses observed

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 · 108 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.

Repeated problem stops: MEADOWLANDS / CLAYMORE, MEADOWLANDS / DEBRA, PRINCE OF WALES / HOG'S BACK, PRINCE OF WALES / DYNES, PRINCE OF WALES / SANFORD and 7 more. These are highlighted from route-specific settled arrivals with at least 60 observations over 3 days; the pattern does not prove a cause.

Open the full-screen map →
Today’s schedule

Service date September 19, 2026

Towards Billings Bridge
38 scheduled trips
5:35 a.m.–12:44 a.m. (next day)
30 min median scheduled gap
Towards Baseline
37 scheduled trips
5:35 a.m.–12:23 a.m. (next day)
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.

  1. Towards Billings Bridge

    Starts at BASELINE 1B

    Provider prediction · Scheduled 2:35 p.m.

    BASELINE 1BOpen scheduled trip

  2. Towards Baseline

    Starts at BILLINGS BRIDGE 3B

    Provider prediction · Scheduled 2:35 p.m.

    BILLINGS BRIDGE 3BOpen scheduled trip

  3. Towards Billings Bridge

    Starts at BASELINE 1B

    Timetable only. No usable prediction is available for this trip.

    BASELINE 1BOpen scheduled trip

  4. Towards Baseline

    Starts at BILLINGS BRIDGE 3B

    Provider prediction · Scheduled 3:05 p.m.

    BILLINGS BRIDGE 3BOpen scheduled trip

Showing 4 of 12 trips. Open a stop for its full departure board.

Buses seen now

2 current vehicle positions match this route.

The feed identifier is not a verified physical bus or fleet number.

Official notices

  • Detour: CityFolk Festival (Route 111)

    Timing not published by the operator
    Read notice →

  • Detour: Routes 7, 10, 48, 111 during Campus Avenue closure (Carleton University)

    Timing not published by the operator
    Read notice →
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 19, 2:30 p.m.

See all stops and route patterns

Stops and stations

8 official stop patterns

Each row below is one exact stop order published in the official schedule. Short turns and alternate destinations stay separate.

Choose a direction or stop pattern
Clear selection

  • Towards Billings Bridge: MERIVALE H.S (STUDENTS ONLY) to BILLINGS BRIDGE 4C

    38 stops · 18 imported trips

    Scheduled from Sep 18, 2026 to Oct 18, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday

    9 official service records

    2 added dates and 18 removed dates

    View stops and calendar →

  • Towards Billings Bridge: BASELINE 1B to BILLINGS BRIDGE 4C

    34 stops · 342 imported trips

    Scheduled from Sep 18, 2026 to Oct 18, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday

    9 official service records

    2 added dates and 18 removed dates

    View stops and calendar →

  • Towards Billings Bridge: BASELINE 1B to BILLINGS BRIDGE 3C

    34 stops · 172 imported trips

    Scheduled from Sep 18, 2026 to Oct 18, 2026

    Published weekly days: Monday, Saturday, Sunday

    5 official service records

    3 added dates and 13 removed dates

    View stops and calendar →

  • Towards Carleton: BASELINE 1B to CARLETON A

    39 stops · 288 imported trips

    Scheduled from Sep 18, 2026 to Oct 18, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday

    9 official service records

    2 added dates and 18 removed dates

    View stops and calendar →

  • Towards Baseline: CARLETON A to BASELINE 2A

    40 stops · 261 imported trips

    Scheduled from Sep 18, 2026 to Oct 18, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday

    9 official service records

    2 added dates and 18 removed dates

    View stops and calendar →

  • Towards Baseline: BILLINGS BRIDGE 3B to BASELINE 2A

    38 stops · 527 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

    View stops and calendar →

  • Towards Baseline: ST PIUS HS to BASELINE 2B

    31 stops · 18 imported trips

    Scheduled from Sep 18, 2026 to Oct 18, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday

    9 official service records

    2 added dates and 18 removed dates

    View stops and calendar →

  • Towards Merivale: BILLINGS BRIDGE 3B to MERIVALE H.S (STUDENTS ONLY)

    37 stops · 18 imported trips

    Scheduled from Sep 18, 2026 to Oct 18, 2026

    Published weekly days: Monday, Tuesday, Wednesday, Thursday, Friday

    9 official service records

    2 added dates and 18 removed dates

    View stops and calendar →

Official feed version 99de510d-89b0-4652-9d93-217659284cf2

Source checksum 2f30d876ae731cae79cf274d036530bb78b0c14f6e0e994d1ad32ca16291b367

Would you count on route 111?

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.

Download evidence image

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.

Open history, reliability and route analysis

Verdict

What this route needs

Timetable short by 3.5 to 5.9 min in 8 hours of the day.

Buses leave about 2.7 min late and lose another 2.2 min along the route.

09:00 drops to 43% on time, against 73% the rest of the day.

Scenario: 4 to 6 min more running time on 697 trips. The schedule-block model estimates 92 additional 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.

Arrivals within five minutes, by hour of day, last 14 days, 21 hours measured
  1. 00:00: 93.1% of arrivals on time, 928 arrivals, typically 0.3 min late
  2. 01:00: 100% of arrivals on time, 216 arrivals, typically 0.4 min early
  3. 02:00: not enough data
  4. 03:00: not enough data
  5. 04:00: not enough data
  6. 05:00: 87.3% of arrivals on time, 861 arrivals, typically 2.1 min late
  7. 06:00: 91.8% of arrivals on time, 2,561 arrivals, typically 1.4 min late
  8. 07:00: 72.8% of arrivals on time, 3,271 arrivals, typically 2.6 min late
  9. 08:00: 45.9% of arrivals on time, 2,933 arrivals, typically 5.7 min late
  10. 09:00: 42.8% of arrivals on time, 3,171 arrivals, typically 6.1 min late
  11. 10:00: 81.8% of arrivals on time, 2,913 arrivals, typically 1.7 min late
  12. 11:00: 81.1% of arrivals on time, 3,043 arrivals, typically 1.7 min late
  13. 12:00: 77.8% of arrivals on time, 3,018 arrivals, typically 2.6 min late
  14. 13:00: 75.7% of arrivals on time, 3,065 arrivals, typically 2.5 min late
  15. 14:00: 73.4% of arrivals on time, 3,661 arrivals, typically 2.3 min late
  16. 15:00: 76.6% of arrivals on time, 2,838 arrivals, typically 2.4 min late
  17. 16:00: 54.9% of arrivals on time, 2,952 arrivals, typically 4.3 min late
  18. 17:00: 55% of arrivals on time, 2,675 arrivals, typically 4.3 min late
  19. 18:00: 61.8% of arrivals on time, 2,847 arrivals, typically 3.2 min late
  20. 19:00: 69.6% of arrivals on time, 3,020 arrivals, typically 2.7 min late
  21. 20:00: 59.8% of arrivals on time, 3,112 arrivals, typically 4 min late
  22. 21:00: 66.7% of arrivals on time, 2,970 arrivals, typically 3.2 min late
  23. 22:00: 73% of arrivals on time, 2,004 arrivals, typically 3.5 min late
  24. 23:00: 79.8% of arrivals on time, 1,213 arrivals, typically 1.7 min late
  • 90% or more on time
  • 80 to 90% on time
  • under 80% on time
  • not enough data
WhatWhenMeasuredScenario or next investigation
ProblemLate by the timetable08:00 to 10:00 · 16:00 to 19:00 · 20:00 to 23:005.9 min late … 3.5 min lateMore running time
ProblemOne hour collapses09:0043%Operations, not the timetable
Measurements
Late by the timetable · 16:00 to 19:00
medianDelaySeconds 259
spreadSeconds 892
observations 8,474
hoursAffected 3
suggestedRunningTimeChangeMinutes 4.3
Late by the timetable · 08:00 to 10:00
medianDelaySeconds 352
spreadSeconds 729
observations 6,104
hoursAffected 2
suggestedRunningTimeChangeMinutes 5.9
Late by the timetable · 20:00 to 23:00
medianDelaySeconds 212
spreadSeconds 498
observations 8,086
hoursAffected 3
suggestedRunningTimeChangeMinutes 3.5
One hour collapses · 09:00
hour 9
onTimePct 42.8
routeMedianOnTimePct 73.4
shortfallPoints 30.6
observations 3,171
08:00 29→3508:00 30→3609:00 28→3409:00 29→3516:00 34→3816:00 35→3917:00 34→3817:00 36→4018:00 31→3518:00 32→3620:00 25→2920:00 30→3421:00 25→2921:00 27→3122:00 22→2622:00 27→31

Route check

How route 111 is doing

A plain-language summary of the strongest evidence we have. We say when the data cannot answer a question.

Bottom line

Service is unreliable often enough to affect riders.

71 in 100 arrivals were within 5 minutes of schedule · 69,778 arrivals checked

Confidence in this summary: High

Based on 69,778 arrivals over 20 weekdays, from Aug 20, 2026 to Sep 19, 2026.

Updated Sep 19, 2026, 1:32 p.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.

  1. 9 a.m.–10 a.m.: 57 in 100 arrivals were more than 5 minutes early or late (3,171 arrivals over 13 days).
  2. 8 a.m.–9 a.m.: 54 in 100 arrivals were more than 5 minutes early or late (2,933 arrivals over 11 days).
  3. 4 p.m.–5 p.m.: 45 in 100 arrivals were more than 5 minutes early or late (2,952 arrivals over 12 days).
  4. 5 p.m.–6 p.m.: 45 in 100 arrivals were more than 5 minutes early or late (2,675 arrivals over 12 days).

2 current notices affect this route

  • • Detour: CityFolk Festival (Route 111)
  • • Detour: Routes 7, 10, 48, 111 during Campus Avenue closure (Carleton University)

Problem places

  1. CAMPUS / COMMONS

    74 in 100 arrivals were more than 5 minutes early or late (366 arrivals over 18 days).

    Open this stop
  2. UNIVERSITY / STADIUM

    68 in 100 arrivals were more than 5 minutes early or late (366 arrivals over 18 days).

    Open this stop
  3. CARLETON B

    63 in 100 arrivals were more than 5 minutes early or late (363 arrivals over 18 days).

    Open this stop
  4. BILLINGS BRIDGE 3C

    58 in 100 arrivals were more than 5 minutes early or late (222 arrivals over 7 days).

    Open this stop

These are route-specific settled arrivals. They identify a repeated location and time difference, but do not prove the 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?
152 of 861 checked trips need a closer look152 of 861 trips with enough public-feed evidence had no matching position over 7 days. 2 of 863 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
How late does this route get?
The slowest 5 in 100 were more than about 13.7 min late71 in 100 arrivals were within 5 minutes of schedule.
Do buses bunch or leave long gaps?
7.7 min average predicted wait0.8 min beyond the scheduled wait, based on 2,875 arrivals at 46 high-frequency stops over 12 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 September 18, 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: September 14, 2026

Scheduled trips
145
Distinct scheduled stops
108
Distinct published paths
7
Published service span
5:11 a.m.–1:11 a.m. next day

Operator calendar-date records: 0 added · 3 removed

Feed fingerprint: d6d50360bb16d494 · 151dbfc4-6745-4fbd-9eef-6885ecb708f4

New schedule

Service date checked: September 21, 2026

Scheduled trips
145
Distinct scheduled stops
108
Distinct published paths
7
Published service span
5:11 a.m.–1:11 a.m. next day

Operator calendar-date records: 0 added · 2 removed

Feed fingerprint: 2f30d876ae731cae · 99de510d-89b0-4652-9d93-217659284cf2

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 48,311 arrivals over 14 days; after has 5,151 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.

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
  1. Official current feed: explicit cancellations, skipped stops and active notices.
  2. Matched observations: vehicle positions and settled predictions tied to the official schedule.
  3. Official timetable: what was planned, kept separate from what was observed.
  4. Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.

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 20, 2026 to September 19, 2026

Within 5 minutes of schedule
71.1%
Arrivals checked
69,778
Weekdays with data
20
How late the worst 5 in 100 were
13.7 min late
Patterns by hour (21)
HourOn timeMedianWorst 5 in 100Evidence
00:0093.1%0.3 min late6.7 min late928 · 10 days
01:00100.0%0.4 min early0.8 min late216 · 9 days
05:0087.3%2.1 min late6.1 min late861 · 10 days
06:0091.8%1.4 min late5.5 min late2,561 · 11 days
07:0072.8%2.6 min late10.4 min late3,271 · 11 days
08:0045.9%5.7 min late18.3 min late2,933 · 11 days
09:0042.8%6.1 min late17.8 min late3,171 · 13 days
10:0081.8%1.7 min late9 min late2,913 · 12 days
11:0081.1%1.7 min late8.7 min late3,043 · 12 days
12:0077.8%2.6 min late10.8 min late3,018 · 12 days
13:0075.7%2.5 min late9.5 min late3,065 · 12 days
14:0073.4%2.3 min late12.7 min late3,661 · 12 days
15:0076.6%2.4 min late10.8 min late2,838 · 12 days
16:0054.9%4.3 min late16.5 min late2,952 · 12 days
17:0055.0%4.3 min late19.2 min late2,675 · 12 days
18:0061.8%3.2 min late20.3 min late2,847 · 12 days
19:0069.6%2.7 min late14.5 min late3,020 · 12 days
20:0059.8%4 min late12.3 min late3,112 · 12 days
21:0066.7%3.2 min late15.5 min late2,970 · 13 days
22:0073.0%3.5 min late9.3 min late2,004 · 12 days
23:0079.8%1.7 min late10.4 min late1,213 · 12 days

8 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

709 / 863 scheduled trips published at least one position across 6 service days (82.2%).

  • 14:0014 / 68 trips without a position79.4%
  • 00:003 / 16 trips without a position81.3%
  • 13:009 / 48 trips without a position81.3%
  • 16:009 / 48 trips without a position81.3%
  • 18:009 / 48 trips without a position81.3%
  • 19:009 / 48 trips without a position81.3%

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.

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
69,778 settled arrivals across 1 matching reliability records.
Coverage
8 published stop patterns containing 291 stop calls are available on this page.
Method or data version
last-prediction-within-ten-minutes-v1; 99de510d-89b0-4652-9d93-217659284cf2; 2f30d876ae731cae79cf274d036530bb78b0c14f6e0e994d1ad32ca16291b367

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.
Suggest a factual correction →

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.