Ward 13 · Ottawa · Councillor: Rawlson King

Rideau-Rockcliffe

Take action for this ward

Rideau-Rockcliffe: 66.2% of predictions within five minutes.

Partial data · 3 days partly captured

Within five minutes: 66.2%
Stops in the ward: 209
Routes serving it: 27
Cancelled trips: Not available yet; Not counted per ward yet

Where it is slowest

80% and up 4
60 to 80% 12
Under 60% 2
Too little data 8

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
Route	Within 5 min	Cancelled	Crowding
23	43.0%	Not published	Not published
17	48.0%	Not published	Not published
7	63.6%	Not published	Not published
12	64.3%	Not published	Not published
19	64.6%	Not published	Not published
20	65.5%	Not published	Not published
18	66.1%	Not published	Not published
15	68.4%	Not published	Not published

Cancellations and crowding are not published per route yet. 8 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 Rideau-Rockcliffe?

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

Provider prediction agreement

66.2%

of eligible predictions within five minutes of schedule

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

Service, per the imported timetable

Scheduled trips at ward stops: Not available yet
Routes: 26
Train lines: 1

Current service inside this boundary

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 27, 2026 – Nov 2, 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

66.2% within five minutes of the timetable across 304,064 eligible final provider predictions and 20 weekdays. These are not verified physical arrivals.

Predictions do not prove physical arrival.

Routes to inspect

Oct 27, 2026 – Nov 2, 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.

616
14 of 15 scheduled trips had a matched vehicle position
Inspect days
15
231 of 240 scheduled trips had a matched vehicle position
Inspect days
105
662 of 682 scheduled trips had a matched vehicle position
Inspect days

Scheduled calls, sources and limits

27 routes · 209 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 27, 2026 – Nov 2, 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.

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.

16 of 18 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 12, predictions later than timetable 09:00 to 21:00, 4 min late.

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

18 of 18 routes here had something measurable to report.

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

00:00: 84% of final predictions within five minutes of the timetable, 18,375 predictions, typically 1.5 min late
01:00: 86.9% of final predictions within five minutes of the timetable, 9,163 predictions, typically 1 min late
02:00: 87% of final predictions within five minutes of the timetable, 4,165 predictions, typically 0.7 min late
03:00: 83.5% of final predictions within five minutes of the timetable, 3,408 predictions, typically 1 min late
04:00: 85.9% of final predictions within five minutes of the timetable, 8,577 predictions, typically 1.3 min late
05:00: 92.3% of final predictions within five minutes of the timetable, 19,152 predictions, typically 0.9 min late
06:00: 86% of final predictions within five minutes of the timetable, 39,823 predictions, typically 1.6 min late
07:00: 79.5% of final predictions within five minutes of the timetable, 50,553 predictions, typically 1.9 min late
08:00: 68.6% of final predictions within five minutes of the timetable, 56,180 predictions, typically 2.8 min late
09:00: 72.7% of final predictions within five minutes of the timetable, 55,759 predictions, typically 2.3 min late
10:00: 77.5% of final predictions within five minutes of the timetable, 53,974 predictions, typically 2.1 min late
11:00: 75% of final predictions within five minutes of the timetable, 53,452 predictions, typically 2.3 min late
12:00: 67.9% of final predictions within five minutes of the timetable, 53,810 predictions, typically 3 min late
13:00: 69.9% of final predictions within five minutes of the timetable, 53,946 predictions, typically 2.7 min late
14:00: 68.3% of final predictions within five minutes of the timetable, 51,758 predictions, typically 2.7 min late
15:00: 61.2% of final predictions within five minutes of the timetable, 52,726 predictions, typically 3.6 min late
16:00: 54.8% of final predictions within five minutes of the timetable, 56,080 predictions, typically 4.5 min late
17:00: 57.1% of final predictions within five minutes of the timetable, 60,540 predictions, typically 4 min late
18:00: 62.6% of final predictions within five minutes of the timetable, 56,547 predictions, typically 3.4 min late
19:00: 69.5% of final predictions within five minutes of the timetable, 45,542 predictions, typically 2.8 min late
20:00: 76.2% of final predictions within five minutes of the timetable, 41,298 predictions, typically 2.2 min late
21:00: 75.3% of final predictions within five minutes of the timetable, 37,824 predictions, typically 2.4 min late
22:00: 78.1% of final predictions within five minutes of the timetable, 34,190 predictions, typically 2.2 min late
23:00: 80.2% of final predictions within five minutes of the timetable, 28,256 predictions, typically 1.9 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	When	Measured	Scenario or next investigation
ProblemPredictions later than timetable12 7 6 24 20 18 19 14 9 17 15 41 25 47 39 2316 routes	09:00 to 21:00 … 04:00	4 min late … 3.8 min late	More running time
ProblemWide prediction spread20 24 19 105 23 66 routes	16:00 to 18:00 … 02:00	28.6 min swing … 37.8 min swing	Operations, not the timetable
ProblemOne hour has a lower prediction match6 7 24 25 20 18 41 40 19 9 15 17 105 47 2315 routes	17:00 … 06:00	48% … 12%	Operations, not the timetable
ProblemPredictions earlier than timetable23 472 routes	17:00 · 12:00	5.1 min early · 1 min early	Less running time, or holding points
StrengthObserved-position lower bound40 18 19 234 routes	All measured hours	100%	Keep what works
CaveatCoverage gap105 39 7 6 14 12 15 41 25 24 20 9 17 4714 routes	All measured hours	97% … 96%	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 RIDEAU-ROCKCLIFFE is doing

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

Measured over 336 route-hours. 3 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: Cost unavailable until fleet, labour, recovery and transfer effects are tested.

Predictions close to the timetable

69%

Route-hours where the median eligible arrival prediction is less than one minute early and less than three minutes late.

Route-hours with repeated late predictions

102of 336

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 336

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

Typical predicted delay

3.8min

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

Operations

Wide variation in arrival predictions calls for an operational review. Traffic, dispatch, boarding and timetable design may contribute; these predictions alone cannot identify the cause or the remedy.

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

Prediction gap below twenty minutes

97.6%

Route-hours where the 95th-percentile eligible prediction is less than twenty minutes later than the median.

Route-hours with wide prediction gaps

8of 336

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

Typical prediction gap

24.8min

The typical gap between the 95th-percentile eligible 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.

27
Routes: 209
Stops: 3
Washrooms: 4
Water locations

Provider-prediction measure66.2%provider prediction within five minutes of the timetable

Provider prediction agreement

66.2% of eligible provider predictions were within five minutes of the timetable. 201,199 of 304,064 settled trip-stop predictions at stops inside this ward matched that range across 20 weekdays with feed evidence, from Oct 1, 2026 to Nov 2, 2026. These are provider predictions, not independently observed arrivals.

3 partial-capture days not counted.

Predictions within five minutes: 201,199
Eligible trip-stop predictions: 304,064
Observed days: 20 weekdays

How this compares

Ranked 20 of 22 measured wards. 12.2 points below the city median of 78.4%.

Highest: ward 22 at 84.9%. 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

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

23Open route
43.0%Predictions within five minutes
5,801 eligible predictions across the whole route
17Open route
48.0%Predictions within five minutes
7,854 eligible predictions across the whole route
7Open route
63.6%Predictions within five minutes
211,381 eligible predictions across the whole route
12Open route
64.3%Predictions within five minutes
205,234 eligible predictions across the whole route
19Open route
64.6%Predictions within five minutes
78,076 eligible predictions across the whole route
20Open route
65.5%Predictions within five minutes
89,846 eligible predictions across the whole route
18Open route
66.1%Predictions within five minutes
96,912 eligible predictions across the whole route
15Open route
68.4%Predictions within five minutes
29,316 eligible predictions across the whole route
14Open route
69.7%Predictions within five minutes
147,898 eligible predictions across the whole route
6Open route
69.8%Predictions within five minutes
191,362 eligible predictions across the whole route

8 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
Route	Scheduled trips	With a position	Without a matched position	Coverage	History
616	15	14	1	93.3%	Day 7 30
15	240	231	9	96.3%	Day 7 30
105	682	662	20	97.1%	Day 7 30
7	931	912	19	98.0%	Day 7 30
14	763	748	15	98.0%	Day 7 30
39	1,128	1,109	19	98.3%	Day 7 30
6	1,007	990	17	98.3%	Day 7 30
17	65	64	1	98.5%	Day 7 30
47	84	83	1	98.8%	Day 7 30
12	1,006	995	11	98.9%	Day 7 30
41	770	762	8	99.0%	Day 7 30
25	760	753	7	99.1%	Day 7 30
20	448	444	4	99.1%	Day 7 30
24	618	613	5	99.2%	Day 7 30
9	472	468	4	99.2%	Day 7 30
40	804	801	3	99.6%	Day 7 30
18	498	496	2	99.6%	Day 7 30
19	483	481	2	99.6%	Day 7 30
23	40	40	0	100.0%	Day 7 30
609	20	20	0	100.0%	Day 7 30
633	10	10	0	100.0%	Day 7 30
606	10	10	0	100.0%	Day 7 30
624	10	10	0	100.0%	Day 7 30
620	5	5	0	100.0%	Day 7 30
615	5	5	0	100.0%	Day 7 30
302	2	2	0	100.0%	Day 7 30

Routes serving the ward

27 scheduled routes

Bus routes · 26

Train lines · 1

1Train

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

Route

━ 26 bus routes═ 1 train lines● 209 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) 3

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

Drinking water (City data) 4

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/en/city/wards/13
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 13: RIDEAU-ROCKCLIFFE
Boundary and vintage: City ward layer · effective not published · imported August 4, 2026
Official civic contacts: Rawlson King · 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: 27 public route records with a stop inside this boundary · operators: OC Transpo
Transit evidence vintage: Timetable import: not published · reliability window: Oct 1, 2026 – Nov 2, 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 3, 2026 at 6:17 p.m.
Sample: 304,064 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:a1440dfa779ab879aae685e4e203d29fab0f3ceeb667c92b91a4afe6bf1c42c6

Sources

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

How we measure this

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.