Feed status · checked 2026-09-05
Tomotetsu Bus (鞆鉄道)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Hiroshima, Japan.
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.
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
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
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
581 of 581 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
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
3085 of 3085 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
- Duplicate key (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Feed evidence
- 581 of 581 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- 3085 of 3085 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
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.
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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 94 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
- Live-arrival data covered 100% of scheduled trips in the sampled window.
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.
Score by category
The MobilityData validator flagged 13 kinds of issue across 3694 instances (3 error, 626 warning, 3065 informational).
Service data covers the next 94 days.
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.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; vehicle position plausibility was not measurable; predictions ran a median of 137s behind schedule.
Routes and stops
This feed has no route shapes, so the map shows its stops only.
This feed has 581 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.
| Route | Type | Line color |
|---|---|---|
| まわローズ(青ルート） | Bus | green (no shape in feed) |
| まわローズ(青ルート） | Bus | green (no shape in feed) |
| 三原駅・如水館線(深線) | Bus | green (no shape in feed) |
| 三原駅・如水館線(深線) | Bus | green (no shape in feed) |
| 鞆線 | Bus | green (no shape in feed) |
| 三原福地線 | Bus | green (no shape in feed) |
| 尾道線 | Bus | green (no shape in feed) |
| 新川線 | Bus | green (no shape in feed) |
| 沼南線 | Bus | green (no shape in feed) |
| 早戸線 | Bus | green (no shape in feed) |
| 明王台線 | Bus | green (no shape in feed) |
| 市内線 | Bus | green (no shape in feed) |
| 尾道工業団地線 | Bus | green (no shape in feed) |
| 如水館線 | Bus | green (no shape in feed) |
| みろくの里・神勝寺 直行便 | Bus | green (no shape in feed) |
List every stop
- 福山駅前
- 福山駅前
- 福山駅前
- 福山駅前
- 福山駅前
- 伏見町
- 藤江
- 藤江
- 藤江交流館下
- 藤江交流館下
- 古野上町
- 古野上町
- 別所
- 別所
- 阿伏兎隧道
- 阿伏兎隧道
- 本庄
- 本庄
- 今宮
- 今宮
- 防地口
- 防地口
- 今免
- 今免
- 町
- 町
- 松永
- 松永
- 松永駅前
- 松永駅前
- 松永駅南口
- 西警察署入口
- 西警察署入口
- 松永ｽﾎﾟｰﾂｾﾝﾀｰ前
- 松永ｽﾎﾟｰﾂｾﾝﾀｰ前
- 松永中学校前
- 松永中学校前
- 松永農協会館前
- 松永農協会館前
- 丸山口
- 丸山口
- 御門町
- 御門町
- 満越
- 道輝会前
- 道輝会前
- 入船町
- 港口
- 港口
- 南小学校前
- 南本通り
- 南本通り
- 南町
- 南松永
- 南松永
- 三成
- 三成
- 三成口
- 三成口
- 三成下組
- 三成下組
- 美之郷温泉口
- 美之郷温泉口
- 水呑
- 水呑
- 水呑大橋
- 水呑大橋
- 水呑高浦
- 水呑高浦
- 水呑小学校入口
- 水呑小学校入口
- 水呑薬師
- 水呑薬師
- 御船町
- 御船町
- 神島橋西詰
- 神島橋西詰
- 明王台小学校前
- 明王台小学校前
- 明王台センター
- 明王台センター
- 明王台中
- 明王台中
- 明王台西
- 明王台西
- 妙見
- 妙見
- 岩川
- 岩川
- 三吉町南
- みろくの里
- みろくの里入口
- みろくの里入口
- みろくの里西
- みろくの里西
- みろくの里東口
- みろくの里東口
- 睦橋
- 睦橋
- 村境
- 村境
- 室浜口
- 室浜口
- 赤坂駅前
- 赤坂駅前
- 木綿橋
- 植松
- 植松
- 矢操
- 矢操
- 柳井
- 柳井
- 柳津
- 柳津
- 柳津東
- 柳津東
- 山庄口
- 山庄口
- 山本病院前
- 山本病院前
- 遊園地前
- 遊園地前
- 長和島南
- 長和島南
- 横引
- 横引
- 四ツ角
- 四ツ角
- 四ツ堂
- 四ツ堂
- 阿藻珍味前
- 阿藻珍味前
- リーデンローズ入口
- リーデンローズ入口
- リム・ふくやま前
- 六本堂
- 六本堂
- 六本堂下
- 六本堂下
- 渡場通り
- 渡場通り
- 青木
- 青木
- 赤石
- 赤石
- 阿伏兎観音
- 内海・横田漁港前
- 一中前
- 一中前
- 糸崎駅前
- 糸崎駅前
- 糸碕神社東
- 糸碕神社東
- 糸碕神社前
- 糸碕神社前
- 内畠
- 内畠
- 浦崎中学校前
- 浦崎中学校前
- 浦崎農協前
- 浦崎農協前
- 運動公園
- 運動公園
- 大橋
- 大橋
- 尾道工業団地
- 上福地
- 観音寺下
- 観音寺下
- 木原小学校下
- 木原小学校下
- 江の浦
- 江の浦
- 寿町
- 寿町
- 海老東
- 海老東
- 下木原
- 下木原
- 園芸センター入口
- 園芸センター入口
- 城町
- 城町
- 新古浜
- 新古浜
- 尾道バイパス西詰
- 尾道バイパス西詰
- 大浦
- 大浦
- 登山口
- 大越峠
- 大越峠
- 大越浜
- 大越浜
- 日赤入口
- 日赤入口
- 日赤前
- 日赤前
- 能登原明神
- 能登原明神
- 大谷団地前
- 大谷団地前
- 太田橋
- 太田橋
- 福地
- 福地
- 福地浜
- 福地浜
- 大富
- 大富
- 芙美子像前
- 芙美子像前
- 糸崎3丁目
- 糸崎3丁目
- 港口
- 港口
- 三原駅
- 三原駅
- 三原駅
- 三原駅
- 三原駅
- 三原古浜橋
- 三原古浜橋
- 尾崎
- 尾崎
- 尾道駅前
- 尾道造船前
- 尾道造船前
- 温泉口
- 温泉口
- 河口大橋
- 河口大橋
- 神島橋
- 神島橋
- ジーベック前
- ジーベック前
- 片山
- 片山
- 葛城
- 葛城
- 金崎
- 金崎
- 上志田原
- 上志田原
- 神村町一区
- 神村町一区
- 神村町二区
- 神村町二区
- 神村町三区
- 神村町三区
- and 331 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
Duplicate key (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: duplicate_key · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3085 instances
3085 of 3085 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)
- Warning581 instances
581 of 581 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)
- Warning424 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning89 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)
- Warning75 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning22 instances
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning13 instances
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)
- Warning2 instances
Two or more routes share the same name.
Riders can't tell the routes apart in apps.
Fix: Give each route a distinct short or long name. (One field per route.)
Finding code: duplicate_route_name · 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)
- Info3014 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info26 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info18 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info4 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)
- Info3 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)
- 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 94 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.
- 13 of 581 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 54s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran a median 137s late versus the schedule, and stayed within 313s nine times in ten. They were on time (about a minute early to five late) 76.2% of the time.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 94 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 40 / 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 52 / 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.
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/tomotetsu-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.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.