Ward 17 · Ottawa · Councillor: Shawn Menard

Capital

Take action for this ward

Capital: 74.5% of predictions within five minutes.

Partial data · 2 days partly captured

Within five minutes: 74.5%
Stops in the ward: 191
Routes serving it: 38
Cancelled trips: Not available yet; Not counted per ward yet

Where it is slowest

80% and up 9
60 to 80% 15
Under 60% 0
Too little data 12

Routes serving the ward, by their share of predictions within five minutes. Each route result covers the whole route.

Routes in this ward

Routes in this ward, least reliable first
Oháha	Within 5 min	Cancelled	Akwé:kon ronnónhstats
7	63.2%	Iah tekahiá:tonte	Iah tekahiá:tonte
19	64.2%	Iah tekahiá:tonte	Iah tekahiá:tonte
18	65.8%	Iah tekahiá:tonte	Iah tekahiá:tonte
56	67.8%	Iah tekahiá:tonte	Iah tekahiá:tonte
6	69.4%	Iah tekahiá:tonte	Iah tekahiá:tonte
110	71.6%	Iah tekahiá:tonte	Iah tekahiá:tonte
111	75.5%	Iah tekahiá:tonte	Iah tekahiá:tonte
9	75.8%	Iah tekahiá:tonte	Iah tekahiá:tonte

Cancellations and crowding are not published per route yet. 12 routes with too little data or a different service purpose are left out.

All routes and their sources

One-page brief

A printable summary of this ward for council and community meetings, with the same numbers, the method in plain words and dated sources.

Open the brief Compare with another ward

What can be verified in Capital?

Arrival predictions, the imported timetable and train notices. Each is shown with its own source.

Provider prediction agreement

74.5%

of eligible predictions within five minutes of schedule

How this compares: Rank 16 of 22 · median 78.4%

Service, per the imported timetable

Scheduled trips at ward stops: Not available yet
Ohahà:: 36
Ne train lines: 2

Kà:sere ó:nen kèn:'en

Open the live map

The live buses inside this boundary are on the Map tab.

Prediction measure, timetable inventory and methods

Service delivery · evidence state

Oct 28, 2026 – Nov 3, 2026

Cancellations at stops in this ward

Not publishable

No zero or missed trip is inferred when exact stop calls cannot be published.

Predictions at stops inside the ward

74.5% within five minutes of the timetable across 459,292 eligible final provider predictions and 20 weekdays. These are not verified physical arrivals.

Predictions do not prove physical arrival.

Routes to inspect

Oct 28, 2026 – Nov 3, 2026

If available, these are route-wide vehicle-position matches for routes serving the ward. They do not locate a missed trip inside this ward or prove a cancellation. Each comparison uses scheduled trips for that same route and window.

45
868 of 906 scheduled trips had a matched vehicle position
Inspect days
628
48 of 50 scheduled trips had a matched vehicle position
Inspect days
697
24 of 25 scheduled trips had a matched vehicle position
Inspect days

Scheduled calls, sources and limits

38 routes · 191 stops. Timetable inventory, not trips delivered.

Cancellations at stops in this ward

Local count cannot be published

Exact stop-call evidence could not be read for Oct 28, 2026 – Nov 3, 2026. No zero is assumed.

Dates, source versions and limits

Method: retained-pre-service-exact-trip-stop-call-v1. Cancellation-feed completeness and position coverage are unverified.

The retained timetables were fetched, imported and first activated before the service day. The archive does not prove they remained the active timetables throughout that period. Comparisons between places remain unavailable.

Ka' nikarihò:ten

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.

16 of 24 show repeated provider predictions later than the timetable, consistent with a possible scheduled running-time shortfall. A scheduler should test that scenario against operations; labour, fleet, recovery and transfer impacts are not established here.

Worst here: route 7, predictions later than timetable 12:00 to 21:00, 4 min late.

Best here: route 98, observed-position lower bound, 100%.

24 of 24 routes here had something measurable to report.

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

00:00: 88.7% of final predictions within five minutes of the timetable, 21,052 predictions, typically 0.9 min late
01:00: 86.6% of final predictions within five minutes of the timetable, 8,654 predictions, typically 1 min late
02:00: 84.8% of final predictions within five minutes of the timetable, 3,740 predictions, typically 1.1 min late
03:00: 82.5% of final predictions within five minutes of the timetable, 3,416 predictions, typically 1.1 min late
04:00: 87.3% of final predictions within five minutes of the timetable, 9,702 predictions, typically 1 min late
05:00: 89.8% of final predictions within five minutes of the timetable, 27,706 predictions, typically 0.9 min late
06:00: 86.8% of final predictions within five minutes of the timetable, 58,560 predictions, typically 1.3 min late
07:00: 82.5% of final predictions within five minutes of the timetable, 75,254 predictions, typically 1.7 min late
08:00: 75% of final predictions within five minutes of the timetable, 78,102 predictions, typically 2.2 min late
09:00: 78.9% of final predictions within five minutes of the timetable, 76,927 predictions, typically 1.7 min late
10:00: 83.3% of final predictions within five minutes of the timetable, 75,083 predictions, typically 1.4 min late
11:00: 80.3% of final predictions within five minutes of the timetable, 72,987 predictions, typically 1.6 min late
12:00: 76.3% of final predictions within five minutes of the timetable, 73,417 predictions, typically 2.1 min late
13:00: 76.3% of final predictions within five minutes of the timetable, 73,417 predictions, typically 2 min late
14:00: 77.1% of final predictions within five minutes of the timetable, 75,574 predictions, typically 1.8 min late
15:00: 69.5% of final predictions within five minutes of the timetable, 78,306 predictions, typically 2.7 min late
16:00: 63.8% of final predictions within five minutes of the timetable, 79,606 predictions, typically 3.2 min late
17:00: 64.2% of final predictions within five minutes of the timetable, 81,772 predictions, typically 3.1 min late
18:00: 70.4% of final predictions within five minutes of the timetable, 76,836 predictions, typically 2.5 min late
19:00: 77.1% of final predictions within five minutes of the timetable, 63,067 predictions, typically 1.9 min late
20:00: 81% of final predictions within five minutes of the timetable, 56,051 predictions, typically 1.7 min late
21:00: 81.8% of final predictions within five minutes of the timetable, 49,297 predictions, typically 1.6 min late
22:00: 84.9% of final predictions within five minutes of the timetable, 42,485 predictions, typically 1.6 min late
23:00: 86.7% of final predictions within five minutes of the timetable, 33,683 predictions, typically 1.3 min late

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

Findings
What	Ó:nen	Tewaterièn:tare	Scenario or next investigation
ProblemPredictions later than timetable7 6 18 19 110 92 56 44 9 5 41 42 39 111 49 4516 routes	12:00 to 21:00 … 01:00	4 min late … 7.2 min late	More running time
ProblemWide prediction spread19 105 63 routes	17:00 … 02:00	21.7 min swing … 37.9 min swing	Operations, not the timetable
ProblemOne hour has a lower prediction match6 92 18 44 111 41 5 19 112 9 105 49 45 5614 routes	17:00 … 01:00	46% … 33%	Operations, not the timetable
ProblemPredictions earlier than timetable110 442 routes	21:00 · 01:00	1.6 min early · 2.7 min early	Less running time, or holding points
StrengthObserved-position lower bound98 18 19 42 925 routes	All measured hours	100%	Keep what works
CaveatCoverage gap45 39 105 7 56 5 6 10 44 41 88 111 85 110 48 90 9 112 4919 routes	All measured hours	96% … 99%	More observation, not a service change

O-Train evidence

What we know about train service here

Open the train observation report

Trains are not in the public data feed

The bus punctuality reports compare archived arrival predictions with published schedules. They do not count independently measured physical arrivals. Otranspo has no comparable public train-position dataset for these reports, so those bus figures cannot show where a train is or whether Lines 1, 2 and 4 run on time.

Publishing train positions, their timestamps, and the measurement method would help build a separate, verifiable record of rail service. The missing dataset does not establish how the trains performed.

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 CAPITAL is doing

These indicators separate repeated delay from changes in the operator's arrival predictions. They suggest questions for planners and operations staff. They do not show the cause. They do not prove when buses arrived. Each figure shows its route-hour sample.

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

Scheduling

Repeated late predictions can point to a timetable worth reviewing. Check actual arrival and dispatch records before deciding whether running time needs to change.

Who can fix it: A service planner
What it costs: Iah tewaterièn:tare tó: nikaná:ien tsi niió:re ahontkáhtho ne ká'sere, ne raotiio'te tánon ne ò:ia.

Tsi ní:ioht kahiatónhsera tánon tsi nihawen:'en iah teiotsén:ion

83.8%

Route-hours: median arrival prediction iáh énska minute early, iáh áhsen minutes late.

Route-hours with repeated late predictions

78of 495

Route-hours where the median eligible arrival prediction is at least three minutes late. Review running time against actual operating records.

Route hours with early predictions

2of 495

Route-hours where the median eligible arrival prediction is at least one minute early. This does not show that buses left early.

Typical predicted delay

3.6min

The typical median predicted delay in flagged route-hours. It is not a validated amount to add to the timetable.

Operations

Iah skátne tewaterièn:tare tsi nahò:ten tó: nikahá:wi ne ká'sere ienkahá:wi. Ensewatkáhtho tsi niiorihò:ten. Ne ká'sere tsi niiohà:te, ne ronterihwakhéhtha, ne ahontá:wen tánon ne tsi kahiatónhsera tsi nikahá:wi iaonteweien'tà:'on. Iah ne ne'ne tsi ienkahá:wi ne tsi ahontaterièn:tara'ne tsi nahò:ten ne rorihwatsíhston.

Who can fix it: Ne ronterihwaién:tas, ó:ni oháha
What it costs: Cost unavailable until the operational cause and remedy are established.

Prediction gap below twenty minutes

99.2%

Ne tsi niiohà:te tánon ne ora'shòn:'a tsi nahò:ten ne 95-percentile ne tsi ienkahá:wi ne ká'sere iah tewáhsen minits tsi nikaié:rite tsi nà:'a ne median.

Route-hours with wide prediction gaps

4of 495

Route-hours where the 95th-percentile eligible prediction is at least twenty minutes later than the median. The cause needs investigation.

Typical prediction gap

23.4min

The usual gap between the 95th-percentile prediction and the median in flagged route-hours.

Service, per the imported timetable

Scheduled transit, provider prediction agreement with the timetable, and public services in this ward.

38
Ohahà:: 191
Tsi nón:we tkatkétskwas: 10
Washrooms: 9
Ohné:kanos tsi nón:we

Provider-prediction measure74.5%provider prediction within five minutes of the timetable

Provider prediction agreement

74.5% of eligible provider predictions were within five minutes of the timetable. 342,336 of 459,292 settled trip-stop predictions at stops inside this ward matched that range across 20 weekdays with feed evidence, from Oct 3, 2026 to Nov 3, 2026. These are provider predictions, not independently observed arrivals.

2 partial-capture days not counted.

Predictions within five minutes: 342,336
Eligible trip-stop predictions: 459,292
Observed days: 20 weekdays

How this compares

Ranked 16 of 22 measured wards. 3.9 points below the city median of 78.4%.

Highest: ward 22 at 85.1%. Lowest: ward 21 at 60.3%.

Only wards whose evidence meets the publication threshold are ranked. Same window and same method for each.

Which routes need closer review

24 of the 36 routes serving this ward have enough provider-prediction evidence to compare. Lowest timetable agreement first.

7Open route
63.2%Predictions within five minutes
211,314 eligible predictions across the whole route
19Open route
64.2%Predictions within five minutes
78,053 eligible predictions across the whole route
18Open route
65.8%Predictions within five minutes
96,916 eligible predictions across the whole route
56Open route
67.8%Predictions within five minutes
59,469 eligible predictions across the whole route
6Open route
69.4%Predictions within five minutes
191,599 eligible predictions across the whole route
110Open route
71.6%Predictions within five minutes
113,377 eligible predictions across the whole route
111Open route
75.5%Predictions within five minutes
114,122 eligible predictions across the whole route
9Open route
75.8%Predictions within five minutes
47,737 eligible predictions across the whole route
42Open route
76.6%Predictions within five minutes
54,954 eligible predictions across the whole route
92Open route
76.6%Predictions within five minutes
28,608 eligible predictions across the whole route

12 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.

Vehicle visibility to investigate
Oháha	Schedule trips	With a position	Without a matched position	Coverage	Oriwà:ke
45	906	868	38	95.8%	Wenhniserá:te 7 30
628	50	48	2	96.0%	Wenhniserá:te 7 30
697	25	24	1	96.0%	Wenhniserá:te 7 30
105	682	662	20	97.1%	Wenhniserá:te 7 30
56	637	621	16	97.5%	Wenhniserá:te 7 30
39	1,128	1,106	22	98.0%	Wenhniserá:te 7 30
7	931	912	19	98.0%	Wenhniserá:te 7 30
5	834	819	15	98.2%	Wenhniserá:te 7 30
10	759	746	13	98.3%	Wenhniserá:te 7 30
6	1,007	992	15	98.5%	Wenhniserá:te 7 30
44	802	791	11	98.6%	Wenhniserá:te 7 30
110	346	341	5	98.6%	Wenhniserá:te 7 30
41	770	761	9	98.8%	Wenhniserá:te 7 30
88	1,043	1,034	9	99.1%	Wenhniserá:te 7 30
49	214	212	2	99.1%	Wenhniserá:te 7 30
111	868	861	7	99.2%	Wenhniserá:te 7 30
48	616	611	5	99.2%	Wenhniserá:te 7 30
9	472	468	4	99.2%	Wenhniserá:te 7 30
85	894	888	6	99.3%	Wenhniserá:te 7 30
90	767	762	5	99.3%	Wenhniserá:te 7 30
112	482	479	3	99.4%	Wenhniserá:te 7 30
18	498	496	2	99.6%	Wenhniserá:te 7 30
98	889	886	3	99.7%	Wenhniserá:te 7 30
19	483	482	1	99.8%	Wenhniserá:te 7 30
42	420	419	1	99.8%	Wenhniserá:te 7 30
92	200	200	0	100.0%	Wenhniserá:te 7 30
698	50	50	0	100.0%	Wenhniserá:te 7 30
647	30	30	0	100.0%	Wenhniserá:te 7 30
646	20	20	0	100.0%	Wenhniserá:te 7 30
689	20	20	0	100.0%	Wenhniserá:te 7 30
609	20	20	0	100.0%	Wenhniserá:te 7 30
645	10	10	0	100.0%	Wenhniserá:te 7 30
617	10	10	0	100.0%	Wenhniserá:te 7 30
606	10	10	0	100.0%	Wenhniserá:te 7 30
613	5	5	0	100.0%	Wenhniserá:te 7 30
304	2	2	0	100.0%	Wenhniserá:te 7 30

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 · 40 boundary vertices · City of Ottawa ward boundaries · imported Aug 4, 2026

Route

━ 36 bus routes═ 2 train lines● 191 stops

Loading live feed

Public amenity record for this ward

Public washrooms and drinking water

Choose a category to check which location details are available.

Public washrooms (City data) 10

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

Drinking water (City data) 9

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

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.

How do you want to address this draft?

Choose an official City recipientEnter another recipient email

Subject

Your editable message

Evidence included with the draft

Canonical Otranspo evidence link: https://otranspo.ca/moh/city/wards/17
Sources and time: Sources and time: open the linked report for its source records and published or imported timestamps.
Limitations: Limitations: Otranspo is independent and may show unknown, suppressed, delayed, or corrected values. Confirm urgent or current service matters with the official agency.

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.

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 17: CAPITAL
Boundary and vintage: City ward layer · effective not published · imported August 4, 2026
Official civic contacts: Shawn Menard · Councillor · source check is older than the publication threshold · source checked August 4, 2026 · official City contact source
Mark Sutcliffe · Rakowá:nen · source check is older than the publication threshold · source checked August 4, 2026 · official City contact source
Relevant scheduled service: 38 public route records with a stop inside this boundary · operators: OC Transpo
Transit evidence vintage: Timetable import: not published · reliability window: Oct 3, 2026 – Nov 3, 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.

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 eligible final OC Transpo provider predictions 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 eligible final provider prediction per trip, stop, and service date in the latest 28 completed service days. Within five minutes is measured against the timetable, not a physical arrival. Publication requires 20 weekdays with prediction evidence and 500 eligible predictions.

Imported: August 4, 2026 at 10:43 a.m.
Computed or assembled: November 4, 2026 at 12:17 p.m.
Kén:k nikón: 459,292 eligible settled provider predictions across 20 weekdays with prediction evidence support the reliability result.
Method or data version: ward-counts-v1 + ward-stop-settled-arrivals-purpose-aware-v3
Source checksum: ward-reliability:eaff436177693c4c95f13493c07f6448356f0150dca519baf0d387d0b8393ad5

Tsi nón: ionkwaién:ta'

Limits to keep in mind

Counts describe the published inventory inside the boundary, not service quality or access from every address.
Reliability covers final OC Transpo provider predictions at geographically assigned stops; physical arrivals are not independently measured. Rail and trips without eligible prediction evidence are not represented.
An unavailable count remains unavailable. It is not changed to zero.

Suggest a factual correction

Tsi ní:ioht tsi iakwaié:ren

For each trip, stop and service date at stops inside the ward, we keep the last eligible OC Transpo prediction and compare it with the timetable. It counts as within five minutes when the two are no more than five minutes apart. This is not a physical arrival.

The window is the latest 28 completed service days. A result is published only with 20 weekdays of prediction evidence and 500 eligible predictions. Route results cover each whole route, not only the part inside the ward.

Read the full method

Contains information licensed under the Open Government Licence – City of Ottawa.

Draft

This translation is a draft.

Help improve it

About 23% of this site is translated so far. The rest is shown in English.

Read this page in English

This page is a machine draft in Mohawk (Kanien’kéha), the language of the Kanien’kehá:ka (Mohawk) communities. It was prepared without review by its speakers, and is waiting for one. Speakers and the community are invited to correct it. We will replace it with their words. Ottawa is on the unceded territory of the Anishinabe Algonquin Nation.

Cette page est une ébauche automatique en mohawk (kanien’kéha), la langue des communautés kanien’kehá:ka (mohawks). Elle a été préparée sans révision par ses locuteurs, et attend l’un d’eux. Les locuteurs et la communauté sont invités à la corriger. Nous la remplacerons par leurs mots. Ottawa se trouve sur le territoire non cédé de la Nation algonquine anishinabe (Anishinabe Algonquin Nation).

Sahró:ri tsi nahò:ten iah tekaié:ri

Capital

Capital: 74.5% of predictions within five minutes.

Where it is slowest

Routes in this ward

One-page brief

What can be verified in Capital?

Provider prediction agreement

Service, per the imported timetable

Kà:sere ó:nen kèn:'en

Service delivery · evidence state

Routes to inspect

What would fix transit here

What we know about train service here

Recent shared train observations

How CAPITAL is doing

Scheduling

Operations

Service, per the imported timetable

Provider prediction agreement

How this compares

Which routes need closer review

Routes serving the ward

Bus routes · 36

Train lines · 2

Current service inside this boundary

Public washrooms and drinking water

Prepare an email for City Hall

Evidence included with the draft

Community reports

Civic evidence brief

What is being shown

How it was produced

Tsi nón: ionkwaién:ta'

Limits to keep in mind

Capital: 74.5% of predictions within five minutes.

Where it is slowest

Routes in this ward

One-page brief

What can be verified in Capital?

Provider prediction agreement

Service, per the imported timetable

Kà:sere ó:nen kèn:'en

Service delivery · evidence state

Routes to inspect

What would fix transit here

What we know about train service here

Recent shared train observations

How CAPITAL is doing

Scheduling

Operations

Service, per the imported timetable

Provider prediction agreement

How this compares

Which routes need closer review

Vehicle visibility to investigate

Routes serving the ward

Bus routes · 36

Train lines · 2

Current service inside this boundary

Public washrooms and drinking water

Prepare an email for City Hall

Evidence included with the draft

Community reports

Civic evidence brief

Share this page

What is being shown

How it was produced

Evidence dates

Tsi nón: ionkwaién:ta'

Limits to keep in mind