ᐱᓗᐊᖅᑐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᒧᑦ ᐊᐅᓪᓚᕐᓗᑎᑦ

ᐱᔨᑦᑎᕐᓂᖅ

ᐊᔪᕐᓇᖅᑐᖅ ᐅᖃᐅᑎᒋᓗᒍ

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

ᖃᓄᐃᓕᖓᓯᒪᕙ?
Full report No account needed

ᖃᐅᔨᒪᒋᐊᖃᖅᑕᑦ

ᐅᔾᔨᕆᒋᐊᕈᑏᑦ ᐋᖅᑭᒃᓱᐃᓂᖏᑦ

ᐅᖃᐅᑎᓗᖓ

ᐃᖏᕐᕋᓂᒃᑲ ᐊᑦᑐᐃᔭᐅᓕᕌᖓᑕ

ᓯᕗᓪᓕᖅᐹᒥ ᑐᖅᑯᕐᓗᒍ ᐊᖁᑦ ᐅᕝᕙᓘᓐᓃᑦ ᓄᖅᑲᕐᕕᒃ. ᑕᐃᒪ ᒪᓕᒃᑕᒃᓴᖃᕐᓂᐊᖅᑐᖅ.

ᐱᓇᓱᐊᕐᓯᐅᑎᒥ ᓇᐃᓈᖅᑕᐅᓯᒪᔪᖅ

ᓱᓕ ᐊᑐᐃᓐᓇᐅᙱᓚᖅ. ᐱᓇᓱᐊᕐᓯᐅᑎᒥ ᓇᐃᓈᖅᑕᐅᓯᒪᔪᖅ ᑐᓂᔭᐅᙱᓚᖅ ᐅᓪᓗᒥ. ᐃᑯᐊᓪᓚᒃᑕᒃᓴᖃᙱᓚᖅ.

ᐊᓯᖏᑦ

O-Train · Tuesday 8:35 AM

Line 1: no official notice right now. Line 2: no official notice right now.

Above the line: Line 1 west, Line 2 north. Live, 41 s ago.

1
Line 1 Tunney's Pasture ⇄ Blair

No official noticeNo official noticelive, 41 s ago

How often trains come now is not measured yet.

How often trains come now is not measured yet.

2
Line 2 Bayview ⇄ Limebank

No official noticeNo official noticelive, 41 s ago

How often trains come now is not measured yet.

How often trains come now is not measured yet.

How we got this number

How we got this number

Today so farᓇᓚᐅᑦᑖᖅᑕᐅᓯᒪᔪᖅ

Estimated: gaps and run times come from live predictions against the timetable, not from seeing each train.

ᓱᓇᒥᒃ ᓇᓗᓇᐃᖅᓯᔪᖅ

How the O-Train is running: how many trips were predicted or cancelled, how far apart trains are, and how long the run takes.

  • ᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅWe saw it happen.
  • ᓇᓚᐅᑦᑖᖅᑕᐅᓯᒪᔪᖅModelled, shown with a range.
  • ExplainedHow it is worked out, in words.

Where it comes from

  • ᓇᓚᐅᑦᑖᖅᑕᐅᓯᒪᔪᖅLive O-Train predictions
  • ᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅPublished timetables, dated
  • ᐅᑦᑐᕋᖅᑕᐅᓯᒪᔪᖅAnnounced slow orders

How we work it out

  1. We count the trips the live feed predicts and the ones it marks cancelled.
  2. We compare the gap between predicted trains with the gap the timetable promises.
  3. We compare the predicted run time with the timetable’s run time.
  4. Announced slow orders are listed as the operator published them. We do not infer them.

Worked example

Illustrative example, rounded

One station, one hour. The numbers are made up to show the steps. They are not from a real hour.

  • Promised gapA train about every 5 minutes5 min
  • Predicted gapsSome close, one long4, 5, 9
  • Longest gapAgainst the promised gap+4 min
  • GapsOne gap about 4 min over the timetable

How sure we are

Counts of predicted and cancelled trips are what the feed says. Gaps and run times are estimates, because a prediction is not a sighting.

Limits, and what would change it

  • A prediction can change before the train arrives.
  • A train missing from the feed can make a gap look longer than it was.
  • It says what is predicted now, not how the day will end.
Read the full method Check a number

Method version 1 · changed October 29, 2026

Trips run, on time and the longest gap for today are not measured yet.

Rider observations, all lines →

OC Transpo publishes no train positions. The trains drawn here are where the timetable puts them, not where they are.

Official notices by line

Checked Nov 3, 2026, 8:35:50 a.m.. The operator’s word, not a measured train position.

Line 1

No current notice names this line.

Line 2

No current notice names this line.

This list is read when the page loads. Reload it for newer notices.