Skip to main content

Next bus

FR

Report a problem

What happened
Full report No account needed

Buses now:on timelateyou

OC Transpo station · 3048

Nepean Woods

Buses at Nepean Woods · liveupdated 30 s ago
Every 26 to 29 min · then 25 · 53 sched.
80
80Barrhaven Centre · platform A · every 26 to 29 min
Not measured yet
Nowlive
then 25 · 53 sched.
Every 15 to 30 min · then 15 · 38 sched.
74
74Limebank · platform A · every 15 to 30 min
Not measured yet
Nowlive
then 15 · 38 sched.
Every 30 min · sched. then 6:46
277
277Nepean Woods · platform B · every 30 to 30 min
Not measured yet
6:16
sched. then 6:46
Every 26 to 30 min · then 33 · 60 sched.
110
110Limebank · platform A · every 26 to 30 min
Not measured yet
4minlive
then 33 · 60 sched.
Every 15 min · then 23 · 38 sched.
80
80Tunney's Pasture · platform B · every 15 to 15 min
Not measured yet
8minlive
then 23 · 38 sched.
Every 56 min · sched. then 7:19
80
80Nepean Woods · platform A · every 56 to 56 min
Not measured yet
6:23
sched. then 7:19
Every 15 to 17 min · then 27 · 42 sched.
70
70Fallowfield · platform B · every 15 to 17 min
Not measured yet
12minlive
then 27 · 42 sched.
Every 28 to 30 min · then 39 · 69 sched.
110
110Innovation · platform B · every 28 to 30 min
Not measured yet
16minlive
then 39 · 69 sched.
Every 28 to 29 min · then 39 · 68 sched.
99
99Barrhaven Centre · platform B · every 28 to 29 min
Not measured yet
19minlive
then 39 · 68 sched.
Every 13 to 15 min · then 27 · 30 sched.
70
70Limebank · platform A · every 13 to 15 min
Not measured yet
21minlive
then 27 · 30 sched.
Every 29 to 30 min · then 51 · 81 sched.
99
99Limebank · platform A · every 29 to 30 min
Not measured yet
22minlive
then 51 · 81 sched.
Every 28 to 30 min · then 52 · 82 sched.
74
74Tunney's Pasture · platform B · every 28 to 30 min
Not measured yet
24minlive
then 52 · 82 sched.
Entrances and elevators

We cannot confirm elevator status right now.

79.6% predicted within five minutes of schedule. 2,990 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 hereBike parking · 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

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 NEPEAN WOODS

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 · 18 live provider predictions

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

    Prediction agreement
    79.6% predicted within five minutes of schedule. 2,990 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.

    79.6% of final provider predictions within 5 minutes of the timetable, from 2,990 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 58%.

    Median predicted difference from the timetable: 2 min late. At the 95th percentile: 10 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: 90.9% of final predictions within five minutes of the timetable, 44 predictions, typically 1.5 min early
    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: 92.4% of final predictions within five minutes of the timetable, 66 predictions, typically 0.2 min early
    7. 06:00: 81.2% of final predictions within five minutes of the timetable, 154 predictions, typically 1.7 min late
    8. 07:00: 88.6% of final predictions within five minutes of the timetable, 185 predictions, typically 1 min late
    9. 08:00: 84.2% of final predictions within five minutes of the timetable, 190 predictions, typically 1.5 min late
    10. 09:00: 76.5% of final predictions within five minutes of the timetable, 187 predictions, typically 1.8 min late
    11. 10:00: 89.6% of final predictions within five minutes of the timetable, 182 predictions, typically 0.8 min late
    12. 11:00: 83.2% of final predictions within five minutes of the timetable, 184 predictions, typically 1.1 min late
    13. 12:00: 85.2% of final predictions within five minutes of the timetable, 183 predictions, typically 0.9 min late
    14. 13:00: 83.2% of final predictions within five minutes of the timetable, 184 predictions, typically 1.1 min late
    15. 14:00: 82.4% of final predictions within five minutes of the timetable, 187 predictions, typically 1.6 min late
    16. 15:00: 69.1% of final predictions within five minutes of the timetable, 191 predictions, typically 2.3 min late
    17. 16:00: 57.7% of final predictions within five minutes of the timetable, 196 predictions, typically 4 min late
    18. 17:00: 69.7% of final predictions within five minutes of the timetable, 195 predictions, typically 3.5 min late
    19. 18:00: 75.8% of final predictions within five minutes of the timetable, 178 predictions, typically 1.9 min late
    20. 19:00: 87.3% of final predictions within five minutes of the timetable, 126 predictions, typically 1.2 min late
    21. 20:00: 77.3% of final predictions within five minutes of the timetable, 119 predictions, typically 1.5 min late
    22. 21:00: 74.3% of final predictions within five minutes of the timetable, 101 predictions, typically 2.2 min late
    23. 22:00: 83.1% of final predictions within five minutes of the timetable, 77 predictions, typically 0.8 min late
    24. 23:00: 83.3% of final predictions within five minutes of the timetable, 54 predictions, typically 0.6 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
    WhatWhenMeasuredScenario or next investigation
    ProblemPredictions later than timetable16:00 to 18:003.8 min lateRunning time on the routes here
    ProblemPredictions earlier than timetable00:001.5 min earlyHolding points on the routes here
    ProblemOne hour has a lower prediction match16:0058%Operations in that hour

    How NEPEAN WOODS is doing

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

    Measured over 20 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
    Cost unavailable until fleet, labour, recovery and transfer effects are tested.

    Predictions close to the timetable

    85%

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

    Route-hours with repeated late predictions

    2of 20

    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

    1of 20

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

    Typical predicted delay

    3.8min

    The typical median predicted delay in flagged route-hours; 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, and no percentile, so the gap between a normal trip and a bad one cannot be worked out. That is a limit of our own measurement, not a finding about this place.

    Measurements

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

    Predictions later than timetable · 16:00 to 18:00
    Median delay 3.8 min
    Measured arrivals 391
    On time 63.7%
    Predictions earlier than timetable · 00:00
    Median delay -1.5 min
    Measured arrivals 44
    On time 90.9%
    One hour has a lower prediction match · 16:00
    On time 57.7%
    Other hours on time 83.2%
    Measured arrivals 196
    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 2 published platform records in the current four-hour board.
    Coverage
    18 departures have a published live prediction; 22 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.