Feed status · checked 2026-07-18
Kumagaya City Yuyu Bus (熊谷市ゆうゆうバス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Saitama, 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.
Checked for changes 3 hours ago; last changed 3 hours ago.
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
397 of 397 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
118 of 118 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 531 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 5 kinds of issue across 3237 instances (0 error, 3231 warning, 6 informational).
Service data covers the next 531 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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (さくら号, グライダー号, グライダーワゴン 妻沼循環, グライダーワゴン, ムサシトミヨ号 籠原駅, and more).
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.
- さくら号 (pink)
- グライダー号 (teal)
- グライダーワゴン 妻沼循環 (gray)
- グライダーワゴン (gray)
- ムサシトミヨ号 籠原駅 (gray)
- ムサシトミヨ号 上之荘 (gray)
- ひまわり号 (orange)
- 直実号 (red)
- ほたる号 熊谷駅南口 (purple)
- ほたる号 籠原駅南口 (purple)
- くまぴあ号 (blue)
| Route | Type | Line color |
|---|---|---|
| さくら号 | Bus | pink |
| グライダー号 | Bus | teal |
| グライダーワゴン 妻沼循環 | Bus | gray |
| グライダーワゴン | Bus | gray |
| ムサシトミヨ号 籠原駅 | Bus | gray |
| ムサシトミヨ号 上之荘 | Bus | gray |
| ひまわり号 | Bus | orange |
| 直実号 | Bus | red |
| ほたる号 熊谷駅南口 | Bus | purple |
| ほたる号 籠原駅南口 | Bus | purple |
| くまぴあ号 | Bus | blue |
This feed has 397 stops.
List every stop
- 籠原駅南口
- 籠原南
- 熊谷文化創造館
- 拾六間北
- NTT前
- 籠原保育所
- 籠原団地
- 寿公園
- 自衛隊前
- 拾六間南
- 三尻公民館
- 三尻郵便局
- 三尻宮島
- 武体
- 大麻生駅入口
- 大麻生小学校
- 運動公園
- 広瀬西
- 熊谷商業高校入口
- 天田屋前
- 石原西
- 堤公園入口
- 伊勢町ふれあい公園
- 見晴郵便局
- 福島病院北
- 熊谷駅南口
- 福島病院北
- 見晴郵便局
- 伊勢町ふれあい公園
- 堤公園入口
- 石原西
- 天田屋前
- 熊谷商業高校入口
- 広瀬西
- 大麻生小学校
- 大麻生駅入口
- 武体
- 三尻宮島
- 三尻郵便局
- 三尻公民館
- 拾六間南
- 自衛隊前
- 籠原団地
- 籠原保育所
- NTT前
- 拾六間北
- 熊谷文化創造館
- 籠原南
- 妻沼行政センター
- 登戸
- 聖天山南入口
- 妻沼聖天前
- 妻沼中央公民館入口
- 妻沼東中学校前
- 善ヶ島西部
- 善ヶ島コミュニティセンター入口
- 弁財
- 西島
- 葛和田老人憩いの家
- 葛和田橋南
- 日向中
- 日向上
- 日向団地
- 西城就業改善センター入口
- 森谷
- 下奈良時花
- 中妻団地前
- 下奈良久保南
- 四方寺農村広場
- 荒宿農村広場
- 観音寺入口
- 中条中学校東
- スポーツ文化公園
- 上川上自治会館前
- 陸上競技場入口
- 大塚
- 下川上
- 愛染堂前
- 池上
- 上之
- 生協病院前
- 上之荘
- 源宗寺入口
- 上之西
- 銀座保育所北
- 総合病院
- 藤間病院前
- 熊谷女子高校北
- 市役所前
- 裁判所前
- 八木橋東
- 八木橋東
- 裁判所前
- 熊谷女子高校北
- 藤間病院前
- 銀座保育所北
- 上之西
- 源宗寺入口
- 上之荘
- 生協病院前
- 上之
- 池上
- 愛染堂前
- 下川上
- 大塚
- 陸上競技場入口
- 上川上自治会館前
- スポーツ文化公園
- 中条中学校東
- 観音寺入口
- 荒宿農村広場
- 四方寺農村広場
- 下奈良久保南
- 中妻団地前
- 下奈良時花
- 森谷
- 西城就業改善センター入口
- 日向団地
- 日向上
- 日向中
- 葛和田橋南
- 葛和田老人憩いの家
- 西島
- 弁財
- 善ヶ島コミュニティセンター入口
- 善ヶ島西部
- 妻沼東中学校前
- 妻沼中央公民館入口
- 聖天山南入口
- 登戸
- 妻沼行政センター
- 大野
- グライダー妻沼訓練所入口
- 向野コミュニティセンター前
- 荒宿
- 俵瀬
- 荻野吟子記念館前
- 俵瀬
- 荒宿
- 日向下
- 上須戸ハイツ
- 武道館前
- 西光院前
- 田島
- 西野
- 妻沼南
- 道の駅めぬま
- 妻沼西中学校前
- 五十石
- 男沼
- 出来島入口
- 間々田
- あじさい寺（能護寺）
- 永井太田
- 太田郵便局
- 前新田
- 市ノ坪
- 備前橋南
- 八木田
- 道ヶ谷戸
- 飯塚
- 市ノ坪南
- 下増田
- 別府荘
- 別府沼公園
- JA別府玉井支店
- 安楽寺入口
- 別府中学校南
- 別府第２公園
- 別府一丁目
- 籠原駅北口
- 別府一丁目
- 別府第２公園
- 別府中学校南
- 安楽寺入口
- JA別府玉井支店
- 別府沼公園
- 別府荘
- 下増田
- 市ノ坪南
- 飯塚
- 道ヶ谷戸
- 備前橋南
- 市ノ坪
- 前新田
- 太田郵便局
- 永井太田
- あじさい寺（能護寺）
- 間々田
- 出来島入口
- 男沼
- 五十石
- 妻沼西中学校前
- JAふれあいセンター
- 久保島自治会館
- テニスコート入口
- 小島土井尻
- 熊谷工業高校入口
- 広瀬北
- 広瀬北
- 熊谷工業高校入口
- 小島土井尻
- テニスコート入口
- 久保島自治会館
- JAふれあいセンター
- 熊谷東中学校南
- 戸出十字路
- ソシオ流通センター駅前
- 組合会館前
- 流通センター中央
- 佐谷田前方
- 太井公民館
- 久下四丁目
- 久下三丁目
- JR行田駅西口
- 久下一丁目
- 太井堂免
- 太井
- 久下公民館入口
- 下久下
- 上久下
- 久下熊久
- 熊久公園入口
- 外科病院前
- ムサシトミヨ保護センター入口
- 桜木公民館入口
- 万平公園
- 正田クリニック前
- 正田クリニック前
- 万平公園
- 桜木公民館入口
- ムサシトミヨ保護センター入口
- 熊久公園入口
- 久下熊久
- 上久下
- 下久下
- 久下公民館入口
- 太井
- 太井堂免
- 久下一丁目
- 久下三丁目
- 久下四丁目
- 佐谷田前方
- 流通センター中央
- 組合会館前
- 戸出十字路
- 熊谷東中学校南
- 長島記念館前
- 小八林境
- 小八林原
- and 147 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
- Warning3217 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)
- Warning397 instances
397 of 397 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)
- Warning118 instances
118 of 118 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)
- Warning14 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)
- Info3 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
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 531 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 531 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 84 / 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/kumagaya-yuyu-bus/2026-07-18.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-18. 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.