Feed status · checked 2026-07-19
Ashikaga City Route 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 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 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
398 of 398 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
81 of 81 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 'duplicate_key' 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 377 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 7 kinds of issue across 2774 instances (1 error, 2771 warning, 2 informational).
Service data covers the next 377 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
8 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.
- 小俣線 (green)
- 小俣線 (green)
- 松田線 (teal)
- 松田線 (teal)
- 行道線 (yellow)
- 行道線 (yellow)
- 行道線 (yellow)
- 富田線 (white)
- 富田線 (white)
- 富田線 (white)
- 山辺線 (red)
- 山辺線 (red)
- 御厨線 (orange)
- 御厨線 (orange)
- おでかけループ (pink)
- おでかけループ (pink)
- 名草線 (purple)
| Route | Type | Line color |
|---|---|---|
| 小俣線 | Bus | green |
| 小俣線 | Bus | green |
| 松田線 | Bus | teal |
| 松田線 | Bus | teal |
| 行道線 | Bus | yellow |
| 行道線 | Bus | yellow |
| 行道線 | Bus | yellow |
| 富田線 | Bus | white |
| 富田線 | Bus | white |
| 富田線 | Bus | white |
| 山辺線 | Bus | red |
| 山辺線 | Bus | red |
| 御厨線 | Bus | orange |
| 御厨線 | Bus | orange |
| おでかけループ | Bus | pink |
| おでかけループ | Bus | pink |
| 名草線 | Bus | purple |
This feed has 398 stops.
List every stop
- 岡崎山
- 寺岡町
- 寺岡町
- 多田木町
- 多田木町
- 富田駅
- 富田駅
- あしかがフラワーパーク駅入口
- あしかがフラワーパーク駅入口
- 迫間町
- 迫間町
- 東大久保
- 東大久保
- 大久保町
- 大久保町
- 大久保川崎入口
- 大久保川崎入口
- 東幸楽荘
- 鶏足寺前
- 鶏足寺前
- 東足利
- 東足利
- 毛野中入口
- 毛野中入口
- 毛野団地東
- 毛野団地東
- 大沼田集会所
- 大沼田集会所
- 足利病院
- 毛野新町中央児童公園
- 毛野新町中央児童公園
- 八椚町
- 八椚町
- 毛野公民館前
- 毛野公民館前
- 毛野郵便局前
- 毛野郵便局前
- 下宮先
- 下宮先
- 中妻
- 中妻
- 上宮先
- 上宮先
- 白鬚神社前
- 白鬚神社前
- 大月入口
- 大月入口
- アシコタウンあしかが
- 龍泉寺前
- 龍泉寺前
- 助戸一丁目
- 助戸一丁目
- 助戸仲町
- 助戸仲町
- 助戸三丁目
- 助戸三丁目
- 東橋
- 東橋
- JR足利駅
- JR足利駅
- JR足利駅
- 稲荷前
- 稲荷前
- 通一丁目
- 通一丁目
- 通二丁目
- 通二丁目
- 旭町
- 旭町
- 滝の宮団地
- 滝の宮団地
- 堀込一丁目
- 堀込一丁目
- 堀込十字路
- 堀込十字路
- 堀里ニュータウン南
- 堀里ニュータウン南
- 新宿十字路
- 新宿十字路
- 矢場川公民館
- 後橋
- 後橋
- 小俣公民館前
- 小俣公民館前
- みなみ保育所入口
- みなみ保育所入口
- 南大町
- 南大町
- 南大町郵便局前
- 南大町郵便局前
- 中川町
- 中川町
- 野州山辺駅入口
- 野州山辺駅入口
- 八幡十字路
- 八幡十字路
- 八幡郵便局
- 八幡郵便局
- 借宿町
- 借宿町
- 浅間下
- 浅間下
- ヨークタウン
- ヨークタウン
- 小俣境町
- 小俣境町
- 卸売市場
- 卸売市場
- 八坂神社入口
- 八坂神社入口
- 八木宿
- 八木宿
- 福居駅入口
- 福居駅入口
- 神明地
- 神明地
- 上渋垂町
- 上渋垂町
- 旧南分署
- 旧南分署
- 梁田公民館
- 梁田公民館
- 福富町一丁目
- 福富町一丁目
- 梁田町自治会館
- 梁田町自治会館
- 下濁沼
- 上加子
- 上加子
- 馬場倉庫前
- 馬場倉庫前
- 下加子
- 下加子
- 野田茂木
- 野田茂木
- 野田中集会所
- 野田中集会所
- 久野小前
- 久野小前
- 久保田駐在所前
- 久保田駐在所前
- 高松町東
- 高松町東
- 観音寺前
- 観音寺前
- 平成橋
- 平成橋
- 浅間神社前
- 小曽根町自治会館
- 小曽根町自治会館
- 筑波小前
- 筑波小前
- 羽刈工業団地南
- 羽刈前河原
- 神明神社
- 羽刈十字路
- 羽刈十字路
- 県十字路
- 県十字路
- 県宿
- 県宿
- 協和中入口
- 協和中入口
- 御厨公民館入口
- 御厨公民館入口
- 入小屋入口
- 消防本部西
- 消防本部西
- 大正町
- 大正町
- 利保町一丁目
- 利保町一丁目
- 新梶川橋
- 新梶川橋
- 大月町
- 大月町
- 山川町
- 山川町
- 勧農郵便局前
- 勧農郵便局前
- 警察署北
- 警察署北
- 入名草
- 箕輪
- 箕輪
- 小俣白髭
- 臥竜院
- 臥竜院
- 足松
- 足松
- 田中
- 田中
- 大橋
- 大橋
- 江保地
- 江保地
- 日光神社
- 日光神社
- 金蔵院
- 金蔵院
- 名草小学校
- 名草小学校
- 下宿橋
- 下宿橋
- 中屋敷
- 中屋敷
- 小俣駅入口
- 小俣駅入口
- 小俣北町
- 大坂入口
- 大坂入口
- 持舟入口
- 持舟入口
- 登戸橋
- 登戸橋
- 菅田
- 菅田
- 北郷小前
- 北郷小前
- 北郷公民館前
- 北郷公民館前
- 江川町自治会館前
- 江川町自治会館前
- 江川町一丁目
- 江川町一丁目
- 新山西団地前
- 新山西団地前
- 市民体育館前
- 市民体育館前
- 小俣中町
- 小俣中町
- 武道館前
- 武道館前
- 梁田町
- 梁田町
- 小俣下町
- 小俣下町
- 小俣公園入口
- 小俣公園入口
- 葉鹿上町
- 葉鹿上町
- 葉鹿仲町
- 葉鹿仲町
- 葉鹿下町
- 葉鹿下町
- 松田新道入口
- 松田新道入口
- 足利西プラザ
- 大原神社前
- 大原神社前
- and 148 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 | 67.4 | first check |
| 2026-07-19 | 67.4 | 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
10 findings, ordered by severity.
Show every finding
- Error1 instance
Duplicate key (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: duplicate_key · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2750 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)
- Warning398 instances
398 of 398 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)
- Warning81 instances
81 of 81 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)
- Warning10 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)
- Warning9 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)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
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)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: scorecard_no_feed_contact · 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 377 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 377 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1 validator error, 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 52 / 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/ashikaga-city-route-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.