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

Ward 12 · Ottawa

RIDEAU-VANIER

Councillor: Stéphanie Plante

45
Routes: 210
Stops: 63.7%
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 12: RIDEAU-VANIER
Boundary and vintage: City ward layer · effective not published · imported August 4, 2026
Official civic contacts: Stéphanie Plante · 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: 45 public route records with a stop inside this boundary · operators: OC Transpo
Transit evidence vintage: Timetable import: not published · reliability window: Aug 23, 2026 – Sep 21, 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.

32 of 36 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 7, late by the timetable 08:00 to 23:00, 4.1 min late.

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

34 of 36 routes here had something measurable to report.

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

00:00: 88.7% of arrivals on time, 36,949 arrivals, typically 1.3 min late
01:00: 88.9% of arrivals on time, 14,834 arrivals, typically 1 min late
02:00: 83.8% of arrivals on time, 8,553 arrivals, typically 0.9 min late
03:00: 85.4% of arrivals on time, 6,284 arrivals, typically 0.8 min late
04:00: 91% of arrivals on time, 12,518 arrivals, typically 1 min late
05:00: 92% of arrivals on time, 32,912 arrivals, typically 1.2 min late
06:00: 88.9% of arrivals on time, 78,571 arrivals, typically 1.4 min late
07:00: 80.7% of arrivals on time, 104,769 arrivals, typically 1.8 min late
08:00: 65.9% of arrivals on time, 110,303 arrivals, typically 3.1 min late
09:00: 68.5% of arrivals on time, 107,877 arrivals, typically 2.9 min late
10:00: 77.1% of arrivals on time, 105,185 arrivals, typically 2 min late
11:00: 76.3% of arrivals on time, 101,885 arrivals, typically 2.2 min late
12:00: 70.9% of arrivals on time, 102,791 arrivals, typically 2.6 min late
13:00: 71% of arrivals on time, 97,969 arrivals, typically 2.5 min late
14:00: 68.5% of arrivals on time, 96,951 arrivals, typically 2.8 min late
15:00: 58.5% of arrivals on time, 100,009 arrivals, typically 3.9 min late
16:00: 53.6% of arrivals on time, 106,875 arrivals, typically 4.7 min late
17:00: 58.3% of arrivals on time, 108,356 arrivals, typically 3.9 min late
18:00: 67.9% of arrivals on time, 102,814 arrivals, typically 3 min late
19:00: 69.1% of arrivals on time, 80,867 arrivals, typically 2.9 min late
20:00: 71.1% of arrivals on time, 74,039 arrivals, typically 2.9 min late
21:00: 73.5% of arrivals on time, 69,978 arrivals, typically 2.6 min late
22:00: 77.9% of arrivals on time, 66,837 arrivals, typically 2.2 min late
23:00: 84.3% of arrivals on time, 56,429 arrivals, typically 1.6 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 timetable7 12 20 56 59STO 6 11 33STO 55STO 32STO 19 18 14 57 10 9 15 34STO 5 85STO 37STO 35STO 31STO 17 38STO 400STO 39 200STO 87STO 36STO 4531 routes	08:00 to 23:00 … 01:00	4.1 min late … 9 min late	More running time
ProblemUnreliable20 32STO 12 37STO 85STO 105 457 routes	16:00 to 18:00 … 09:00	23.6 min swing … 20.5 min swing	Operations, not the timetable
ProblemOne hour collapses55STO 57 59STO 33STO 56 14 32STO 5 37STO 35STO 31STO 15 20 87STO 9 85STO 36STO 17 45 38STO20 routes	16:00 … 00:00	43% … 57%	Operations, not the timetable
CaveatCoverage gap400STO 38STO 59STO 31STO 55STO 200STO 34STO 67STO 32STO 37STO 35STO 33STO 87STO 36STO14 routes	All measured hours	98% … 99%	More observation, not a service change
StrengthObserved-position lower bound85STO1 routes	All measured hours	100%	Keep what works

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

Route

━ 44 bus routes═ 1 train lines● 210 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 RIDEAU-VANIER 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 691 route-hours. 4 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

70.2%

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

Route-hours where the timetable is short

206of 691

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 691

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

Running time a short hour needs

3.9min

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

98.8%

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

Route-hours that are unpredictable

8of 691

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

How far behind a bad trip runs

22.8min

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.

45
Routes: 210
Stops: 9
Washrooms: 9
Water locations

Named ward measure63.7%within five minutes

Observed reliability

63.7% within five minutes. 168,961 of 265,248 settled OC Transpo arrivals at stops inside this ward were on time across 20 observed weekdays, from Aug 23, 2026 to Sep 21, 2026.

On-time arrivals: 168,961
Settled arrivals: 265,248
Observed days: 20 weekdays

How this compares

Ranked 21 of 22 measured wards. 13.9 points below the city median of 77.6%.

Highest: ward 22 at 85.7%. Lowest: ward 21 at 56.5%.

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

Which routes are pulling this ward down

36 of the 44 routes serving this ward have enough evidence to compare. Least punctual first.

Route	Within five minutes	Arrivals checked
17	52.3%	5,509
56	57.8%	41,665
7	61.0%	148,744
20	62.2%	63,544
18	62.4%	67,101
12	62.5%	142,235
19	63.5%	54,133
15	65.1%	20,879
14	65.5%	104,258
11	68.0%	127,218

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.

Route	Scheduled trips	With a position	Without a matched position	Coverage	History
E1	180	133	47	73.9%	Day 7 30
609	20	15	5	75.0%	Day 7 30
15	240	185	55	77.1%	Day 7 30
17	65	52	13	80.0%	Day 7 30
602	30	24	6	80.0%	Day 7 30
616	15	12	3	80.0%	Day 7 30
606	10	8	2	80.0%	Day 7 30
624	10	8	2	80.0%	Day 7 30
615	5	4	1	80.0%	Day 7 30
5	834	683	151	81.9%	Day 7 30
56	637	524	113	82.3%	Day 7 30
12	1,000	830	170	83.0%	Day 7 30
6	1,006	836	170	83.1%	Day 7 30
45	904	751	153	83.1%	Day 7 30
57	601	500	101	83.2%	Day 7 30
19	483	402	81	83.2%	Day 7 30
11	797	664	133	83.3%	Day 7 30
18	498	416	82	83.5%	Day 7 30
10	759	636	123	83.8%	Day 7 30
14	763	640	123	83.9%	Day 7 30
61	752	632	120	84.0%	Day 7 30
9	472	397	75	84.1%	Day 7 30
39	1,124	949	175	84.4%	Day 7 30
7	931	787	144	84.5%	Day 7 30
85	889	751	138	84.5%	Day 7 30
75	1,259	1,066	193	84.7%	Day 7 30
105	678	574	104	84.7%	Day 7 30
20	448	382	66	85.3%	Day 7 30
38	552	535	17	96.9%	Day 7 30
200	300	292	8	97.3%	Day 7 30
59	607	593	14	97.7%	Day 7 30
37	340	333	7	97.9%	Day 7 30
31	509	500	9	98.2%	Day 7 30
34	442	434	8	98.2%	Day 7 30
35	335	329	6	98.2%	Day 7 30
400	1,227	1,206	21	98.3%	Day 7 30
87	115	113	2	98.3%	Day 7 30
67	485	477	8	98.4%	Day 7 30
55	608	599	9	98.5%	Day 7 30
32	505	498	7	98.6%	Day 7 30
36	70	69	1	98.6%	Day 7 30
33	487	483	4	99.2%	Day 7 30
371	328	326	2	99.4%	Day 7 30
85	105	105	0	100.0%	Day 7 30

Routes serving the ward

45 scheduled routes

Bus routes · 44

Train lines · 1

1Train

Public washrooms (City data) 9

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.

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 22, 2026 at 10:18 p.m.
Sample: 265,248 settled arrivals across 20 observed weekdays support the reliability result.
Method or data version: ward-counts-v1 + ward-stop-settled-arrivals-purpose-aware-v3
Source checksum: ward-reliability:e551512b7c6a587766951a862cc40f419fe141fafa2c9eeb709f420cf2f0e1e0

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.