← All agencies

Feed status · checked 2026-09-05

Hiroden Bus (広島電鉄バス)

Based on the official feed source on file

Service mode Bus

FDCBA

66.0 / 100

First scorecard for this agency

Catalogued in Hiroshima, Japan.

Covers 164 daysAccessibility gaps

Hiroshima Electric Railway's bus network in and around Hiroshima City. The feed also carries Fuchu Town's contracted service. The portal publishes the current-data archive alongside a future-data archive for a pending timetable revision; this record scores the current data.

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.

Checked for changes 1 hours ago; last changed 1 hours ago.

Measured 4 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: high.

All four score categories were measured this run.
Realtime was sampled in one bounded window of 9 snapshots.
The feed was downloaded from the official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Add the required column named in the finding to the flagged file.Likely your export tool

A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.

⏱ Often an export setting; ask your vendor if it recurs.worth about +12 points in its category

Fix 02

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team

2421 of 2421 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 03

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

9707 of 9707 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence: A file is missing a column that GTFS requires.
Next action: Add the required column named in the finding to the flagged file.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.

Copy handoff text

Agency: Hiroden Bus (広島電鉄バス)
Finding: missing_required_column
Feed evidence: A file is missing a column that GTFS requires.
Why it matters: Apps may reject the whole file, so riders could lose the affected routes or stops.
Requested change: Add the required column named in the finding to the flagged file.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/hiroden-bus/?finding=missing_required_column#finding-handoff

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

Add the required column named in the finding to the flagged file. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility: The feed's last published service date is in 164 days.
Published accessibility data: Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information: Fare information is published using GTFS Fares v1.
Realtime information: One or more realtime feeds were reachable; live-arrival coverage is not known.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Hi,

Our GTFS feed (Hiroden Bus (広島電鉄バス)) scored D (66.0 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Add the required column named in the finding to the flagged file.
   What: A file is missing a column that GTFS requires.
   Finding code: missing_required_column
   Guide: https://gtfsscorecard.org/fix/missing_required_column/

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 2421 of 2421 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 9707 of 9707 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

Full scorecard: https://gtfsscorecard.org/agency/hiroden-bus/

Score by category

Correctness45.8 / 100

The MobilityData validator flagged 11 kinds of issue across 268405 instances (3 error, 268184 warning, 218 informational).

Freshness100.0 / 100

Service data covers the next 164 days.

Rider experience39.9 / 100

0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

FaresLegacy fares

Fares are applied to trips.

Realtime quality100.0 / 100

Sampled 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 2421 stops.

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

4-1 (green)
34-1 (green)
6-1・6-3 (green)
11-8 (green)
4-3 (green)
1-5 (green)
54-1 (green)
10 (green)
40-11 (green)
8 (green)
2-1 (green)
5-1 (green)
3 (green)
21 (green)
63-2 (green)
61-2 (green)
五日市駅南口発着 (green)
32-2 (green)
70-3 (green)
3-2 (green)
2-6 (green)
40 (green)
7 (green)
74-7 (green)
4 (green)
広島空港アクセス路線 (green)
34-C (green)
2-1 (green)
高速：クレアライン (green)
1-3 (green)
61 (green)
54 (green)
34-N (green)
イオンモールシャトル (green)
40-12 (green)
64 (green)
63-1 (green)
65-3 (green)
55-4 (green)
2-2 (green)
322 (green)
54-2 (green)
11-6 (green)
2 (green)
63 (green)
302 (green)
41-1 (green)
40-12 (green)
31 (green)
1-1 (green)
15-7 (green)
4-2 (green)
1-3 (green)
ジアウトレット広島線 (green)
6-1・6-2 (green)
21-4 (green)
41-2 (green)
65 (green)
12-1 (green)
6-1 (green)
1 (green)
62-1 (green)
28 (green)
6 (green)
15 (green)
73-9 (green)
60-3 (green)
7-3 (green)
41-3 (green)
53 (green)
2 (green)
15-6 (green)
1-4 (green)
64-1 (green)
つばきバス（左回り） (green)
62-3 (green)
72-4 (green)
広島空港アクセス宮島路線 (green)
32-1 (green)
74K (green)
41 (green)
28-1 (green)
2-7 (green)
3-1 (green)
5 (green)
101 (green)
55-3 (green)
11-4 (green)
301 (green)
61-4 (green)
55-2 (green)
103 (green)
12-3 (green)
102 (green)
62-2 (green)
52-2 (green)
5-2 (green)
3 (green)
21-1 (green)
4-1 (green)
16-6 (green)
101 (green)
55 (green)
6・6-3 (green)
1-9 (green)
62 (green)
3 (green)
6-3 (green)
3-4 (green)
12-4 (green)
54-3 (green)
4 (green)
8-1 (green)
3 (green)
55-5 (green)
7-1 (green)
40-5 (green)
4 (green)
16-7 (green)
34-2 (green)
2-2 (green)
63-4 (green)
331・332 (green)
55-6 (green)
70H (green)
54-4 (green)
2-5 (green)
3-1 (green)
201 (green)
34 (green)
12 (green)
53-7 (green)
3-3 (green)
16 (green)
6・6-2 (green)
13 (green)
28-2 (green)
52-1 (green)
11-N (green)
60 (green)
つばきバス（右回り） (green)
21-2 (green)
1-1 (green)
73K (green)
3-2 (green)
63-3 (green)
28-7 (green)
74 (green)
6-2 (green)
11 (green)
11-7 (green)
70-4 (green)
321 (green)
202 (green)
1 (green)
55-1 (green)
61-1 (green)
61-9 (green)
72K (green)
31-1 (green)
12 (green)
4-1 (green)
75K (green)
40 (green)
52 (green)

Routes in Hiroden Bus (広島電鉄バス)'s feed
Route	Type	Line color
4-1 4号線	Bus	green
34-1 吉浦天応線	Bus	green
6-1・6-3 6号線	Bus	green
11-8 広仁方線/郷原黒瀬線	Bus	green
4-3 4号線	Bus	green
1-5 五日市駅北口発着	Bus	green
54-1 西広島バイパス線	Bus	green
10 10号線	Bus	green
40-11 広島～熊野方面	Bus	green
8 8号線	Bus	green
2-1 五日市駅北口発着	Bus	green
5-1 5号線	Bus	green
3 矢野～熊野・焼山方面	Bus	green
21 焼山熊野苗代線	Bus	green
63-2 西風新都線	Bus	green
61-2 五月が丘団地・免許センター・ジアウトレット広島・そらの線	Bus	green
五日市駅南口発着	Bus	green
32-2 長の木長迫線	Bus	green
70-3 あさひが丘線	Bus	green
3-2 宮原線	Bus	green
2-6 2号線	Bus	green
40 矢野～熊野・焼山方面	Bus	green
7 7号線	Bus	green
74-7 三段峡線	Bus	green
4 五日市駅南口発着	Bus	green
広島空港アクセス路線	Bus	green
34-C 吉浦天応線	Bus	green
2-1 2号線	Bus	green
高速：クレアライン	Bus	green
1-3 五日市駅北口発着	Bus	green
61 五月が丘団地・免許センター・ジアウトレット広島・そらの線	Bus	green
54 西広島バイパス線	Bus	green
34-N 吉浦天応線	Bus	green
イオンモールシャトル	Bus	green
40-12 広島～熊野方面	Bus	green
64 くすの木台線	Bus	green
63-1 西風新都線	Bus	green
65-3 くすのき台線	Bus	green
55-4 西広島バイパス線	Bus	green
2-2 五日市駅北口発着	Bus	green
322 広島駅～大学病院前	Bus	green
54-2 西広島バイパス線	Bus	green
11-6 広仁方線/郷原黒瀬線	Bus	green
2 2号線	Bus	green
63 西風新都線	Bus	green
302 まちのわループ	Bus	green
41-1 広島～熊野・焼山方面	Bus	green
40-12 矢野～熊野方面	Bus	green
31 辰川線	Bus	green
1-1 呉倉橋島線	Bus	green
15-7 阿品駅発着（阿品台線）	Bus	green
4-2 4号線	Bus	green
1-3 呉倉橋島線	Bus	green
ジアウトレット広島線	Bus	green
6-1・6-2 6号線	Bus	green
21-4 焼山熊野苗代線	Bus	green
41-2 広島～熊野・焼山方面	Bus	green
65 くすのき台線	Bus	green
12-1 12号線	Bus	green
6-1 6号線	Bus	green
1 五日市駅北口発着	Bus	green
62-1 西風新都線	Bus	green
28 アルパーク・新井口駅発着	Bus	green
6 6号線	Bus	green
15 阿品駅発着（阿品台線）	Bus	green
73-9 豊平・琴谷線/今吉田線	Bus	green
60-3 五月が丘団地・免許センター・ジアウトレット広島・そらの線	Bus	green
7-3 7号線	Bus	green
41-3 広島～熊野・焼山方面	Bus	green
53 西広島バイパス線	Bus	green
2 五日市駅北口発着	Bus	green
15-6 阿品駅発着（阿品台線）	Bus	green
1-4 五日市駅北口発着	Bus	green
64-1 くすの木台線	Bus	green
つばきバス（左回り）	Bus	green
62-3 西風新都線	Bus	green
72-4 上根・吉田線	Bus	green
広島空港アクセス宮島路線	Bus	green
32-1 長の木長迫線	Bus	green
74K 三段峡線	Bus	green
41 広島～熊野・焼山方面	Bus	green
28-1 アルパーク・新井口駅発着	Bus	green
2-7 2号線	Bus	green
3-1 宮原線	Bus	green
5 5号線	Bus	green
101 エキまちループ（左回り）	Bus	green
55-3 西広島バイパス線	Bus	green
11-4 広仁方線/郷原黒瀬線	Bus	green
301 まちのわループ	Bus	green
61-4 五月が丘団地・免許センター・ジアウトレット広島・そらの線	Bus	green
55-2 西広島バイパス線	Bus	green
103 エキまちループ（市役所行き）	Bus	green
12-3 12号線	Bus	green
102 エキまちループ（右回り）	Bus	green
62-2 西風新都線	Bus	green
52-2 西広島バイパス線	Bus	green
5-2 5号線	Bus	green
3 五日市駅南口発着	Bus	green
21-1 焼山熊野苗代線	Bus	green
4-1 宮原線	Bus	green
16-6 阿品駅発着（阿品台線）	Bus	green
101 エキまちループ	Bus	green
55 西広島バイパス線	Bus	green
6・6-3 6号線	Bus	green
1-9 五日市駅北口発着	Bus	green
62 西風新都線	Bus	green
3 3号線	Bus	green
6-3 6号線	Bus	green
3-4 矢野～熊野・焼山方面	Bus	green
12-4 12号線	Bus	green
54-3 西広島バイパス線	Bus	green
4 4号線	Bus	green
8-1 8号線	Bus	green
3 宮原線	Bus	green
55-5 西広島バイパス線	Bus	green
7-1 7号線	Bus	green
40-5 広島～熊野方面	Bus	green
4 宮原線	Bus	green
16-7 阿品駅発着（阿品台線）	Bus	green
34-2 吉浦天応線	Bus	green
2-2 2号線	Bus	green
63-4 西風新都線	Bus	green
331・332 広島駅～旭町～広島駅	Bus	green
55-6 西広島バイパス線	Bus	green
70H あさひが丘線	Bus	green
54-4 西広島バイパス線	Bus	green
2-5 2号線	Bus	green
3-1 矢野～熊野・焼山方面	Bus	green
201 西風みなとライン	Bus	green
34 吉浦天応線	Bus	green
12 12号線	Bus	green
53-7 西広島バイパス線	Bus	green
3-3 矢野～熊野・焼山方面	Bus	green
16 阿品駅発着（阿品台線）	Bus	green
6・6-2 6号線	Bus	green
13 宮内串戸駅・廿日市市役所前駅発着（佐伯線）	Bus	green
28-2 アルパーク・新井口駅発着	Bus	green
52-1 西広島バイパス線	Bus	green
11-N 広仁方線/郷原黒瀬線	Bus	green
60 五月が丘団地・免許センター・ジアウトレット広島・そらの線	Bus	green
つばきバス（右回り）	Bus	green
21-2 焼山熊野苗代線	Bus	green
1-1 五日市駅北口発着	Bus	green
73K 豊平・琴谷線/今吉田線	Bus	green
3-2 矢野～熊野・焼山方面	Bus	green
63-3 西風新都線	Bus	green
28-7 アルパーク・新井口駅発着	Bus	green
74 三段峡線	Bus	green
6-2 6号線	Bus	green
11 広仁方線/郷原黒瀬線	Bus	green
11-7 広仁方線/郷原黒瀬線	Bus	green
70-4 あさひが丘線	Bus	green
321 大学病院前～広島駅	Bus	green
202 西風みなとライン	Bus	green
Jリーグシャトル	Bus	green (no shape in feed)
1 呉倉橋島線	Bus	green
55-1 西広島バイパス線	Bus	green
61-1 五月が丘団地・免許センター・ジアウトレット広島・そらの線	Bus	green
61-9 五月が丘団地・免許センター・ジアウトレット広島・そらの線	Bus	green
72K 上根・吉田線	Bus	green
31-1 辰川線	Bus	green
12 宮内串戸駅・廿日市市役所前駅発着（四季が丘線）	Bus	green
4-1 五日市駅南口発着	Bus	green
75K 三段峡線	Bus	green
40 広島～熊野方面	Bus	green
52 西広島バイパス線	Bus	green

List every stop

広島バスセンター
広島バスセンター
広島バスセンター
広島バスセンター
広島バスセンター
広島バスセンター
広島バスセンター
広島バスセンター
広島バスセンター
玖波分れ
玖波分れ
河津
河津
中山
中山
浜本工芸前
浜本工芸前
佐伯中学校前
佐伯中学校前
アルパーク
アルパーク
佐伯高校前
佐伯高校前
津田神社
津田神社
十王堂
十王堂
さいき文化センター
佐伯支所
佐伯支所
津田
旭園
旭園
上飯室
上飯室
関の内
関の内
下烏帽子
下烏帽子
上烏帽子
上烏帽子
杉の迫
杉の迫
鈴張市
鈴張市
鈴張
鈴張
鈴張神社
鈴張神社
下西谷
下西谷
中西谷
中西谷
大正橋
大正橋
藤河内
藤河内
鈴張落合
鈴張落合
上西谷
上西谷
柏尾
柏尾
久保角橋
久保角橋
ゆりかご荘前
ゆりかご荘前
大仙原
大仙原
吉木口
吉木口
橋詰橋
橋詰橋
瀬山
瀬山
龍頭山登山口
龍頭山登山口
都志見
都志見
龍頭神社前
龍頭神社前
都志見原
都志見原
掛札
掛札
細河内
細河内
細河内下
細河内下
都谷田の原
都谷田の原
戸谷
戸谷
戸谷上
戸谷上
向原口
向原口
庄原口
庄原口
豊平支所
豊平支所
琴谷
琴谷
琴谷車庫
海老山公園前
海老山公園前
豊平学園下
上大町
上大町
安小峠
安小峠
下相田
下相田
相田
相田
安田女子大入口
安田女子大入口
日浦口
日浦口
安中央
安中央
安小学校
安小学校
上安
上安
高取
高取
長楽寺
長楽寺
伴安
伴安
下向
下向
下向
下向
下伴
下伴
広陵学園入口
広陵学園入口
松宗
松宗
三菱団地入口
三菱団地入口
三菱団地入口
三菱団地入口
広域公園前駅
広域公園前駅
広域公園前駅
中大塚
中大塚
大塚駅
大塚駅
佐伯区役所前
佐伯区役所前
三菱団地下
三菱団地下
三菱団地中
三菱団地中
三菱団地上
三菱団地上
鳴る谷
鳴る谷
中東口
中東口
下向上
下向上
細坂上
細坂上
新畑
新畑
下大下
下大下
大下
大下
久地境原
久地境原
幸の神
幸の神
中田口
中田口
久地魚切
久地魚切
くすの木台下
くすの木台下
くすの木台中
くすの木台中
くすの木台
くすの木台
海老園一丁目
海老園一丁目
下萩原
下萩原
中萩原
中萩原
上萩原
上萩原
荒谷
荒谷
安佐動物公園
安佐動物公園
後山上
後山上
あさひが丘下
あさひが丘下
あさひが丘下
あさひが丘下
あさひが丘中
あさひが丘中
あさひが丘上
あさひが丘上
県営あさひが丘住宅
県営あさひが丘住宅
あさひが丘１番
あさひが丘１番
あさひが丘２番
あさひが丘２番
あさひが丘３番
あさひが丘３番
楽々園
楽々園
五月が丘公園前
五月が丘公園前
五月が丘一丁目中
五月が丘三丁目中
広島高等技術専門校前
広島高等技術専門校前
美鈴モール前
美鈴モール前
美鈴モール前
高井上
高井上
美鈴が丘東三丁目
美鈴が丘東三丁目
山田団地下
山田団地下
山田団地
山田団地
山田団地車庫前
山田団地車庫前
波出石
波出石
坪井
坪井
ジアウトレット広島
ジアウトレット広島
そらの北
そらの北
宮内河本
宮内河本
地御前三丁目
and 2171 more (see the full list on the map or in the GeoJSON)

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

16 findings, ordered by severity.

Show every finding

Error3 instances
A file is missing a column that GTFS requires.
Apps may reject the whole file, so riders could lose the affected routes or stops.
Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)
Finding code: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning257948 instances
Some rows in stop_times.txt leave the timepoint column blank.
That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)
Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning9868 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning9707 instances
9707 of 9707 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning8109 instances
8109 of 9707 trips have no headsign, the text that tells riders where the bus is going.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Warning2421 instances
2421 of 2421 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning360 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning5 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Info205 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info11 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info2 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Conformance mark Not yet

Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet: 1 validator error to resolve.
Current Met: Service data covers the next 164 days.
Accessible Not yet: States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

1 of 2420 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Realtime reliability

The realtime feed responded on 100.0% of 7 checks over the last 1 day, with 21s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Clears the Google and Apple Maps four-week coverage bar. This feed has 164 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 3 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.

Correctness 46 / 100: GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
Freshness 100 / 100: GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
Rider experience 40 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 100 / 100: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

[![Hiroden Bus (広島電鉄バス) GTFS data quality grade: D](https://gtfsscorecard.org/data/artifacts/hiroden-bus/badge.svg)](https://gtfsscorecard.org/agency/hiroden-bus/)

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/hiroden-bus/2026-09-05.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-09-05. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

GTFS Scorecard. (2026). Hiroden Bus (広島電鉄バス) GTFS feed-quality record, dated 2026-09-05 (grade D (66.0/100), rubric v1.3, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 3b9433fe48e3…). https://gtfsscorecard.org/data/artifacts/hiroden-bus/2026-09-05.json

@misc{gtfsscorecard-hiroden-bus-2026-09-05,
  title        = {Hiroden Bus (広島電鉄バス) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/hiroden-bus/2026-09-05.json}},
  note         = {Checked 2026-09-05; rubric v1.3; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (66.0/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.