No 6 trips cancelled now · 11 did not run in 11月Cancellations →

Previous measure: 69.4% of arrivals were within five minutes of the timetable (191,599 arrivals over 27 days). The report card below uses the newer one-minute-early to five-minutes-late measure when it has readings.

路線 6: Greenboro ⇄ Rockcliffe

6分から28分ごと

方面Greenboro2 buses · boards at · under each stop: the next bus (live dot = live, grey = sched.)

Scheduled service and available evidence

Did the scheduled service run?

Open dated evidence

Evidence period: 2026/10/29 – 2026/11/04

Scheduled trips with cancellation notices

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: 10 trips with qualifying later matching vehicle observations. Trips with any notice: 16.

Trips needing investigation

16 of 1,000 trips with a usable feed window (1.6%) had no matching position.

These counts may overlap; do not add them. A missing position confirms neither cancellation nor a no-show.

984 with position · 16 to investigate · 7 excluded · 1,007 scheduled trips

Current feed. No explicit notice for this route in the current feed; this does not guarantee service. Observed: 2026/11/05 1:36.

Coverage, exclusions and sources

0 of 6 endpoint departures scheduled in the next four hours carried an explicit cancellation at the last check.

7 scheduled trips were excluded from the position check for feed or identity gaps.

Published position coverage: 984 / 1,007 (97.7%). 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: 2026/11/05 0:18

Method: explicit provider notices, archived trip windows and retained timetables. Predictions and positions alone do not prove that a bus ran or was missed.

What does the evidence show?

Predictions against the timetable

69.4%

of eligible provider predictions were within five minutes of the timetable.

Predictions in the source: 191,599
Weekdays with evidence: 19
Evidence window: 2026/10/06 – 2026/11/03

The hours we have evidence for

0時80% · 1,605 predictions · 14 days
1時76% · 1,167 predictions · 14 days
2時90% · 260 predictions · 11 days
4時79% · 479 predictions · 13 days
5時89% · 1,979 predictions · 13 days
6時90% · 3,878 predictions · 15 days
7時81% · 5,673 predictions · 15 days
8時75% · 7,358 predictions · 15 days
9時73% · 6,567 predictions · 15 days
10時74% · 6,878 predictions · 15 days
11時68% · 6,543 predictions · 15 days
12時63% · 6,569 predictions · 15 days
13時67% · 6,839 predictions · 15 days
14時68% · 5,849 predictions · 15 days
15時58% · 5,181 predictions · 15 days
16時53% · 5,853 predictions · 15 days
17時45% · 7,908 predictions · 15 days
18時57% · 8,117 predictions · 15 days
19時68% · 5,710 predictions · 15 days
20時78% · 4,317 predictions · 15 days
21時75% · 3,453 predictions · 15 days
22時79% · 3,483 predictions · 15 days
23時78% · 3,081 predictions · 15 days

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: 2026/11/05

2 partial-capture days not counted.

What about time of day?

23 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.

Explore the dated evidence Source of this result

バスが続けて到着

Last 28 days, 2026年10月8日 to 2026年11月4日: 25 days counted.

2 days left out because the live feed was only partly recorded or its trip numbers did not match the timetable: 2026年10月8日, 2026年10月15日.

値と解釈

5% of back-to-back buses on this route arrived bunched together: 7,511 of 157,250 pairs checked at stops in the last 28 days. When buses bunch, the wait after them is usually longer.

3% of pairs (4,840) had a long gap: more than 1.75 times the planned wait between them.

バスが続けて到着
時間帯	確認したペア	団子運転	長い間隔
早朝(午前4時から6時)	504	0% (0)	0% (0)
朝のラッシュ (午前6時から9時)	20,997	4% (874)	4% (742)
昼間（午前9時から午後3時）	61,932	4% (2,199)	2% (1,440)
午後のラッシュ(午後3時から6時)	27,488	9% (2,540)	6% (1,557)
夜（午後6時から10時）	33,106	6% (1,867)	3% (1,064)
夜間(午後10時から午前4時)	13,223	0% (31)	0% (37)

測定方法について →How we got this number全路線の団子運転と低速区間 →

この路線で最も遅い区間

Slowest: ST PATRICK / COBOURG to MAPLE LANE / SPRINGFIELD, 7.4 km/h actual against 8.2 km/h planned.

この路線で最も遅い区間
出発地	到着地	距離	計画速度	実際の速度	測定した便数	遅い便
ST PATRICK / COBOURG	MAPLE LANE / SPRINGFIELD	1.3 km	8.2 km/h	7.4 km/h	31	23%
BILLINGS BRIDGE 4B	BANK / TRANSITWAY	310 m	14.4 km/h	7.9 km/h	1,306	54%
RIDEAU A	PARLIAMENT B	940 m	9.2 km/h	8.6 km/h	1,682	11%
PARLIAMENT A	RIDEAU B	770 m	11.4 km/h	9.5 km/h	1,301	16%
PARLIAMENT B	BANK / GLADSTONE	1.2 km	11 km/h	9.9 km/h	1,710	6%
RIDEAU B	ST PATRICK / COBOURG	1.7 km	12 km/h	10.3 km/h	1,280	10%
BANK / GLADSTONE	PARLIAMENT A	1.2 km	10.2 km/h	10.5 km/h	1,750	1%
BEECHWOOD / MACKAY	RIDEAU A	2.2 km	11.6 km/h	10.6 km/h	1,246	4%

遅いトリップとは、予定の時間の1.5倍以上かかったトリップです。

測定方法について →

この路線の近くの市の道路工事

オタワ市が公表した道路工事とイベントによる道路閉鎖のうち、この路線の経路の近くにあるものです。近くにあっても、バスが迂回するとは限りません。迂回については、事業者の運行情報をご確認ください。

市の道路工事リストを現在読み取れません。

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.

情報源：オタワ市の交通イベント情報（道路工事と通行止め）。オタワ市のオープンガバメントライセンスに基づく情報を含みます。市によると、この一覧は可能な範囲でまとめたもので、すべてを含まない場合があります。オタワ市の交通マップ ↗

この路線の運休

これらの言葉の意味 →

2 partial-capture days not counted.

18 scheduled trips with counted cancellation notices from 10月8日(木) to 11月4日(水).

Not counted: 31 trips with qualifying later matching vehicle observations and 0 for trips not in that day’s timetable.

運休が最も多い時間帯: 15時 (3), 16時 (3), 18時 (3)

What this route needs

Median provider predictions are 3.5 to 4.1 min later than the timetable in 6 hours of the day.

Predictions near the start are about 2.4 min later than the timetable; the difference grows by another 4.2 min along the route.

Wide prediction spread 00:00, 02:00: the 95th percentile is 37.9 min later than the median.

Predicted waits All measured hours are 1.9 min longer than scheduled waits.

17:00 has 45% of predictions within five minutes of the timetable, against 75% the rest of the day.

Only 98% of scheduled trips were seen; the rest are not counted as missed.

Scenario: 4 min more running time on 636 trips. The schedule-block model estimates 2 additional buses; fleet and workforce feasibility are unverified.

Assumptions: published departure times, trip blocks and service pattern stay fixed while running time changes. A scheduler must test headways, transfers, recovery, fleet circulation, operator shifts, labour rules and cost before use.

Final provider predictions within five minutes of the timetable, by hour, last 14 days, 23 hours with samples

00:00: 80.2% of final predictions within five minutes of the timetable, 1,605 predictions, typically 1.4 min late. Provider predictions have a wide spread.
01:00: 75.7% of final predictions within five minutes of the timetable, 1,167 predictions, typically 1.6 min late
02:00: 89.6% of final predictions within five minutes of the timetable, 260 predictions, typically 2 min late. Provider predictions have a wide spread.
03:00: not enough data
04:00: 79.1% of final predictions within five minutes of the timetable, 479 predictions, typically 3.6 min late
05:00: 88.8% of final predictions within five minutes of the timetable, 1,979 predictions, typically 1.9 min late
06:00: 89.5% of final predictions within five minutes of the timetable, 3,878 predictions, typically 0.9 min late
07:00: 81.2% of final predictions within five minutes of the timetable, 5,673 predictions, typically 1.8 min late
08:00: 74.9% of final predictions within five minutes of the timetable, 7,358 predictions, typically 2.3 min late
09:00: 73.1% of final predictions within five minutes of the timetable, 6,567 predictions, typically 1.9 min late
10:00: 74.1% of final predictions within five minutes of the timetable, 6,878 predictions, typically 2 min late
11:00: 67.8% of final predictions within five minutes of the timetable, 6,543 predictions, typically 2.5 min late
12:00: 63% of final predictions within five minutes of the timetable, 6,569 predictions, typically 3.5 min late
13:00: 67.1% of final predictions within five minutes of the timetable, 6,839 predictions, typically 2.6 min late
14:00: 68.1% of final predictions within five minutes of the timetable, 5,849 predictions, typically 2.5 min late
15:00: 58.1% of final predictions within five minutes of the timetable, 5,181 predictions, typically 3.5 min late
16:00: 53.4% of final predictions within five minutes of the timetable, 5,853 predictions, typically 4.5 min late
17:00: 44.9% of final predictions within five minutes of the timetable, 7,908 predictions, typically 5.8 min late
18:00: 57.4% of final predictions within five minutes of the timetable, 8,117 predictions, typically 3.7 min late
19:00: 68% of final predictions within five minutes of the timetable, 5,710 predictions, typically 1.9 min late
20:00: 77.5% of final predictions within five minutes of the timetable, 4,317 predictions, typically 0.9 min late
21:00: 74.6% of final predictions within five minutes of the timetable, 3,453 predictions, typically 1.1 min late
22:00: 78.7% of final predictions within five minutes of the timetable, 3,483 predictions, typically 2.1 min late
23:00: 78.3% of final predictions within five minutes of the timetable, 3,081 predictions, typically 2.1 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
prediction spread of 20 min or more between the 95th percentile and median

Findings
What	いつ	測定済み	Scenario or next investigation
ProblemPredictions later than timetable	04:00 · 12:00 · 15:00 to 19:00	3.6 min late … 4.1 min late	More running time
ProblemLong predicted waits on a frequent route	All measured hours	1.9 min extra wait	Manage the headway
ProblemOne hour has a lower prediction match	17:00	45%	Operations, not the timetable
ProblemWide prediction spread	00:00 · 02:00	20.6 min swing · 37.9 min swing	Overnight operations
CaveatCoverage gap	All measured hours	98%	More observation, not a service change

Measurements

Predictions later than timetable · 15:00 to 19:00: Measured arrivals 27,059; Hours affected 4; Spread 14.6 min; Median delay 4.1 min; Suggested running time change 4.1 min
Long predicted waits on a frequent route · All measured hours: 停留所 119; Extra wait share 35.8%; 一致した到着 19,431; 追加の待ち時間 1.9 min; Scheduled wait 5.2 min
Predictions later than timetable · 12:00: Measured arrivals 6,569; Hours affected 1; Spread 11 min; Median delay 3.5 min; Suggested running time change 3.5 min
One hour has a lower prediction match · 17:00: 時間 17:00; 定刻通り 44.9%; Measured arrivals 7,908; Shortfall 29.7 pts; Route median on time 74.6%
Wide prediction spread · 00:00: Measured arrivals 1,605; Hours affected 1; Spread 20.6 min; Median delay 1.4 min; Suggested running time change 1.4 min
Predictions later than timetable · 04:00: Measured arrivals 479; Hours affected 1; Spread 3.6 min; Median delay 3.6 min; Suggested running time change 3.6 min
Wide prediction spread · 02:00: Measured arrivals 260; Hours affected 1; Spread 37.9 min; Median delay 2 min; Suggested running time change 2 min
Coverage gap · All measured hours: 目標 99.5%; Trips with a matching position 97.8%; 運行日 7; Trips with a matching position 985; 予定の便 1,007

履歴、信頼性、路線の分析を開く

路線チェック

How route 6 has been running

わかっていることの短いまとめです。答えられない質問には、そのとおりに示します。

結論

事業者の予測は、時刻表と異なることが多くありました。実際の到着は別途測定していません。

69 in 100 eligible predictions were within 5 minutes of the timetable · 191,599 predictions checked

予測のサンプル数: サンプル数が多い

Based on 191,599 eligible provider predictions over 27 measured days, from 2026年10月6日 to 2026年11月3日.

Updated 2026/11/05 0:33

予測が何度もずれたのは、どこで、いつですか。

これらは、予測と時刻表の差が繰り返し出たものです。独立して測定した運行の不具合ではありません。上の結果と同じ対象の予測を使っていますが、時間帯ではなくバス停ごとにまとめています。そのため、一覧が行ごとに一致するとは限りません。

17時–18時: 55 in 100 eligible predictions differed from the timetable by more than 5 minutes (7,908 predictions over 15 days).
16時–17時: 47 in 100 eligible predictions differed from the timetable by more than 5 minutes (5,853 predictions over 15 days).
18時–19時: 43 in 100 eligible predictions differed from the timetable by more than 5 minutes (8,117 predictions over 15 days).
15時–16時: 42 in 100 eligible predictions differed from the timetable by more than 5 minutes (5,181 predictions over 15 days).

この路線に当てはまる現在の公式のお知らせはありません。

停留所ごとの予測の差

MURRAY / KING EDWARD
60 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,502 predictions over 29 days).
この停留所を開く
MURRAY / DALHOUSIE
58 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,503 predictions over 29 days).
この停留所を開く
MURRAY / CUMBERLAND
57 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,502 predictions over 29 days).
この停留所を開く
DALHOUSIE / CLARENCE
57 in 100 eligible predictions differed from the timetable by more than 5 minutes (1,503 predictions over 29 days).
この停留所を開く

これは、路線ごとの事業者の予測を時刻表と比べたものです。特定の場所と時間帯で予測の差が繰り返し出ていることを示します。実際の到着を測ったものではなく、原因も示しません。

すべての trip と日付を確認

時間帯を開くと、各運行日、予定された便、データの欠落、観測された公開車両ID、この概要の元になった正確な件数を確認できます。

利用者が知りたいこと

今、運休している便はありますか?: 0 of 6今後4時間以内に、路線の端の停留所から出発する便を確認します。過去の運休率ではありません。
フィードの欠落を確認した後の、来なかった可能性がある便: 16 of 1,000 checked trips need a closer look16 of 1,000 trips with enough public-feed evidence had no matching position over 7 days. 7 of 1,007 scheduled trips were excluded because the feed record was incomplete. These are cases to investigate, not confirmed no-shows.
事業者の予測は時刻表とどう違いましたか。: At the 95th percentile, the predicted difference was 14.5 min (positive means later; negative means earlier)69 in 100 eligible provider predictions were within 5 minutes of the timetable; actual arrivals were not measured here.
事業者の予測では、どれくらいの待ち時間でしたか？: 7.1 min average predicted wait1.9 min beyond the scheduled wait, based on 19,431 eligible predictions at 119 high-frequency stops over 21 days.

ダイヤ変更の確認

公開されている時刻表：変更前と変更後

これは、現在保存している公式の時刻表と、以前に保存した版を比べたものです。時刻表の変更は、計画された内容についての事実です。トリップが実際に運行されたことを示すものではありません。

Current published schedule began 2026年10月30日

公表されている各時刻表から選んだ運行日

新しい時刻表が始まった後の最初の月曜日と、その一週間前の月曜日を調べます。すべての数値は、下に記載した、保管されている公式のGTFSバージョンから取得しています。

選択した日付の少なくとも一つに、カレンダー-日付による運行の追加または削除があります。これは通常の平日の増加ではなく、祝日または特別運行の状況として扱ってください。

変更前

確認したサービス日: 2026年10月26日

予定の便: 148
予定されている停留所の数（重複なし）: 120
公開されている異なる経路: 6
公表されている運行時間帯: 4:35–2:19 next day

Operator calendar-date records: 0 added · 2 removed

フィードのフィンガープリント: 1d13d0abb2506002 · 3932bee1-4577-4968-9a97-2987e88312ad

新しいダイヤ

確認したサービス日: 2026年11月2日

予定の便: 148
予定されている停留所の数（重複なし）: 120
公開されている異なる経路: 6
公表されている運行時間帯: 4:35–2:19 next day

Operator calendar-date records: 0 added · 2 removed

フィードのフィンガープリント: 91dd8e4251604344 · 6ee8491d-8f94-4122-a67b-ef228d9e0945

変更後にサービスは改善しましたか?

変更の前後それぞれ14日間について、確定した到着を比較します。比較は、前後の両方でサービス日が7日以上、到着が200件以上になってから公開します。

Still collecting: before has 101,346 arrivals over 14 days; after has 42,911 arrivals over 6 days. No improvement or decline is claimed yet.

チェックサムを使うと、保存された時刻表のどれから件数が出たかを、誰でも確認できます。件数が変わっても、原因、運休、事業者の判断、乗客への影響は分かりません。

この路線の評価方法: 全停留所に停まる通常の路線

各到着予定について、対象となる最後の事業者の予測と公式の時刻表を比べます。これは独立して測定した到着ではありません。結果には、対象の予測が200件以上必要です。5分以内は、ここで使うお客様向けの目標です。

このデータでは証明できないこと

公開フィードには、信頼できる乗客数や乗客を乗せずに通過した事象のデータがありません。位置情報がないだけでは、運休、運行なし、折り返し運転、またはその原因を証明することはできません。

定義、しきい値、データの優先順位を見る

公式の最新フィード：明示的な運休、通過した停留所、現在有効なお知らせです。
照合した観測データ:公式の時刻表に結び付けた車両位置と確定した予測です。
公式の時刻表です。計画された内容を、観測された内容とは分けて示します。
利用者と事業者からの報告：路線、時刻、場所について調べるための手がかりです。それだけでは数値による証拠にはなりません。

暫定的な結果、公表されたデータ

予測は時刻表とどう比べられましたか?

各時間帯ごとに、予定された到着について対象となる最後の事業者の予測を、時刻表と比べています。「5分以内」は予測と時刻表の差を示します。実際の到着を測ったものではなく、バスが運行した証拠でもありません。

根拠の期間: 2026年10月6日 to 2026年11月3日

予定から5分以内: 69.4%
確認した対象の予測: 191,599
データのある平日: 19
予測遅延の95パーセンタイル: 14.5 min late

Patterns by hour (23)

Patterns by hour (23)
時間	定刻通り	中央値	95パーセンタイル	データ
00:00	80.2%	1.4 min late	22.1 min late	1,605 · 14 days
01:00	75.7%	1.6 min late	16.7 min late	1,167 · 14 days
02:00	89.6%	2 min late	39.9 min late	260 · 11 days
04:00	79.1%	3.6 min late	7.2 min late	479 · 13 days
05:00	88.8%	1.9 min late	9.1 min late	1,979 · 13 days
06:00	89.5%	0.9 min late	6.9 min late	3,878 · 15 days
07:00	81.2%	1.8 min late	8 min late	5,673 · 15 days
08:00	74.9%	2.3 min late	9.8 min late	7,358 · 15 days
09:00	73.1%	1.9 min late	10.6 min late	6,567 · 15 days
10:00	74.1%	2 min late	10.5 min late	6,878 · 15 days
11:00	67.8%	2.5 min late	10.8 min late	6,543 · 15 days
12:00	63.0%	3.5 min late	14.4 min late	6,569 · 15 days
13:00	67.1%	2.6 min late	13.7 min late	6,839 · 15 days
14:00	68.1%	2.5 min late	13.7 min late	5,849 · 15 days
15:00	58.1%	3.5 min late	15.5 min late	5,181 · 15 days
16:00	53.4%	4.5 min late	19.6 min late	5,853 · 15 days
17:00	44.9%	5.8 min late	22 min late	7,908 · 15 days
18:00	57.4%	3.7 min late	17.9 min late	8,117 · 15 days
19:00	68.0%	1.9 min late	18.8 min late	5,710 · 15 days
20:00	77.5%	0.9 min late	16.5 min late	4,317 · 15 days
21:00	74.6%	1.1 min late	11.2 min late	3,453 · 15 days
22:00	78.7%	2.1 min late	11.4 min late	3,483 · 15 days
23:00	78.3%	2.1 min late	12.2 min late	3,081 · 15 days

9 hourly block(s) are below 70% across at least three service days: a repeated pattern, not one bad day.

時刻表にはあるバスですが、リアルタイムでは観測されていません

985 / 1,007 scheduled trips published at least one position across 7 service days (97.8%).

02:003 / 6 trips without a position50.0%
01:008 / 23 trips without a position65.2%
18:003 / 61 trips without a position95.1%
00:001 / 22 trips without a position95.5%
19:002 / 46 trips without a position95.7%
23:001 / 23 trips without a position95.7%

これは確認された運休ではありません。 位置情報がないのは、バスの運休や運行漏れが原因の場合があります。便IDが割り当てられていない場合や、事業者のフィードに欠落がある場合もあります。利用者にとって大切な情報なので、Otranspoはこの欠落を公開します。ただし、結論は正直に控えめにしています。

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. ソースと制限事項.

Dated service

Trips scheduled that day

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.

Service day

November 4, 2026 November 3, 2026 November 2, 2026 November 1, 2026 October 31, 2026 October 30, 2026 October 29, 2026

November 4, 2026 · 148 trips in the retained timetable · retained notices; capture coverage unverified

In short: 138 with a matched position · 3 with no matching position (to investigate) · 7 with an unknown outcome.

04:35– 05:03
Trip 33858040Vehicle position matchedFirst / last feed position: 4:11 a.m. EST / 5:08 a.m. EST; not actual start or end times.
05:00– 05:44
Trip 94040Vehicle position matchedFirst / last feed position: 4:48 a.m. EST / 5:51 a.m. EST; not actual start or end times.
05:05– 05:36
Trip 9902040Vehicle position matchedFirst / last feed position: 4:48 a.m. EST / 5:37 a.m. EST; not actual start or end times.
05:30– 06:16
Trip 18450040Vehicle position matchedFirst / last feed position: 5:09 a.m. EST / 6:31 a.m. EST; not actual start or end times.
05:35– 06:09
Trip 16127040Vehicle position matchedFirst / last feed position: 5:16 a.m. EST / 6:06 a.m. EST; not actual start or end times.
05:55– 06:45
Trip 22384040Vehicle position matchedFirst / last feed position: 5:30 a.m. EST / 6:43 a.m. EST; not actual start or end times.
06:00– 06:48
Trip 34631040Vehicle position matchedFirst / last feed position: 5:35 a.m. EST / 6:53 a.m. EST; not actual start or end times.
06:02– 07:04
Trip 29385040Vehicle position matchedFirst / last feed position: 5:36 a.m. EST / 7:14 a.m. EST; not actual start or end times.
06:15– 07:09
Trip 21414040Vehicle position matchedFirst / last feed position: 5:49 a.m. EST / 7:19 a.m. EST; not actual start or end times.
06:30– 07:27
Trip 6567040Vehicle position matchedFirst / last feed position: 6:32 a.m. EST / 7:36 a.m. EST; not actual start or end times.
06:34– 07:38
Trip 35024040Vehicle position matchedFirst / last feed position: 6:12 a.m. EST / 7:47 a.m. EST; not actual start or end times.
06:45– 07:46
Trip 11003040Vehicle position matchedFirst / last feed position: 6:38 a.m. EST / 7:52 a.m. EST; not actual start or end times.

· Open all evidence for this day

路線 6: Greenboro ⇄ Rockcliffe

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

What does the evidence show?

The hours we have evidence for

What about time of day?

バスが続けて到着

この路線で最も遅い区間

この路線の近くの市の道路工事

この路線の運休

最近の運休便

What this route needs

予測が何度もずれたのは、どこで、いつですか。

すべての trip と日付を確認

利用者が知りたいこと

公表されている各時刻表から選んだ運行日

変更前

新しいダイヤ

変更後にサービスは改善しましたか?

予測は時刻表とどう比べられましたか?

Trips scheduled that day

Did the scheduled service run?

Scheduled trips with cancellation notices

Trips needing investigation

What does the evidence show?

The hours we have evidence for

What about time of day?

バスが続けて到着

この路線で最も遅い区間

この路線の近くの市の道路工事

この路線の運休

最近の運休便

What this route needs

予測が何度もずれたのは、どこで、いつですか。

すべての trip と日付を確認

利用者が知りたいこと

公表されている各時刻表から選んだ運行日

変更前

新しいダイヤ

変更後にサービスは改善しましたか?

予測は時刻表とどう比べられましたか?

Trips scheduled that day