Feed status · checked 2026-07-19
Nagai Bus (永井バス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
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.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
401 of 401 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
520 of 520 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 3 kinds of issue across 34330 instances (0 error, 34321 warning, 9 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.
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.
- 70A マイバス東循環線 (green)
- 70B マイバス東循環線 (green)
- 71A マイバス西循環線 (green)
- 71B マイバス西循環線 (green)
- 30A 前橋玉村線 (green)
- 30B 前橋玉村線 (green)
- 30C 前橋玉村線 (green)
- 30E 前橋玉村線 (green)
- 30F 前橋玉村線 (green)
- 30G 前橋玉村線 (green)
- 30H 前橋玉村線 (green)
- 30J 前橋玉村線 (green)
- 30K 前橋玉村線 (green)
- 54A 嶺公園線 (green)
- 54B 嶺公園線 (green)
- 40A 東大室線 (green)
- 40B 東大室線 (green)
- 56 石関町前橋大島駅線 (white)
- 53A 荻窪公園線 (green)
- 53B 荻窪公園線 (green)
- 53C 荻窪公園線 (green)
- 53E 荻窪公園線 (green)
- 53F 荻窪公園線 (green)
- 53G 荻窪公園線 (green)
| Route | Type | Line color |
|---|---|---|
| 70A マイバス東循環線 | Bus | green |
| 70B マイバス東循環線 | Bus | green |
| 71A マイバス西循環線 | Bus | green |
| 71B マイバス西循環線 | Bus | green |
| 30A 前橋玉村線 | Bus | green |
| 30B 前橋玉村線 | Bus | green |
| 30C 前橋玉村線 | Bus | green |
| 30E 前橋玉村線 | Bus | green |
| 30F 前橋玉村線 | Bus | green |
| 30G 前橋玉村線 | Bus | green |
| 30H 前橋玉村線 | Bus | green |
| 30J 前橋玉村線 | Bus | green |
| 30K 前橋玉村線 | Bus | green |
| 54A 嶺公園線 | Bus | green |
| 54B 嶺公園線 | Bus | green |
| 40A 東大室線 | Bus | green |
| 40B 東大室線 | Bus | green |
| 56 石関町前橋大島駅線 | Bus | white |
| 53A 荻窪公園線 | Bus | green |
| 53B 荻窪公園線 | Bus | green |
| 53C 荻窪公園線 | Bus | green |
| 53E 荻窪公園線 | Bus | green |
| 53F 荻窪公園線 | Bus | green |
| 53G 荻窪公園線 | Bus | green |
This feed has 401 stops.
List every stop
- 前橋公園
- 前橋公園
- 県庁前
- 県庁前
- 市役所・合庁前
- 市役所・合庁前
- 日銀前
- 本町
- 本町
- 表町
- 表町
- 前橋駅
- 前橋駅
- 前橋駅
- 前橋駅
- 前橋駅
- 永寿寺前
- 永寿寺前
- 三河町
- 三河町
- 境橋
- 境橋
- ココルンシティ入口
- ココルンシティ入口
- 朝日町
- 朝日町
- 朝日町団地
- 朝日町団地
- 前橋東警察署入口
- 前橋東警察署入口
- 天川大島町三丁目
- 天川大島町三丁目
- 県勤労福祉センター入口
- 県勤労福祉センター入口
- 野中町
- 野中町
- 上長磯町
- 上長磯町
- 女屋町
- 女屋町
- 前橋東高校入口
- 前橋東高校入口
- 今井町
- 今井町
- 御蔵橋
- 御蔵橋
- 城南支所前
- 城南支所前
- 総合運動公園入口
- 総合運動公園入口
- 二之宮町神社裏
- 二之宮町神社裏
- 二之宮町
- 二之宮町
- 飯土井町
- 飯土井町
- 城南工業団地入口
- 城南工業団地入口
- 東大室
- 表町二丁目
- 表町二丁目
- 前橋駅南口
- 前橋駅南口
- 南町四丁目
- 南町四丁目
- 前商入口
- 前商入口
- 城南小入口
- 城南小入口
- 六供八幡前
- 六供八幡前
- 六供町
- 六供町
- 六供南
- 六供南
- 市民体育館入口
- 市民体育館入口
- 前橋工科大前
- 前橋工科大前
- 上佐鳥町
- 上佐鳥町
- 後閑町入口
- 後閑町入口
- 南高校入口
- 南高校入口
- 亀里町
- 亀里町
- 鶴亀
- 鶴亀
- 農協ビル前
- 農協ビル前
- 鶴光路町
- 鶴光路町
- 下川淵公民館前
- 下川淵公民館前
- 産業技術センター前
- 産業技術センター前
- 東横手
- 東横手
- 西通り
- 西通り
- 油田橋
- 油田橋
- グランド前
- グランド前
- 中央通り
- 中央通り
- 新堀町
- 新堀町
- 群馬ヘリポート入口
- 群馬ヘリポート入口
- 上福島
- 上福島
- 福島橋
- 福島橋
- 福島公民館
- 福島公民館
- 福島
- 福島
- 玉村町役場入口
- 玉村町役場入口
- 玉村町役場
- 女子大入口
- 女子大入口
- 玉村六丁目
- 玉村六丁目
- 玉村五丁目
- 玉村五丁目
- 玉村四丁目
- 玉村四丁目
- 玉村三丁目
- 玉村三丁目
- 町営上新田団地
- 町営上新田団地
- 総合運動公園
- 総合運動公園
- 上之手団地
- 上之手団地
- 上之手公民館前
- 上之手公民館前
- ダイヤパレス西
- ダイヤパレス西
- 県立女子大前
- 県立女子大前
- 上之手
- 上之手
- 上之手南
- 上之手南
- 角渕北
- 角渕北
- 角渕南
- 角渕南
- 上武大入口
- 上武大入口
- 自衛隊前
- 自衛隊前
- 新町郵便局前
- 新町郵便局前
- 橋場町
- 橋場町
- 新町駅
- 聾学校西
- 聾学校西
- 六供町北
- 六供町北
- 六供中央公園
- 六供中央公園
- 坂下
- 坂下
- 中央駅
- 中央駅
- 城東町二丁目
- 城東町二丁目
- 城東町一丁目
- 城東町一丁目
- 県民会館前
- 県民会館前
- 若宮町一丁目
- 若宮町一丁目
- 附属小前
- 附属小前
- みずき中入口
- みずき中入口
- 日吉町
- 日吉町
- 上三俣町
- 上三俣町
- 三俣町
- 三俣町
- 幸塚入口
- 幸塚入口
- 霊園入口
- 霊園入口
- 県立前橋高校北
- 県立前橋高校北
- 県民健康科学大学前
- 県民健康科学大学前
- 上沖入口
- 上沖入口
- 端気町
- 端気町
- 芳賀工業団地
- 芳賀工業団地
- 鳥取町
- 鳥取町
- 東部住宅団地入口
- 東部住宅団地入口
- 芳賀小前
- 芳賀小前
- 高花台団地
- 高花台団地
- 団地中央
- 団地中央
- 団地北
- 団地北
- 公田
- 公田
- 西新井
- 西新井
- 集荷所
- 集荷所
- 小坂子
- 小坂子
- みずき中前
- みずき中前
- 日吉児童館入口
- 日吉児童館入口
- 総合福祉会館
- 総合福祉会館
- 県民健康科学大学
- 県民健康科学大学
- 小坂子東
- 小坂子東
- 荻窪公園
- 若宮町三丁目
- 若宮町三丁目
- 若宮十字路
- 若宮十字路
- 北代田町
- 北代田町
- 下細井町
- 下細井町
- 県営住宅前
- 県営住宅前
- 学校前
- 学校前
- 鎌倉坂
- 鎌倉坂
- 小神明三叉路
- 小神明三叉路
- and 151 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 | 80.2 | first check |
| 2026-07-19 | 80.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
5 findings, ordered by severity.
Show every finding
- Warning33778 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)
- Warning543 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)
- Warning520 instances
520 of 520 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)
- Warning401 instances
401 of 401 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)
- Info9 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)
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 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/nagai-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.