Feed status · checked 2026-09-05
Gunma Chuo Bus (群馬中央バス)
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.
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
369 of 369 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
267 of 267 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
- 369 of 369 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
- 267 of 267 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 236 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 3 kinds of issue across 16960 instances (0 error, 16952 warning, 8 informational).
Service data covers the next 236 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
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (11A 前橋高崎線（芝塚経由）, 11B 前橋高崎線（芝塚経由）, 17 高崎玉村線, 伊勢崎玉村線, スマーク伊勢崎線).
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.
This feed has 369 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.
- スマーク伊勢崎線 (orange)
- 伊勢崎玉村線 (pink)
- 11A 前橋高崎線（芝塚経由） (red)
- 11B 前橋高崎線（芝塚経由） (red)
- 47A 新前橋駅西口線 (brown)
- 47B 新前橋駅西口線 (brown)
- 17 高崎玉村線 (pink)
- 7 ぐるりん京ヶ島線 (purple)
- 8 ぐるりん京ヶ島線 (purple)
- 9 ぐるりん群馬の森線 (teal)
- 10 ぐるりん群馬の森線 (teal)
| Route | Type | Line color |
|---|---|---|
| スマーク伊勢崎線 | Bus | orange |
| 伊勢崎玉村線 | Bus | pink |
| 11A 前橋高崎線（芝塚経由） | Bus | red |
| 11B 前橋高崎線（芝塚経由） | Bus | red |
| 47A 新前橋駅西口線 | Bus | brown |
| 47B 新前橋駅西口線 | Bus | brown |
| 17 高崎玉村線 | Bus | pink |
| 7 ぐるりん京ヶ島線 | Bus | purple |
| 8 ぐるりん京ヶ島線 | Bus | purple |
| 9 ぐるりん群馬の森線 | Bus | teal |
| 10 ぐるりん群馬の森線 | Bus | teal |
List every stop
- あら町銀行前
- あら町銀行前
- 連雀町
- 連雀町
- 田町
- 田町
- 本町三丁目
- 本町三丁目
- 総合文化センター前
- 総合文化センター前
- 高砂町
- 高砂町
- 芝塚
- 芝塚
- 飯玉町
- 飯玉町
- 島前
- 島前
- 島貝沢
- 島貝沢
- 貝沢
- 貝沢
- 井野川橋
- 井野川橋
- 井野駅入口
- 井野駅入口
- 井野
- 井野
- 中尾中入口
- 中尾中入口
- 日高病院
- 日高
- 日高
- プレイランド日高
- プレイランド日高
- 染谷橋
- 染谷橋
- 江田
- 江田
- フォレストモール新前橋
- フォレストモール新前橋
- 新前橋駅入口
- 新前橋駅入口
- 新前橋駅
- 滝川橋
- 滝川橋
- 石倉
- 石倉
- 上石倉
- 上石倉
- 中央病院入口
- 中央病院入口
- 県庁前
- 県庁前
- 市役所・合庁前
- 市役所・合庁前
- 日銀前
- 本町
- 本町
- 表町
- 表町
- 前橋駅
- 前橋駅
- 前橋駅
- あら町
- 高崎駅
- 高崎駅
- 伊勢崎市民病院北
- 弓町
- 東町十字路
- 東町十字路
- 江木町十字路
- 江木町十字路
- 江木町東
- 江木町東
- 江木町東
- 高関町
- 高関町
- 高関
- 高関
- 稲村クリニック前
- 稲村クリニック前
- 柳原
- 柳原
- 柴崎
- 柴崎
- 寄居
- 寄居
- 寄居
- 下大類
- 下大類
- 綿貫入口
- 綿貫入口
- 慈眼寺裏
- 慈眼寺裏
- 上滝
- 上滝
- 榎町
- 榎町
- 板井団地入口
- 板井団地入口
- 板井
- 板井
- 辰巳
- 辰巳
- 斉田
- 斉田
- 玉村高校
- 玉村高校
- 四丁目角
- 四丁目角
- 玉村五丁目
- 玉村五丁目
- 玉村六丁目
- 玉村六丁目
- 玉村町役場南
- 玉村町役場南
- 県立女子大学
- 矢中町入口
- 矢中町入口
- 玉村町役場入口
- 玉村町役場入口
- 福島
- 福島
- 福島公民館
- 福島公民館
- 福島橋
- 福島橋
- 玉村大橋北
- 玉村大橋北
- 上福島
- 上福島
- 森下
- 森下
- 岡本医院前
- 岡本医院前
- 西上の宮
- 西上の宮
- 上の宮
- 上の宮
- 東上の宮
- 東上の宮
- 田中神社
- 田中神社
- 連取十字路西
- 連取十字路西
- 連取
- 連取
- 宮郷第二小西
- 宮郷第二小西
- 連取町南
- 連取町南
- 若葉町
- 若葉町
- 伊勢崎郵便局前
- 伊勢崎郵便局前
- 本町二番
- 本町二番
- 信用金庫前
- 信用金庫前
- 伊勢崎駅前
- 伊勢崎郵便局前三光町経由
- 三光町
- 永久橋西
- 連取元町
- 平和町
- 平和町
- 伊勢崎市文化会館
- 伊勢崎市文化会館
- 上諏訪町
- 上諏訪町
- スマーク
- Gメッセ群馬
- 坂下
- 坂下
- 中央前橋駅前
- 中央前橋駅前
- 立川町通り東
- 立川町通り東
- 立川町通り西
- 立川町通り西
- 遊園地坂下
- 遊園地坂下
- 公社ビル入口
- 公社ビル入口
- 大渡温水プール前
- 大渡温水プール前
- 元総社二丁目
- 問屋会館前
- 老年病研究所前
- 老年病研究所前
- マーキュリーホテル前
- マーキュリーホテル前
- 大友町
- 大友町
- ＮＨＫ入口
- ＮＨＫ入口
- 産業道路入口
- 産業道路入口
- 明神東
- 明神東
- 明神前
- 明神前
- 総社神社南
- 総社神社南
- 元総社
- 元総社
- 県民共済前
- 県民共済前
- 市町村会館前
- 市町村会館前
- 新前橋駅西口
- 高崎駅東口
- 税務署前
- 税務署前
- 江木十字路
- 江木十字路
- 江木町
- 江木町
- 希望館病院入口
- 希望館病院入口
- 高崎女子高校前
- 高崎女子高校前
- 高崎女子高校入口
- 高崎女子高校入口
- 天神町
- 天神町
- 高崎問屋町駅貝沢口
- 貝沢町南
- 貝沢町南
- 東部小学校西
- 東部小学校西
- 高崎商業高校入口
- 高崎商業高校入口
- 東貝沢町四丁目
- 東貝沢町四丁目
- 井野町東
- 井野町東
- 変電所前
- 変電所前
- 松之木橋
- 松之木橋
- 中央中等教育学校前
- 中央中等教育学校前
- 群馬医療福祉大学入口
- 群馬医療福祉大学入口
- 育英短大前
- 育英短大前
- 上京目公民館前
- 上京目公民館前
- and 119 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
5 findings, ordered by severity.
Show every finding
- Warning16676 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)
- Warning369 instances
369 of 369 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)
- Warning276 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)
- Warning267 instances
267 of 267 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)
- Info8 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 236 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 236 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 83 / 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/gunma-chuo-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.