Skip to main content
Otranspo
FR

OC Transpo · Regular service

Route 17

Wateridge · Parliament ~ Parlement

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
No matching current notice in a healthy feed
Current buses
Cannot be confirmed from the current feed

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 · 66 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: MONTRÉAL / LAFONTAINE, MONTRÉAL / DE L'ÉGLISE, MONTRÉAL / NOTRE-DAME CEMETERY, ST-LAURENT / MONTRÉAL, ST-LAURENT / AD. 505 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

The current official GTFS contains no service for this route on this service date.

Next trips from the ends of the route

These are trip starts. For the time at your stop, open that stop’s departure board.

No upcoming trip start is published in the next four hours.

The realtime prediction feed is unavailable or stale. Timetable times remain labelled as scheduled only.

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 19, 9:18 p.m.

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.

Choose a direction or stop pattern
Clear selection

  • Towards Wateridge: PARLIAMENT A to CODD'S / MIKINAK

    36 stops · 63 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 Parliament ~ Parlement: WANAKI / MIKINAK to PARLIAMENT B

    35 stops · 54 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 17?

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 9.3 to 10.6 min in 4 hours of the day.

Scenario: 9 to 11 min more running time on 72 trips. The schedule-block model adds no 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, 7 hours measured
  1. 00:00: not enough data
  2. 01:00: not enough data
  3. 02:00: not enough data
  4. 03:00: not enough data
  5. 04:00: not enough data
  6. 05:00: not enough data
  7. 06:00: 91.3% of arrivals on time, 612 arrivals, typically 1.3 min late
  8. 07:00: 96.4% of arrivals on time, 612 arrivals, typically 1.1 min late
  9. 08:00: 16.9% of arrivals on time, 544 arrivals, typically 9.3 min late
  10. 09:00: not enough data
  11. 10:00: not enough data
  12. 11:00: not enough data
  13. 12:00: not enough data
  14. 13:00: not enough data
  15. 14:00: not enough data
  16. 15:00: 6.7% of arrivals on time, 595 arrivals, typically 10.6 min late
  17. 16:00: 8.4% of arrivals on time, 594 arrivals, typically 14.5 min late
  18. 17:00: 26.3% of arrivals on time, 630 arrivals, typically 9.5 min late
  19. 18:00: 83.7% of arrivals on time, 288 arrivals, typically 3 min late
  20. 19:00: not enough data
  21. 20:00: not enough data
  22. 21:00: not enough data
  23. 22:00: not enough data
  24. 23:00: not enough data
  • 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 · 15:00 to 18:009.3 min late · 10.6 min lateMore running time
Measurements
Late by the timetable · 15:00 to 18:00
medianDelaySeconds 635
spreadSeconds 553
observations 1,819
hoursAffected 3
suggestedRunningTimeChangeMinutes 10.6
Late by the timetable · 08:00
medianDelaySeconds 557
spreadSeconds 935
observations 544
hoursAffected 1
suggestedRunningTimeChangeMinutes 9.3
08:00 30→3915:00 31→4216:00 31→4217:00 31→42

Route check

How route 17 is doing

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

Bottom line

This route is often far from its schedule.

52 in 100 arrivals were within 5 minutes of schedule · 5,097 arrivals checked

Confidence in this summary: High

Based on 5,097 arrivals over 18 weekdays, from Aug 20, 2026 to Sep 19, 2026.

Updated Sep 19, 2026, 8: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. 3 p.m.–4 p.m.: 93 in 100 arrivals were more than 5 minutes early or late (595 arrivals over 9 days).
  2. 4 p.m.–5 p.m.: 92 in 100 arrivals were more than 5 minutes early or late (594 arrivals over 9 days).
  3. 8 a.m.–9 a.m.: 83 in 100 arrivals were more than 5 minutes early or late (544 arrivals over 9 days).
  4. 5 p.m.–6 p.m.: 74 in 100 arrivals were more than 5 minutes early or late (630 arrivals over 9 days).

No current official notice matches this route.

Problem places

  1. MONTRÉAL / NOTRE-DAME CEMETERY

    84 in 100 arrivals were more than 5 minutes early or late (73 arrivals over 15 days).

    Open this stop
  2. MONTRÉAL / CUMMINGS

    83 in 100 arrivals were more than 5 minutes early or late (75 arrivals over 17 days).

    Open this stop
  3. WANAKI / PROVENDER

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

    Open this stop
  4. MONTRÉAL / LAFONTAINE

    82 in 100 arrivals were more than 5 minutes early or late (74 arrivals over 16 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?
No live cancellation answerOC Transpo’s live trip-update feed did not answer this check. That is a feed gap. It does not mean zero cancellations, and it is not proof of a cancellation. Open the evidence to see the schedule, retained explicit cancellation notices, and every labelled data gap.
Possible no-shows after checking feed gaps?
13 of 65 checked trips need a closer look13 of 65 trips with enough public-feed evidence had no matching position over 7 days. 0 of 65 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 21.3 min late52 in 100 arrivals were within 5 minutes of schedule.
Do buses bunch or leave long gaps?
No route-level result meets the evidence threshold yet. This does not mean gaps did not happen.

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
13
Distinct scheduled stops
66
Distinct published paths
2
Published service span
6:00 a.m.–6:29 p.m.

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
13
Distinct scheduled stops
66
Distinct published paths
2
Published service span
6:00 a.m.–6:29 p.m.

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 3,488 arrivals over 8 days; after has 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
52.2%
Arrivals checked
5,097
Weekdays with data
18
How late the worst 5 in 100 were
21.3 min late
Patterns by hour (8)
HourOn timeMedianWorst 5 in 100Evidence
06:0091.3%1.3 min late6.1 min late612 · 9 days
07:0096.4%1.1 min late4.3 min late612 · 9 days
08:0016.9%9.3 min late24.9 min late544 · 9 days
14:0059.3%3.4 min late9.4 min late27 · 9 days
15:006.7%10.6 min late19.8 min late595 · 9 days
16:008.4%14.5 min late27.7 min late594 · 9 days
17:0026.3%9.5 min late18.3 min late630 · 9 days
18:0083.7%3 min late6.7 min late288 · 9 days

5 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

52 / 65 scheduled trips published at least one position across 5 service days (80.0%).

  • 15:003 / 10 trips without a position70.0%
  • 06:002 / 10 trips without a position80.0%
  • 07:002 / 10 trips without a position80.0%
  • 14:001 / 5 trips without a position80.0%
  • 16:002 / 10 trips without a position80.0%
  • 17:002 / 10 trips without a position80.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.

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

Computed or assembled
Sample
5,097 settled arrivals across 1 matching reliability records.
Coverage
2 published stop patterns containing 71 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.