Feed status · checked 2026-09-05
Nippon Chuo Bus Maebashi Area (日本中央バス 前橋エリア)
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 2 hours ago; last changed 2 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
580 of 580 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
800 of 800 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
- 580 of 580 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
- 800 of 800 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 207 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 73072 instances (0 error, 73066 warning, 6 informational).
Service data covers the next 207 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.
2 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (42B 広瀬線, 42A 広瀬線, 51 青柳富士見線, 59A シャトルバス, 59B シャトルバス).
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.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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 580 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.
- 59A シャトルバス (orange)
- 59B シャトルバス (orange)
- 高速バス シルクライナー (red)
- 高速バス シルクライナー (red)
- 高速バス 桐生・太田・館林～羽田空港線 (red)
- 高速バス 前橋・高崎～池袋・新宿線 (red)
- 高速バス 前橋・高崎～池袋・新宿・東京駅線 (red)
- 高速バス 前橋・高崎～東京駅線 (red)
- 高速バス 前橋・高崎～羽田空港線 (red)
- 19B 前橋吉岡線 (blue)
- 19C 前橋吉岡線 (blue)
- 19E 前橋吉岡線 (blue)
- 18A 前橋榛東線 (blue)
- 18B 前橋榛東線 (blue)
- 18C 前橋榛東線 (blue)
- 18E 前橋榛東線 (blue)
- 18F 前橋榛東線 (blue)
- 18G 前橋榛東線 (blue)
- 41A 城南運動公園線 (green)
- 41B 城南運動公園線 (green)
- 57 石関町前橋駅線 (green)
- 奥多野線 (orange)
- 奥多野線 (orange)
- 43A 川曲線 (white)
- 43B 川曲線 (white)
- 42A 広瀬線 (pink)
- 42B 広瀬線 (pink)
- 高速バス 東京・さいたま・群馬～富山・金沢線 (red)
- 高速バス 群馬～仙台線 (red)
- 51 青柳富士見線 (orange)
| Route | Type | Line color |
|---|---|---|
| 59A シャトルバス | Bus | orange |
| 59B シャトルバス | Bus | orange |
| 高速バス シルクライナー | Bus | red |
| 高速バス シルクライナー | Bus | red |
| 高速バス 桐生・太田・館林～羽田空港線 | Bus | red |
| 高速バス 前橋・高崎～池袋・新宿線 | Bus | red |
| 高速バス 前橋・高崎～池袋・新宿・東京駅線 | Bus | red |
| 高速バス 前橋・高崎～東京駅線 | Bus | red |
| 高速バス 前橋・高崎～羽田空港線 | Bus | red |
| 19B 前橋吉岡線 | Bus | blue |
| 19C 前橋吉岡線 | Bus | blue |
| 19E 前橋吉岡線 | Bus | blue |
| 18A 前橋榛東線 | Bus | blue |
| 18B 前橋榛東線 | Bus | blue |
| 18C 前橋榛東線 | Bus | blue |
| 18E 前橋榛東線 | Bus | blue |
| 18F 前橋榛東線 | Bus | blue |
| 18G 前橋榛東線 | Bus | blue |
| 41A 城南運動公園線 | Bus | green |
| 41B 城南運動公園線 | Bus | green |
| 57 石関町前橋駅線 | Bus | green |
| 奥多野線 | Bus | orange |
| 奥多野線 | Bus | orange |
| 43A 川曲線 | Bus | white |
| 43B 川曲線 | Bus | white |
| 42A 広瀬線 | Bus | pink |
| 42B 広瀬線 | Bus | pink |
| 高速バス 東京・さいたま・群馬～富山・金沢線 | Bus | red |
| 高速バス 群馬～仙台線 | Bus | red |
| 51 青柳富士見線 | Bus | orange |
List every stop
- 河原橋
- 神流町中里合同庁舎前
- 神流町役場前
- 亀甲橋
- 旧十二柱神社前
- 旧十二柱神社前
- 旧榛東村役場前
- 旧榛東村役場前
- 赤坂電停
- 赤坂電停
- 行根
- 行根
- 恐竜センター
- 玉蔵院
- 玉蔵院
- 玉蔵院東
- 玉蔵院東
- 清里小学校前
- 清里小学校前
- 清野
- 清野
- 赤土橋
- 倉海戸
- 倉海戸
- 黒田
- くわばら整形外科前
- くわばら整形外科前
- 群銀広瀬支店前
- 群銀広瀬支店前
- 群馬医療福祉大学前
- 群馬銀行・東和銀行前
- 群馬銀行・東和銀行前
- 群馬総社駅
- 群馬藤岡駅
- けやきウォーク前橋北
- けやきウォーク前橋北
- 元景寺
- 元景寺
- 県庁前
- 県庁前
- 県庁前
- 県庁前
- 県民会館前
- 県民会館前
- 前橋女子高入口
- 前橋女子高入口
- 公会堂前
- 公会堂前
- 公社ビル入口
- 公社ビル入口
- 合同庁舎入口
- 合同庁舎入口
- 高八木
- 公立藤岡総合病院
- 国道十字路
- 国道十字路
- 小平
- 小平西
- 古鉄橋
- 駒寄
- 駒寄
- 駒寄小学校前
- 駒寄小学校前
- 駒寄診療所
- 駒寄診療所
- 坂井
- 境橋
- 境橋
- 坂下
- 坂下
- 坂本
- 笹熊公会堂前
- 笹熊公会堂前
- 蚕業試験場東
- 蚕業試験場東
- 珊瑚寺入口
- 珊瑚寺入口
- 三中前
- 三中前
- 三宮住宅入口
- 三宮住宅入口
- 自衛隊前
- しおじの湯
- 児童館入口
- 児童館入口
- 柴原集会所前
- 鬼石下相生町
- 鬼石下相生町
- 下新井
- 下新井
- 下小越
- 下久保
- 下栗須宮本
- 下栗須宮本
- 下郷
- 下郷
- 下野田
- 下野田
- 社会福祉総合センター前
- 社会福祉総合センター前
- 市役所・合庁前
- 市役所・合庁前
- 十二沢
- 十二沢
- 宿神田
- 宿神田
- 小学校前
- あじさいの里公園入口
- あじさいの里公園入口
- 相生北
- 相生北
- 城東町一丁目
- 城東町一丁目
- 城東町二丁目
- 城東町二丁目
- 城南運動公園
- 城南病院
- 城南病院
- 浄法寺
- 浄法寺
- 浄法寺スポーツ公園入口
- 浄法寺スポーツ公園入口
- 浄法寺郵便局前
- 浄法寺郵便局前
- 生利
- 公民館入口
- 公民館入口
- 白井入口
- 神田
- 神田
- 新高瀬橋
- しんとう温泉
- 榛東村役場
- 新前橋駅
- 新前橋駅
- 新前橋駅
- 新町駅
- 新町第十区市営住宅入口
- 新町第十区市営住宅入口
- 信用金庫前
- 信用金庫前
- 麻生
- 諏訪神社前
- 諏訪神社前
- 静和幼稚園前
- 静和幼稚園前
- 総合グランド入口
- 総社山王
- 総社山王
- 総社高井
- 総社高井
- 総社郵便局前
- 総社郵便局前
- アニバーサリーコートラシーネ
- アニバーサリーコートラシーネ
- 第１区コミセン前
- 第１区コミセン前
- 体験学習館マグ
- 高井
- 高井
- 高崎駅東口
- 高崎駅東口
- 高崎駅東口
- 高崎駅東口
- 高崎バスセンター
- 高瀬入口
- 高橋
- ふれあい公園北
- ふれあい公園北
- 田島十字路
- 田島十字路
- 立石
- 立石
- 田の頭
- ダムサイト入口
- 団地入口
- 団地入口
- 団地南
- 団地南
- 中央病院前
- 中央病院前
- 中央前橋駅
- 中央前橋駅
- 中央前橋駅
- 中央前橋駅
- 辻
- 辻
- 堤
- 堤
- 露久保
- 鶴が谷公民館
- 鶴が谷公民館
- 鶴が谷団地
- 鶴が谷団地
- 鶴巻
- 鶴巻
- 寺山
- 寺山
- 天神山
- 天神山
- 飯玉
- 飯玉
- 伝田郷
- 砥根平
- 利根橋
- 利根橋
- 富田
- 富田
- 問屋町二丁目
- 問屋町二丁目
- 長井屋前
- 長岡
- 長岡
- 中島
- 中島
- 中神田
- 中神田
- 中村
- 中屋敷
- 中屋敷
- 楢原
- 石井
- 石井
- 西片貝三丁目
- 西片貝三丁目
- 西片貝二丁目
- 西片貝二丁目
- 西黒田
- 日銀前
- 二丁目
- 二丁目
- 石関町南
- 新田
- 新田
- 新羽
- 新羽坂の上
- 日本中央タクシー前
- 農協神流支店
- 農協神流支店
- 箱田新橋入口
- 箱田新橋入口
- 鬼石相生町
- 鬼石相生町
- 箱田中前
- 箱田中前
- 箱田町北
- 箱田町北
- 箱田町南
- 箱田町南
- 八幡神社
- and 330 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
7 findings, ordered by severity.
Show every finding
- Warning72552 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)
- Warning800 instances
800 of 800 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)
- Warning580 instances
580 of 580 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)
- Warning512 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)
- 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
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)
- 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.)
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 207 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 207 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/nippon-chuo-bus-maebashi/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.