Wà:s ne kahiatónhsera

Bus ohnà:ken

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

Oh nahò:ten iahà:wen
Full report No account needed

Buses now:Kwah tsi nikahwistà:kelateyou

OC Transpo station · 3043

Fallowfield

Buses at Fallowfield · liveupdated 30 s ago
Tiótkon 30 min · sched. then 11:36
173
173Fallowfield · platform B · every 30 to 30 min
Shé:kon iah tetewatahsónteren
11:06
sched. then 11:36
Tiótkon 30 min · then 32 · 62 sched.
73
73Limebank · platform A · every 30 to 30 min
Shé:kon iah tetewatahsónteren
2minitò:nen
then 32 · 62 sched.
Tiótkon 15 min · then 21 · 35 sched.
74
74Limebank · platform A · every 15 to 15 min
Shé:kon iah tetewatahsónteren
5minitò:nen
then 21 · 35 sched.
Every 15 to 16 min · then 20 · 35 sched.
75
75Cambrian · platform A · every 15 to 16 min
Shé:kon iah tetewatahsónteren
5minitò:nen
then 20 · 35 sched.
Tiótkon 15 min · then 23 · 38 sched.
75
75Tunney's Pasture · platform B · every 15 to 15 min
Shé:kon iah tetewatahsónteren
7minitò:nen
then 23 · 38 sched.
Tiótkon 15 min · then 25 · 41 sched.
74
74Tunney's Pasture · platform B · every 15 to 15 min
Shé:kon iah tetewatahsónteren
10minitò:nen
then 25 · 41 sched.
Tiótkon 30 min · sched. then 11:51
70
70Fallowfield · platform B · every 30 to 30 min
Shé:kon iah tetewatahsónteren
11:21
sched. then 11:51
Tiótkon 30 min · sched. then 11:56
73
73Fallowfield · platform B · every 30 to 30 min
Shé:kon iah tetewatahsónteren
11:26
sched. then 11:56
Tiótkon 30 min · then 52 · 82 sched.
70
70Limebank · platform A · every 30 to 30 min
Shé:kon iah tetewatahsónteren
23minitò:nen
then 52 · 82 sched.
Tiótkon 30 min · then 52 · 82 sched.
173
173Citigate · platform A · every 30 to 30 min
Shé:kon iah tetewatahsónteren
23minitò:nen
then 52 · 82 sched.
Entrances and elevators

We cannot confirm elevator status right now.

89.4% predicted within five minutes of schedule. 2,742 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 here3 places within 5 min · nearest: Racks for 10 bikes, covered, 1 min ohsitá:keBike 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
Iah JavaScriptBoards and departures still show without JavaScript

Station details

Step-free route

Iah teiotòn:'on aonsakheweiénhste' ó:nen. Kahiatónhsera kèn:'en iah tewakaterièn:tare tó: nikahá:wi tánon ka nón:we tkawé:non. Satkáhtho OC Transpo tóka' STO ohén:ton tsi enhsátiake ohahà:ke.

All elevators in the network

Buses from here

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

In the station

No published source lists amenities here yet.

Performance

Service delivery · evidence state

Service at FALLOWFIELD

Cancellations at this station

Local count cannot be published

Exact stop-call evidence could not be read for Oct 28, 2026 – Nov 3, 2026. No zero is assumed.

Dates, source versions and limits

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.

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

    Server snapshot assembled Nov 4, 2026, 11:05 a.m.; open Departures for a refreshed board. This is not a cancellation count.

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

    Ka' nikarihò:ten

    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.

    89.4% of final provider predictions within 5 minutes of the timetable, from 2,742 predictions over 6 weekdays. The lowest sampled hour is 15:00 at 75%.

    Median predicted difference from the timetable: 43 s 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.

    We use the agency’s last prediction within ten minutes of each scheduled arrival. 6 weekdays with eligible predictions, 2026-10-28 to 2026-11-04. 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: 94.3% of final predictions within five minutes of the timetable, 35 predictions, typically 0 min late
    2. 01:00: 90.3% of final predictions within five minutes of the timetable, 31 predictions, typically 0 min late
    3. 02:00: not enough data
    4. 03:00: not enough data
    5. 04:00: 97.6% of final predictions within five minutes of the timetable, 41 predictions, typically 0 min late
    6. 05:00: 96.8% of final predictions within five minutes of the timetable, 62 predictions, typically 0.3 min late
    7. 06:00: 94.7% of final predictions within five minutes of the timetable, 150 predictions, typically 0.4 min late
    8. 07:00: 95.9% of final predictions within five minutes of the timetable, 193 predictions, typically 0.3 min late
    9. 08:00: 88.3% of final predictions within five minutes of the timetable, 180 predictions, typically 0.8 min late
    10. 09:00: 89.5% of final predictions within five minutes of the timetable, 152 predictions, typically 0.5 min late
    11. 10:00: 92.9% of final predictions within five minutes of the timetable, 156 predictions, typically 0.6 min late
    12. 11:00: 95.8% of final predictions within five minutes of the timetable, 142 predictions, typically 0.4 min late
    13. 12:00: 94.2% of final predictions within five minutes of the timetable, 137 predictions, typically 0.7 min late
    14. 13:00: 90.4% of final predictions within five minutes of the timetable, 136 predictions, typically 0.7 min late
    15. 14:00: 93.2% of final predictions within five minutes of the timetable, 132 predictions, typically 0.8 min late
    16. 15:00: 75.4% of final predictions within five minutes of the timetable, 167 predictions, typically 1.6 min late
    17. 16:00: 79.6% of final predictions within five minutes of the timetable, 186 predictions, typically 1.7 min late
    18. 17:00: 83.6% of final predictions within five minutes of the timetable, 177 predictions, typically 1.3 min late
    19. 18:00: 82% of final predictions within five minutes of the timetable, 172 predictions, typically 0.9 min late
    20. 19:00: 94.3% of final predictions within five minutes of the timetable, 122 predictions, typically 1 min late
    21. 20:00: 91.1% of final predictions within five minutes of the timetable, 112 predictions, typically 0.9 min late
    22. 21:00: 94.4% of final predictions within five minutes of the timetable, 107 predictions, typically 1 min late
    23. 22:00: 85.5% of final predictions within five minutes of the timetable, 62 predictions, typically 0.5 min late
    24. 23:00: 97.8% of final predictions within five minutes of the timetable, 45 predictions, typically 0.4 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
    WhatÓ:nenTewaterièn:tareScenario or next investigation
    ProblemOne hour has a lower prediction match15:0075%Operations in that hour

    How FALLOWFIELD is doing

    These indicators separate repeated delay from changes in the operator's arrival predictions. They suggest questions for planners and operations staff. They do not show the cause. They do not prove when buses arrived. Each figure shows its route-hour sample.

    Measured over 22 route-hours. 0 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
    Iah tewaterièn:tare tó: nikaná:ien tsi niió:re ahontkáhtho ne ká'sere, ne raotiio'te tánon ne ò:ia.

    Tsi ní:ioht kahiatónhsera tánon tsi nihawen:'en iah teiotsén:ion

    100%

    Route-hours: median arrival prediction iáh énska minute early, iáh áhsen minutes late.

    Route-hours with repeated late predictions

    0of 22

    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

    0of 22

    Route-hours where the median eligible arrival prediction is at least one minute early. This does not show that buses left early.

    Typical predicted delay

    Not enough evidence this month to publish this indicator.

    The typical median predicted delay in flagged route-hours. It is not a validated amount to add to the timetable.

    Operations: not measurable here

    This site records a median delay for each hour at a stop. It does not record a percentile. So we cannot work out the gap between a normal trip and a bad one. That is a limit of our own measurement. It is not a finding about this place.

    Measurements

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

    One hour has a lower prediction match · 15:00
    Ioiánere tsi nikarì:wes 75.4%
    Other hours on time 93.2%
    Measured arrivals 167
    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
    Kén:k nikón
    40 departures across 2 published platform records in the current four-hour board.
    Coverage
    15 departures have a published live prediction; 25 are timetable-only.

    Tsi nón: ionkwaién:ta'

    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.