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

OC Transpo · Regular service

Route 8

Gatineau · Terrasses de la Chaudière · Dow's Lake ~ Lac Dow

Current service date: Sep 20, 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 20, 2026
Official notices: No matching current notice in a healthy feed
Current buses: 2 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 · 37 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: LAVAL / LAURIER, DU PORTAGE / DE L' HÔTEL-DE-VILLE, LAURIER / VICTORIA, LAURIER / ÉLISABETH-BRUYÈRE, MAISONNEUVE / DES ALLUMETTIÈRES and 4 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 20, 2026

Towards Gatineau: 26 scheduled trips
5:55 a.m.–8:09 p.m.: 30 min median scheduled gap
Towards Terrasses de la Chaudière: 5 scheduled trips
8:23 p.m.–12:04 a.m. (next day): 60 min median scheduled gap
Towards Dow's Lake ~ Lac Dow: 31 scheduled trips
7:04 a.m.–12:29 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.

7:34 a.m.
Towards Gatineau
Starts at DOW'S LAKE
Provider prediction · Scheduled 7:33 a.m.
DOW'S LAKE Open scheduled trip
7:54 a.m.
Towards Dow's Lake ~ Lac Dow
Starts at LAURIER / ÉLISABETH-BRUYÈRE
Provider prediction · Scheduled 7:54 a.m.
LAURIER / ÉLISABETH-BRUYÈRE Open scheduled trip
8:23 a.m.
Towards Gatineau
Starts at DOW'S LAKE
Timetable only. No usable prediction is available for this trip.
DOW'S LAKE Open scheduled trip
8:40 a.m.
Towards Dow's Lake ~ Lac Dow
Starts at LAURIER / ÉLISABETH-BRUYÈRE
Timetable only. No usable prediction is available for this trip.
LAURIER / ÉLISABETH-BRUYÈRE Open scheduled trip

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

Buses seen now

2 current vehicle positions match this route.

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

Towards Gatineau
Feed vehicle 2507
Updated Sep 20, 7:34 a.m.
Follow this vehicle in Explore →
Towards Gatineau
Feed vehicle 2145
Updated Sep 20, 7:34 a.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 20, 7:35 a.m.

See all stops and route patterns

Stops and stations

4 official stop patterns

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

Towards Gatineau: DOW'S LAKE to LAURIER / ÉLISABETH-BRUYÈRE
18 stops · 384 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 →
Towards Terrasses de la Chaudière: DOW'S LAKE to LAVAL / LAURIER
15 stops · 110 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 →
Towards Dow's Lake ~ Lac Dow: LAURIER / ÉLISABETH-BRUYÈRE to DOW'S LAKE C
20 stops · 384 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 →
Towards Dow's Lake ~ Lac Dow: LAURIER / MAISONNEUVE to DOW'S LAKE C
15 stops · 123 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 8?

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

15:00 drops to 44% on time, against 77% the rest of the day.

Scenario: 3 to 6 min more running time on 224 trips. The schedule-block model estimates 112 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, 22 hours measured

00:00: 89.1% of arrivals on time, 329 arrivals, typically 1 min late
01:00: not enough data
02:00: not enough data
03:00: not enough data
04:00: 99.6% of arrivals on time, 252 arrivals, typically 1.3 min late
05:00: 100% of arrivals on time, 350 arrivals, typically 0.4 min late
06:00: 97.7% of arrivals on time, 709 arrivals, typically 0.5 min late
07:00: 76.7% of arrivals on time, 721 arrivals, typically 2.4 min late
08:00: 68.1% of arrivals on time, 842 arrivals, typically 3 min late
09:00: 60.3% of arrivals on time, 941 arrivals, typically 3.3 min late
10:00: 82.6% of arrivals on time, 933 arrivals, typically 1.8 min late
11:00: 87.9% of arrivals on time, 961 arrivals, typically 0.7 min late
12:00: 67.6% of arrivals on time, 924 arrivals, typically 3 min late
13:00: 69.6% of arrivals on time, 934 arrivals, typically 2.7 min late
14:00: 70.8% of arrivals on time, 946 arrivals, typically 3 min late
15:00: 43.8% of arrivals on time, 949 arrivals, typically 6.1 min late
16:00: 45% of arrivals on time, 915 arrivals, typically 5.6 min late
17:00: 69.2% of arrivals on time, 848 arrivals, typically 3.3 min late
18:00: 75.3% of arrivals on time, 930 arrivals, typically 2.2 min late
19:00: 73% of arrivals on time, 837 arrivals, typically 2.5 min late
20:00: 90% of arrivals on time, 752 arrivals, typically 1.5 min late
21:00: 89.1% of arrivals on time, 626 arrivals, typically 1.5 min late
22:00: 89.5% of arrivals on time, 478 arrivals, typically 2.6 min late
23:00: 95.3% of arrivals on time, 341 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	09:00 · 15:00 to 18:00	3.3 min late · 5.6 min late	More running time
ProblemOne hour collapses	15:00	44%	Operations, not the timetable

Measurements

Late by the timetable · 15:00 to 18:00: medianDelaySeconds 338; spreadSeconds 857; observations 2,712; hoursAffected 3; suggestedRunningTimeChangeMinutes 5.6
Late by the timetable · 09:00: medianDelaySeconds 196; spreadSeconds 746; observations 941; hoursAffected 1; suggestedRunningTimeChangeMinutes 3.3
One hour collapses · 15:00: hour 15; onTimePct 43.8; routeMedianOnTimePct 76.7; shortfallPoints 32.9; observations 949

Route check

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

76 in 100 arrivals were within 5 minutes of schedule · 20,253 arrivals checked

Confidence in this summary: High

Based on 20,253 arrivals over 19 weekdays, from Aug 21, 2026 to Sep 20, 2026.

Updated Sep 20, 2026, 7:32 a.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.

3 p.m.–4 p.m.: 56 in 100 arrivals were more than 5 minutes early or late (949 arrivals over 13 days).
4 p.m.–5 p.m.: 55 in 100 arrivals were more than 5 minutes early or late (915 arrivals over 13 days).
9 a.m.–10 a.m.: 40 in 100 arrivals were more than 5 minutes early or late (941 arrivals over 13 days).
12 p.m.–1 p.m.: 32 in 100 arrivals were more than 5 minutes early or late (924 arrivals over 13 days).

No current official notice matches this route.

Problem places

LAVAL / LAURIER
48 in 100 arrivals were more than 5 minutes early or late (448 arrivals over 23 days).
Open this stop
DU PORTAGE / DE L' HÔTEL-DE-VILLE
47 in 100 arrivals were more than 5 minutes early or late (450 arrivals over 23 days).
Open this stop
LAURIER / VICTORIA
40 in 100 arrivals were more than 5 minutes early or late (448 arrivals over 23 days).
Open this stop
LAURIER / ÉLISABETH-BRUYÈRE
33 in 100 arrivals were more than 5 minutes early or late (455 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?: 81 of 505 checked trips need a closer look81 of 505 trips with enough public-feed evidence had no matching position over 7 days. 2 of 507 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 12.9 min late76 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: 75
Distinct scheduled stops: 37
Distinct published paths: 4
Published service span: 4:37 a.m.–12:58 a.m. next day

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: 75
Distinct scheduled stops: 37
Distinct published paths: 4
Published service span: 4:37 a.m.–12:58 a.m. next day

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 13,259 arrivals over 14 days; after has 2,335 arrivals over 2 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 21, 2026 to September 20, 2026

Within 5 minutes of schedule: 75.5%
Arrivals checked: 20,253
Weekdays with data: 19
How late the worst 5 in 100 were: 12.9 min late

Patterns by hour (22)

Hour	On time	Median	Worst 5 in 100	Evidence
00:00	89.1%	1 min late	5.4 min late	329 · 13 days
01:00	77.8%	0.9 min late	10.3 min late	36 · 2 days
04:00	99.6%	1.3 min late	2.5 min late	252 · 9 days
05:00	100.0%	0.4 min late	2.4 min late	350 · 12 days
06:00	97.7%	0.5 min late	4.2 min late	709 · 12 days
07:00	76.7%	2.4 min late	8.9 min late	721 · 12 days
08:00	68.1%	3 min late	11.5 min late	842 · 12 days
09:00	60.3%	3.3 min late	15.7 min late	941 · 13 days
10:00	82.6%	1.8 min late	12.9 min late	933 · 13 days
11:00	87.9%	0.7 min late	8.1 min late	961 · 14 days
12:00	67.6%	3 min late	12.7 min late	924 · 13 days
13:00	69.6%	2.7 min late	12.9 min late	934 · 13 days
14:00	70.8%	3 min late	10.6 min late	946 · 14 days
15:00	43.8%	6.1 min late	20.4 min late	949 · 13 days
16:00	45.0%	5.6 min late	21.8 min late	915 · 13 days
17:00	69.2%	3.3 min late	13.1 min late	848 · 14 days
18:00	75.3%	2.2 min late	12.4 min late	930 · 14 days
19:00	73.0%	2.5 min late	18.4 min late	837 · 14 days
20:00	90.0%	1.5 min late	6.5 min late	752 · 13 days
21:00	89.1%	1.5 min late	6 min late	626 · 14 days
22:00	89.5%	2.6 min late	6.3 min late	478 · 13 days
23:00	95.3%	1.7 min late	4.8 min late	341 · 13 days

7 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

424 / 507 scheduled trips published at least one position across 7 service days (83.6%).

19:008 / 28 trips without a position71.4%
21:006 / 26 trips without a position76.9%
11:006 / 28 trips without a position78.6%
22:004 / 19 trips without a position78.9%
04:002 / 10 trips without a position80.0%
10:005 / 28 trips without a position82.1%

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 20, 2026 at 7:35 a.m.
Computed or assembled: September 20, 2026 at 7:32 a.m.
Sample: 20,253 settled arrivals across 1 matching reliability records.
Coverage: 4 published stop patterns containing 68 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.