Skip to main content
Otranspo

Route

5

OC Transpo

Waller <> Elmvale

This page includes all 2 current versions of the route, including short trips and different destinations.

All imported trips are marked accessible.Imported schedule valid through: Sep 20, 2026

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.

Route check

How route 5 is doing

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.

82 in 100 arrivals were within 5 minutes of schedule · 40,034 arrivals checked

Confidence in this summary: High

Based on 40,034 arrivals over 22 weekdays, from 2026-07-29T18:45:47.010Z to 2026-08-28T18:45:47.010Z.

Updated Aug 28, 2026, 2:45 p.m.

Problems to fix

These are repeated patterns, not one bad day or an unverified rider report.

  1. 8 a.m.–9 a.m.: 47 in 100 arrivals were more than 5 minutes early or late (381 arrivals over 3 days).
  2. 2 p.m.–3 p.m.: 43 in 100 arrivals were more than 5 minutes early or late (336 arrivals over 7 days).
  3. 9 a.m.–10 a.m.: 39 in 100 arrivals were more than 5 minutes early or late (441 arrivals over 3 days).

Official notices cannot be confirmed right now.

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.

The questions riders ask

Cancelled trips right now
Cannot confirm right now

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

Trips that may not have shown up
No confirmed count yet

293 of 716 scheduled trips had no matching vehicle position over 6 days. The feed covered 59.1%. These are cases to investigate—not confirmed no-shows.

Late service
The slowest 5 in 100 were more than about 10.6 min late

82 in 100 arrivals were within 5 minutes of schedule.

Long gaps or bunching
8.6 min average predicted wait

1.8 min beyond the scheduled wait, based on 10 arrivals at 1 high-frequency stop over 1 days.

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.

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

Open the full-screen map
Today’s schedule

Service date August 28, 2026

Towards Waller
58 scheduled trips
5:22 a.m.–12:31 a.m. (next day)
15 min median scheduled gap
Towards Elmvale
59 scheduled trips
5:39 a.m.–12:38 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 Waller

    Starts at ELMVALE A

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

  2. Towards Elmvale

    Starts at WALLER / LAURIER E

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

  3. Towards Elmvale

    Starts at WALLER / LAURIER E

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

  4. Towards Waller

    Starts at ELMVALE A

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

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

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

Buses seen now

Current vehicle positions cannot be confirmed. No zero is shown.

Official notices

The operator notice feed is unavailable or stale, so no all-clear is claimed.

Planned changes

The planned-change register is unavailable. No planned change is confirmed or ruled out.

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 Aug 28, 5:09 p.m.

Check the numbers

Data behind this result

This route has more than one official schedule record. We keep each record separate so the totals stay checkable and we do not invent a combined worst-case result.

Open any result below to see the hours, denominators, observed days, and position coverage behind it.

Observed evidence cohort 5

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: July 29, 2026 to August 28, 2026

82.3%
Within ±5 min
40,034
Settled arrivals
22
Observed weekdays
10.6 min late
How late the worst 5 in 100 were
Patterns by hour (20)
HourOn timeMedianWorst 5 in 100Evidence
00:0092.1%0.2 min early5.1 min late140 · 2 days
05:0076.9%1.4 min late6.2 min late78 · 2 days
06:0092.0%2.8 min late7.2 min late312 · 2 days
07:0079.9%2.3 min late8 min late353 · 2 days
08:0052.8%3.8 min late39.4 min late381 · 3 days
09:0061.5%3.5 min late17 min late441 · 3 days
10:0084.3%1.1 min late6.9 min late464 · 2 days
11:0085.6%0.3 min late27.1 min late458 · 4 days
12:0072.1%2.1 min late14.9 min late380 · 5 days
13:0071.9%2.4 min late87.4 min late587 · 8 days
14:0057.1%3.1 min late89.9 min late336 · 7 days
15:0061.9%3.7 min late10.6 min late215 · 2 days
16:0073.2%3.4 min late7.4 min late265 · 2 days
17:0070.7%2.5 min late41 min late259 · 3 days
18:0082.4%1.3 min late11.6 min late318 · 3 days
19:00100.0%0.1 min late3.3 min late169 · 2 days
20:00100.0%0.4 min late3 min late130 · 1 days
21:00100.0%1.5 min late3.5 min late121 · 1 days
22:0074.8%2.8 min late16.3 min late131 · 3 days
23:00100.0%0 min early3.7 min late122 · 1 days

3 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

423 / 716 scheduled trips published at least one position across 6 service days (59.1%).

  • 00:007 / 11 trips without a position36.4%
  • 23:0014 / 23 trips without a position39.1%
  • 17:0026 / 45 trips without a position42.2%
  • 19:0018 / 32 trips without a position43.8%
  • 20:0015 / 27 trips without a position44.4%
  • 18:0026 / 47 trips without a position44.7%

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.

Method: last prediction within ten minutes of each arrival; one arrival per trip, stop and service date. Trip coverage: GTFS schedule compared with any GTFS-RT position carrying the same trip and local service date. Sources and limitations.

See all stops and route patterns

Stops and stations

5 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 Hospital ~ Hôpital: ELMVALE A to RING / TOH GENERAL CAMPUS

    8 stops · 33 imported trips

    Scheduled from Aug 14, 2026 to Sep 20, 2026

    Published weekly days: Monday, Saturday, Sunday

    9 official service records

    4 added dates and 16 removed dates

    View stops and calendar
  • Towards Waller: ELMVALE A to WALLER / NICHOLAS

    31 stops · 1277 imported trips

    Scheduled from Aug 14, 2026 to Sep 20, 2026

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

    25 official service records

    10 added dates and 30 removed dates

    View stops and calendar
  • Towards Elmvale: WALLER / LAURIER E to ELMVALE A

    32 stops · 1236 imported trips

    Scheduled from Aug 14, 2026 to Sep 20, 2026

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

    25 official service records

    10 added dates and 30 removed dates

    View stops and calendar
  • Towards Elmvale: LEES A to ELMVALE A

    24 stops · 10 imported trips

    Scheduled from Aug 30, 2026 to Sep 20, 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 Elmvale: RING / TOH GENERAL CAMPUS to ELMVALE A

    9 stops · 49 imported trips

    Scheduled from Aug 14, 2026 to Sep 20, 2026

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

    25 official service records

    10 added dates and 30 removed dates

    View stops and calendar

The stop patterns are available, but this environment cannot name the imported feed version.

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

2 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
40,034 settled arrivals across 1 matching reliability records.
Coverage
5 published stop patterns containing 104 stop calls are available on this page.
Method or data version
last-prediction-within-ten-minutes-v1

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.