Mapa
Previous measure: 76.6% of arrivals were within five minutes of the timetable (28,608 arrivals over 18 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.
Bawat 29 hanggang 60 min
Scheduled service and available evidence
Evidence period: Okt 29, 2026 – Nob 4, 2026
0
Trips in the published timetable marked cancelled without qualifying later matching vehicle observations in our archive. This does not prove the trip did not operate. Not counted: 12 trips with qualifying later matching vehicle observations. Trips with any notice: 12.
0
0 of 200 trips with a usable feed window (0%) had no matching position.
These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.
200 with position · 0 to investigate · 0 excluded · 200 scheduled trips
Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: Nob 5, 2026, 7:18 AM.
0 of 10 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.
0 scheduled trips were excluded from the position check for feed or identity gaps.
Published position coverage: 200 / 200 (100%). This is not a delivered-service rate. 7 service days in this source.
Timetables retained before the service day: 7 / 7 requested days · 0 missing days.
Historical calculation: Nob 5, 2026, 6:09 AM
Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.
Predictions against the timetable
76.6%
of eligible provider predictions were within five minutes of the timetable.
Share of predictions within five minutes of the timetable. Only eligible hours are shown; an absent hour does not mean zero.
These are provider predictions, not independently measured arrivals. Missing evidence is not counted as on-time service.
Calculated: Nob 5, 2026
2 partial-capture days not counted.
18 hourly cohorts meet the thresholds of 30 predictions and 5 service days. Hourly thresholds are assessed separately from the route-wide aggregate.
Improvement or decline requires comparable periods. This single result cannot establish a trend.
Last 28 days, Oktubre 8, 2026 to Nobyembre 4, 2026: 25 days counted.
2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: Oktubre 8, 2026, Oktubre 15, 2026.
2% of back-to-back buses on this route arrived bunched together: 118 of 7,345 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.
1% of pairs (101) had a long gap: more than 1.75 times the planned wait between them.
| Oras ng araw | Mga pares na sinuri | Nagkumpol | Mahabang pagitan |
|---|---|---|---|
| Rush hour sa umaga (6 hanggang 9 a.m.) | 1,435 | 0% (0) | 0% (0) |
| Tanghali (9 a.m. hanggang 3 p.m.) | 624 | 0% (0) | 0% (0) |
| Rush hour sa hapon (3 hanggang 6 p.m.) | 4,476 | 2% (92) | 2% (96) |
| Gabi (6 hanggang 10 p.m.) | 810 | 3% (26) | 1% (5) |
Slowest: BILLINGS BRIDGE 4B to WALKLEY D, 13.5 km/h actual against 18.4 km/h planned.
| Mula sa | Patungo sa | Layo | Planong bilis | Aktuwal na bilis | Mga biyaheng sinukat | Mabagal na biyahe |
|---|---|---|---|---|---|---|
| BILLINGS BRIDGE 4B | WALKLEY D | 6.1 km | 18.4 km/h | 13.5 km/h | 95 | 15% |
| WALKLEY C | BILLINGS BRIDGE 2A (B) | 6.3 km | 20.7 km/h | 15.2 km/h | 88 | 22% |
| PAUL ANKA / UPLANDS | SOUTH KEYS A | 2.5 km | 20.7 km/h | 23.1 km/h | 315 | 1% |
| UPLANDS / PAUL ANKA | WALKLEY C | 5.2 km | 21.4 km/h | 24.5 km/h | 92 | 0% |
| SOUTH KEYS E | UPLANDS / PAUL ANKA | 2.2 km | 23.1 km/h | 25.3 km/h | 293 | 2% |
| WALKLEY D | PAUL ANKA / UPLANDS | 5.1 km | 24.5 km/h | 27.1 km/h | 317 | 1% |
| GREENBORO B | SOUTH KEYS E | 830 m | 17.9 km/h | 30.2 km/h | 267 | 3% |
| HURDMAN D | BILLINGS BRIDGE 4B | 3.3 km | 40.1 km/h | 33.8 km/h | 91 | 18% |
Ang mabagal na biyahe ay inabot nang hindi bababa sa 1.5 beses ng planadong oras.
Mga gawaing kalsada at pagsasara ng kalsada para sa event na inilathala ng City of Ottawa, na sinukat bilang malapit sa daanan ng rutang ito. Ang malapit ay hindi patunay na iniiba ang daan ng bus. Tingnan po ang sariling abiso ng tagapagpatakbo para doon.
Hindi po mabasa ngayon ang listahan ng lungsod ng mga gawaing pangkalsada.
A route counts as near when its timetable path passes within 40 m of the City’s mapped closure; a stop counts when it is within 75 m.
Pinagmulan: mga traffic event ng City of Ottawa (road work at mga pagsasara ng daan). May impormasyong lisensyado sa ilalim ng Open Government Licence, City of Ottawa. Ayon sa Lungsod, pinagsikapan lamang ang listahang ito at maaaring hindi kumpleto. Mapa ng trapiko ng Lungsod ng Ottawa ↗
2 partial-capture days not counted.
1 scheduled trips with counted cancellation notices from Huw, Okt 8 to Miy, Nob 4.
Not counted: 14 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.
Mga oras na may pinakamaraming kanseladong biyahe: 4 PM (1)
Hindi nagbibigay ang OC Transpo ng dahilan para sa isang biyahe, kaya walang ipinapakita.
Hindi dumating (walang nakitang bus, walang abiso), huling 7 araw: wala sa mga biyaheng nasuri namin.
Hatol
Median provider predictions are 6.5 min later than the timetable in 3 hours of the day.
Predictions near the start are about 4.5 min later than the timetable, with a similar difference near the end. This does not establish the cause.
Provider predictions are about 1 min earlier than the timetable, 14:00.
16:00 has 17% of predictions within five minutes of the timetable, against 96% the rest of the day.
Matched public positions cover 100% of scheduled trips. This is a lower bound on operated service, not an audited delivery result.
Next investigation: test terminal recovery and the preceding trip against operational records. Predictions alone do not establish the cause.
| What | Kailan | Nasukat | Scenario or next investigation |
|---|---|---|---|
| ProblemPredictions later than timetable | 15:00 to 18:00 | 6.5 min late | Recovery time at the terminal |
| ProblemOne hour has a lower prediction match | 16:00 | 17% | Operations, not the timetable |
| ProblemPredictions earlier than timetable | 14:00 | 1 min early | Less running time, or holding points |
| StrengthObserved-position lower bound | All measured hours | 100% | Keep what works |
Pagsusuri ng ruta
Maikling buod ng alam namin. Sinasabi namin kapag hindi namin masagot ang isang tanong.
Pangunahing punto
Resultang may petsa, hindi live na serbisyo
This prediction-to-timetable result describes the dated period, not service right now. It was last calculated 5 hours ago. Current vehicle positions and official notices are checked separately.
77 in 100 eligible predictions were within 5 minutes of the timetable · 28,608 predictions checkedLaki ng sample ng prediksyon: Mas malaking sample
Based on 28,608 eligible provider predictions over 18 measured days, from Okt 6, 2026 to Nob 3, 2026.
Updated Nob 5, 2026, 2:32 AM
Ito ay mga paulit-ulit na pagkakaiba ng hula at ng iskedyul, hindi mga pagkabigo sa serbisyo na sinukat nang hiwalay. Ginagamit nito ang parehong karapat-dapat na mga hula gaya ng resulta sa itaas, pero pinagsasama-sama ayon sa hintuan, hindi ayon sa oras. Kaya maaaring hindi magkapareho ang mga listahan sa bawat linya.
Walang kasalukuyang opisyal na abiso na tumutugma sa rutang ito.
Pagkakaiba ng hula ayon sa hintuan
98 in 100 eligible predictions differed from the timetable by more than 5 minutes (119 predictions over 20 days).
Buksan ang hintuang ito97 in 100 eligible predictions differed from the timetable by more than 5 minutes (119 predictions over 20 days).
Buksan ang hintuang ito96 in 100 eligible predictions differed from the timetable by more than 5 minutes (119 predictions over 20 days).
Buksan ang hintuang ito93 in 100 eligible predictions differed from the timetable by more than 5 minutes (119 predictions over 20 days).
Buksan ang hintuang itoIto ay mga hula ng provider para sa partikular na ruta, na inihambing sa iskedyul. Ipinapakita nito ang paulit-ulit na pagkakaiba ng hula sa isang lugar at oras. Hindi ito nasukat na pagdating at hindi nito sinasabi ang dahilan.
Magbukas ng yugto ng panahon para makita ang bawat araw ng serbisyo, nakatakdang biyahe, puwang sa feed, naobserbahang pampublikong ID ng sasakyan, at ang eksaktong bilang sa likod ng buod na ito.
Pagsusuri ng pagbabago sa iskedyul
Ikinukumpara po nito ang kasalukuyang opisyal na iskedyul na iniingatan sa naunang bersyon na iniingatan. Ang mga pagbabago sa iskedyul ay mga katotohanan tungkol sa kung ano ang binalak. Hindi po nito pinatutunayan na naganap ang isang biyahe.
Current published schedule began Oktubre 30, 2026
Sinusuri po namin ang unang Lunes pagkatapos magsimula ang bagong iskedyul at ang Lunes isang linggo bago nito. Ang bawat bilang ay galing sa mga opisyal na bersyon ng GTFS na itinabi at nakasaad sa ibaba.
Hindi bababa sa isa sa mga napiling petsa ang may idinagdag o inalis na serbisyo sa petsa ng kalendaryo. Ituring po ito bilang konteksto ng holiday o espesyal na serbisyo, hindi karaniwang paglago tuwing karaniwang araw.
Petsa ng serbisyo na sinuri: Oktubre 26, 2026
Operator calendar-date records: 0 added · 2 removed
Fingerprint ng feed: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad
Petsa ng serbisyo na sinuri: Nobyembre 2, 2026
Operator calendar-date records: 0 added · 2 removed
Fingerprint ng feed: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945
Ihahambing po namin ang mga natapos na dating ng sasakyan sa loob ng 14 na araw bago at pagkatapos ng pagbabago. Ilalathala lamang po namin ang paghahambing kapag may hindi bababa sa 7 araw ng serbisyo at 200 dating ang magkabilang panig.
Still collecting: before has 15,796 arrivals over 10 days; after has 6,360 arrivals over 4 days. No improvement or decline is claimed yet.
Sa checksum, maaaring tiyakin ng sinuman kung aling iskedyul na itinabi ang pinagmulan ng mga bilang. Ang pagbabago sa bilang ay hindi nagpapakita ng dahilan, pagkansela, desisyon ng operator, o epekto sa mga pasahero.
Inihahambing namin ang huling karapat-dapat na hula ng provider para sa bawat nakaiskedyul na pagdating sa opisyal na iskedyul. Hindi ito mga pagdating na sinukat nang hiwalay. Kailangan ng hindi bababa sa 200 karapat-dapat na hula para magkaroon ng resulta. Ang loob ng 5 minuto ang target para sa mga sakay na ginagamit dito.
Ang public feed po ay hindi nagbibigay ng maaasahang bilang ng pasahero o ng mga pagkakataong nilampasan ang mga naghihintay na pasahero. Ang kawalan ng posisyon ay hindi nangangahulugang patunay ng pagkansela, hindi pagdating, maikling biyahe o sanhi nito.
Pansamantalang resulta, inilathalang ebidensya
Sa bawat oras, inihahambing ang huling karapat-dapat na predicted na dating mula sa provider para sa isang scheduled na pagdating sa timetable. Ang "Within 5 minutes" ay naglalarawan ng pagkakaiba ng prediksyon, hindi ng nasukat na pagdating o patunay na bumiyahe ang bus.
Saklaw ng ebidensya: Oktubre 6, 2026 to Nobyembre 3, 2026
| Oras | Nasa oras | Median | 95th percentile | Ebidensya |
|---|---|---|---|---|
| 06:00 | 95.2% | 0.6 min late | 5 min late | 1,100 · 11 days |
| 07:00 | 89.7% | 0.6 min late | 6.4 min late | 1,746 · 11 days |
| 08:00 | 87.3% | 0.5 min late | 6.9 min late | 1,386 · 11 days |
| 09:00 | 98.8% | 0.2 min early | 2.2 min late | 1,012 · 11 days |
| 10:00 | 96.2% | 0.2 min late | 2.7 min late | 660 · 11 days |
| 11:00 | 97.4% | 0.2 min late | 3.6 min late | 662 · 11 days |
| 12:00 | 99.4% | 0.2 min early | 2.9 min late | 651 · 11 days |
| 13:00 | 94.1% | 0.6 min late | 5.3 min late | 660 · 11 days |
| 14:00 | 95.2% | 1 min early | 4.5 min late | 703 · 11 days |
| 15:00 | 43.3% | 6.5 min late | 19.2 min late | 1,748 · 11 days |
| 16:00 | 17.0% | 9.2 min late | 24.9 min late | 1,391 · 11 days |
| 17:00 | 42.0% | 6 min late | 16.3 min late | 1,709 · 11 days |
| 18:00 | 81.9% | 2.1 min late | 6.9 min late | 934 · 11 days |
| 19:00 | 99.7% | 0.4 min late | 2.4 min late | 693 · 11 days |
| 20:00 | 98.5% | 0.8 min late | 4.3 min late | 662 · 11 days |
| 21:00 | 98.8% | 2 min late | 3.5 min late | 662 · 11 days |
| 22:00 | 96.2% | 2.7 min late | 4.5 min late | 601 · 11 days |
| 23:00 | 100.0% | 1.7 min late | 2.7 min late | 325 · 11 days |
3 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.
200 / 200 scheduled trips published at least one position across 5 service days (100.0%).
Hindi ito kumpirmadong hindi pagsipot. Ang nawawalang posisyon ay maaaring mangahulugang kinansela o nalagpasang bus, pero maaari rin itong mangahulugang walang nakatalagang ID ng biyahe o may puwang sa feed ng operator. Inilalathala ng Otranspo ang puwang dahil mahalaga ito sa mga sakay, habang nananatiling tapat ang konklusyon.
Prediction check: the last eligible provider prediction no earlier than ten minutes before the scheduled arrival, counted once per trip, stop and scheduled Toronto calendar date. It is compared with the timetable, not an independently measured arrival. Trip-position check: the timetable kept before each service day, matched to recorded positions. Exact IDs are preferred; an OC timetable suffix is matched only to one trip on the same route and date with an overlapping time window. Missing timetables, ambiguous matches and feed gaps stay labelled; they are not confirmed no-shows. Mga pinagmulan at limitasyon.
Dated service
The timetable, notices and what the live feed says are shown apart. Seeing a bus on the map does not prove you can board it.
November 4, 2026 · 40 trips in the retained timetable · retained notices; capture coverage unverified
In short: 40 with a matched position · 0 with no matching position (to investigate) · 0 with an unknown outcome.