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

ᑐᓪᓕᐊ ᐸᓯ

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

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

Buses now:ᐃᑲᕐᕋᖓᓂᑭᖑᕙᖅᑐᖅyou

OC Transpo station · 3076

Millennium

Buses at Millennium · liveupdated 30 s ago
21 ᐊᒻᒪ 32 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 6:55
39
39Millennium · platform A · every 21 to 32 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:35
sched. then 6:55
13 ᐊᒻᒪ 18 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 14 · 29 sched.
30
30Blair · platform B · every 13 to 18 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
ᒫᓐᓇᒫᓐᓇᐅᔪᖅ
then 14 · 29 sched.
14 ᐊᒻᒪ 16 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 16 · 32 sched.
25
25Wateridge · platform B · every 14 to 16 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
2ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 16 · 32 sched.
31 ᐊᒻᒪ 64 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 7:46
25
25Millennium · platform A · every 31 to 64 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:42
sched. then 7:46
29 ᐊᒻᒪ 31 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · sched. then 7:17
30
30Millennium · platform A · every 29 to 31 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
6:46
sched. then 7:17
13 ᐊᒻᒪ 17 ᒥᓂᑦ ᐊᑯᓐᓂᖓᓂ ᐊᑐᓂ · then 25 · 41 sched.
39
39Blair · platform B · every 13 to 17 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
12ᒥᓂᑦᒫᓐᓇᐅᔪᖅ
then 25 · 41 sched.
ᑕᒪᑦ 4 ᒥᓂᑦᓂ · sched. then 7:27
618
618Louis Riel · platform B · every 4 to 4 min
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
7:23
sched. then 7:27
539
539Blair
platform B
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
7:27
from the timetable
630
630Colonel By
platform B
ᓱᓕ ᐅᒃᑐᖅᑕᐅᓯᒪᙱᑦᑐᖅ
8:10
sched. then 8:10
Entrances and elevators

We cannot confirm elevator status right now.

88.6% predicted within five minutes of schedule. 825 eligible provider predictions; arrivals not independently measured
Why →

More at this station

Save, plan, shareSave the station, plan a trip from it, or share it
ᐸᕐᓇᒋᐊᖅ ᐅᕙᓐᖓᑦ
Bike parking here2 places within 5 min · nearest: Racks for 5 bikes, 2 ᒥᓂᑦ ᐱᓱᖕᓂᖅBike parking: OpenStreetMap, data as of Jun 1, 2026. The walk is an estimate.
Details →
Print this stationA print sheet with the page link at the foot
Station dataDownload the station as JSON or CSV
JSON · CSV
Report a station problemSent to our station log and counted on this page
ᔮᕙᔅᑯᕆᑉ ᐊᑐᖅᑕᐅᙱᑦᑐᖅBoards and departures still show without JavaScript

Station details

Step-free route

ᐅᓪᓗᒥ ᑐᓴᒐᒃᓴᐃᑦ ᓇᓗᓇᐃᖅᑕᐅᔪᓐᓇᙱᑦᑐᑦ. ᐊᑖᓂ ᑐᓴᒐᒃᓴᐃᑦ ᖃᖓᓂᖓ ᐅᕝᕙᓘᓐᓃᑦ ᓇᖕᒥᑦ ᐱᓂᖏᑦ ᓇᓗᓇᐃᖅᑕᐅᓯᒪᙱᑦᑐᑦ. ᐃᖏᕐᕋᓚᐅᙱᓐᓂᕐᓂ ᐊᐅᓚᑦᑎᔨ ᐊᐱᕆᓗᒍ.

All elevators in the network

Buses from here

Tap a route for live buses and how full they are.

In the station

  • Washroom nearby

Performance

Service delivery · evidence state

Service at MILLENNIUM

Cancellations at this station

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.

Departure-board snapshot
40 listed departures · 8 live provider predictions

Server snapshot assembled Nov 5, 2026, 6:35 a.m.; open Departures for a refreshed board. This is not a cancellation count.

Prediction agreement
88.6% predicted within five minutes of schedule. 825 eligible provider predictions; arrivals not independently measured
Bus prediction reliability at this station

ᐃᓱᓕᑦᑎᓂᖅ

Bus prediction reliability at this station

Early evidence: 6 of 20 weekdays with eligible final provider predictions. This updates hourly; more records will make the estimate steadier.

88.6% of final provider predictions within 5 minutes of the timetable, from 825 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 74%.

Median predicted difference from the timetable: 2 min ᑭᖑᕙᖅᑐᖅ. At the 95th percentile: 8 min ᑭᖑᕙᖅᑐᖅ.

Final provider predictions for conventional bus arrivals at OC Transpo and STO stations; physical arrivals are not independently verified. Express (200/500), shopper/community (300), event (400), and school (600) routes are excluded because each needs a purpose-specific measure. STO routes are included and graded by their own families: Rapibus 100, 200, 400 and 800 count, and STO school journeys numbered 300 and above are excluded the way OC Transpo’s 600s are. Each operator is measured against its own service, never against the other’s.

We use the agency’s last prediction within ten minutes of each scheduled arrival. 6 weekdays with eligible predictions, 2026-10-29 to 2026-11-05. Within five minutes means the final prediction differs from the schedule by no more than five minutes.

Final provider predictions within five minutes of the timetable, by hour, 6 weekdays
  1. 00:00: not enough data
  2. 01:00: not enough data
  3. 02:00: not enough data
  4. 03:00: not enough data
  5. 04:00: not enough data
  6. 05:00: 91.1% of final predictions within five minutes of the timetable, 45 predictions, typically 0.8 min late
  7. 06:00: 95.1% of final predictions within five minutes of the timetable, 61 predictions, typically 1.2 min late
  8. 07:00: 87.5% of final predictions within five minutes of the timetable, 64 predictions, typically 1.9 min late
  9. 08:00: 83.6% of final predictions within five minutes of the timetable, 61 predictions, typically 2.9 min late
  10. 09:00: 76.7% of final predictions within five minutes of the timetable, 43 predictions, typically 2.2 min late
  11. 10:00: 96.1% of final predictions within five minutes of the timetable, 51 predictions, typically 1.1 min late
  12. 11:00: 95.5% of final predictions within five minutes of the timetable, 44 predictions, typically 1.2 min late
  13. 12:00: 90% of final predictions within five minutes of the timetable, 50 predictions, typically 1.6 min late
  14. 13:00: 88.1% of final predictions within five minutes of the timetable, 42 predictions, typically 1.8 min late
  15. 14:00: 84.4% of final predictions within five minutes of the timetable, 45 predictions, typically 1.8 min late
  16. 15:00: 90% of final predictions within five minutes of the timetable, 50 predictions, typically 2 min late
  17. 16:00: 73.7% of final predictions within five minutes of the timetable, 38 predictions, typically 2.7 min late
  18. 17:00: 81.4% of final predictions within five minutes of the timetable, 43 predictions, typically 1.9 min late
  19. 18:00: 85.7% of final predictions within five minutes of the timetable, 35 predictions, typically 1.9 min late
  20. 19:00: 86.5% of final predictions within five minutes of the timetable, 37 predictions, typically 2.4 min late
  21. 20:00: 94.9% of final predictions within five minutes of the timetable, 39 predictions, typically 2.1 min late
  22. 21:00: not enough data
  23. 22:00: not enough data
  24. 23:00: not enough data
  • 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

How MILLENNIUM is doing

ᑖᒃᑯᐊ ᓇᓗᓇᐃᒃᑯᑕᐃᑦ ᐊᕕᒃᑐᐃᔪᑦ ᐅᑎᖅᑕᖅᐸᒃᑐᒥᒃ ᑭᖑᕙᕐᓂᕐᒥᒃ ᐊᒻᒪ ᐱᓕᕆᕝᕕᐅᑉ ᑎᑭᓐᓂᐊᕐᓂᖏᑦ ᐃᓱᒪᒋᔭᖏᑦ ᐊᓯᔾᔨᖅᐸᓐᓂᖏᓐᓂᒃ. ᐊᐱᖁᑎᓂᒃ ᐃᓱᒪᒋᐊᖅᑎᑦᑎᔪᑦ ᐸᕐᓇᐃᔨᓄᑦ ᐊᒻᒪ ᐱᓕᕆᔨᓄᑦ. ᐱᔾᔪᑎᖓ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ. ᐱᐊᓯᑦ ᖃᖓ ᑎᑭᒻᒪᖔᑕ ᓇᓗᓇᐃᖅᓯᖏᑦᑐᑦ. ᓈᓴᐅᑎ ᑕᒪᐃᓐᓂ ᑕᑯᒃᓴᐅᑎᑦᑎᔪᖅ ᖃᑦᓯᓂᒃ ᐃᖏᕐᕋᕝᕕᒃ-ᐃᑲᕐᕋᓂᒃ ᐊᑐᖅᓯᒪᒻᒪᖔᑦ.

Measured over 16 route-hours. 0 more were observed too thinly to count, and are excluded rather than assumed good.

ᐃᑲᕐᕋᓄᑦ ᐋᖅᑭᒃᓯᓂᖅ

ᐊᑯᓂ ᑭᖑᕙᕐᓂᖏᑦ ᓂᕆᐅᒋᔭᐅᔪᑦ ᑕᑯᑎᑦᑎᔪᓐᓇᖅᑐᑦ ᐃᑲᕐᕋᓕᐊᖑᔪᖅ ᕿᒥᕐᕈᔭᐅᒃᓴᐅᓂᖓᓂᒃ. ᕿᒥᕐᕈᓗᒋᑦ ᑎᑭᑦᑐᑦ ᐃᑲᕐᕋᖏᑦ ᐊᒻᒪ ᐊᐅᓪᓚᑎᑦᑎᓂᕐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ. ᑕᐃᒪ ᐃᓱᒪᓕᐅᕐᓗᑎᑦ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐱᕕᒃ ᐊᓯᔾᔨᕆᐊᖃᕐᒪᖔᑦ.

ᑭᓇ ᐋᖅᑭᒃᓯᔪᓐᓇᖅᐸ
ᐃᖏᕐᕋᓂᕐᒧᑦ ᐸᕐᓇᐃᔨ
ᖃᓄᖅ ᐊᑭᖃᖅᐸ
ᐊᑭᖏᑦ ᓇᓗᓇᖅᐳᑦ ᓱᓕ. ᖃᐅᔨᓴᖅᑕᐅᔭᕆᐊᖃᖅᐳᑦ ᐊᖅᑲᐅᑏᑦ, ᐃᖅᑲᓇᐃᔭᖅᑏᑦ, ᐊᑭᓕᖅᑕᐅᓂᖏᑦ ᐊᒻᒪ ᐊᓯᔾᔨᖅᓯᓂᖏᑦ.

ᓇᓚᐅᑦᑖᖅᑕᐅᓯᒪᔪᑦ ᐃᑲᕐᕋᐃᑦ ᐊᓪᓚᓯᒪᔪᓂᒃ ᖃᓂᒋᔭᖃᖅᑐᑦ

100%

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

ᐊᖅᑯᑎᐅᑉ ᐃᑲᕐᕋᖏᑦ ᑭᖑᕙᕆᐊᖃᑦᑕᕐᓂᐊᖅᑐᖅ ᐅᖃᐅᓯᐅᖃᑦᑕᖅᑐᑦ

0of 16

ᐃᖏᕐᕋᕝᕕᐅᑉ ᐃᑲᕐᕋᖏᑦ, ᑎᑭᓂᐊᕐᓂᖏᑦ ᓂᕆᐅᒋᔭᐅᔪᑦ ᐊᑯᓐᓂᐊᓂ ᐱᖓᓱᓂᒃ ᒥᓂᑦᓂᒃ ᐅᖓᑖᓄᓪᓘᓐᓃᑦ ᑭᖑᕙᖅᑐᑦ. ᐃᖏᕐᕋᓂᖓᑕ ᐊᑯᓐᓂᖓ ᖃᐅᔨᓴᕐᓗᒍ ᐃᖏᕐᕋᓂᕐᒧᑦ ᑎᑎᕋᖅᓯᒪᔪᓂᒃ ᓴᓂᐊᓂᒃ.

ᐃᖏᕐᕋᕝᕕᐃᑦ ᐃᑲᕐᕋᖏᑦ, ᐸᔅ ᓯᕗᓪᓕᐅᕐᓂᐊᕐᓂᖓᓂᒃ ᓇᓚᐅᑦᑖᖅᑕᐅᑎᓪᓗᒍ

0of 16

ᐊᖁᑎ ᐃᑲᕐᕋᖏᑦ, ᑕᐃᑦᓱᒪᓂ ᑎᑭᓐᓂᐊᕐᓂᖓᓄᑦ ᓇᓚᐅᑦᑖᕐᓂᖅ ᐊᑯᓐᓂᐊᓂ ᓯᕗᓪᓕᐅᕐᓂᐊᖅᑐᖅ ᐊᑕᐅᓯᕐᒥᒃ ᒥᓂᑦᒥᒃ ᐅᖓᑖᓄᓪᓘᓃᑦ. ᐅᓇ ᓇᓗᓇᐃᖅᓯᙱᑦᑐᖅ ᐸᓯᑦ ᓯᕗᓪᓕᐅᖅᖢᑎᒃ ᐊᐅᓪᓚᓚᐅᖅᓯᒪᓂᖏᓐᓂᒃ.

ᑭᖑᕙᕆᐊᕐᓂᖅ ᓂᕆᐅᒋᔭᐅᑦᑕᐃᓐᓇᖅᑐᖅ

ᑖᔅᓱᒪ ᑕᖅᑭᐅᑉ ᐃᓗᐊᓂ ᓇᓗᓇᐃᖅᓯᒍᑎᑦ ᓈᒻᒪᙱᑦᑐᑦ ᑖᓐᓇ ᓴᖅᑭᑎᑦᑎᓂᐊᕐᓗᒍ.

ᑭᖑᕙᕆᐊᖃᕐᓂᖅ ᐊᑐᐃᓐᓇᐅᓂᖅᐹᖅ ᓂᕆᐅᒋᔭᐅᔪᖅ ᐃᖏᕐᕋᕝᕕᓐᓂ ᓇᓗᓇᐃᖅᑕᐅᓯᒪᔪᓂ. ᐅᓇ ᓇᓗᓇᐃᖅᑕᐅᑦᑎᐊᖏᑦᑐᖅ ᐃᓚᓗᒍ ᐃᖏᕐᕋᓂᕐᒧᑦ ᐱᕕᒃᓴᓄᑦ.

ᐊᐅᓚᑦᑎᓂᖅ: not measurable here

ᐅᓇ ᐃᑭᐊᖅᑭᕖᒃᑯᑦ ᑐᑭᓯᒋᐊᕐᕕᒃ ᑎᑎᕋᖅᐸᒃᑐᖅ ᑭᖑᕙᕐᓂᐅᔪᒥᒃ ᐊᑯᓐᓂᐅᔪᒥᒃ ᐃᑲᕐᕋᓂ ᑕᒪᐃᓐᓂ ᓄᖅᑲᖓᕝᕕᒻᒥ. ᐊᓯᖏᓐᓂᒃ ᓈᓴᐅᑎᓂᒃ ᑎᑎᕋᖅᐸᙱᑦᑐᖅ. ᑕᐃᒪ ᓇᓗᓇᖅᑐᖅ ᖃᓄᖅ ᐊᔾᔨᒌᙱᓐᓂᖓ ᐃᖏᕐᕋᓂᖅ ᓈᒻᒪᒃᑐᖅ ᐃᖏᕐᕋᓂᕐᓗ ᐱᐅᙱᑦᑐᖅ. ᑖᓐᓇ ᐅᕙᒍᑦ ᖃᐅᔨᓴᕈᓯᑦᑎᓐᓂ ᑭᒡᓕᖃᖅᑐᖅ. ᑕᒪᓐᓇ ᓇᔪᒐᖅ ᐱᓪᓗᒍ ᑐᑭᓯᓂᐊᕐᓂᐅᙱᑦᑐᖅ.

Measurements

Calculated: · Method: settled-arrivals-oc-sto-conventional-v5

Station evidence and sources
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.

ᑖᑦᓱᒪ ᒪᑉᐱᒐᐅᑉ ᓇᓗᓇᐃᖅᓯᒍᑎᖏᑦᐅᒃᑯᐃᓗᒍ ᑐᑭᖓ, ᖃᓄᖅ ᐱᓕᕆᓯᒪᓂᖅ, ᓇᑭᙶᕐᓂᖏᑦ, ᐅᓪᓗᖏᑦ, ᓇᒧᑦ ᐊᐅᓚᓂᖏᑦ, ᐊᒻᒪ ᑭᒡᓕᖏᑦ ᖃᐅᔨᒪᔭᐅᔪᑦ.

ᓴᖅᑭᑎᑕᐅᔪᑦ

ᐊᖁᑏᑦ ᓄᖑᕐᕕᐊᑕ ᑕᑯᒃᓴᐅᑎᖓ ᒫᓐᓇ. ᐱᕕᒃᓴᖏᑦ ᑎᑎᕋᖅᓯᒪᔪᑦ ᐊᒻᒪ ᐊᐅᓚᑦᑎᔨᐅᑉ ᓇᓚᐅᑦᑖᕈᑎᖓ ᐃᖏᕐᕋᓂᕐᒧᑦ ᑕᒪᐃᓐᓄᑦ.

How it was produced

Platforms sharing the station stop code are grouped, scheduled trips are read from the current GTFS, and a live time is used only when the operator publishes a matching prediction.

ᓇᓗᓇᐃᖅᓯᒍᑏᑦ ᐅᓪᓗᖏᑦ

ᓈᓴᐅᑎᓕᐅᖅᑕᐅᔪᖅ ᐅᕝᕙᓘᓐᓃᑦ ᑲᑐᔾᔨᖅᑕᐅᔪᖅ
ᐆᒃᑐᕋᐅᑎ
40 departures across 2 published platform records in the current four-hour board.
ᐃᓚᐅᔪᑦ
8 departures have a published live prediction; 32 are timetable-only.

ᓇᑭᑦ ᑐᓴᒐᒃᓴᐃᑦ

ᑭᒡᓕᖏᑦ ᐃᖅᑲᐅᒪᔭᐅᑎᐊᕆᐊᓖᑦ

  • OC Transpo ᓴᖅᑭᑦᑎᙱᓚᖅ O-Train ᒫᓐᓇ ᓇᐅᓐᓂᖓᓂᒃ ᐅᕝᕙᓘᓐᓃᑦ ᖃᖓ ᑎᑭᓐᓂᐊᕐᓂᖓᓂᒃ ᑐᓴᒐᒃᓴᓂ ᐅᕙᓂ ᐊᑐᖅᑕᐅᔪᓂ. ᑕᐃᒪ O-Train ᐱᕕᖏᑦ ᐸᕐᓇᐅᑎᒥᑦ ᑭᓯᐊᓂ.
  • The stop source does not publish a complete station accessibility chain, entrances, or indoor paths.
ᓱᓕᔪᒥᒃ ᐋᖅᑭᒋᐊᕐᓂᕐᒥᒃ ᐊᑐᓕᖁᔨᓗᑎᑦ

Contains information licensed under the Open Government Licence – City of Ottawa.