Skip to main content

Next bus

FR

Report a problem

Filled in: station 3011 · 3:01 p.m. · pick one

What happened
Full report No account needed

Buses now:on timelateyou

1O-Train Line 1 · station 3011

Tunney's Pasture

Trains · timetableon timelateno reading
Every 4 min · sched. then 3:03
1
1Blair · platform 2
Not measured yet
3:01
sched. then 3:03
Every 4 min · sched. then 3:05
1
1Tunney's Pasture · platform 1
Not measured yet
3:01
sched. then 3:05
Buses at Tunney's Pasture · liveupdated 30 s ago
Every 15 min · sched. then 3:16
12
12Blair · platform E · every 15 to 15 min
Not measured yet
3:01
sched. then 3:16
61
61Tunney's Pasture
platform C
Not measured yet
3:01
from the timetable
74
74Tunney's Pasture
platform C
Not measured yet
3:01
from the timetable
61
61Terry Fox
platform B
Not measured yet
1minlive
262
262West Ridge
platform A
Not measured yet
3minlive
75
75Tunney's Pasture
platform C
Not measured yet
3:05
from the timetable
12
12Tunney's Pasture
platform C
Not measured yet
3:05
from the timetable
74
74Limebank
platform F
Not measured yet
5minlive
11
11Bayshore
platform D
Not measured yet
6minlive
14
14Tunney's Pasture
platform E
Not measured yet
3:07
from the timetable
566
566Tunney's Pasture
platform C
Not measured yet
6minlive
13
13Tunney's Pasture
platform B
Not measured yet
3:07
from the timetable
75
75Barrhaven Centre
platform F
Not measured yet
7minlive
51
51Tunney's Pasture
platform D
Not measured yet
3:08
from the timetable
87
87Tunney's Pasture
platform C
Not measured yet
3:08
from the timetable
75
75Cambrian
platform F
Not measured yet
8minlive
87
87Baseline
platform D
Not measured yet
8minlive
63
63Tunney's Pasture
platform C
Not measured yet
3:09
from the timetable
86
86C - Colonnade
platform D
Not measured yet
10minlive
62
62Tunney's Pasture
platform C
Not measured yet
3:11
from the timetable
279
279Manotick
platform G
Not measured yet
11minlive
57
57Tunney's Pasture
platform C
Not measured yet
3:12
from the timetable
56
56King Edward
platform E
Not measured yet
11minlive
51
51Britannia
platform D
Not measured yet
11minlive
81
81Tunney's Pasture
platform E
Not measured yet
3:13
from the timetable
11
11Waller
platform E
Not measured yet
12minlive
61
61Stittsville
platform B
Not measured yet
14minlive
14
14St-Laurent
platform E
Not measured yet
14minlive
53
53Baseline
platform D
Not measured yet
15minlive
86
86Tunney's Pasture
platform C
Not measured yet
3:16
from the timetable
Entrances and elevators

We cannot confirm elevator status right now.

81.8% predicted within five minutes of schedule. 6,851 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 here9 places within 5 min · nearest: Racks for 30 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 TUNNEY'S PASTURE

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

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

Prediction agreement
81.8% predicted within five minutes of schedule. 6,851 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 6,851 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 66%.

Median predicted difference from the timetable: 3 min late. At the 95th percentile: 9 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: 85% of final predictions within five minutes of the timetable, 107 predictions, typically 1.7 min late
  2. 01:00: 77.1% of final predictions within five minutes of the timetable, 96 predictions, typically 0.2 min late
  3. 02:00: 86.8% of final predictions within five minutes of the timetable, 68 predictions, typically 1.1 min late
  4. 03:00: 94.3% of final predictions within five minutes of the timetable, 35 predictions, typically 0.2 min early
  5. 04:00: 91% of final predictions within five minutes of the timetable, 67 predictions, typically 0 min late
  6. 05:00: 96.4% of final predictions within five minutes of the timetable, 140 predictions, typically 1.4 min late
  7. 06:00: 95.7% of final predictions within five minutes of the timetable, 370 predictions, typically 1.5 min late
  8. 07:00: 88.2% of final predictions within five minutes of the timetable, 451 predictions, typically 2.1 min late
  9. 08:00: 74.1% of final predictions within five minutes of the timetable, 490 predictions, typically 3.2 min late
  10. 09:00: 81% of final predictions within five minutes of the timetable, 401 predictions, typically 3 min late
  11. 10:00: 85.5% of final predictions within five minutes of the timetable, 387 predictions, typically 2.5 min late
  12. 11:00: 90.4% of final predictions within five minutes of the timetable, 384 predictions, typically 2.6 min late
  13. 12:00: 88.5% of final predictions within five minutes of the timetable, 375 predictions, typically 2.6 min late
  14. 13:00: 86.2% of final predictions within five minutes of the timetable, 399 predictions, typically 2.3 min late
  15. 14:00: 87.5% of final predictions within five minutes of the timetable, 368 predictions, typically 2.8 min late
  16. 15:00: 74.4% of final predictions within five minutes of the timetable, 426 predictions, typically 3.1 min late
  17. 16:00: 66.2% of final predictions within five minutes of the timetable, 441 predictions, typically 3.5 min late
  18. 17:00: 71.6% of final predictions within five minutes of the timetable, 447 predictions, typically 3.5 min late
  19. 18:00: 78.8% of final predictions within five minutes of the timetable, 339 predictions, typically 2.9 min late
  20. 19:00: 82.8% of final predictions within five minutes of the timetable, 261 predictions, typically 2.6 min late
  21. 20:00: 80.7% of final predictions within five minutes of the timetable, 243 predictions, typically 2.7 min late
  22. 21:00: 71.5% of final predictions within five minutes of the timetable, 228 predictions, typically 3.5 min late
  23. 22:00: 74.3% of final predictions within five minutes of the timetable, 183 predictions, typically 2.9 min late
  24. 23:00: 89% of final predictions within five minutes of the timetable, 145 predictions, typically 2 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 timetable08:003.2 min lateRunning time on the routes here
ProblemPredictions later than timetable15:00 to 18:003.3 min lateRunning time on the routes here
ProblemPredictions later than timetable21:003.5 min lateRunning time on the routes here
ProblemOne hour has a lower prediction match16:0066%Operations in that hour

How TUNNEY'S PASTURE 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 24 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

79.2%

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

5of 24

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 24

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.5min

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 · 08:00
Median delay 3.2 min
Measured arrivals 490
On time 74.1%
Predictions later than timetable · 15:00 to 18:00
Median delay 3.3 min
Measured arrivals 1,314
On time 71.6%
Predictions later than timetable · 21:00
Median delay 3.5 min
Measured arrivals 228
On time 71.5%
One hour has a lower prediction match · 16:00
On time 66.2%
Other hours on time 85.5%
Measured arrivals 441

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