Skip to main content
Otranspo
FR

Route

61

OC Transpo

Tunney's Pasture & N Rideau ↔ Stittsville
All imported trips are marked accessible.Imported schedule valid through: Oct 4, 2026

Verdict

What this route needs

Timetable short by 3.8 min in 2 hours of the day.

Unreliable 18:00: a bad trip runs 23.7 min behind a normal one.

16:00 drops to 55% on time, against 78% the rest of the day.

Fix: 4 min more running time on 111 trips. No extra buses.

This changes running time only. It does not move departure times, rewrite headways, or check that a driver’s shift still fits, and a scheduler has to.

Arrivals within five minutes, by hour of day, last 14 days, 24 hours measured
  1. 00:00: 84.5% of arrivals on time, 741 arrivals, typically 0.9 min late
  2. 01:00: 69% of arrivals on time, 587 arrivals, typically 2 min late
  3. 02:00: 87.6% of arrivals on time, 857 arrivals, typically 1.6 min late
  4. 03:00: 87.9% of arrivals on time, 321 arrivals, typically 0.9 min early
  5. 04:00: 88.5% of arrivals on time, 417 arrivals, typically 0.4 min late
  6. 05:00: 97.2% of arrivals on time, 563 arrivals, typically 0.8 min late
  7. 06:00: 88.1% of arrivals on time, 1,350 arrivals, typically 1.1 min late
  8. 07:00: 78.9% of arrivals on time, 1,558 arrivals, typically 2.6 min late
  9. 08:00: 81% of arrivals on time, 1,095 arrivals, typically 0.7 min late
  10. 09:00: 91.4% of arrivals on time, 1,082 arrivals, typically 0.6 min late
  11. 10:00: 77% of arrivals on time, 1,094 arrivals, typically 1.4 min late
  12. 11:00: 87% of arrivals on time, 1,466 arrivals, typically 0.3 min late
  13. 12:00: 77.1% of arrivals on time, 1,142 arrivals, typically 0.4 min late
  14. 13:00: 67.6% of arrivals on time, 1,165 arrivals, typically 2.9 min late
  15. 14:00: 61% of arrivals on time, 1,317 arrivals, typically 2.9 min late
  16. 15:00: 76.8% of arrivals on time, 1,092 arrivals, typically 1.5 min late
  17. 16:00: 55.3% of arrivals on time, 949 arrivals, typically 3.6 min late
  18. 17:00: 57.4% of arrivals on time, 861 arrivals, typically 4.1 min late
  19. 18:00: 65.7% of arrivals on time, 1,099 arrivals, typically 2.4 min late. Unreliable: a bad trip runs far behind a normal one.
  20. 19:00: 72.1% of arrivals on time, 956 arrivals, typically 1.5 min late
  21. 20:00: 74% of arrivals on time, 791 arrivals, typically 1.3 min late
  22. 21:00: 72.7% of arrivals on time, 717 arrivals, typically 1.4 min late
  23. 22:00: 87.5% of arrivals on time, 937 arrivals, typically 0.8 min late
  24. 23:00: 92.1% of arrivals on time, 870 arrivals, typically 0.5 min late
  • 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
WhatWhenMeasuredFix
ProblemLate by the timetable16:00 to 18:003.8 min lateMore running time
ProblemUnreliable18:0023.7 min swingOperations, not the timetable
ProblemOne hour collapses16:0055%Operations, not the timetable
Measurements
Late by the timetable · 16:00 to 18:00
medianDelaySeconds 228
spreadSeconds 1,029.5
observations 1,810
hoursAffected 2
suggestedRunningTimeChangeMinutes 3.8
Unreliable · 18:00
medianDelaySeconds 142
spreadSeconds 1,424
observations 1,099
hoursAffected 1
suggestedRunningTimeChangeMinutes 2.4
One hour collapses · 16:00
hour 16
onTimePct 55.3
routeMedianOnTimePct 78
shortfallPoints 22.7
observations 949
16:00 77→8116:00 71→7517:00 76→8017:00 72→76

Route check

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

72 in 100 arrivals were within 5 minutes of schedule · 36,178 arrivals checked

Confidence in this summary: High

Based on 36,178 arrivals over 19 weekdays, from Aug 8, 2026 to Sep 7, 2026.

Updated Sep 7, 2026, 11:34 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. 4 p.m.–5 p.m.: 45 in 100 arrivals were more than 5 minutes early or late (949 arrivals over 10 days).
  2. 5 p.m.–6 p.m.: 43 in 100 arrivals were more than 5 minutes early or late (861 arrivals over 11 days).
  3. 2 p.m.–3 p.m.: 39 in 100 arrivals were more than 5 minutes early or late (1,317 arrivals over 9 days).
  4. 6 p.m.–7 p.m.: 34 in 100 arrivals were more than 5 minutes early or late (1,099 arrivals over 8 days).

2 current notices affect this route

  • • Stop impacts: #3019 -- Pinecrest A and B relocation
  • • NCC Weekend Bikedays: Routes 57, 61, 62, 63, 74, 75, 87 to detour

Problem places

  1. HAZELDEAN / TERRY FOX

    54 in 100 arrivals were more than 5 minutes early or late (262 arrivals over 25 days).

    Open this stop
  2. HAZELDEAN / FRINGEWOOD

    54 in 100 arrivals were more than 5 minutes early or late (263 arrivals over 24 days).

    Open this stop
  3. HAZELDEAN / IBER

    53 in 100 arrivals were more than 5 minutes early or late (264 arrivals over 25 days).

    Open this stop
  4. HAZELDEAN / LOWE'S

    53 in 100 arrivals were more than 5 minutes early or late (262 arrivals over 25 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 11

Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.

Possible no-shows after checking feed gaps?
330 of 670 checked trips need a closer look

330 of 670 trips with enough public-feed evidence had no matching position over 7 days. 51 of 721 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 15.1 min late

72 in 100 arrivals were within 5 minutes of schedule.

Do buses bunch or leave long gaps?
7.2 min average predicted wait

0.9 min beyond the scheduled wait, based on 549 arrivals at 5 high-frequency stops over 9 days.

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.

Before

Service date checked: August 31, 2026

Scheduled trips
116
Distinct scheduled stops
150
Distinct published paths
15
Published service span
03:54–27:41

Feed fingerprint: ecc28a3727bcaff4 · 345fd07d-fb05-4eaa-8ec2-3daf8b7fcbe9

New schedule

Service date checked: September 7, 2026

Scheduled trips
85
Distinct scheduled stops
142
Distinct published paths
8
Published service span
05:15–27:12

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 20,061 arrivals over 13 days; after has 3,774 arrivals over 4 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.

Would you count on route 61?

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.

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 · 150 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: CASTLEFRANK / KATIMAVIK, CASTLEFRANK / MCCURDY, CASTLEFRANK / KAKULU, CASTLEFRANK / HUNGERFORD, HAZELDEAN / TERRY FOX 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 8, 2026

Towards Rideau
6 scheduled trips
3:54 a.m.–3:41 a.m. (next day)
30 min median scheduled gap
Towards Tunney's Pasture
54 scheduled trips
4:24 a.m.–12:56 a.m. (next day)
24 min median scheduled gap
Towards Stittsville
39 scheduled trips
5:20 a.m.–12:33 a.m. (next day)
30 min median scheduled gap
Towards Terry Fox
17 scheduled trips
4:05 a.m.–3:31 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 Rideau

    Starts at TERRY FOX 4A

    Provider prediction · Scheduled 2:11 a.m.

    TERRY FOX 4AOpen scheduled trip

  2. Towards Terry Fox

    Starts at RIDEAU A

    Provider prediction · Scheduled 2:11 a.m.

    RIDEAU AOpen scheduled trip

  3. Towards Rideau

    Starts at TERRY FOX 4A

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

    TERRY FOX 4AOpen scheduled trip

  4. Towards Terry Fox

    Starts at RIDEAU A

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

    RIDEAU AOpen scheduled trip

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

Buses seen now

5 current vehicle positions match this route.

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

Official notices

  • Stop impacts: #3019 -- Pinecrest A and B relocation

    Timing not published by the operator
    Read notice →

  • NCC Weekend Bikedays: Routes 57, 61, 62, 63, 74, 75, 87 to detour

    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 8, 2:09 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 8, 2026 to September 7, 2026

Within 5 minutes of schedule
71.6%
Arrivals checked
36,178
Weekdays with data
19
How late the worst 5 in 100 were
15.1 min late
Patterns by hour (24)
HourOn timeMedianWorst 5 in 100Evidence
00:0084.5%0.9 min late6.7 min late741 · 7 days
01:0069.0%2 min late9.4 min late587 · 7 days
02:0087.6%1.6 min late6 min late857 · 9 days
03:0087.9%0.9 min early3.7 min late321 · 9 days
04:0088.5%0.4 min late6.4 min late417 · 5 days
05:0097.2%0.8 min late4.3 min late563 · 6 days
06:0088.1%1.1 min late6.9 min late1,350 · 7 days
07:0078.9%2.6 min late8.6 min late1,558 · 8 days
08:0081.0%0.7 min late8.4 min late1,095 · 9 days
09:0091.4%0.6 min late5.4 min late1,082 · 9 days
10:0077.0%1.4 min late8.6 min late1,094 · 8 days
11:0087.0%0.3 min late7.1 min late1,466 · 7 days
12:0077.1%0.4 min late10.2 min late1,142 · 9 days
13:0067.6%2.9 min late13.4 min late1,165 · 9 days
14:0061.0%2.9 min late11.5 min late1,317 · 9 days
15:0076.8%1.5 min late13.5 min late1,092 · 9 days
16:0055.3%3.6 min late18 min late949 · 10 days
17:0057.4%4.1 min late23.9 min late861 · 11 days
18:0065.7%2.4 min late26.1 min late1,099 · 8 days
19:0072.1%1.5 min late14.3 min late956 · 8 days
20:0074.0%1.3 min late17.2 min late791 · 8 days
21:0072.7%1.4 min late15 min late717 · 7 days
22:0087.5%0.8 min late7.5 min late937 · 8 days
23:0092.1%0.5 min late6.2 min late870 · 9 days

6 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

339 / 636 scheduled trips published at least one position across 6 service days (53.3%).

  • 14:0022 / 36 trips without a position38.9%
  • 00:0011 / 20 trips without a position45.0%
  • 23:0013 / 25 trips without a position48.0%
  • 01:0012 / 24 trips without a position50.0%
  • 06:0012 / 24 trips without a position50.0%
  • 16:0016 / 32 trips without a position50.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.

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

17 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 Rideau: CARDELREC-GOULBOURN COMPLEX to RIDEAU B

    75 stops · 20 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    10 official service records

    2 added dates and 18 removed dates

    View stops and calendar →

  • Towards Rideau: TERRY FOX 4A to RIDEAU B

    36 stops · 71 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 Tunney's Pasture: CARDELREC-GOULBOURN COMPLEX to TUNNEY'S PASTURE C

    59 stops · 212 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 Tunney's Pasture: CARDELREC-GOULBOURN COMPLEX to TUNNEY'S PASTURE C

    59 stops · 155 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Tunney's Pasture: TERRY FOX 4A to TUNNEY'S PASTURE C

    24 stops · 5 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Tunney's Pasture: TERRY FOX 4A to TUNNEY'S PASTURE C

    24 stops · 10 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Tunney's Pasture: TERRY FOX 4A to TUNNEY'S PASTURE C

    20 stops · 53 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

    Published weekly days: Monday, Saturday, Sunday

    7 official service records

    3 added dates and 22 removed dates

    View stops and calendar →

  • Towards Tunney's Pasture: TERRY FOX 4A to TUNNEY'S PASTURE C

    20 stops · 70 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Stittsville: RIDEAU A to CARDELREC-GOULBOURN COMPLEX

    73 stops · 19 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

    Published weekly days: Monday, Saturday, Sunday

    7 official service records

    3 added dates and 22 removed dates

    View stops and calendar →

  • Towards Stittsville: TUNNEY'S PASTURE B to CARDELREC-GOULBOURN COMPLEX

    63 stops · 10 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Stittsville: TUNNEY'S PASTURE B to CARDELREC-GOULBOURN COMPLEX

    62 stops · 5 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Stittsville: TUNNEY'S PASTURE B to CARDELREC-GOULBOURN COMPLEX

    59 stops · 209 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 Stittsville: TUNNEY'S PASTURE B to CARDELREC-GOULBOURN COMPLEX

    58 stops · 165 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Terry Fox: RIDEAU A to TERRY FOX 3C

    37 stops · 10 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

  • Towards Terry Fox: RIDEAU A to TERRY FOX 3C

    33 stops · 64 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 Terry Fox: TUNNEY'S PASTURE B to TERRY FOX 3C

    19 stops · 61 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 Terry Fox: TUNNEY'S PASTURE B to TERRY FOX 3C

    18 stops · 40 imported trips

    Scheduled from Sep 4, 2026 to Oct 4, 2026

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

    5 official service records

    0 added dates and 1 removed date

    View stops and calendar →

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
36,178 settled arrivals across 1 matching reliability records.
Coverage
17 published stop patterns containing 739 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.
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.