Independent, citizen-led transit information for Ottawa–Gatineau riders. Not affiliated with OC Transpo or STO.

OC Transpo · Regular service

Route 30

Blair · Millennium

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: 3 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 · 73 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: JEANNE D'ARC / ORLÉANS, JEANNE D'ARC / BOYER, JEANNE D'ARC / HUNTER'S RUN, JEANNE D'ARC / AD. 5810, JEANNE D'ARC / GREY NUNS 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 Blair: 29 scheduled trips
7:21 a.m.–10:49 p.m.: 30 min median scheduled gap
Towards Millennium: 29 scheduled trips
7:15 a.m.–10:44 p.m.: 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.

2:45 p.m.
Towards Millennium
Starts at BLAIR D
Provider prediction · Scheduled 2:45 p.m.
BLAIR D Open scheduled trip
2:51 p.m.
Towards Blair
Starts at MILLENNIUM B
Provider prediction · Scheduled 2:51 p.m.
MILLENNIUM B Open scheduled trip
3:15 p.m.
Towards Millennium
Starts at BLAIR D
Timetable only. No usable prediction is available for this trip.
BLAIR D Open scheduled trip
3:21 p.m.
Towards Blair
Starts at MILLENNIUM B
Timetable only. No usable prediction is available for this trip.
MILLENNIUM B Open scheduled trip

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

Buses seen now

3 current vehicle positions match this route.

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

Towards Blair
Feed vehicle 2168
Updated Sep 19, 2:26 p.m.
Follow this vehicle in Explore →
Towards Blair
Feed vehicle 4841
Updated Sep 19, 2:26 p.m.
Follow this vehicle in Explore →
Towards Millennium
Feed vehicle 4817
Updated Sep 19, 2:26 p.m.
Follow this vehicle in Explore →

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, 2:29 p.m.

See all stops and route patterns

Stops and stations

3 official stop patterns

Each row below is one exact stop order published in the official schedule. Short turns and alternate destinations stay separate.

Towards Blair: MILLENNIUM B to BLAIR C
37 stops · 333 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 Blair: MILLENNIUM B to BLAIR C
36 stops · 142 imported trips
Scheduled from Sep 18, 2026 to Oct 18, 2026
Published weekly days: Monday, Saturday, Sunday
5 official service records
3 added dates and 13 removed dates
View stops and calendar →
Towards Millennium: BLAIR D to MILLENNIUM A
36 stops · 505 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 30?

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

Open history, reliability and route analysis

Verdict

What this route needs

Timetable short by 3.2 to 4.5 min in 7 hours of the day.

08:00 drops to 47% on time, against 77% the rest of the day.

Scenario: 3 to 5 min more running time on 412 trips. The schedule-block model estimates 89 additional 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, 19 hours measured

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: 95.4% of arrivals on time, 738 arrivals, typically 2.3 min late
06:00: 83.7% of arrivals on time, 1,589 arrivals, typically 2.1 min late
07:00: 62.5% of arrivals on time, 2,024 arrivals, typically 3.2 min late
08:00: 47.1% of arrivals on time, 1,710 arrivals, typically 5.3 min late
09:00: 61% of arrivals on time, 1,589 arrivals, typically 4.2 min late
10:00: 77.1% of arrivals on time, 1,702 arrivals, typically 2.1 min late
11:00: 86.7% of arrivals on time, 1,710 arrivals, typically 2 min late
12:00: 87.9% of arrivals on time, 1,691 arrivals, typically 1 min late
13:00: 89.5% of arrivals on time, 1,626 arrivals, typically 1.5 min late
14:00: 82% of arrivals on time, 1,542 arrivals, typically 2.5 min late
15:00: 65% of arrivals on time, 1,608 arrivals, typically 3.7 min late
16:00: 47.8% of arrivals on time, 1,800 arrivals, typically 5.3 min late
17:00: 75.5% of arrivals on time, 2,292 arrivals, typically 1.2 min late
18:00: 71.1% of arrivals on time, 2,325 arrivals, typically 2.3 min late
19:00: 69.5% of arrivals on time, 1,724 arrivals, typically 3.2 min late
20:00: 70.5% of arrivals on time, 1,620 arrivals, typically 3.3 min late
21:00: 90.4% of arrivals on time, 1,559 arrivals, typically 1.8 min late
22:00: 89.1% of arrivals on time, 843 arrivals, typically 2.6 min late
23:00: 95.5% of arrivals on time, 292 arrivals, typically 1.7 min late

90% or more on time
80 to 90% on time
under 80% on time
not enough data

What	When	Measured	Scenario or next investigation
ProblemLate by the timetable	07:00 to 10:00 · 15:00 to 17:00 · 19:00 to 21:00	4.2 min late … 3.2 min late	More running time
ProblemOne hour collapses	08:00	47%	Operations, not the timetable

Measurements

Late by the timetable · 07:00 to 10:00: medianDelaySeconds 249; spreadSeconds 582; observations 5,323; hoursAffected 3; suggestedRunningTimeChangeMinutes 4.2
Late by the timetable · 15:00 to 17:00: medianDelaySeconds 270; spreadSeconds 382; observations 3,408; hoursAffected 2; suggestedRunningTimeChangeMinutes 4.5
Late by the timetable · 19:00 to 21:00: medianDelaySeconds 193.5; spreadSeconds 407.5; observations 3,344; hoursAffected 2; suggestedRunningTimeChangeMinutes 3.2
One hour collapses · 08:00: hour 8; onTimePct 47.1; routeMedianOnTimePct 77.1; shortfallPoints 30; observations 1,710

Route check

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

75 in 100 arrivals were within 5 minutes of schedule · 39,208 arrivals checked

Confidence in this summary: High

Based on 39,208 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.

8 a.m.–9 a.m.: 53 in 100 arrivals were more than 5 minutes early or late (1,710 arrivals over 11 days).
4 p.m.–5 p.m.: 52 in 100 arrivals were more than 5 minutes early or late (1,800 arrivals over 12 days).
9 a.m.–10 a.m.: 39 in 100 arrivals were more than 5 minutes early or late (1,589 arrivals over 12 days).
7 a.m.–8 a.m.: 38 in 100 arrivals were more than 5 minutes early or late (2,024 arrivals over 11 days).

No current official notice matches this route.

Problem places

JEANNE D'ARC 2A
38 in 100 arrivals were more than 5 minutes early or late (548 arrivals over 22 days).
Open this stop
BRIAN COBURN / GERRY LALONDE
38 in 100 arrivals were more than 5 minutes early or late (578 arrivals over 26 days).
Open this stop
BRIAN COBURN / CHAPERAL
38 in 100 arrivals were more than 5 minutes early or late (579 arrivals over 26 days).
Open this stop
MER BLEUE / HYDRO
36 in 100 arrivals were more than 5 minutes early or late (585 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?: 75 of 500 checked trips need a closer look75 of 500 trips with enough public-feed evidence had no matching position over 7 days. 2 of 502 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 10.5 min late75 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: 78
Distinct scheduled stops: 73
Distinct published paths: 2
Published service span: 5:09 a.m.–11:30 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: 78
Distinct scheduled stops: 73
Distinct published paths: 2
Published service span: 5:09 a.m.–11:30 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 27,573 arrivals over 13 days; after has 2,568 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

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

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: 75.4%
Arrivals checked: 39,208
Weekdays with data: 20
How late the worst 5 in 100 were: 10.5 min late

Patterns by hour (19)

Hour	On time	Median	Worst 5 in 100	Evidence
05:00	95.4%	2.3 min late	4.8 min late	738 · 9 days
06:00	83.7%	2.1 min late	8.5 min late	1,589 · 9 days
07:00	62.5%	3.2 min late	12.9 min late	2,024 · 11 days
08:00	47.1%	5.3 min late	13.1 min late	1,710 · 11 days
09:00	61.0%	4.2 min late	13.9 min late	1,589 · 12 days
10:00	77.1%	2.1 min late	8.5 min late	1,702 · 13 days
11:00	86.7%	2 min late	6.9 min late	1,710 · 13 days
12:00	87.9%	1 min late	9.5 min late	1,691 · 13 days
13:00	89.5%	1.5 min late	5.8 min late	1,626 · 12 days
14:00	82.0%	2.5 min late	7.9 min late	1,542 · 12 days
15:00	65.0%	3.7 min late	10 min late	1,608 · 12 days
16:00	47.8%	5.3 min late	11.8 min late	1,800 · 12 days
17:00	75.5%	1.2 min late	10.6 min late	2,292 · 13 days
18:00	71.1%	2.3 min late	10.6 min late	2,325 · 12 days
19:00	69.5%	3.2 min late	10.2 min late	1,724 · 12 days
20:00	70.5%	3.3 min late	9.9 min late	1,620 · 12 days
21:00	90.4%	1.8 min late	6 min late	1,559 · 12 days
22:00	89.1%	2.6 min late	5.8 min late	843 · 12 days
23:00	95.5%	1.7 min late	4.8 min late	292 · 10 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

425 / 502 scheduled trips published at least one position across 5 service days (84.7%).

22:003 / 14 trips without a position78.6%
05:003 / 15 trips without a position80.0%
06:006 / 30 trips without a position80.0%
07:006 / 34 trips without a position82.4%
17:006 / 38 trips without a position84.2%
18:006 / 38 trips without a position84.2%

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.

Collected or observed: September 19, 2026 at 2:28 p.m.
Computed or assembled: September 19, 2026 at 1:32 p.m.
Sample: 39,208 settled arrivals across 1 matching reliability records.
Coverage: 3 published stop patterns containing 109 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.