Skip to main content
Otranspo
FR

OC Transpo · Regular service

Route 6

Billings Bridge · Greenboro · Rideau · Rockcliffe

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
1 matching notice
Current buses
10 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 · 120 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: SOUTH KEYS A, DALHOUSIE / RIDEAU, DALHOUSIE / CLARENCE, MURRAY / DALHOUSIE, MURRAY / CUMBERLAND 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
16 scheduled trips
9:23 a.m.–2:22 a.m. (next day)
29 min median scheduled gap
Towards Greenboro
58 scheduled trips
5:35 a.m.–1:37 a.m. (next day)
17 min median scheduled gap
Towards Rideau
21 scheduled trips
4:58 a.m.–1:48 a.m. (next day)
30 min median scheduled gap
Towards Rockcliffe
53 scheduled trips
6:28 a.m.–12:33 a.m. (next day)
15 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 Rockcliffe

    Starts at GREENBORO B

    Origin stop explicitly skipped in the current provider feed

    GREENBORO BOpen scheduled trip

  2. Towards Greenboro

    Starts at MAPLE LANE / SPRINGFIELD

    Provider prediction · Scheduled 1:38 p.m.

    MAPLE LANE / SPRINGFIELDOpen scheduled trip

  3. Towards Rockcliffe

    Starts at GREENBORO B

    Provider prediction · Scheduled 1:44 p.m.

    GREENBORO BOpen scheduled trip

  4. Towards Greenboro

    Starts at MAPLE LANE / SPRINGFIELD

    Provider prediction · Scheduled 1:50 p.m.

    MAPLE LANE / SPRINGFIELDOpen scheduled trip

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

Buses seen now

10 current vehicle positions match this route.

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

Official notices

  • Detour: Downtown routes 5, 6, 7, 9, 10, 11, 12, 14, 18, 19, 39, 45, 57, 61, 75, 105, during Canada Army Run

    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, 1:33 p.m.

See all stops and route patterns

Stops and stations

6 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: RIDEAU A to BILLINGS BRIDGE 4B

    25 stops · 218 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 Greenboro: MAPLE LANE / SPRINGFIELD to GREENBORO C

    61 stops · 720 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 Greenboro: RIDEAU A to GREENBORO C

    47 stops · 44 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 Rideau: GREENBORO B to RIDEAU B

    47 stops · 36 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 Rideau: BILLINGS BRIDGE 4C to RIDEAU B

    25 stops · 231 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 Rockcliffe: GREENBORO B to MAPLE LANE / SPRINGFIELD

    61 stops · 733 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 →

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

Source checksum 2f30d876ae731cae79cf274d036530bb78b0c14f6e0e994d1ad32ca16291b367

Would you count on route 6?

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.3 to 3.8 min in 3 hours of the day.

Buses already leave about 3.1 min late and hold it to the end. The running time is right; the terminal is the problem.

Gaps All measured hours: waits run 1.6 min longer than the timetable promises.

Next investigation: test terminal recovery and the preceding trip. The arrival pattern alone does not establish the cause.

Arrivals within five minutes, by hour of day, last 14 days, 23 hours measured
  1. 00:00: 84.2% of arrivals on time, 1,336 arrivals, typically 1.6 min late
  2. 01:00: 96.2% of arrivals on time, 939 arrivals, typically 1.5 min late
  3. 02:00: 100% of arrivals on time, 184 arrivals, typically 1.7 min late
  4. 03:00: not enough data
  5. 04:00: 84.9% of arrivals on time, 390 arrivals, typically 3.3 min late
  6. 05:00: 95% of arrivals on time, 1,689 arrivals, typically 1.8 min late
  7. 06:00: 93.2% of arrivals on time, 3,015 arrivals, typically 1.1 min late
  8. 07:00: 77.1% of arrivals on time, 4,295 arrivals, typically 2 min late
  9. 08:00: 71.2% of arrivals on time, 5,515 arrivals, typically 2.4 min late
  10. 09:00: 74.5% of arrivals on time, 5,105 arrivals, typically 2 min late
  11. 10:00: 70.3% of arrivals on time, 5,467 arrivals, typically 1.8 min late
  12. 11:00: 76.5% of arrivals on time, 5,191 arrivals, typically 1.8 min late
  13. 12:00: 66.7% of arrivals on time, 5,264 arrivals, typically 2.9 min late
  14. 13:00: 68.9% of arrivals on time, 5,352 arrivals, typically 2.3 min late
  15. 14:00: 64.5% of arrivals on time, 4,543 arrivals, typically 2.6 min late
  16. 15:00: 62.2% of arrivals on time, 4,031 arrivals, typically 3 min late
  17. 16:00: 59.5% of arrivals on time, 4,637 arrivals, typically 3.7 min late
  18. 17:00: 56.8% of arrivals on time, 6,059 arrivals, typically 3.9 min late
  19. 18:00: 66.2% of arrivals on time, 6,095 arrivals, typically 2.7 min late
  20. 19:00: 70.3% of arrivals on time, 4,240 arrivals, typically 2.1 min late
  21. 20:00: 72% of arrivals on time, 3,149 arrivals, typically 2 min late
  22. 21:00: 65.1% of arrivals on time, 2,637 arrivals, typically 2.1 min late
  23. 22:00: 71.9% of arrivals on time, 2,768 arrivals, typically 2 min late
  24. 23:00: 81.3% of arrivals on time, 2,573 arrivals, typically 1.6 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 timetable04:00 · 16:00 to 18:003.3 min late · 3.8 min lateRecovery time at the terminal
ProblemLong gaps on a frequent routeAll measured hours1.6 min extra waitManage the headway
Measurements
Late by the timetable · 16:00 to 18:00
medianDelaySeconds 227
spreadSeconds 825
observations 10,696
hoursAffected 2
suggestedRunningTimeChangeMinutes 3.8
Long gaps on a frequent route · All measured hours
excessWaitSeconds 95.1
scheduledWaitSeconds 315
excessSharePct 30.2
matchedArrivals 11,564
stopCount 119
Late by the timetable · 04:00
medianDelaySeconds 198
spreadSeconds 136
observations 390
hoursAffected 1
suggestedRunningTimeChangeMinutes 3.3
04:00 28→3116:00 66→7016:00 69→7317:00 56→6017:00 67→71

Route check

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

70 in 100 arrivals were within 5 minutes of schedule · 114,049 arrivals checked

Confidence in this summary: High

Based on 114,049 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. 5 p.m.–6 p.m.: 43 in 100 arrivals were more than 5 minutes early or late (6,059 arrivals over 14 days).
  2. 4 p.m.–5 p.m.: 41 in 100 arrivals were more than 5 minutes early or late (4,637 arrivals over 14 days).
  3. 3 p.m.–4 p.m.: 38 in 100 arrivals were more than 5 minutes early or late (4,031 arrivals over 14 days).
  4. 2 p.m.–3 p.m.: 36 in 100 arrivals were more than 5 minutes early or late (4,543 arrivals over 14 days).

1 current notice affects this route

  • • Detour: Downtown routes 5, 6, 7, 9, 10, 11, 12, 14, 18, 19, 39, 45, 57, 61, 75, 105, during Canada Army Run

Problem places

  1. MURRAY / KING EDWARD

    61 in 100 arrivals were more than 5 minutes early or late (848 arrivals over 26 days).

    Open this stop
  2. MURRAY / DALHOUSIE

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

    Open this stop
  3. MURRAY / CUMBERLAND

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

    Open this stop
  4. DALHOUSIE / CLARENCE

    57 in 100 arrivals were more than 5 minutes early or late (840 arrivals over 26 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?
170 of 1,006 checked trips need a closer look170 of 1,006 trips with enough public-feed evidence had no matching position over 7 days. 0 of 1,006 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 14.4 min late70 in 100 arrivals were within 5 minutes of schedule.
Do buses bunch or leave long gaps?
6.8 min average predicted wait1.6 min beyond the scheduled wait, based on 11,564 arrivals at 119 high-frequency stops over 18 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
148
Distinct scheduled stops
120
Distinct published paths
6
Published service span
4:35 a.m.–2:19 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
148
Distinct scheduled stops
120
Distinct published paths
6
Published service span
4:35 a.m.–2:19 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 77,184 arrivals over 14 days; after has 7,414 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
69.9%
Arrivals checked
114,049
Weekdays with data
20
How late the worst 5 in 100 were
14.4 min late
Patterns by hour (23)
HourOn timeMedianWorst 5 in 100Evidence
00:0084.2%1.6 min late9.6 min late1,336 · 12 days
01:0096.2%1.5 min late4.7 min late939 · 12 days
02:00100.0%1.7 min late4.3 min late184 · 8 days
04:0084.9%3.3 min late5.6 min late390 · 10 days
05:0095.0%1.8 min late4.7 min late1,689 · 10 days
06:0093.2%1.1 min late5.4 min late3,015 · 11 days
07:0077.1%2 min late8.8 min late4,295 · 11 days
08:0071.2%2.4 min late10.2 min late5,515 · 11 days
09:0074.5%2 min late10.3 min late5,105 · 12 days
10:0070.3%1.8 min late11.7 min late5,467 · 12 days
11:0076.5%1.8 min late10.9 min late5,191 · 13 days
12:0066.7%2.9 min late14.5 min late5,264 · 13 days
13:0068.9%2.3 min late12.1 min late5,352 · 13 days
14:0064.5%2.6 min late16.8 min late4,543 · 14 days
15:0062.2%3 min late20.1 min late4,031 · 14 days
16:0059.5%3.7 min late18 min late4,637 · 14 days
17:0056.8%3.9 min late17.1 min late6,059 · 14 days
18:0066.2%2.7 min late15.6 min late6,095 · 12 days
19:0070.3%2.1 min late14.8 min late4,240 · 13 days
20:0072.0%2 min late16.1 min late3,149 · 13 days
21:0065.1%2.1 min late12.2 min late2,637 · 13 days
22:0071.9%2 min late13.4 min late2,768 · 12 days
23:0081.3%1.6 min late8.8 min late2,573 · 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

836 / 1,006 scheduled trips published at least one position across 7 service days (83.1%).

  • 21:007 / 28 trips without a position75.0%
  • 08:0015 / 74 trips without a position79.7%
  • 20:007 / 35 trips without a position80.0%
  • 17:0014 / 77 trips without a position81.8%
  • 18:0011 / 61 trips without a position82.0%
  • 05:005 / 28 trips without a position82.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.

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
114,049 settled arrivals across 1 matching reliability records.
Coverage
6 published stop patterns containing 266 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.