GTFS Scorecard
← All agencies

Feed status · checked 2026-09-01

Yuki City Loop Bus (結城市巡回バス)

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

76.6 / 100

unchanged since 2026-08-31

Catalogued in Ibaraki, Japan.

Covers 699 daysAccessibility gapsRealtime not yet published

Yuki City's circulating community bus (巡回バス) in western Ibaraki; counted as one feed record.

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.3, validator 8.0.1.

Checked for changes 59 minutes ago; last changed 30 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

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

127 of 127 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

Fix 02

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

42 of 42 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

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
127 of 127 stops don't say whether a wheelchair user can board there.
Next action
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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.

  1. 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. See this feed's finding-clearance log.

  2. 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. See this feed's finding-clearance log.

  3. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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. See this feed's finding-clearance log.

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 699 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

Correctness80.5 / 100

The MobilityData validator flagged 7 kinds of issue across 18 instances (0 error, 13 warning, 5 informational).

Freshness100.0 / 100

Service data covers the next 699 days.

Rider experience52.5 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (「結城市巡回バス」 北部東ルート, 「結城市巡回バス」 北部西ルート, 「結城市巡回バス」 絹川ルート, 「結城市巡回バス」 江川Ａルート, 「結城市巡回バス」 江川Ｂルート).

    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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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.

This feed has 127 stops.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

Routes in Yuki City Loop Bus (結城市巡回バス)'s feed
RouteTypeLine color
「結城市巡回バス」 北部東ルートBuspink (no shape in feed)
「結城市巡回バス」 北部西ルートBusgreen (no shape in feed)
「結城市巡回バス」 絹川ルートBusorange (no shape in feed)
「結城市巡回バス」 江川ＡルートBuspink (no shape in feed)
「結城市巡回バス」 江川ＢルートBusteal (no shape in feed)
「結城市巡回バス」 山川ＡルートBusyellow (no shape in feed)
「結城市巡回バス」 山川ＢルートBuspurple (no shape in feed)
List every stop
  • 城跡公園入口
  • 福良橋西
  • 三ツ谷大谷瀬
  • パークゴルフ場
  • 伝統工芸館前
  • 東結城駅
  • 筑西遊湯館
  • 人手観音
  • 栄町西
  • 四ツ京北
  • 中住宅集会所
  • 富士見ニュータウン入口
  • 結城郵便局西
  • 小田林駅
  • 新福寺
  • 富士見町東
  • 下り松
  • カインズ結城店
  • 人手町
  • 城の内北
  • 鹿窪西
  • 林市営住宅
  • 鬼怒商業高等学校
  • 曽我殿台
  • 逆井
  • 結城警察署
  • 工業団地東
  • 一ツ木
  • 青嵐荘
  • 渡邉医院前
  • 特別支援学校
  • かなくぼ総合体育館
  • 山川新宿
  • 善右ヱ門新田
  • 蓮縄田公民館
  • 前新田
  • 東茂呂十字路
  • 江川大町西
  • 結城駅北口
  • 江川出張所
  • 京平寿司
  • 大戦防
  • 江川大町東
  • 大木西
  • 大木東公民館
  • 結城南中学校南
  • 大木北
  • 日本花の会入口
  • 生井鉄工
  • 結城駅南口
  • 浜田屋酒店
  • 新田間町
  • 青木菓子店
  • 森石油店
  • 上成西
  • 作の谷グリーンタウン
  • 作の谷北
  • 結城病院
  • 公達
  • 七五三場
  • 結城信用金庫前
  • 七五三場公民館
  • 北茂呂
  • しもふさの郷
  • 染谷商店
  • ふじや
  • 片蓋十字路
  • 山川文化会館
  • 田向集会所
  • 山川小学校北
  • 芳賀崎
  • 市役所・アクロス
  • 水海道
  • 浜野辺五差路
  • 山王
  • 香取神社西
  • 馬場延命観音
  • 上山川消防第10分団
  • 瓦塚
  • 円城庵
  • 才光寺公園
  • 林ふるさとコミュニティセンター
  • カスミ
  • 鹿窪旧道
  • 粕礼
  • 粕礼上
  • 長徳院入口
  • 今宿上坪集会所
  • 山川不動尊
  • 中央集会所
  • 辻道東
  • 古宿毘沙門
  • 前法内集会所
  • 小森
  • 原集会所
  • 芝崎
  • 平間
  • 鹿窪団地入口
  • 南部中央コミュニティセンター入口
  • 見晴町
  • 結城西小学校東
  • 川木谷野球場
  • 結城中学校南
  • 小田林コミュニティセンター
  • 久保田
  • 黒田児童会館
  • 生きいき診療所前
  • 仁軒地
  • 城南小学校
  • とりせん南
  • はつらつサロン
  • 大町
  • 穀町
  • 公民館北部分館
  • 四季の杜
  • 宮﨑
  • 神明町
  • 栄町東
  • 松木合農村集落センター
  • ヨークタウン
  • 五助
  • 城西病院
  • 富士見町西
  • 大橋町
  • 山田燃料設備
  • 結城出張所・公民館
  • 中

Over time

Overall score across the last 5 checks — unchanged since 2026-08-31.

2026-08-06: 76.62026-08-07: 76.62026-08-10: 76.62026-08-31: 76.62026-09-01: 76.6
Show the numbers
CheckScoreChange
2026-08-0676.6 first check
2026-08-0776.6 no change
2026-08-1076.6 no change
2026-08-3176.6 no change
2026-09-0176.6 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-08-31.

Same feed file as 2026-08-31; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

10 findings, ordered by severity.

Show every finding
  • Warning127 instances

    127 of 127 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.)

    Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning42 instances

    42 of 42 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.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • 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.)

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • 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.)

    Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules

  • 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.)

    Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    Many of the feed's trips don't run at all in the next 7 days.

    It usually means old service periods are still in the export, making the feed bigger and harder to check.

    Fix: Trim past service periods the next time you export. (One setting in most export tools.)

    Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • 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.)

    Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules

  • Info1 instance

    Future calendar (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: future_calendar · See MobilityData GTFS Validator rules

  • Info1 instance

    Future feed (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: future_feed · See MobilityData GTFS Validator rules

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

Conformance mark Not yet

One requirement remains for this feed to earn 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 699 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 699 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 80 / 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.

Yuki City Loop Bus (結城市巡回バス) GTFS data quality grade: C

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/yuki-city-loop-bus/2026-09-01.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-09-01. 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.