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

Ward 20 · Ottawa

OSGOODE

Councillor: Isabelle Skalski

6
Routes: 104
Stops: -
within five minutes

Boundaries: City of Ottawa ward layer; imported August 4, 2026.Prepare an email for City Hall →

Civic evidence brief

The identity, boundary, contacts, service scope and evidence dates behind this ward report, kept together so the page can be cited without losing its qualifications.

Municipality: City of Ottawa, Ontario
Geographic unit: Official City of Ottawa municipal ward 20: OSGOODE
Boundary and vintage: City ward layer · effective not published · imported August 4, 2026
Official civic contacts: Isabelle Skalski · Councillor · source check is older than the publication threshold · source checked August 4, 2026 · official City contact source
Mark Sutcliffe · Mayor · source check is older than the publication threshold · source checked August 4, 2026 · official City contact source
Relevant scheduled service: 6 public route records with a stop inside this boundary · operators: OC Transpo
Transit evidence vintage: Timetable import: not published · reliability window: Aug 25, 2026 – Sep 22, 2026

A ward boundary, route inventory, destination list, population count or employment count supplies civic context. None of those values alone measures passenger demand, household trip effects, transfers or daily attendance.

Ottawa wards are municipal wards. They are not Gatineau electoral districts, and results from the two boundary systems are not interchangeable.

Verdict

What would fix transit here

Worked out from the routes that serve this ward. Each item names the route, when it happens, and what would change it.

1 of 2 show a repeated lateness pattern consistent with insufficient scheduled running time. A scheduler should test a running-time scenario; labour, fleet, recovery and transfer impacts are not established here.

Worst here: route 110, late by the timetable 16:00 to 18:00, 4.1 min late.

2 of 2 routes here had something measurable to report.

Arrivals within five minutes, by hour of day, across the 2 routes graded here, last 14 days

00:00: 85.9% of arrivals on time, 1,864 arrivals, typically 0.9 min late
01:00: 83% of arrivals on time, 1,561 arrivals, typically 1.3 min late
02:00: 82.7% of arrivals on time, 1,475 arrivals, typically 1 min late
03:00: 89.5% of arrivals on time, 1,529 arrivals, typically 0.6 min late
04:00: 92.5% of arrivals on time, 2,264 arrivals, typically 1.2 min late
05:00: 83.2% of arrivals on time, 5,390 arrivals, typically 1.5 min late
06:00: 89.2% of arrivals on time, 5,825 arrivals, typically 0.8 min late
07:00: 83% of arrivals on time, 6,328 arrivals, typically 1.3 min late
08:00: 77.4% of arrivals on time, 5,615 arrivals, typically 1.8 min late
09:00: 76.9% of arrivals on time, 5,878 arrivals, typically 1.7 min late
10:00: 80.4% of arrivals on time, 5,726 arrivals, typically 1.2 min late
11:00: 81.1% of arrivals on time, 5,172 arrivals, typically 1.1 min late
12:00: 78.2% of arrivals on time, 5,281 arrivals, typically 1.7 min late
13:00: 78.7% of arrivals on time, 5,166 arrivals, typically 1.5 min late
14:00: 82.6% of arrivals on time, 4,827 arrivals, typically 0.8 min late
15:00: 71.9% of arrivals on time, 4,574 arrivals, typically 1.9 min late
16:00: 58.3% of arrivals on time, 4,940 arrivals, typically 3.9 min late
17:00: 63% of arrivals on time, 5,683 arrivals, typically 2.9 min late. Unreliable: a bad trip runs far behind a normal one.
18:00: 69.5% of arrivals on time, 5,926 arrivals, typically 1.7 min late
19:00: 75.3% of arrivals on time, 5,623 arrivals, typically 1.7 min late
20:00: 72.4% of arrivals on time, 4,937 arrivals, typically 2.5 min late
21:00: 85.5% of arrivals on time, 2,238 arrivals, typically 0.8 min late
22:00: 90.5% of arrivals on time, 1,453 arrivals, typically 0.9 min late
23:00: 83.7% of arrivals on time, 1,378 arrivals, typically 1 min late

90% or more on time
80 to 90% on time
under 80% on time
not enough data
unreliable: a bad trip runs 20 min or more behind a normal one

What	When	Measured	Scenario or next investigation
ProblemLate by the timetable1101 routes	16:00 to 18:00 … 04:00	4.1 min late … 3.1 min late	More running time
ProblemUnreliable1051 routes	17:00	30.6 min swing	Operations, not the timetable
ProblemOne hour collapses1101 routes	16:00	49%	Operations, not the timetable

Map & current service

Current service inside this boundary

Scheduled lines, stops, and observed buses share one map. Select a route or vehicle for details.

Evidence & sources

Imported municipal polygon · 95 boundary vertices · City of Ottawa ward boundaries · imported Aug 4, 2026

Route

━ 5 bus routes═ 1 train lines● 104 stops

Loading live feed

O-Train evidence

What we know about train service here

Open the train observation report

Trains are not in the public data feed

OC Transpo publishes live positions for its buses, and this site measures them: millions of bus arrivals every month, which is where every bus figure on this site comes from. The same public feed carries no train positions, so this site has never recorded a single train arrival. Nothing here can tell you where a train is, or whether Lines 1, 2 and 4 run on time.

This is a gap in what is published, not a gap in the trains. If train positions were published the way bus positions already are, riders would get the same record for rail that they have for every bus route on this site.

Recent shared train observations

These are rider sightings approved by a moderator. They show a reported time and place. They are not official train positions, a complete train count, or proof of a cause.

No approved rider observation matches this place or line in the last 31 days. That does not mean no train ran or no problem occurred.

Share what you observed Check all official service alerts Open train research and history

Official timetable

OC Transpo does not publish O-Train positions or arrival predictions in the public feed Otranspo receives. Schedules, official alerts, and rider observations are shown separately so one source cannot impersonate another.

Ask for this data

Turn this gap into a public-data request

OC Transpo does not publish live O-Train positions in the public feed Otranspo can use. You can ask the City to publish them in a stable, reusable format.

This is your message. Edit it before opening your own email app. Otranspo does not send it, track delivery, or speak for you. Write to one relevant recipient; do not use this tool for mass email, harassment, or personal or sensitive information.

How do you want to address this draft?

Choose an official recipientEnter another recipient email

Subject

Message

Choose an official recipient or enter one valid other email address to open an email draft.

Check the official councillor directory →Send through OC Transpo’s official feedback form →Official contact sources →

How OSGOODE is doing

Two different failures hide inside one on-time percentage, and they have opposite fixes. These separate them. Each figure is a share of the route-hours this site measured well enough to speak for, and the count it is out of is shown beside it.

Measured over 42 route-hours. 0 more were observed too thinly to count, and are excluded rather than assumed good.

Scheduling

Whether the timetable describes the trip that is actually made. A route late by the same amount every day is not unreliable, it is mis-scheduled, and every operator is driving a schedule nobody can keep.

Who can fix it: A service planner
What it costs: Cost unavailable until fleet, labour, recovery and transfer effects are tested.

Timetable matches the trip

90.5%

Hours where the middle arrival is within three minutes late and one minute early of the timetable.

Route-hours where the timetable is short

4of 42

Hours where the middle arrival is three minutes late or worse. Each is a candidate for a running-time rewrite.

Route-hours running early

0of 42

Hours where buses typically leave early. Riders who arrive on time can still watch one go.

Running time a short hour needs

3.2min

For a typical short hour, the minutes a planner would add.

Operations

Whether a bad trip is close to a normal one. A route on time on average but wildly variable has a timetable that is right and something else that is not. Padding the schedule here makes every rider’s trip longer while the bad trips stay bad.

Who can fix it: Operations, and often the road itself
What it costs: Cost unavailable until the operational cause and remedy are established.

A bad trip is close to a normal one

97.6%

Hours where the worst trips run less than twenty minutes behind the normal one.

Route-hours that are unpredictable

1of 42

Hours where they run twenty minutes or more behind it. Adding running time does not fix these.

How far behind a bad trip runs

30.6min

For a typical unpredictable hour, how far behind a bad trip runs.

Service, per the imported timetable

A readable view of scheduled transit, observed reliability, and public services in this ward.

6
Routes: 104
Stops: 13
Washrooms: 3
Water locations

Named ward measurenot publishedwithin five minutes

Observed reliability

74 settled OC Transpo arrivals are available at stops inside this ward across 16 observed weekdays. A percentage remains unavailable until the evidence reaches 500 arrivals and 20 observed weekdays.

On-time arrivals: 40
Settled arrivals: 74
Observed days: 16 weekdays

Which routes are pulling this ward down

2 of the 5 routes serving this ward have enough evidence to compare. Least punctual first.

Route	Within five minutes	Arrivals checked
110	72.2%	84,521
105	88.4%	48,484

3 more routes here are not ranked: school, express, shopper or event service, whose schedule result does not compare the same way.

Vehicle visibility to investigate

The current summary uses seven days. For every route, you can also open yesterday, the last 7 days, or the last 30 days and inspect the day, scheduled trip, excluded feed gaps, and every observed public vehicle ID. An absence does not prove a vehicle fault or operator decision.

Route	Scheduled trips	With a position	Without a matched position	Coverage	History
299	50	39	11	78.0%	Day 7 30
222	30	24	6	80.0%	Day 7 30
110	344	280	64	81.4%	Day 7 30
105	678	575	103	84.8%	Day 7 30
304	2	2	0	100.0%	Day 7 30

Routes serving the ward

6 scheduled routes

Bus routes · 5

Train lines · 1

2Train

Public washrooms (City data) 13

The public ward snapshot publishes the count but not the individual locations for this ward. No locations are being invented.

Drinking water (City data) 3

The public ward snapshot publishes the count but not the individual locations for this ward. No locations are being invented.

Rate or report an issue

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.

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.

Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.

What is being shown

A ward-level inventory of scheduled transit, public washrooms, drinking-water locations, and observed OC Transpo bus arrivals at stops inside the ward.

How it was produced

Current imported records are assigned by point-in-polygon to the sourced ward boundary. Reliability uses one settled arrival per trip, stop, and service date in the latest 28 completed service days. On time is within ±5 minutes, with publication thresholds of 20 observed weekdays and 500 arrivals.

Imported: August 4, 2026 at 10:43 a.m.
Computed or assembled: September 23, 2026 at 10:18 a.m.
Sample: 74 settled arrivals across 16 observed weekdays support the reliability result.
Method or data version: ward-counts-v1 + ward-stop-settled-arrivals-purpose-aware-v3
Source checksum: ward-reliability:be07a0c0a6ec935fcf284718f61d00d411f94b93be4446b7bf50f68318f51ad6

Sources

Limits to keep in mind

Counts describe the published inventory inside the boundary, not service quality or access from every address.
Reliability covers observed OC Transpo bus arrivals at geographically assigned stops. Rail and arrivals without settled evidence are not represented.
An unavailable count remains unavailable. It is not changed to zero.

Suggest a factual correction →

Prepare an email for City Hall

Choose one current office or enter one other recipient, edit the neutral draft, then review it in your own email app.

Otranspo never sends this message and cannot see whether it was sent, received, or answered.

Send only to the relevant office. Avoid mass email, harassment, report receipts, account details, health information, phone numbers, or an exact personal location. Remove anything you do not want the recipient or email provider to retain.

If no email app opens, copy the draft below and paste it into the email service you choose.