STO · Regular service

Route 41

Pob Allum, Ottawa

Route 41 right now

Running: Cannot be confirmed; 3:00 a.m.
Cancelled trips now: None reported
Service alerts: 0 confirmed current notices

Where will you board?

Choose a destination, then find your stop on this route.

Route patternFind a stop in this pattern

Search by stop name or code. Results follow the published stop order, not distance.

Enter a stop name or code to see matching stops.

All stops and patterns

Toward Pob Allum · STATION LYON to PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée

Toward Ottawa · PARC-O-BUS ALLUMETTIÈRES to BANK/WELLINGTON

Route and live buses

Service date: October 8, 2026

0 official shapes · 103 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: du PORTAGE/AUBRY, du PORTAGE/LAVAL, ALEXANDRE-TACHÉ/SAINTE-THÉRÈSE, ALEXANDRE-TACHÉ/SAINT-DOMINIQUE, chemin d'AYLMER/ROYALE and 7 more. These are highlighted from route-specific provider predictions compared with the timetable, with at least 60 eligible predictions over 3 days. They do not establish actual arrivals or a cause.

Open the full-screen map

The line is the official route. Dots show published stops, buses seen now and stops named in current notices.

Where the buses are now

Buses we can see right now appear on the route below. A marker stops when we stop hearing from that bus. We never make up movement.

Service date: October 8, 2026
Official notices: No matching current notice in a healthy feed
Current buses: Cannot be confirmed from the current feed

Today’s schedule

Service date October 8, 2026

Towards Pob Allum: 5 scheduled trips
3:10 p.m.–6:05 p.m.: 30 min median scheduled gap
Towards Ottawa: 5 scheduled trips
6:22 a.m.–9:17 a.m.: 31.5 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.

6:22 a.m.
Towards Ottawa
Starts at PARC-O-BUS ALLUMETTIÈRES
Timetable only. No usable prediction is available for this trip.
PARC-O-BUS ALLUMETTIÈRES Open scheduled trip
6:55 a.m.
Towards Ottawa
Starts at PARC-O-BUS ALLUMETTIÈRES
Timetable only. No usable prediction is available for this trip.
PARC-O-BUS ALLUMETTIÈRES Open scheduled trip

Buses seen now

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

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 Oct 8, 3:01 a.m.

Explore the route

Choose a destination, then select a stop on the map or route diagram.

2 official stop patterns

0 verified representative shapes · 103 stops

Dashed lines connect the published stop order; they are not claimed street paths

Map source and limits

A solid line matches one published representative trip whose stops and order were checked. Another trip with the same stops may follow a different shape. Dashed lines connect published stops only; they do not describe streets.

This view does not show live vehicle positions.

Open the full-screen map

All published paths

Where does it go?

Different journeys can take different branches. Choose a published path above to see its stops in order.

You can also select any stop on the map to open its departure board.

Pob Allum1 official stop pattern

Ottawa1 official stop pattern

Published stop order does not prove that a vehicle is running now.

Schedule and source records

STATION LYON to PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée · 54 stops

Scheduled from Sep 28, 2026 to Nov 20, 2026

This service is published only as specific added dates, not as a weekly calendar.

3 official service records

39 added dates and 0 removed dates

Open this scheduled trip progression

Review the official service records

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

Service records for this stop pattern

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

PARC-O-BUS ALLUMETTIÈRES to BANK/WELLINGTON · 49 stops

Scheduled from Sep 28, 2026 to Nov 20, 2026

This service is published only as specific added dates, not as a weekly calendar.

3 official service records

39 added dates and 0 removed dates

Open this scheduled trip progression

Review the official service records

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

Service records for this stop pattern

Service sto:H01S926S-Semaine-0-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 28, 2026, Sep 29, 2026, Oct 1, 2026, Oct 5, 2026, Oct 6, 2026, Oct 7, 2026, Oct 8, 2026, Oct 9, 2026, Oct 13, 2026, Oct 14, 2026, Oct 15, 2026, Oct 19, 2026, Oct 20, 2026, Oct 21, 2026, Oct 22, 2026, Oct 23, 2026, Oct 26, 2026, Oct 27, 2026, Oct 28, 2026, Oct 29, 2026, Oct 30, 2026, Nov 2, 2026, Nov 3, 2026, Nov 4, 2026, Nov 5, 2026, Nov 6, 2026, Nov 9, 2026, Nov 10, 2026, Nov 11, 2026, Nov 12, 2026, Nov 13, 2026, Nov 16, 2026, Nov 17, 2026, Nov 18, 2026, Nov 19, 2026, Nov 20, 2026
Service sto:H01S926S-Semaine-10-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Sep 30, 2026
Service sto:H01S926S-Semaine-11-_26AUT-1111100-
sto:41
This service is published only as specific added dates, not as a weekly calendar.
Added dates: Oct 2, 2026, Oct 16, 2026

Official feed version ca455c71-c30a-4e4d-8b72-2709212731cd

Source checksum a7e1f22955084828484cca5e8f1ebff9e785c70984ad5dd93b872a5d64ace6e4

Schedule and accessibility details

Current service date: Oct 8, 2026
Selected direction: Every published direction
Imported schedule valid through: Nov 22, 2026

Some imported trips are marked accessible and others are not or are unstated; verify each departure.

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: Oct 1, 2026 – Oct 7, 2026

Scheduled trips with cancellation notices

—

No retained notice returned; this does not prove zero cancellations. 1 partial-capture day not counted.

Trips needing investigation

2 of 40 trips with a usable feed window (5%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

38 with position · 2 to investigate · 10 excluded · 50 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Oct 8, 2026, 3:01 a.m..

Coverage, exclusions and sources

0 of 2 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

10 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 38 / 50 (76%). This is not a delivered-service rate. 7 service days in this source.

Timetables retained before the service day: 7 / 7 requested days · 0 missing days.

Historical calculation: Oct 8, 2026, 2:08 a.m.

Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.

Cancellations on this route

What these words mean →

1 partial-capture day not counted.

2 scheduled trips with counted cancellation notices from Thu, Sep 10 to Wed, Oct 7.

Not counted: 0 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.

Hours with the most cancellations: 5 p.m. (2)

Latest cancelled trips

Mon, Sep 21, scheduled 17:10
Thu, Sep 10, scheduled 17:10

A cause is shown only when STO’s own alert for that trip gives one.

Did not come (no bus seen, no notice), last 7 days: 2 of 40 trips we could check.

Buses arriving bunched

Bunching and slow spots on every route →

Not measured yet. The daily count has not reached these days, so there is no number to show.

City road work near this route

Road work and event road closures the City of Ottawa has published, measured as near this route’s path. Near is not proof that the bus is detoured: check the operator’s own alerts for that.

Event road closure
Bank at Queen
Sep 23, 2026, 12:00 a.m. to Nov 1, 2026, 5:00 p.m.
Bank traffic disruptions at Queen due to a demonstration, from September 23rd to November 1st between 7:00am and 5:00pm.
about 0 m from the route
City record updated Oct 5, 2026, 6:16 a.m..
Road work
ALBERT at LYON
Dates not published
Albert and Lyon off-peak lane reductions at the intersection due to construction.
about 3 m from the route
City record updated Sep 9, 2026, 6:32 p.m..

A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.

Source: City of Ottawa traffic events (road work and closures). Contains information licensed under the Open Government Licence, City of Ottawa. The City says this list is best effort and may be incomplete. City of Ottawa traffic map ↗

When this route is usually busy

From the load level STO’s buses report, over the last eight weeks. A time is marked usually busy when at least half of the trips with a reading reached standing room or fuller.

No time of day was usually busy in the last eight weeks.

When this route is usually busy	Weekdays	Saturdays	Sundays
Before 6 am	Not enough readings	Not enough readings	Not enough readings
6 to 9 am	Usually seats42.5% of 134 trips	Not enough readings	Not enough readings
9 am to 3 pm	Usually seats7.4% of 27 trips	Not enough readings	Not enough readings
3 to 6 pm	Usually seats10.2% of 127 trips	Not enough readings	Not enough readings
6 to 10 pm	Usually seats0% of 19 trips	Not enough readings	Not enough readings
After 10 pm	Not enough readings	Not enough readings	Not enough readings

Based on 55 computed days.

Source: the occupancy status in STO’s public real-time vehicle feed, which STO sets from each bus’s load sensor (seats available under 60% full, standing room under 90%, full above 90%).
Each trip counts once per time of day, at the highest load it reported.
Reports of an empty bus are left out, because older records could not tell an empty bus from one with no sensor.
A time of day needs at least 12 trips on at least 4 different days before anything is shown. Holidays are counted with their day of the week.

What does the evidence show?

Predictions against the timetable

59.8%

of eligible provider predictions were within five minutes of the timetable.

These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.

Predictions in the source: 9,395
Weekdays with evidence: 20
Evidence window: Sep 8, 2026 – Oct 6, 2026

Calculated: Oct 8, 2026

1 partial-capture day not counted.

Explore the dated evidence Source of this result

The hours we have evidence for

Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.

87%6 a.m.435 predictions · 10 days
81%7 a.m.911 predictions · 10 days
76%8 a.m.980 predictions · 10 days
90%9 a.m.62 predictions · 10 days
84%3 p.m.486 predictions · 9 days
40%4 p.m.837 predictions · 9 days
40%5 p.m.853 predictions · 9 days
75%6 p.m.40 predictions · 8 days

What about time of day?

8 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.

Improvement or decline requires comparable periods. This single result cannot establish a trend.

Open the dated prediction analysis

Verdict

What this route needs

Median provider predictions are 7.1 min later than the timetable in 2 hours of the day.

Predictions near the start are about 6.2 min later than the timetable, with a similar difference near the end. This does not establish the cause.

Wide prediction spread 18:00: the 95th percentile is 20.7 min later than the median.

16:00 has 40% of predictions within five minutes of the timetable, against 79% the rest of the day.

Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 8 hours with samples

00:00: not enough data
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: not enough data
05:00: not enough data
06:00: 86.7% of final predictions within five minutes of the timetable, 435 predictions, typically 2.4 min late
07:00: 81.2% of final predictions within five minutes of the timetable, 911 predictions, typically 2.3 min late
08:00: 76.3% of final predictions within five minutes of the timetable, 980 predictions, typically 2.1 min late
09:00: 90.3% of final predictions within five minutes of the timetable, 62 predictions, typically 0.7 min early
10:00: not enough data
11:00: not enough data
12:00: not enough data
13:00: not enough data
14:00: not enough data
15:00: 83.5% of final predictions within five minutes of the timetable, 486 predictions, typically 3 min late
16:00: 39.8% of final predictions within five minutes of the timetable, 837 predictions, typically 7.5 min late
17:00: 40.3% of final predictions within five minutes of the timetable, 853 predictions, typically 6.8 min late
18:00: 75% of final predictions within five minutes of the timetable, 40 predictions, typically 1.2 min late. Provider predictions have a wide spread.
19:00: not enough data
20:00: not enough data
21:00: not enough data
22:00: not enough data
23:00: not enough data

90% or more of predictions within five minutes
80 to 90% of predictions within five minutes
under 80% of predictions within five minutes
not enough data
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	When	Measured	Scenario or next investigation
ProblemPredictions later than timetable	16:00 to 18:00	7.1 min late	Recovery time at the terminal
ProblemOne hour has a lower prediction match	16:00	40%	Operations, not the timetable
ProblemWide prediction spread	18:00	20.7 min swing	Operations, not the timetable

Measurements

Predictions later than timetable · 16:00 to 18:00: Measured arrivals 1,690; Hours affected 2; Spread 10.7 min; Median delay 7.1 min; Suggested running time change 7.1 min
One hour has a lower prediction match · 16:00: Hour 16:00; On time 39.8%; Measured arrivals 837; Shortfall 39 pts; Route median on time 78.8%
Wide prediction spread · 18:00: Measured arrivals 40; Hours affected 1; Spread 20.7 min; Median delay 1.2 min; Suggested running time change 1.2 min

Open history, reliability and route analysis

Route check

How route 41 has been running

A short summary of what we know. We say so when we cannot answer a question.

Bottom line

Provider predictions were often far from the timetable in this dated sample.

60 in 100 eligible predictions were within 5 minutes of the timetable · 9,395 predictions checked

Prediction sample size: Larger sample

Based on 9,395 eligible provider predictions over 20 measured days, from Sep 8, 2026 to Oct 6, 2026.

Updated Oct 8, 2026, 2:32 a.m.

Where and when did predictions differ repeatedly?

These are repeated prediction-to-timetable differences, not independently measured service failures. They use the same eligible predictions as the result above, but group by stop rather than hour, so the lists need not match line for line.

4 p.m.–5 p.m.: 60 in 100 eligible predictions differed from the timetable by more than 5 minutes (837 predictions over 9 days).
5 p.m.–6 p.m.: 60 in 100 eligible predictions differed from the timetable by more than 5 minutes (853 predictions over 9 days).

No current official notice matches this route.

Prediction differences by stop

PARC-O-BUS ALLUMETTIÈRES
65 in 100 eligible predictions differed from the timetable by more than 5 minutes (92 predictions over 20 days).
Open this stop
du PORTAGE/AUBRY
65 in 100 eligible predictions differed from the timetable by more than 5 minutes (86 predictions over 20 days).
Open this stop
PRINCIPALE/FRANK-ROBINSON
64 in 100 eligible predictions differed from the timetable by more than 5 minutes (84 predictions over 20 days).
Open this stop
PRINCIPALE/PARKER
63 in 100 eligible predictions differed from the timetable by more than 5 minutes (84 predictions over 20 days).
Open this stop

These are route-specific provider predictions compared with the timetable. They identify repeated prediction differences at a place and time, not measured arrivals or their 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 2Checks trips starting at route endpoints in the next 4 hours. This is not a historical cancellation rate.
Possible no-shows after checking feed gaps?: 2 of 40 checked trips need a closer look2 of 40 trips with enough public-feed evidence had no matching position over 7 days. 10 of 50 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
How did provider predictions differ from the timetable?: At the 95th percentile, the predicted difference was 17.3 min (positive means later; negative means earlier)60 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
What wait did provider predictions imply?: 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 27, 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 21, 2026

Scheduled trips: 0
Distinct scheduled stops: 0
Distinct published paths: 0
Published service span: —–—

Feed fingerprint: a1fd9699f40664cc · 1a4ea4f3-91a8-43db-8c05-e3b01b5bf24c

New schedule

Service date checked: September 28, 2026

Scheduled trips: 10
Distinct scheduled stops: 103
Distinct published paths: 2
Published service span: 6:22 a.m.–6:05 p.m.

Operator calendar-date records: 1 added · 0 removed

Feed fingerprint: a7e1f22955084828 · ca455c71-c30a-4e4d-8b72-2709212731cd

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.

Before

September 13, 2026 – September 26, 2026

60.3 in 100 arrivals were within 5 minutes

Average: 5.2 min from schedule

Slowest 5 in 100: about 16.9 min late

4,629 · 10 days

New schedule

September 27, 2026 – October 7, 2026

65.2 in 100 arrivals were within 5 minutes

Average: 4.4 min from schedule

Slowest 5 in 100: about 16.8 min late

3,341 · 7 days

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 the last eligible provider prediction for each scheduled arrival with the official schedule. These are not independently measured arrivals. A result needs at least 200 eligible predictions. 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

Official current feed: explicit cancellations, skipped stops and active notices.
Matched observations: vehicle positions and settled predictions tied to the official schedule.
Official timetable: what was planned, kept separate from what was observed.
Rider and operator reports: leads about routes, times and places to investigate, not numeric proof by themselves.

Provisional results, published evidence

How did predictions compare with the timetable?

Each hour compares the last eligible provider prediction for a scheduled arrival with the timetable. “Within 5 minutes” describes that prediction difference, not a measured arrival or proof that a bus ran.

Evidence window: September 8, 2026 to October 6, 2026

Within 5 minutes of schedule: 59.8%
Eligible predictions checked: 9,395
Weekdays with data: 20
95th-percentile predicted delay: 17.3 min late

Patterns by hour (8)

Patterns by hour (8)
Hour	On time	Median	95th percentile	Evidence
06:00	86.7%	2.4 min late	8 min late	435 · 10 days
07:00	81.2%	2.3 min late	7.8 min late	911 · 10 days
08:00	76.3%	2.1 min late	10.9 min late	980 · 10 days
09:00	90.3%	0.7 min early	3.2 min late	62 · 10 days
15:00	83.5%	3 min late	6.2 min late	486 · 9 days
16:00	39.8%	7.5 min late	15.4 min late	837 · 9 days
17:00	40.3%	6.8 min late	20.2 min late	853 · 9 days
18:00	75.0%	1.2 min late	21.9 min late	40 · 8 days

2 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

38 / 40 scheduled trips published at least one position across 4 service days (95.0%).

06:001 / 8 trips without a position87.5%
15:001 / 8 trips without a position87.5%
07:000 / 8 trips without a position100.0%
16:000 / 8 trips without a position100.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.

Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position 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.

Dated service

Trips scheduled that day

The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.

Service day

October 7, 2026 October 6, 2026 October 5, 2026 October 4, 2026 October 3, 2026 October 2, 2026 October 1, 2026

October 7, 2026 · 10 trips in the retained timetable · retained notices; capture coverage unverified

In short: 9 with a matched position · 1 with no matching position (to investigate) · 0 with an unknown outcome.

06:22– 07:14
Trip sto:62731009Vehicle position matchedFirst / last feed position: 6:24 a.m. EDT / 7:06 a.m. EDT; not actual start or end times.
06:55– 07:48
Trip sto:62731199Vehicle position matchedFirst / last feed position: 6:45 a.m. EDT / 7:41 a.m. EDT; not actual start or end times.
07:29– 08:24
Trip sto:62731808Vehicle position matchedFirst / last feed position: 7:23 a.m. EDT / 8:30 a.m. EDT; not actual start or end times.
07:55– 08:50
Trip sto:62730808Vehicle position matchedFirst / last feed position: 7:57 a.m. EDT / 8:51 a.m. EDT; not actual start or end times.
08:25– 09:17
Trip sto:62730463Vehicle position matchedFirst / last feed position: 8:16 a.m. EDT / 9:15 a.m. EDT; not actual start or end times.
15:10– 16:05
Trip sto:62730626No matching position; investigate, not a confirmed cancellation
15:40– 16:37
Trip sto:62731007Vehicle position matchedFirst / last feed position: 3:38 p.m. EDT / 4:46 p.m. EDT; not actual start or end times.
16:12– 17:13
Trip sto:62730878Vehicle position matchedFirst / last feed position: 4:26 p.m. EDT / 5:38 p.m. EDT; not actual start or end times.
16:40– 17:36
Trip sto:62730221Vehicle position matchedFirst / last feed position: 4:43 p.m. EDT / 5:47 p.m. EDT; not actual start or end times.
17:10– 18:05
Trip sto:62731219Vehicle position matchedFirst / last feed position: 5:31 p.m. EDT / 6:01 p.m. EDT; not actual start or end times.

Loading the route history. Live times above are ready to use.

Would you count on route 41?

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.

Download evidence image

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 reliability from matching eligible final provider predictions 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.

Collected or observed: October 8, 2026 at 3:01 a.m.
Computed or assembled: October 8, 2026 at 2:32 a.m.
Sample: 9,395 eligible settled provider predictions across 1 matching reliability records.
Coverage: 2 published stop patterns containing 103 stop calls are available on this page.
Method or data version: last-prediction-within-ten-minutes-v1; ca455c71-c30a-4e4d-8b72-2709212731cd; a7e1f22955084828484cca5e8f1ebff9e785c70984ad5dd93b872a5d64ace6e4

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 STO GTFS. Check the Alerts panel for current official notices and each stop page for observed departures.

Ride now

Route 41 right now

Where will you board?

Toward Pob Allum · STATION LYON to PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée

Toward Ottawa · PARC-O-BUS ALLUMETTIÈRES to BANK/WELLINGTON

Stops and map

Explore the route

Where does it go?

STATION LYON to PARC-O-BUS ALLUMETTIÈRES arrêt d'arrivée · 54 stops

Service records for this stop pattern

PARC-O-BUS ALLUMETTIÈRES to BANK/WELLINGTON · 49 stops

Service records for this stop pattern

Performance

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

Cancellations on this route

Latest cancelled trips

Buses arriving bunched

City road work near this route

When this route is usually busy

What does the evidence show?

The hours we have evidence for

What about time of day?

What this route needs

Where and when did predictions differ repeatedly?

Check every trip and date

What riders want to know

Selected service day from each published schedule

Before

New schedule

Did service improve after the change?

Before

New schedule

How did predictions compare with the timetable?

Trips scheduled that day

Share this page

What is being shown

How it was produced

Evidence dates

Sources

Limits to keep in mind

Community reports

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

Cancellations on this route

Latest cancelled trips

Buses arriving bunched

City road work near this route

When this route is usually busy

What does the evidence show?

The hours we have evidence for

What about time of day?

What this route needs

Where and when did predictions differ repeatedly?

Check every trip and date

What riders want to know

Selected service day from each published schedule

Before

New schedule

Did service improve after the change?

Before

New schedule

How did predictions compare with the timetable?

Trips scheduled that day

What is being shown

How it was produced

Evidence dates

Sources

Limits to keep in mind