Feed status · checked 2026-07-19
Nasushiobara City Community Bus (那須塩原市地域バス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Tochigi, 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 2 hours ago; last changed 2 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
219 of 219 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
234 of 234 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 4 kinds of issue across 17622 instances (0 error, 17621 warning, 1 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.
- S10 (yellow)
- S10 (yellow)
- S11 (yellow)
- W1 (purple)
- W2 (orange)
- K30 (green)
- W1 (green)
- K5 (green)
- N3 (green)
- W1 (green)
- K5 (green)
- W1 (green)
- K31 (red)
- N3 (red)
- K5 (red)
- N3 (red)
- K31 (red)
- K5 (red)
- K31 (red)
- K5 (red)
- K5 (red)
- N3 (red)
- K30 (pink)
- K5 (pink)
- K30 (white)
- K5 (pink)
| Route | Type | Line color |
|---|---|---|
| S10 | Bus | yellow |
| S10 | Bus | yellow |
| S11 | Bus | yellow |
| W1 | Bus | purple |
| W2 | Bus | orange |
| K30 | Bus | green |
| W1 | Bus | green |
| K5 | Bus | green |
| N3 | Bus | green |
| W1 | Bus | green |
| K5 | Bus | green |
| W1 | Bus | green |
| K31 | Bus | red |
| N3 | Bus | red |
| K5 | Bus | red |
| N3 | Bus | red |
| K31 | Bus | red |
| K5 | Bus | red |
| K31 | Bus | red |
| K5 | Bus | red |
| K5 | Bus | red |
| N3 | Bus | red |
| K30 | Bus | pink |
| K5 | Bus | pink |
| K30 | Bus | white |
| K5 | Bus | pink |
This feed has 219 stops.
List every stop
- 健康長寿センター前
- 資材センター前
- 新南
- 乃木神社参道入口
- 石林
- 那須清峰高校入口
- 緑２丁目
- 二つ室
- 二つ室公民館
- 太夫塚４丁目
- 太夫塚４丁目
- 三島中学校入口
- 三島中学校入口
- 西幸町
- 西幸町
- 那須拓陽高校前
- 那須拓陽高校前
- 西那須野駅東口
- 晩翠橋
- 晩翠橋
- 青葉台団地前
- 青葉台団地前
- 黒磯駅東口
- 東栄１丁目
- 東栄１丁目
- 東豊浦
- 東豊浦
- エイトタウン那須塩原
- ビバモール前
- 東三島６丁目
- 東三島６丁目
- 松ヶ丘団地
- 松ヶ丘団地
- 日新中学校前
- 日新中学校前
- 三軒茶屋
- 三軒茶屋
- 笹掛
- 笹掛
- 鍋掛小学校入口
- 鍋掛小学校入口
- 鍋掛十文字
- 鍋掛十文字
- 樋沢公民館前
- 樋沢公民館前
- 野間十文字
- 野間十文字
- 那須北病院
- 国際医療福祉大学病院
- 国際医療福祉大学病院
- 共墾社
- 共墾社
- 住吉町
- 黒磯保健センター前
- 黒磯保健センター前
- 本町
- 本町
- 東赤田
- 東赤田
- 井口北
- 井口北
- 井口工業団地入口
- 井口工業団地入口
- 上中野十文字
- 上中野十文字
- イオンタウン那須塩原
- 南郷屋４丁目
- 上中野
- 上中野
- みんなの歩道橋
- みんなの歩道橋
- 西那須野駅西口
- 那須塩原警察署前
- 那須塩原警察署前
- 方京１丁目
- 方京１丁目
- 那須塩原駅西口
- 前弥六南
- 前弥六南
- 東那須野中学校入口
- 東那須野中学校入口
- 唐杉南
- 唐杉南
- 唐杉東
- 唐杉東
- 北弥六
- 北弥六
- 沓掛新田十文字
- 沓掛新田十文字
- 上厚崎２丁目
- 上厚崎２丁目
- 黒磯南高校前
- 西那須野庁舎
- 西那須野庁舎
- 埼玉小学校前
- 埼玉小学校前
- 下埼玉
- 下埼玉
- 上厚崎３丁目
- 上厚崎３丁目
- ヨークベニマル上厚崎店
- ヨークタウン前
- ヨークタウン前
- 厚崎中学校入口
- 厚崎中学校入口
- 上厚崎４丁目
- 上厚崎４丁目
- 上厚崎東
- 上厚崎東
- 那須塩原市役所
- 黒磯中学校西
- 黒磯中学校西
- 疏水パーク前
- 疏水パーク前
- 菅間記念病院
- 黒磯高校入口
- 黒磯高校入口
- いきいきふれあいセンター前
- いきいきふれあいセンター前
- 宮町
- 宮町
- 宮町
- 宮町
- 中央町
- 中央町
- 中央町
- 中央町
- 黒磯駅西口
- 上三依塩原温泉口駅
- 上塩原
- 上塩原
- 別当坂
- 別当坂
- 塚原
- 塚原
- 西那須野公民館前
- 西那須野公民館前
- 元湯温泉口
- 元湯温泉口
- 宮島
- 宮島
- 塩原田代
- 塩原田代
- 明神下
- 明神下
- 木の葉化石園入口
- 木の葉化石園入口
- 塩原支所
- 源三窟
- 源三窟
- 追沢橋
- 追沢橋
- 塩原温泉バスターミナル
- 塩原温泉バスターミナル
- 塩原門前
- 塩原門前
- 西原町
- 西原町
- 塩原畑下
- 塩原畑下
- 塩原塩釜
- 塩原塩釜
- 七ツ岩吊橋
- 七ツ岩吊橋
- 塩原福渡
- 塩原福渡
- 福渡口
- 福渡口
- 夕の原
- 夕の原
- 天皇の間記念公園前
- 天皇の間記念公園前
- ビジターセンター前
- ビジターセンター前
- 医師会塩原温泉病院
- 四季の里
- 四季の里
- 狩野宿前
- 狩野宿前
- 湯っ歩の里入口
- 湯っ歩の里入口
- ホテルニュー塩原前
- ホテルニュー塩原前
- 生きいきの里入口
- 生きいきの里入口
- 紅葉橋
- 紅葉橋
- 足利銀行前
- 南郷屋１丁目
- 睦
- 北赤田公民館前
- 赤田工業団地入口
- 四区工業団地入口
- 西三島５丁目
- 西三島５丁目
- 四区公民館前
- 西小学校
- 雲照寺入口
- そすいの郷
- 国道４号線東
- JA植木センター
- 二区町公民館入口
- 南小学校前
- 一区町公民館入口
- 一区町十文字
- 三島３丁目
- 三島３丁目
- 一区町東
- 二ツ室岳西
- 常盤が丘
- つくし共同作業所前
- 西三島７丁目
- 西那須野消防署前
- 三島体育センター前
- 那須野が原博物館
- 東三島４丁目
- 東三島２丁目
- 三島
- 三島
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
6 findings, ordered by severity.
Show every finding
- Warning17338 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)
- Warning265 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)
- Warning234 instances
234 of 234 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)
- Warning219 instances
219 of 219 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)
- Warning18 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.)
Validator rule: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Validator rule: big_gap_in_service · 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 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 78 / 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/nasushiobara-community-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.