Feed status · checked 2026-07-19
Nikko City Bus (日光市営バス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
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.
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
Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required field (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
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
387 of 387 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
405 of 405 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
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.
Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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_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.
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 23819 instances (200 error, 23619 warning, 0 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
This feed has no route shapes, so the map shows its stops only.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| 下今市線 | Bus | green (no shape in feed) |
| 下野大沢線 | Bus | green (no shape in feed) |
| 今中・市営住宅線 | Bus | green (no shape in feed) |
| 大渡線 | Bus | green (no shape in feed) |
| 小百線 | Bus | green (no shape in feed) |
| 温泉線 | Bus | green (no shape in feed) |
| 足尾JR日光駅線 | Bus | green (no shape in feed) |
| 鬼怒川温泉女夫渕線 | Bus | green (no shape in feed) |
This feed has 387 stops.
List every stop
- 七本桜
- 七本桜
- JR日光駅
- JR日光駅
- 東武日光駅
- 東武日光駅
- 東武日光駅
- 東武日光駅
- 霧降大橋
- 霧降大橋
- 第一発電所前
- 第一発電所前
- 所野公園前
- 所野公園前
- 相の道
- 相の道
- 市民ゴルフ場前
- 市民ゴルフ場前
- 所野第二団地
- 所野第二団地
- 緑の里
- 緑の里
- 第二発電所前
- 第二発電所前
- ゴルフ場前
- ゴルフ場前
- 広久保
- 広久保
- 東照宮晃陽苑
- 東照宮晃陽苑
- 今市特別支援学校
- 今市特別支援学校
- 市営松原住宅入口
- 市営松原住宅入口
- 小幡南
- 小幡南
- 清住町
- 清住町
- 瀬尾入口
- 瀬尾入口
- サンヒルズ瀬尾入口
- サンヒルズ瀬尾入口
- 今市警察署前
- 今市警察署前
- 第二小学校前
- 第二小学校前
- 春日町
- 春日町
- 住吉町(下今市線)
- 住吉町(下今市線)
- 下今市駅
- 鬼怒川温泉駅
- 鬼怒川公園駅前
- 鬼怒川公園駅前
- 新藤原駅前
- 新藤原駅前
- 朝日町
- 朝日町
- 龍王峡入口
- 龍王峡入口
- 川治温泉駅前
- 柏屋ホテル前
- 柏屋ホテル前
- 登隆館前
- 登隆館前
- 宿屋伝七前
- 宿屋伝七前
- 東山閣前
- 東山閣前
- 川治湯元駅入口
- 川治湯元駅入口
- 五十里ダムサイド
- 五十里ダムサイド
- 川治ダムサイド
- 川治ダムサイド
- 小指
- 小指
- 大谷向（小百線）
- 大谷向（小百線）
- 戸中
- 戸中
- 野尻入口
- 野尻入口
- 野尻
- 野尻
- 旧日向公民館前
- 旧日向公民館前
- 旧栗山中学校前
- 旧栗山中学校前
- 大王入口
- 大王入口
- 松ノ木平
- 松ノ木平
- 日蔭
- 日蔭
- 日蔭木工所
- 日蔭木工所
- 青柳車庫前
- 材木町
- 材木町
- 材木町
- 材木町
- 青柳平
- 青柳平
- 黒部
- 黒部
- 観光ドライブイン前
- 観光ドライブイン前
- 栗山行政センター前
- 栗山行政センター前
- 上栗山
- 上栗山
- 蛇王の滝
- 蛇王の滝
- 蛇王平温泉民宿村
- 蛇王平温泉民宿村
- 大川筑
- 大川筑
- 家康の里民宿村入口
- 家康の里民宿村入口
- 萓峠
- 萓峠
- 火の見下
- 火の見下
- 川俣平家塚
- 川俣平家塚
- 中わらび
- 中わらび
- 川俣湖温泉民宿村
- 川俣湖温泉民宿村
- 川俣大橋
- 川俣大橋
- またぎの里
- またぎの里
- 川俣温泉入口
- 川俣温泉入口
- 川俣温泉
- 川俣温泉
- ふくよ館前
- ふくよ館前
- 間欠泉
- 間欠泉
- 仙心亭前
- 仙心亭前
- 明静寺前
- 明静寺前
- 一柳閣前
- 一柳閣前
- 川俣温泉運動公園前
- 川俣温泉運動公園前
- 平家平温泉
- 平家平温泉
- 女夫渕
- 双愛病院
- 遠下
- 遠下
- 中才
- 中才
- 砂畑入口
- 砂畑入口
- 銅山観光前
- 銅山観光前
- 銅山観光入口
- 銅山観光入口
- 田野母
- 田野母
- 通洞駅前
- 通洞駅前
- 足尾小中学校入口
- 足尾小中学校入口
- 郵便局前
- 郵便局前
- 多島医院前
- 多島医院前
- 足尾橋
- 足尾橋
- 足尾駅前
- 足尾駅前
- 渡良瀬橋
- 渡良瀬橋
- 田元
- 田元
- 田元
- 田元
- 田元橋
- 田元橋
- 間藤駅前
- 間藤駅前
- 斎場入口
- 斎場入口
- 下間藤
- 下間藤
- 上間藤
- 上間藤
- 南橋
- 南橋
- 赤倉
- 龍蔵寺前
- 龍蔵寺前
- 銅親水公園入口
- 旧高校前
- 旧高校前
- 野路又
- 野路又
- 足尾石油前
- 足尾石油前
- 神子内橋
- 神子内橋
- 高畑
- 高畑
- 日光市役所前
- 日光市役所前
- 三号
- 三号
- 小学校前
- 小学校前
- 天王様前
- 天王様前
- 皇海荘入口
- 皇海荘入口
- 神子内
- 神子内
- 遠上回転所
- 遠上
- 遠上
- 黒沢
- 黒沢
- 栃木平
- 栃木平
- 細尾リンク入口
- 細尾リンク入口
- 馬坂
- 馬坂
- 清滝
- 清滝
- 日光市民病院前
- 日光市民病院前
- 安川町
- 安川町
- 鉢石町
- 鉢石町
- 大谷向（大渡線）
- 大谷向（大渡線）
- ベイシア今市モール前
- ベイシア今市モール前
- 安良沢
- 安良沢
- 日光植物園
- 日光植物園
- 日光行政センター前
- and 137 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 | 70.0 | first check |
| 2026-07-19 | 70.0 | 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
- Error200 instances
Missing required field (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_required_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning23271 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)
- Warning405 instances
405 of 405 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)
- Warning387 instances
387 of 387 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)
- Warning348 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)
Conformance mark Not yet
This feed is close to the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- 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. The feed also carries 200 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 60 / 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/nikko-city-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.