当前公交车：准点晚点您
目前我们无法确认电梯的状态。
More at this station
Station details
Step-free route
目前无法确认通告的覆盖范围。下方保留的通告，其时间或来源数据可能未经确认。出行前，请向运营商核实。
All elevators in the networkBuses from here
Tap a route for live buses and how full they are.
In the station
No published source lists amenities here yet.
Transfers and paths
Platforms and wayfinding (6)→
Each row is an individual platform stop. Open it for departures from that platform; use Departures for every platform together.
- Platform 1PIMISI O-TRAIN WEST / OUEST→
- Platform 2PIMISI O-TRAIN EAST / EST→
- Platform APIMISI A→
- Platform BPIMISI B→
- Platform CPIMISI C→
- Platform DPIMISI D→
Station sources can include entrances and indoor paths. Check Transfers and paths for what this station’s source actually contains. A published path does not verify an entrance is open, a step-free route is usable, or how to reach a bay from the street.
The platform list above is the structured text alternative to the station-centre map link. It includes every linked platform record that the current imported feed provides.
Open the station centre in OpenStreetMapTransfers and paths→
Official paths inside the station
Otranspo reads the optional GTFS station files separately from the timetable. A linked platform does not prove that a physical path exists, is open, or is step-free.
No step-by-step guide for this station yet. This feed version contains no published station path or transfer rule that can support a platform-to-platform guide.
A published path is not a verified accessible path. It does not prove that elevators are operating, every entrance is represented, or the route is suitable for a particular rider.
Source details
What this feed version includes
Imported source observed 2026/10/30 01:00:32
- Station levels
- The operator omitted this optional file from the feed
- Indoor paths
- The operator omitted this optional file from the feed
- 换乘规则
- The operator omitted this optional file from the feed
- Feed version
- 6ee8491d-8f94-4122-a67b-ef228d9e0945
- 解析器版本
- 2026-09-30.1
- Combined source checksum
- 44beccfc80480bcb5f6084066f2aa70a08abb7e234cb0bbc90f550e65ea08188
Find your way through this station
Start with what we know for sure. Open any row for platforms, transfers, accessibility and nearby services.
Published entrances and exits
No entrance record is published. Approach routes and exits remain unknown.
The operator may publish a station map or guide outside its machine-readable transit feed.
Open OC Transpo station information无障碍
→
Imported boarding information is shown separately when available. It does not verify a complete accessible route or current operating condition. Missing information is not a confirmation.
- Complete accessible route
- Unverified. The imported station record does not confirm a complete accessible route.
- Current operating condition
- Unknown. Current alerts cannot be matched completely to every entrance, elevator, pathway, and platform.
No verified accessible alternative is available in current data.
已发布的上车信息
以下是导入的 GTFS 时刻表中的轮椅上车静态信息。这些信息不能确认电梯目前是否运行、通道是否畅通，或是否有可用车辆。
这条记录的来源数据集版本和导入时间尚未核实。
- 已发布的车站记录
- 车站记录未注明是否可以乘轮椅上车。
无法为所有站台给出统一的上车答案。
- 站台 1
- 此站台未说明是否可供轮椅上车。
- 站台 2
- 此站台未说明是否可供轮椅上车。
- 站台 A
- 此站台未说明是否可供轮椅上车。
- 站台 B
- 此站台未说明是否可供轮椅上车。
- 站台 C
- 此站台未说明是否可供轮椅上车。
- 站台 D
- 此站台未说明是否可供轮椅上车。
无障碍出行链
未知。现有来源无法确认存在完整的无障碍行程。
All 8 links are unverified. Review the element list before relying on this station for an accessible trip.
来源: 当前导入的机构 GTFS。此导入的时刻表尚未核实车站无障碍的详细信息。
Review 8 unverified links
- 01Path to the station未知
- 02Station entrance未知
- 03Fare gate or paid-area entry未知
- 04Path to the platform未知
- 05Required elevators未知
- 06Boarding at 6 platform(s)未知
- 07Transfer links未知
- 08Destination-side exit未知
表现
服务运行情况 · 证据状态
Service at PIMISI
Cancellations at this station
Local count cannot be published
Exact stop-call evidence could not be read for 2026年10月27日 – 2026年11月2日. 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 · 0 live provider predictions
- Prediction agreement
- 70.3% 预测与时刻表相差在五分钟以内. 1,973 eligible provider predictions; arrivals not independently measured
Server snapshot assembled 2026年11月3日 11:51; open Departures for a refreshed board. This is not a cancellation count.
本站公交车预测的可靠性 →
结论
本站公交车预测的可靠性
Early evidence: 6 of 20 weekdays with eligible final provider predictions. This updates hourly; more records will make the estimate steadier.
70.3% of final provider predictions within 5 minutes of the timetable, from 1,973 predictions over 6 weekdays. The lowest sampled hour is 16:00 at 39%.
Median predicted difference from the timetable: 3 min 晚点. At the 95th percentile: 15 min 晚点.
这是运营方对 OC Transpo 和 STO 车站常规公交到站的最终预测。实际到站情况没有经过独立核实。 快线 (200/500)、购物/社区线 (300)、活动线 (400) 和学校线 (600) 不在范围内,因为每一类都需要专门的衡量方法。 STO 的线路也已纳入，并按各自的类别分级：Rapibus 100、200、400 和 800 线计入，编号为 300 及以上的 STO 校车班次则不计入，与 OC Transpo 的 600 系列做法相同。每家运营方只按自己的服务来衡量，绝不与另一家比较。 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.
- 00:00: not enough data00
- 01:00: 94% of final predictions within five minutes of the timetable, 50 predictions, typically 0.8 min late01
- 02:00: 86.8% of final predictions within five minutes of the timetable, 68 predictions, typically 1.7 min late02
- 03:00: 92.5% of final predictions within five minutes of the timetable, 40 predictions, typically 0.4 min early03
- 04:00: 93.4% of final predictions within five minutes of the timetable, 61 predictions, typically 0.5 min late04
- 05:00: not enough data05
- 06:00: 89.1% of final predictions within five minutes of the timetable, 110 predictions, typically 1.6 min late06
- 07:00: 68.8% of final predictions within five minutes of the timetable, 154 predictions, typically 3.3 min late07
- 08:00: 54.3% of final predictions within five minutes of the timetable, 186 predictions, typically 3.8 min late08
- 09:00: 70.5% of final predictions within five minutes of the timetable, 132 predictions, typically 2.9 min late09
- 10:00: 83.5% of final predictions within five minutes of the timetable, 85 predictions, typically 1.9 min late10
- 11:00: 74.1% of final predictions within five minutes of the timetable, 81 predictions, typically 2.6 min late11
- 12:00: 74.6% of final predictions within five minutes of the timetable, 71 predictions, typically 2.7 min late12
- 13:00: 69.3% of final predictions within five minutes of the timetable, 75 predictions, typically 2.9 min late13
- 14:00: 72% of final predictions within five minutes of the timetable, 75 predictions, typically 2.5 min late14
- 15:00: 50.7% of final predictions within five minutes of the timetable, 140 predictions, typically 4.8 min late15
- 16:00: 38.7% of final predictions within five minutes of the timetable, 137 predictions, typically 6.5 min late16
- 17:00: 65% of final predictions within five minutes of the timetable, 123 predictions, typically 2.7 min late17
- 18:00: 70.6% of final predictions within five minutes of the timetable, 109 predictions, typically 2.8 min late18
- 19:00: 72.3% of final predictions within five minutes of the timetable, 65 predictions, typically 2 min late19
- 20:00: 76.9% of final predictions within five minutes of the timetable, 52 predictions, typically 2.1 min late20
- 21:00: 77.8% of final predictions within five minutes of the timetable, 45 predictions, typically 2.8 min late21
- 22:00: 77.1% of final predictions within five minutes of the timetable, 35 predictions, typically 2.8 min late22
- 23:00: 78.1% of final predictions within five minutes of the timetable, 32 predictions, typically 1.6 min late23
- 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
| What | 时间 | 已测量 | Scenario or next investigation |
|---|---|---|---|
| Problem!Predictions later than timetable | 07:00 to 09:00 | 3.5 min late | Running time on the routes here |
| Problem!Predictions later than timetable | 15:00 to 17:00 | 5.7 min late | Running time on the routes here |
| Problem!One hour has a lower prediction match | 16:00 | 39% | Operations in that hour |
How PIMISI is doing
这些指标把反复出现的延误与运营方到达预测的波动区分开来。它们可为规划人员和运营人员提供可探讨的问题，但不能确定原因，也不能证明公共汽车何时到达。每个数字都显示其线路时段样本。
Measured over 22 route-hours. 0 more were observed too thinly to count, and are excluded rather than assumed good.
排班
如果多次出现预测晚点，可能说明时刻表值得检查。在决定是否调整运行时间之前，请先查看实际到达和发车记录。
- 谁能解决
- 服务规划人员
- 费用
- 在车队、人力、恢复和换乘的影响测试完成之前，成本暂不可知。
与时刻表接近的预测
81.8%
线路小时中，符合条件的到站预测中位数早于实际不到一分钟，且晚于实际不到三分钟。
多次预计晚点的线路时段
4of 22
路线小时数：符合条件的到达预测中位数至少晚点三分钟。请对照实际运营记录检查运行时间。
有提前预测的线路小时数
0of 22
线路-小时中，符合条件的到站预测中位数至少提前一分钟的部分。这并不能证明公交车提前发车。
典型预测延误
4.3min
在被标记的线路时段中，预测延误的典型中位数。这不是可直接加到时刻表上的经过验证的数值。
运营: not measurable here
本网站记录的是某个站点每小时的延误中位数，没有百分位数，所以无法算出正常行程与糟糕行程之间的差距。这是我们自身测量方式的限制，不是对这个地方的结论。
Measurements
计算时间: · 方法: settled-arrivals-oc-sto-conventional-v5
- Predictions later than timetable · 07:00 to 09:00
- Median delay 3.5 min
- Measured arrivals 340
- 准点 61.6%
- Predictions later than timetable · 15:00 to 17:00
- Median delay 5.7 min
- Measured arrivals 277
- 准点 44.7%
- One hour has a lower prediction match · 16:00
- 准点 38.7%
- Other hours on time 74.6%
- Measured arrivals 137
O-Train 数据
我们了解的本地列车服务情况
公共数据源中没有列车
公交准点报告将存档的到站预测与已公布的时刻表进行比较。报告不统计独立测得的实际到站情况。Otranspo 没有可用于这些报告的同类公开列车位置数据，因此这些公交数据无法显示列车在哪里，也无法说明 1 号线、2 号线和 4 号线是否准点。
公布列车位置、时间戳和测量方法，有助于另外建立可核实的轨道服务记录。缺少这份数据，并不能说明列车运行得如何。
近期共享的列车观测
这些是经审核员批准的乘客目击记录。它们显示乘客报告的时间和地点。它们不是列车的官方位置，不是完整的列车数量，也不能证明原因。
在最近 31 天内，没有与该地点或线路相符的已核准乘客观察记录。这并不表示没有列车运行，或没有发生问题。
Station information
Lines served (6)→
- 1timetable only→
- 8realtime published→
- 12realtime published→
- 13realtime published→
- 75realtime published→
- 562realtime published→
OC Transpo does not publish live train positions or predictions for O-Train lines. Train times shown here therefore come from the timetable.
Nearby amenities→
Nearby municipal washrooms and drinking fountains are shown separately from station-owned amenities. The source does not establish that they are inside the station, open now, or reachable by a step-free path.
Nearby amenities
Loading after departures…
Station evidence and sources
Print view prepared from the station record shown on this page. https://otranspo.ca/zh-Hans/stations/3010_stn
评价或报告问题→
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
- Elevator unavailable →
- Accessibility barrier →
- Washroom unavailable →
- Cleanliness →
- Graffiti →
- Damage →
- Lighting →
- Snow or ice →
- Safety →
- Other issue →
Emergency: call 9-1-1. Check official OC Transpo or STO notices before travelling.
本页的佐证数据打开定义、方法、来源、日期、覆盖范围和已知限制。
这里显示的内容
当前车站时刻板,由导入的时刻表和每个班次可用的运营方预测汇总而成。
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.
数据日期
- 计算或汇总时间
- 样本
- 40 departures across 6 published platform records in the current four-hour board.
- 覆盖范围
- 0 departures have a published live prediction; 40 are timetable-only.
来源
请注意的局限
- OC Transpo 在此处使用的数据源中不提供轨道交通的实时位置或预测,因此轨道交通时间仅为时刻表时间。
- 该站点数据源没有发布完整的车站无障碍通道链、出入口或室内路径。
Contains information licensed under the Open Government Licence – City of Ottawa.