Skip to main content

Service

FR

Report a problem

This page is not about one stop, route, station or vehicle. Open one to have the report name it, or use the full report.

What happened
Full report No account needed

Ward 8 · Ottawa · Councillor: Laine Johnson

College

College: 79.4% of predictions within five minutes.

Partial data · 2 days partly captured
Within five minutes
79.4%
Stops in the ward
331
Routes serving it
58
Cancelled trips
Not available yet
Not counted per ward yet

Where it is slowest

  • 80% and up 20
  • 60 to 80% 10
  • Under 60% 0
  • Too little data 28

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
RouteWithin 5 minCancelledCrowding
1163.3%Not publishedNot published
5365.8%Not publishedNot published
8170.6%Not publishedNot published
11071.6%Not publishedNot published
5772.7%Not publishedNot published
8074.2%Not publishedNot published
11175.5%Not publishedNot published
6275.5%Not publishedNot published

Cancellations and crowding are not published per route yet. 28 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.

What can be verified in College?

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

Provider prediction agreement

79.4%

of eligible predictions within five minutes of schedule

How this compares
Rank 10 of 22 · median 78.4%

Service, per the imported timetable

Scheduled trips at ward stops
Not available yet
Routes
58
Train lines
0

Current service inside this boundary

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

79.4% within five minutes of the timetable across 555,148 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.

Scheduled calls, sources and limits

58 routes · 331 stops. Timetable inventory, not trips delivered.

Cancellations at stops in this ward

Local count unavailable

The exact stop-call lookup did not finish within this page’s time budget. No zero, cancellation, or missed call is inferred.

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.

19 of 30 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 11, predictions later than timetable 14:00 to 23:00, 4.1 min late.

Best here: route 67, predictions consistently close to timetable, 96%.

30 of 30 routes here had something measurable to report.

Arrivals within five minutes, by hour of day, across the 30 routes graded here, last 14 days
  1. 00:00: 90.9% of final predictions within five minutes of the timetable, 21,816 predictions, typically 0.7 min late
  2. 01:00: 89.6% of final predictions within five minutes of the timetable, 7,735 predictions, typically 0.8 min late
  3. 02:00: 83.9% of final predictions within five minutes of the timetable, 4,220 predictions, typically 0.9 min late
  4. 03:00: 91.3% of final predictions within five minutes of the timetable, 2,491 predictions, typically 0.1 min late
  5. 04:00: 93.1% of final predictions within five minutes of the timetable, 6,870 predictions, typically 0.6 min late
  6. 05:00: 88.3% of final predictions within five minutes of the timetable, 26,827 predictions, typically 1.3 min late
  7. 06:00: 89.8% of final predictions within five minutes of the timetable, 59,655 predictions, typically 1.1 min late
  8. 07:00: 82.5% of final predictions within five minutes of the timetable, 77,675 predictions, typically 1.7 min late
  9. 08:00: 75.2% of final predictions within five minutes of the timetable, 78,124 predictions, typically 2.2 min late
  10. 09:00: 78.8% of final predictions within five minutes of the timetable, 76,807 predictions, typically 1.8 min late
  11. 10:00: 82.5% of final predictions within five minutes of the timetable, 74,821 predictions, typically 1.4 min late
  12. 11:00: 81.7% of final predictions within five minutes of the timetable, 74,291 predictions, typically 1.5 min late
  13. 12:00: 81% of final predictions within five minutes of the timetable, 74,718 predictions, typically 1.6 min late
  14. 13:00: 80.9% of final predictions within five minutes of the timetable, 74,219 predictions, typically 1.5 min late
  15. 14:00: 80.4% of final predictions within five minutes of the timetable, 76,158 predictions, typically 1.6 min late
  16. 15:00: 73% of final predictions within five minutes of the timetable, 77,640 predictions, typically 2.3 min late
  17. 16:00: 66.5% of final predictions within five minutes of the timetable, 84,066 predictions, typically 2.9 min late
  18. 17:00: 67.1% of final predictions within five minutes of the timetable, 85,032 predictions, typically 2.9 min late
  19. 18:00: 71.4% of final predictions within five minutes of the timetable, 79,687 predictions, typically 2.4 min late
  20. 19:00: 79.3% of final predictions within five minutes of the timetable, 67,800 predictions, typically 1.8 min late
  21. 20:00: 82.7% of final predictions within five minutes of the timetable, 62,551 predictions, typically 1.6 min late
  22. 21:00: 83.3% of final predictions within five minutes of the timetable, 56,139 predictions, typically 1.6 min late
  23. 22:00: 85.1% of final predictions within five minutes of the timetable, 45,796 predictions, typically 1.5 min late
  24. 23:00: 87.3% of final predictions within five minutes of the timetable, 34,387 predictions, typically 1 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
WhatWhenMeasuredScenario or next investigation
ProblemPredictions later than timetable11538157110806274731681611118287586611718715819 routes14:00 to 23:00 … 14:004.1 min late … 8.6 min lateMore running time
ProblemWide prediction spread11801173 routes18:00 to 20:00 … 15:0025 min swing … 47.8 min swingOperations, not the timetable
StrengthPredictions consistently close to timetable67842 routes05:00 to 22:00 · 06:00, 07:00, 08:00, 15:00, 16:00, 17:0096% · 98%Keep what works
ProblemOne hour has a lower prediction match5753168746211182877311258606611718715 routes16:00 … 08:0046% … 36%Operations, not the timetable
ProblemPredictions earlier than timetable1101 routes21:001.6 min earlyLess running time, or holding points
StrengthObserved-position lower bound7568116163571681611896760731166618715 routesAll measured hours100%Keep what works
CaveatCoverage gap5362748811111087808111258821171588415 routesAll measured hours98% … 95%More observation, not a service change

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

87.2%

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

68of 541

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

1of 541

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.6min

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

99.3%

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

Route-hours with wide prediction gaps

4of 541

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

Typical prediction gap

30.4min

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.

Provider prediction agreement

79.4% of eligible provider predictions were within five minutes of the timetable. 440,603 of 555,148 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
440,603
Eligible trip-stop predictions
555,148
Observed days
20 weekdays

How this compares

Ranked 10 of 22 measured wards. 1 points above 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

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

  1. 11Open route
    63.3%Predictions within five minutes

    179,840 eligible predictions across the whole route

  2. 53Open route
    65.8%Predictions within five minutes

    132,043 eligible predictions across the whole route

  3. 81Open route
    70.6%Predictions within five minutes

    146,779 eligible predictions across the whole route

  4. 110Open route
    71.6%Predictions within five minutes

    113,377 eligible predictions across the whole route

  5. 57Open route
    72.7%Predictions within five minutes

    101,116 eligible predictions across the whole route

  6. 80Open route
    74.2%Predictions within five minutes

    181,776 eligible predictions across the whole route

  7. 111Open route
    75.5%Predictions within five minutes

    114,122 eligible predictions across the whole route

  8. 62Open route
    75.5%Predictions within five minutes

    87,323 eligible predictions across the whole route

  9. 73Open route
    75.8%Predictions within five minutes

    39,126 eligible predictions across the whole route

  10. 158Open route
    77.0%Predictions within five minutes

    178 eligible predictions across the whole route

28 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

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.

Routes serving the ward

58 scheduled routes

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

━ 58 bus routes● 331 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) 7

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

Drinking water (City data) 5

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.

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 8: COLLEGE
Boundary and vintage
City ward layer · effective not published · imported August 4, 2026
Official civic contacts
  • Laine Johnson · 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
58 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.

Evidence dates

Imported
Computed or assembled
Sample
555,148 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:755b76d868f26c55dc74bfa12187134fcb667526dccfb826ea2689df6bf3c50b

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.