Feed status · checked 2026-07-19
Ryujin Bus (龍神自動車)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Wakayama, 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.2, validator 8.0.1.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
449 of 449 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
76 of 76 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
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.
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.
⏱ A planned ID change, not a quick text cleanup.worth about +8 points in its category
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.
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.
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.
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 255 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
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
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 6 kinds of issue across 4437 instances (0 error, 4429 warning, 8 informational).
Service data covers the next 255 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.
1 accessibility depth signal
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (市内線 外回り, 市内線 内回り, 龍神線).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 80 熊野本宮線 (yellow)
- 81 熊野本宮線 (yellow)
- 84 熊野本宮線 (yellow)
- 85 熊野本宮線 (yellow)
- 聖地巡礼バス (green)
- 市内線 外回り (teal)
- 市内線 内回り (orange)
- 龍神線 (yellow)
- みなべ線 (brown)
- みなべ梅林臨時バス (green)
| Route | Type | Line color |
|---|---|---|
| 80 熊野本宮線 | Bus | yellow |
| 81 熊野本宮線 | Bus | yellow |
| 84 熊野本宮線 | Bus | yellow |
| 85 熊野本宮線 | Bus | yellow |
| 聖地巡礼バス | Bus | green |
| 市内線 外回り | Bus | teal |
| 市内線 内回り | Bus | orange |
| 龍神線 | Bus | yellow |
| みなべ線 | Bus | brown |
| みなべ梅林臨時バス | Bus | green |
This feed has 449 stops.
List every stop
- 紀南病院
- 東部小学校
- 東部小学校
- 南新万
- 南新万
- 南新万１番地
- 南新万１番地
- 喜久住
- 喜久住
- あけぼの
- あけぼの
- つぶり坂
- つぶり坂
- 鬪雞神社
- 鬪雞神社
- 湊
- 湊
- 紀伊田辺駅
- 紀伊田辺駅
- 鶴ヶ丘
- 鶴ヶ丘
- 工業高校前
- 工業高校前
- 橋谷
- 橋谷
- 紀伊新庄駅
- 紀伊新庄駅
- 名喜里
- 名喜里
- 田鶴口
- 田鶴口
- 技術専門校前
- 技術専門校前
- 南紀の台下
- 南紀の台下
- 峠
- 峠
- 鳶野
- 鳶野
- 朝来
- 朝来
- 生馬口
- 生馬口
- 熊野高校前
- 熊野高校前
- 三宝寺
- 三宝寺
- 紀伊岩田
- 紀伊岩田
- 上岩田
- 上岩田
- 稲葉根王子
- 稲葉根王子
- 根皆田
- 根皆田
- 市ノ瀬診療所前
- 市ノ瀬診療所前
- 紀伊市ノ瀬
- 紀伊市ノ瀬
- 紀伊一乗寺
- 紀伊一乗寺
- 登尾
- 登尾
- 下鮎川
- 下鮎川
- 下附
- 下附
- 鮎川診療所
- 鮎川診療所
- 鮎川新橋
- 鮎川新橋
- 宇立
- 宇立
- 向越
- 向越
- 鮎川温泉
- 鮎川温泉
- 蕨尾橋
- 蕨尾橋
- 北郡
- 北郡
- 清姫
- 清姫
- 真砂
- 真砂
- 滝尻
- 滝尻
- 戸土
- 戸土
- 鍛冶屋川口
- 鍛冶屋川口
- 下芝下
- 下芝下
- 下芝
- 下芝
- 古道ヶ丘
- 古道ヶ丘
- 中芝
- 中芝
- 林木育種場前
- 林木育種場前
- 中辺路行政局前
- 中辺路行政局前
- 栗栖川
- 栗栖川
- 朝来平口
- 朝来平口
- 紀伊中川
- 紀伊中川
- 古道の里
- 古道の里
- 野々尻
- 野々尻
- 皆ノ川口
- 皆ノ川口
- 紀伊大川
- 紀伊大川
- 三善橋
- 三善橋
- 福定
- 福定
- 氏山橋
- 氏山橋
- 牛馬童子口
- 牛馬童子口
- 柿平
- 柿平
- 古道歩きの里ちかつゆ
- 古道歩きの里ちかつゆ
- なかへち美術館前
- 近露王子
- 近露王子
- 観音寺前
- 観音寺前
- 宮の上
- 宮の上
- 国道笠松
- 国道笠松
- 野中一方杉
- 野中一方杉
- 小広王子口
- 小広王子口
- 小広峠
- 小広峠
- 道湯川橋
- 道湯川橋
- 尾和田橋
- 尾和田橋
- 熊野大瀬
- 熊野大瀬
- 武住
- 武住
- 野竹
- 野竹
- 上地
- 上地
- 皆地
- 皆地
- 小々森
- 小々森
- 細井
- 細井
- 桧葉
- 桧葉
- 廻り
- 廻り
- 串峠口
- 串峠口
- 渡瀬
- 渡瀬
- 将監の峯
- 将監の峯
- 下湯川
- 下湯川
- 下湯の峰
- 下湯の峰
- 湯の峰温泉
- 湯の峰温泉
- 渡瀬温泉
- 渡瀬温泉
- 川湯温泉
- 川湯温泉
- かめや前
- かめや前
- ふじや前
- ふじや前
- 本宮小学校前
- 本宮小学校前
- 成石
- 成石
- 請川
- 請川
- 請川
- 請川
- 請川柿
- 請川柿
- 大日越登り口
- 大日越登り口
- 大斎原前
- 大斎原前
- 本宮行政局前
- 本宮行政局前
- 本宮大社前
- 祓戸団地前
- 祓戸団地前
- 下向橋
- 下向橋
- 大居口
- 大居口
- 平岩口
- 平岩口
- 道の駅奥熊野
- 道の駅奥熊野
- 竹の本
- 竹の本
- 伏拝口
- 伏拝口
- 発心門口
- 発心門口
- 発心門王子
- 西
- 西
- 季楽里龍神
- 季楽里龍神
- 大熊
- 大熊
- 護摩壇山
- 龍神温泉（国道）
- 龍神温泉（国道）
- 龍神温泉（温泉街）
- 龍神温泉（温泉街）
- 田辺市役所前
- 田辺市役所前
- 田辺市役所南
- 田辺市役所南
- 海蔵寺町
- 海蔵寺町
- 市民総合センター
- 市民総合センター
- 秋津口
- 秋津口
- 高雄二丁目
- 高雄二丁目
- 高雄中学校
- 高雄中学校
- 小泉
- 小泉
- 青木
- 青木
- 青木橋
- and 199 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 73.2 | first check |
| 2026-07-19 | 73.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning4158 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.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning449 instances
449 of 449 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning236 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.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning76 instances
76 of 76 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning34 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.)
Validator rule: mixed_case_recommended_field · 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.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info6 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.)
Validator rule: platform_without_parent_station · 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.)
Validator rule: 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).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: 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
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 255 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 255 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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 73 / 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 Not yet published
- 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/ryujin-bus/2026-07-19.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-07-19. 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.