Skip to main content

Next bus

FR

Report a problem

Filled in: station 3010 · 2:38 a.m. · pick one

What happened
Full report No account needed

Buses now:on timelateyou

1O-Train Line 1 · station 3010

Pimisi

Trains · timetableon timelateno reading
Every 6 to 11 min · sched. then 5:09
1
1Blair · platform 2
Not measured yet
5:01
sched. then 5:09
Every 6 to 12 min · sched. then 5:30
1
1Tunney's Pasture · platform 1
Not measured yet
5:21
sched. then 5:30
Buses at Pimisi · liveupdated 30 s ago
Every 26 to 40 min · sched. then 3:05
75
75Rideau · platform D · every 26 to 40 min
Not measured yet
2:38
sched. then 3:05
57
57Rideau
platform D
Not measured yet
5minlive
Every 31 to 90 min · then 92 · 123 sched.
61
61Terry Fox · platform C · every 31 to 90 min
Not measured yet
8minlive
then 92 · 123 sched.
Every 28 to 32 min · then 31 · 61 sched.
75
75Barrhaven Centre · platform C · every 28 to 32 min
Not measured yet
8minlive
then 31 · 61 sched.
Every 28 to 74 min · then 52 · 126 sched.
61
61Rideau · platform D · every 28 to 74 min
Not measured yet
24minlive
then 52 · 126 sched.
57
57Bayshore
platform C
Not measured yet
27minlive
75
75Cambrian
platform C
Not measured yet
4:37
from the timetable
Every 33 to 60 min · sched. then 5:12
8
8Dow's Lake ~ Lac Dow · platform B · every 33 to 60 min
Not measured yet
4:39
sched. then 5:12
8
8Terrasses de la Chaudière
platform A
Not measured yet
4:53
from the timetable
8
8Gatineau
platform A
Not measured yet
5:50
from the timetable
12
12Blair
platform D
Not measured yet
6:04
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

69% predicted within five minutes of schedule. 1,849 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 6 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

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 PIMISI

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

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

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

    Verdict

    Bus prediction reliability at this station

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

    69% of final provider predictions within 5 minutes of the timetable, from 1,849 predictions over 5 weekdays. The lowest sampled hour is 16:00 at 36%.

    Median predicted difference from the timetable: 3 min late. At the 95th percentile: 16 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. 5 weekdays with eligible predictions, 2026-10-28 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, 5 weekdays
    1. 00:00: not enough data
    2. 01:00: 92% of final predictions within five minutes of the timetable, 50 predictions, typically 0.5 min late
    3. 02:00: 88.3% of final predictions within five minutes of the timetable, 60 predictions, typically 1.1 min late
    4. 03:00: 90.9% of final predictions within five minutes of the timetable, 33 predictions, typically 0.3 min early
    5. 04:00: 92.5% of final predictions within five minutes of the timetable, 53 predictions, typically 0.5 min late
    6. 05:00: not enough data
    7. 06:00: 88.5% of final predictions within five minutes of the timetable, 96 predictions, typically 1.6 min late
    8. 07:00: 69.7% of final predictions within five minutes of the timetable, 132 predictions, typically 3.2 min late
    9. 08:00: 55.4% of final predictions within five minutes of the timetable, 157 predictions, typically 3.6 min late
    10. 09:00: 71.4% of final predictions within five minutes of the timetable, 112 predictions, typically 2.8 min late
    11. 10:00: 82.2% of final predictions within five minutes of the timetable, 73 predictions, typically 2 min late
    12. 11:00: 75.9% of final predictions within five minutes of the timetable, 79 predictions, typically 2.7 min late
    13. 12:00: 72.9% of final predictions within five minutes of the timetable, 70 predictions, typically 3 min late
    14. 13:00: 69.3% of final predictions within five minutes of the timetable, 75 predictions, typically 2.6 min late
    15. 14:00: 72% of final predictions within five minutes of the timetable, 75 predictions, typically 3 min late
    16. 15:00: 47.1% of final predictions within five minutes of the timetable, 140 predictions, typically 5.3 min late
    17. 16:00: 36.2% of final predictions within five minutes of the timetable, 138 predictions, typically 6.9 min late
    18. 17:00: 56.7% of final predictions within five minutes of the timetable, 120 predictions, typically 3.3 min late
    19. 18:00: 64.5% of final predictions within five minutes of the timetable, 110 predictions, typically 3.1 min late
    20. 19:00: 72.3% of final predictions within five minutes of the timetable, 65 predictions, typically 2 min late
    21. 20:00: 80.8% of final predictions within five minutes of the timetable, 52 predictions, typically 2.1 min late
    22. 21:00: 80% of final predictions within five minutes of the timetable, 45 predictions, typically 2.8 min late
    23. 22:00: 74.3% of final predictions within five minutes of the timetable, 35 predictions, typically 2.8 min late
    24. 23:00: 81.3% of final predictions within five minutes of the timetable, 32 predictions, typically 1.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 timetable07:00 to 09:003.4 min lateRunning time on the routes here
    ProblemPredictions later than timetable15:00 to 19:004.8 min lateRunning time on the routes here
    ProblemOne hour has a lower prediction match16:0036%Operations in that hour

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

    Predictions close to the timetable

    72.7%

    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

    6of 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 establish that buses departed early.

    Typical predicted delay

    3.4min

    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 · 07:00 to 09:00
    Median delay 3.4 min
    Measured arrivals 289
    On time 62.6%
    Predictions later than timetable · 15:00 to 19:00
    Median delay 4.8 min
    Measured arrivals 508
    On time 51.9%
    One hour has a lower prediction match · 16:00
    On time 36.2%
    Other hours on time 74.3%
    Measured arrivals 138

    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 6 published platform records in the current four-hour board.
    Coverage
    7 departures have a published live prediction; 33 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.