Wà:s ne kahiatónhsera

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

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

Oh nahò:ten iahà:wen
Full report No account needed
  1. Reading
  2. Tsi ní:ioht
  3. Tsi niió:re wahón:nise

Rider time lost counts the hours riders lose to missing and late service.

It says how many hours were lost, where they went and who carried them. Nobody counts riders on each trip, so the riders are modelled, and every figure carries a range.

  1. Bus timesTewaterièn:tare
  2. Riders per tripEstimated
  3. Hours lost, by causeExplained
  4. Total, with rangeEstimated
When the buses came is measured. How many riders were on them is modelled. The range comes from the modelled part.

What is measured, estimated and explained

Tewaterièn:tare

When each bus reached each stop, from live positions, compared with the timetable.

Estimated

How many riders were on each trip, and so the hours lost and the dollars. These carry a range.

Explained

How the pieces fit together. This page says it in words; it does not publish settings.

Where the numbers come from

  • Tewaterièn:tareOC Transpo and STO live bus positions
  • Tewaterièn:tarePublished timetables, dated
  • Tewaterièn:tarePublished boardings by route
  • EstimatedOur ridership model

How we work it out

  1. We find the trips that did not come, ran late or ran slow. This uses where each bus actually was, as the On time page explains.
  2. We estimate the riders on each trip. We take the route’s published boardings for the day type and spread them across the day, then divide by the trips scheduled.
  3. For each problem we work out the time a typical rider lost. The five kinds are listed below.
  4. We add the hours up. A trip is counted once: a cancelled trip is not also counted as a missed transfer.
  5. We share each trip’s hours across the places it passes through, and print a range beside the total. The route total is firmer than any one ward.

Ka' nón:we ó:ra iahatiiá:ke

  1. Waiting for buses that never cameThe riders who would have taken the trip, times the wait for the next bus that did come.
  2. Tesa'kwenhá:ra ne busRiders on trips more than 5 minutes after the timetable, times how late they ran, weighted for how busy the route is.
  3. Iah tha'kató:ken ne ó:ia busWhen a trip runs later than a short connection allowance, some riders miss their connection and wait for the next one.
  4. Slow tripsRunning time beyond the timetable. A rider is on board for part of it, on average.
  5. Trains, ohnà:kenThe same idea for the O-Train.

Riders per trip are modelled

Nobody counts riders on each trip. The model starts from a route’s published boardings for a day type. It spreads them over the day using a published or network profile, and divides by the trips scheduled in each hour. The page names the model, its sources and its limits next to every figure.

Worked example

Illustrative example, rounded

Route 7, one weekday morning, one direction. These numbers are made up to show the steps, then rounded. They are not from a real day, and other routes will not look like this.

#CauseWhat we worked withHours lost
1One trip did not comeAbout 40 riders waited about 10 minutes for the next bus7 h
2Three trips ran lateRiders on those trips, weighted for how busy the route is3 h
3A late trip, missed transfersA few riders missed their connection1 h
4The route ran a little slowExtra time on board2 h
Totalrange about 10 to 16About 13 h

The causes are worked the same way, each with its own allowances. The example shows the shape of the sum, not the settings.

How sure we are

Every figure is an estimate with a range printed next to it. The range is wider when the model has less to go on, and a trip it has no figure for is left out, counted and lowers our confidence. It is never counted as no loss.

We will publish test results once a real back-test exists.

Tsi niió:re

  • It is an average. A full peak trip and an empty trip share a number.
  • Direction is split by the timetable unless the operator publishes it.
  • Where a route has no hourly profile of its own, the network’s is used.
  • Riders who gave up on the bus are not counted.
  • By place: a trip’s hours are shared across the places of its timepoints. Any one ward is approximate. Stops with no known ward are shown as “Not placed”.
  • Dollars appear only when a published value of time is supplied, with its source.

What would change the number

  • More trips judged, or a fix to how a trip was judged.
  • New published boardings, or a better hourly profile.
  • A change to the method. Each change is dated on this page and past months keep the method they were worked out with.

Check a number

Anyone can send us a case. City staff and councillors’ offices are answered first. We run it ourselves, from the raw record, and send back the figure and the working in words.

What to include

  • The route or ward
  • The date or month
  • The figure you saw, with a link or a screenshot
  • What you expected, and why (optional)
Send the case

It goes to us through the contact form.

What happens next

We run the case ourselves and reply with our figure and the steps in words. If we find an error, it goes on the corrections page. We do not send the formula or its settings, so a figure cannot be tuned for or against.

Where the numbers come from

  • OC Transpo and STO live bus positions
  • Published boardings by route
  • Our ridership model

Method version and change log

A published month never changes. If a method is revised, past months keep the method they were worked out with.

  • Version 1 · October 25, 2026. First published. Hours lost by cause, with a modelled count of riders and a range on every figure.