Feed status · checked 2026-09-05
Kan-etsu Transportation (関越交通)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Gunma, 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.
Checked for changes 1 hours ago; last changed 1 hours ago.
Measured 3 of 4 score categories from the official feed URL on file.
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 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
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
2213 of 2213 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
2953 of 2953 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
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
- 2213 of 2213 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
- 2953 of 2953 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
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- 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.
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 360 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 4 kinds of issue across 194474 instances (0 error, 194429 warning, 45 informational).
Service data covers the next 360 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.
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.
This feed has 2213 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.
- 21 ぐるりん かみつけの里線 (orange)
- 22 ぐるりん かみつけの里線 (orange)
- 19 ぐるりん こうづけ国分寺線 (orange)
- 20 ぐるりん こうづけ国分寺線 (orange)
- アップル号 (orange)
- 73 マイバス北循環線 (orange)
- 72 マイバス南循環線 (orange)
- 中山本宿線 (orange)
- 中野循環線 (orange)
- 伊香保タウンバス３号線 (orange)
- 佐山線 (orange)
- 55A 前橋公園線 (orange)
- 55B 前橋公園線 (orange)
- 55C 前橋公園線 (orange)
- 55E 前橋公園線 (orange)
- 26A 前橋土屋文明線 (orange)
- 26B 前橋土屋文明線 (orange)
- 22A 前橋渋川線 (orange)
- 22B 前橋渋川線 (orange)
- 22C 前橋渋川線 (orange)
- 22E 前橋渋川線 (orange)
- 22F 前橋渋川線 (orange)
- 22G 前橋渋川線 (orange)
- 22H 前橋渋川線 (orange)
- 22J 前橋渋川線 (orange)
- 22K 前橋渋川線 (orange)
- 22L 前橋渋川線 (orange)
- 22M 前橋渋川線 (orange)
- 48A 前橋赤城山線 (orange)
- 48B 前橋赤城山線 (orange)
- 48C 前橋赤城山線 (orange)
- 25A 前橋金古王塚台線 (orange)
- 25B 前橋金古王塚台線 (orange)
- 勝保沢線 (orange)
- 南柏木線 (orange)
- 南郷線 (orange)
- 原美術館ＡＲＣ線 (orange)
- 四万温泉線 (orange)
- 5 ぐるりん 大八木線 (orange)
- 6 ぐるりん 大八木線 (orange)
- 大戸線 (orange)
- 46 大渡町線 (orange)
- 天狗の湯循環線 (orange)
- 50A 富士見温泉線 (orange)
- 50B 富士見温泉線 (orange)
- 50C 富士見温泉線 (orange)
- 50E 富士見温泉線 (orange)
- 50F 富士見温泉線 (orange)
- 49 富士見赤城山線 (orange)
- 岩本線 (orange)
- 44A 川原町線（緑が丘経由） (orange)
- 44B 川原町線（緑が丘経由） (orange)
- 45A 川原町線（附属小経由） (orange)
- 45B 川原町線（附属小経由） (orange)
- 川場循環線 (orange)
- 桜の木線 (orange)
- 水上線 (orange)
- 永井線 (orange)
- 沢渡線 (orange)
- 渋川伊香保温泉線 (orange)
- 渋川医療センター線 (orange)
- 渋川温泉りんご団地線 (orange)
- 湯中子線 (orange)
- 湯元温泉線 (orange)
- 猿ヶ京線 (orange)
- 神田原・祖母島線 (orange)
- 赤谷循環線 (orange)
- 迦葉山線 (orange)
- 鎌田線 (orange)
- 青葉台・りんご団地線 (orange)
- 高崎渋川線 (orange)
| Route | Type | Line color |
|---|---|---|
| 21 ぐるりん かみつけの里線 | Bus | orange |
| 22 ぐるりん かみつけの里線 | Bus | orange |
| 19 ぐるりん こうづけ国分寺線 | Bus | orange |
| 20 ぐるりん こうづけ国分寺線 | Bus | orange |
| アップル号 | Bus | orange |
| 73 マイバス北循環線 | Bus | orange |
| 72 マイバス南循環線 | Bus | orange |
| 中山本宿線 | Bus | orange |
| 中野循環線 | Bus | orange |
| 伊香保タウンバス３号線 | Bus | orange |
| 佐山線 | Bus | orange |
| 55A 前橋公園線 | Bus | orange |
| 55B 前橋公園線 | Bus | orange |
| 55C 前橋公園線 | Bus | orange |
| 55E 前橋公園線 | Bus | orange |
| 26A 前橋土屋文明線 | Bus | orange |
| 26B 前橋土屋文明線 | Bus | orange |
| 22A 前橋渋川線 | Bus | orange |
| 22B 前橋渋川線 | Bus | orange |
| 22C 前橋渋川線 | Bus | orange |
| 22E 前橋渋川線 | Bus | orange |
| 22F 前橋渋川線 | Bus | orange |
| 22G 前橋渋川線 | Bus | orange |
| 22H 前橋渋川線 | Bus | orange |
| 22J 前橋渋川線 | Bus | orange |
| 22K 前橋渋川線 | Bus | orange |
| 22L 前橋渋川線 | Bus | orange |
| 22M 前橋渋川線 | Bus | orange |
| 48A 前橋赤城山線 | Bus | orange |
| 48B 前橋赤城山線 | Bus | orange |
| 48C 前橋赤城山線 | Bus | orange |
| 25A 前橋金古王塚台線 | Bus | orange |
| 25B 前橋金古王塚台線 | Bus | orange |
| 勝保沢線 | Bus | orange |
| 千本桜シャトルバス | Bus | orange (no shape in feed) |
| 南柏木線 | Bus | orange |
| 南郷線 | Bus | orange |
| 原美術館ＡＲＣ線 | Bus | orange |
| 四万温泉線 | Bus | orange |
| 5 ぐるりん 大八木線 | Bus | orange |
| 6 ぐるりん 大八木線 | Bus | orange |
| 大戸線 | Bus | orange |
| 46 大渡町線 | Bus | orange |
| 天狗の湯循環線 | Bus | orange |
| 50A 富士見温泉線 | Bus | orange |
| 50B 富士見温泉線 | Bus | orange |
| 50C 富士見温泉線 | Bus | orange |
| 50E 富士見温泉線 | Bus | orange |
| 50F 富士見温泉線 | Bus | orange |
| 49 富士見赤城山線 | Bus | orange |
| 岩本線 | Bus | orange |
| 44A 川原町線（緑が丘経由） | Bus | orange |
| 44B 川原町線（緑が丘経由） | Bus | orange |
| 45A 川原町線（附属小経由） | Bus | orange |
| 45B 川原町線（附属小経由） | Bus | orange |
| 川場循環線 | Bus | orange |
| 桜の木線 | Bus | orange |
| 水上線 | Bus | orange |
| 永井線 | Bus | orange |
| 沢渡線 | Bus | orange |
| 渋川伊香保温泉線 | Bus | orange |
| 渋川医療センター線 | Bus | orange |
| 渋川温泉りんご団地線 | Bus | orange |
| 湯中子線 | Bus | orange |
| 湯元温泉線 | Bus | orange |
| 猿ヶ京線 | Bus | orange |
| 神田原・祖母島線 | Bus | orange |
| 赤谷循環線 | Bus | orange |
| 迦葉山線 | Bus | orange |
| 鎌田線 | Bus | orange |
| 青葉台・りんご団地線 | Bus | orange |
| 高崎渋川線 | Bus | orange |
List every stop
- ミツバ前
- ミツバ前
- ＪＡ元総社入口
- ＪＡ元総社入口
- ＪＡ直売所前
- ＪＡ直売所前
- ＮＨＫ東
- ＮＨＫ東
- ＮＴＴ前
- ＮＴＴ前
- まえばしガレリア前
- あかぎ育成園入口
- あかぎ広場前
- あら町銀行前
- あら町銀行前
- イオンモール高崎
- イオンモール高崎
- カーリット前
- カーリット前
- かみつけの里博物館前
- かみつけの里博物館前
- カルチャーセンター前
- カルチャーセンター前
- グリーン牧場前
- グリーン牧場前
- けやきウォーク前橋
- さくらの広場入口
- さくらの広場入口
- サニータウン前
- サニータウン前
- スズラン前
- たくみの里
- ダム管理事務所入口
- ダム管理事務所入口
- たんばらセンターハウス
- たんばらラベンダーパーク
- パークタウン梅ヶ丘
- パークタウン梅ヶ丘
- フェリカ専門学校南
- ふれあい福祉センター
- ホスピタル入口
- 群馬パース病院入口
- みずき中入口
- みずき通り北
- みよし公園
- ゆびそ駅前
- ゆびそ駅前
- ゆびそ温泉
- ゆびそ温泉
- ゆびそ温泉街
- ゆびそ温泉街
- ゆびそ入口
- ゆびそ入口
- ロックハート城前
- ロックハート城前
- 阿久津
- 阿久津
- 阿久津口
- 阿久津口
- 阿久津北原
- 阿久津北原
- 旭ヶ丘
- 旭ヶ丘
- 旭ヶ丘下
- 旭ヶ丘下
- 芦間
- 芦間
- 綾戸橋
- 綾戸橋
- 粟沢
- 粟沢
- 粟沢橋
- 粟沢橋
- 伊熊
- 伊熊
- 伊香原
- 伊香原
- 伊香保カントリークラブ前
- 伊香保カントリークラブ前
- 伊香保バスターミナル
- 伊香保バスターミナル
- 伊香保温泉
- 伊香保榛名口
- 伊香保中学校入口
- 伊香保中学校入口
- 井戸尻
- 井戸尻
- 井出西
- 井出西
- 井出東
- 井出東
- 井堤神社入口
- 井堤神社入口
- 井土上
- 井土上
- 一の瀬
- 一の瀬
- 一畝田
- 一畝田
- 一中南
- 一杯清水
- 一杯清水
- 一本松
- 一本松
- 一里塚
- 一里塚
- 稲荷台
- 稲荷台
- 稲荷台南
- 稲荷台南
- 羽場
- 羽場
- 雨堤
- 雨堤
- 栄
- 栄
- 栄分校前
- 栄分校前
- 永井
- 永井口
- 永井口
- 永寿寺前
- 永寿寺前
- 越本
- 越本
- 猿ヶ京
- 塩の井
- 塩の井
- 塩尻
- 塩尻
- 押出
- 押出
- 横塚町
- 横塚町
- 岡谷
- 岡谷
- 岡谷下
- 岡谷下
- 岡谷上
- 岡谷上
- 沖門
- 沖門
- 屋形原
- 屋形原
- 恩田
- 恩田
- 温泉センター
- 温泉センター
- 下永井
- 下永井
- 下河原
- 下河原
- 下街道
- 下街道
- 下久屋
- 下久屋
- 下久屋原
- 下久屋原
- 下久屋上
- 下久屋上
- 下郷
- 下郷
- 下原
- 下原
- 下佐山
- 下佐山
- 下三原田
- 下三原田
- 下宿
- 下宿
- 下小出
- 下小出
- 下小出町一丁目
- 下小出町一丁目
- 下小川
- 下小川
- 下新田
- 下新田
- 下川島
- 下川島
- 下組
- 下組
- 下沢橋
- 下沢橋
- 下坪野
- 下坪野
- 下箱田
- 下箱田
- 下発知
- 下発知
- 下方
- 下方
- 下牧
- 下牧
- 下野田
- 下野田
- 迦葉山
- 迦葉山
- 廻戸
- 廻戸
- 蟹枠団地入口
- 開協前
- 開協前
- 貝野瀬
- 貝野瀬
- 貝野瀬農協前
- 貝野瀬農協前
- 柿平
- 柿平
- 覚満淵入口
- 覚満淵入口
- 角田接骨前
- 角田接骨前
- 学校下
- 学校下
- 学校橋
- 学校橋
- 学校前
- 学校前
- 学校入口
- 学校入口
- 鎌沢
- 鎌沢
- 鎌田
- 鎌田
- 観音寺
- 観音寺
- 観音寺前
- 観音寺前
- 観音前
- 観音前
- 観光会館前
- 観光会館前
- 関越交通 前橋営業所
- 関口入口
- 関口入口
- 関根
- 関根
- 関根町三丁目
- 関所跡
- 関所跡
- 関水
- 関水
- 丸沼高原第１ペンション村
- 丸沼高原第１ペンション村
- 丸沼高原第２ペンション村
- 丸沼高原第２ペンション村
- 岩室
- 岩室
- 岩室下
- and 1963 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
6 findings, ordered by severity.
Show every finding
- Warning192215 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)
- Warning2953 instances
2953 of 2953 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)
- Warning2213 instances
2213 of 2213 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)
- Warning2211 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)
- Warning3 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)
- Info45 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)
Conformance mark Not yet
One requirement remains for this feed to earn 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 360 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.
- 3 of 2213 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 360 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 79 / 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 60 / 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/kan-etsu-transportation/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.