Skip to main content

Next bus

FR

Report a problem

Filled in: station 3026 · 7:10 p.m. · pick one

What happened
Full report No account needed

Buses now:on timelateyou

1O-Train Line 1 · station 3026

Cyrville

Trains · timetableon timelateno reading
Every 7 to 10 min · sched. then 7:15
1
1Tunney's Pasture · platform 1
Not measured yet
7:07
sched. then 7:15
Every 7 to 9 min · sched. then 7:16
1
1Blair · platform 2
Not measured yet
7:09
sched. then 7:16
Entrances and elevators

We cannot confirm elevator status right now.

81.8% predicted within five minutes of schedule. 121 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
Plan from here
Bike parking here6 places within 5 min · nearest: Racks for 5 bikes, 1 min walkBike 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
Without JavaScriptBoards and departures still show without JavaScript

Station details

Step-free route

Current notice coverage cannot be confirmed. Retained notices below may have unconfirmed timing or source evidence. Check the operator before you travel.

All elevators in the network

In the station

No published source lists amenities here yet.

Performance

Service delivery · evidence state

Service at CYRVILLE

Cancellations at this station

3 stop calls with a recorded explicit cancellation

2,687 scheduled calls at exact stops in the same window (Oct 27, 2026 – Nov 2, 2026). The cancellation feed may be incomplete; this is not a comparable rate between places.

Dates, source versions and limits
Stop calls whose trip has a vehicle position
122
Unclassified calls
2,562

A cancellation notice may coexist with vehicle positions. A position somewhere on the trip does not prove arrival at this stop. Unclassified calls are not confirmed no-shows. No cancellation cause is inferred.

Method: retained-pre-service-exact-trip-stop-call-v1. Cancellation-feed completeness and position coverage are unverified.

The retained timetables were fetched, imported and first activated before the service day. The archive does not prove they remained the active timetables throughout that period. Comparisons between places remain unavailable.

  • 2026-10-27 · 3932bee1-4577-4968-9a97-2987e88312ad · 1d13d0abb2506002092feaff3dc08c45abd96d7b94ad4ed13c73616dab7e8ed8
    Fetched: 2026-10-23T01:15:52.775Z · Imported: 2026-10-23T01:16:19.765Z · First activated: 2026-10-23T01:21:23.821Z
  • 2026-10-28 · 3932bee1-4577-4968-9a97-2987e88312ad · 1d13d0abb2506002092feaff3dc08c45abd96d7b94ad4ed13c73616dab7e8ed8
    Fetched: 2026-10-23T01:15:52.775Z · Imported: 2026-10-23T01:16:19.765Z · First activated: 2026-10-23T01:21:23.821Z
  • 2026-10-29 · 3932bee1-4577-4968-9a97-2987e88312ad · 1d13d0abb2506002092feaff3dc08c45abd96d7b94ad4ed13c73616dab7e8ed8
    Fetched: 2026-10-23T01:15:52.775Z · Imported: 2026-10-23T01:16:19.765Z · First activated: 2026-10-23T01:21:23.821Z
  • 2026-10-30 · 6ee8491d-8f94-4122-a67b-ef228d9e0945 · 91dd8e42516043447b7a3e7185d65557916494aaafeb36792fa1c09c514e2bbb
    Fetched: 2026-10-30T01:00:32.195Z · Imported: 2026-10-30T01:00:56.502Z · First activated: 2026-10-30T01:05:20.914Z
  • 2026-10-31 · 6ee8491d-8f94-4122-a67b-ef228d9e0945 · 91dd8e42516043447b7a3e7185d65557916494aaafeb36792fa1c09c514e2bbb
    Fetched: 2026-10-30T01:00:32.195Z · Imported: 2026-10-30T01:00:56.502Z · First activated: 2026-10-30T01:05:20.914Z
  • 2026-11-01 · 6ee8491d-8f94-4122-a67b-ef228d9e0945 · 91dd8e42516043447b7a3e7185d65557916494aaafeb36792fa1c09c514e2bbb
    Fetched: 2026-10-30T01:00:32.195Z · Imported: 2026-10-30T01:00:56.502Z · First activated: 2026-10-30T01:05:20.914Z
  • 2026-11-02 · 6ee8491d-8f94-4122-a67b-ef228d9e0945 · 91dd8e42516043447b7a3e7185d65557916494aaafeb36792fa1c09c514e2bbb
    Fetched: 2026-10-30T01:00:32.195Z · Imported: 2026-10-30T01:00:56.502Z · First activated: 2026-10-30T01:05:20.914Z
Departure-board snapshot
40 listed departures · 0 live provider predictions

Server snapshot assembled Nov 3, 2026, 7:07 p.m.; open Departures for a refreshed board. This is not a cancellation count.

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

Verdict

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.

81.8% of final provider predictions within 5 minutes of the timetable, from 121 predictions over 6 weekdays. No single hour has enough predictions to break that down.

Median predicted difference from the timetable: 1 min late. At the 95th percentile: 7 min late.

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. This station also has 1 O-Train line. This line is not included because OC Transpo does not publish realtime rail data.

We use the agency’s last prediction within ten minutes of each scheduled arrival. 6 weekdays with eligible predictions, 2026-10-27 to 2026-11-03. 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: not enough data
  7. 06:00: not enough data
  8. 07:00: not enough data
  9. 08:00: not enough data
  10. 09:00: not enough data
  11. 10:00: not enough data
  12. 11:00: not enough data
  13. 12:00: not enough data
  14. 13:00: not enough data
  15. 14:00: not enough data
  16. 15:00: not enough data
  17. 16:00: not enough data
  18. 17:00: not enough data
  19. 18:00: not enough data
  20. 19:00: not enough data
  21. 20:00: not enough data
  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
Measurements

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

O-Train evidence

What we know about train service here

Open the train observation report

Trains are not in the public data feed

The bus punctuality reports compare archived arrival predictions with published schedules. They do not count independently measured physical arrivals. Otranspo has no comparable public train-position dataset for these reports, so those bus figures cannot show where a train is or whether Lines 1, 2 and 4 run on time.

Publishing train positions, their timestamps, and the measurement method would help build a separate, verifiable record of rail service. The missing dataset does not establish how the trains performed.

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 observedCheck all official service alertsOpen train research and history
Station evidence and sources
Français
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.

Evidence behind this pageOpen the definition, method, sources, dates, coverage, and known limits.

What is being shown

A current station board assembled from the imported timetable and any usable operator prediction for each trip.

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.

Evidence dates

Computed or assembled
Sample
40 departures across 3 published platform records in the current four-hour board.
Coverage
0 departures have a published live prediction; 40 are timetable-only.

Sources

Limits to keep in mind

  • OC Transpo does not publish live rail positions or predictions in the feed used here, so rail times are timetable-only.
  • The stop source does not publish a complete station accessibility chain, entrances, or indoor paths.
Suggest a factual correction

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