Feed status · checked 2026-07-19
Chikuma Bus (千曲バス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Nagano, 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
407 of 407 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
310 of 310 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 34016 instances (0 error, 34014 warning, 2 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.
1 accessibility depth signal
11 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.
- 上田松本線 (teal)
- 中仙道線 (teal)
- 佐久御代田線 (teal)
- 室賀線 (teal)
- 山手線 (teal)
- 武石線 (teal)
- 白駒線 (teal)
- 祢津線 (teal)
- 美ヶ原高原観光バス (teal)
- 青木線 (teal)
- 鹿教湯線 (teal)
| Route | Type | Line color |
|---|---|---|
| 上田松本線 | Bus | teal |
| 中仙道線 | Bus | teal |
| 佐久御代田線 | Bus | teal |
| 室賀線 | Bus | teal |
| 山手線 | Bus | teal |
| 武石線 | Bus | teal |
| 白駒線 | Bus | teal |
| 祢津線 | Bus | teal |
| 美ヶ原高原観光バス | Bus | teal |
| 青木線 | Bus | teal |
| 鹿教湯線 | Bus | teal |
This feed has 407 stops.
List every stop
- 東内農協前
- 東内農協前
- 新屋
- 新屋
- 丸子郷土博物館
- 丸子郷土博物館
- 和子公民館
- 和子公民館
- 和子上
- 和子上
- 梨の木
- 梨の木
- 下荻窪
- 下荻窪
- 上荻窪
- 上荻窪
- 荻窪上組
- 荻窪上組
- 下虚空蔵
- 下虚空蔵
- 皎月原
- 虚空蔵
- 虚空蔵
- 宮沢
- 宮沢
- 戸羽
- 戸羽
- 茂沢公民館前
- 茂沢公民館前
- 茂沢
- 茂沢
- 中村
- 中村
- 穴沢
- 穴沢
- 西内農協前
- 西内農協前
- 大塩温泉
- 大塩温泉
- 高梨
- 高梨
- 小田井下宿
- 鹿教湯温泉入口
- 鹿教湯温泉入口
- 鹿教湯橋
- 鹿教湯橋
- 鹿教湯病院
- 鹿教湯温泉
- 鹿教湯温泉
- 鹿教湯温泉上
- 鹿教湯温泉上
- 鹿教湯車庫
- 鹿教湯車庫
- アリオ上田入口
- アリオ上田入口
- 三好町一丁目
- 三好町一丁目
- 上田四中前
- 上田四中前
- 三好町二丁目
- 三好町二丁目
- 小田井中央
- 三ツ角
- 三ツ角
- 阪美精密
- 阪美精密
- 上田原駅前
- 上田原駅前
- JA農協川辺支所前
- JA農協川辺支所前
- 宮島
- 宮島
- 福田
- 福田
- 吉田会館前
- 吉田会館前
- 古吉町
- 古吉町
- 横山入口
- 横山入口
- 小泉
- 小泉
- 小泉
- 小田井上宿
- 川西小学校入口
- 和合
- 嶽の組
- 池下
- 押切
- 田中組
- 日陰
- 御屋敷
- 長谷
- 本組
- 荒町
- 原組
- 室賀温泉ささらの湯前
- 中組
- 中畝
- 入組
- 生島足島神社前
- 生島足島神社前
- 松本バスターミナル
- 松本バスターミナル
- 川西小学校前
- 川西小学校前
- 花の木
- 花の木
- 白銀
- 白銀
- 荒町上宿
- 寺軒町
- 寺軒町
- 出浦
- 出浦
- 出浦上町
- 出浦上町
- 当郷
- 当郷
- 殿戸
- 殿戸
- 工場団地前
- 工場団地前
- 村松
- 村松
- 細谷
- 細谷
- 青木バスターミナル
- 千曲高校
- 栄町
- 諏訪部橋
- 城跡公園南
- 天神二丁目
- 上田常入
- 日の出町
- 小林脳外科前
- 小林脳外科前
- 東公園前
- 旧SBC放送局前
- 旧SBC放送局前
- 岩門
- 笹井
- 笹井
- 御代田駅
- 林之郷
- 豊里団地
- 町吉田
- 町吉田
- 三反田
- 三反田
- 尚武橋
- 尚武橋
- 腰越
- 腰越
- 明神下
- 依田窪広域プール入口
- 依田窪広域プール入口
- 中込駅
- 下沖
- 下沖
- 鳥屋口
- 中沖
- 上沖
- メクトロン前
- メクトロン前
- 藪合入口
- 藪合入口
- 鳥居前
- 下武石
- 学校前
- 学校前
- 堀の内
- 浅間総合病院
- 一の瀬
- 堂坂
- 二本木
- 二本木
- 裏二本木
- ふれあい教室前
- 権現
- 中権現
- 上権現
- 小原
- 唐沢
- 下築地
- 築地原
- 大布施入口
- 大布施前
- 下巣栗
- 武石少年自然の家入口
- 中巣栗
- 巣栗上
- 下小寺尾
- 中居
- 上小寺尾
- 佐久医療センター
- 佐久平駅
- 市民交流ひろば前
- 市民交流ひろば前
- 赤岩
- 赤岩
- 常田入口
- 常田入口
- 上塚原
- 上塚原
- 塩名田
- 塩名田
- 御馬寄
- 御馬寄
- 下原中央
- 下原中央
- 八幡神社前
- 八幡神社前
- 支所入口
- 支所入口
- 日赤病院入口
- 日赤病院入口
- 御桐谷西
- 東信免許センター
- 東信免許センター
- 旧小学校前
- 旧小学校前
- 観音寺入口
- 観音寺入口
- 茂田井入口
- 茂田井中央
- 寺前
- 野沢バスセンター
- 茂田井上
- 古町口
- 芦田
- 芦田
- 立科町役場前
- 蓼科高校
- 佐久穂町農産物直売所
- 八千穂駅
- 大石川
- 堂河原
- 八郡入口
- 本町
- 本町
- 大石下
- 公民館前
- 大石
- 夢の森
- 別荘管理棟前
- 八千穂高原自然園
- 八千穂高原スキー場
- ふるさとの森
- 諏訪門
- and 157 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
- Warning33908 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)
- Warning407 instances
407 of 407 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)
- Warning310 instances
310 of 310 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)
- Warning106 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)
- Info2 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)
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 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/chikuma-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.