Feed status · checked 2026-07-19
Ryugasaki City Community Bus (龍ケ崎市コミュニティバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Ibaraki, 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
196 of 196 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
61 of 61 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 165 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 5 kinds of issue across 2632 instances (0 error, 2629 warning, 3 informational).
Service data covers the next 165 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
3 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.
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.
- 循環ルート 外回り (black)
- 循環ルート 内回り (black)
- 南が丘・サプラ線 (pink)
- 南が丘・サプラ線(竜ヶ崎南高経由) (pink)
- 佐貫・川原代線 (red)
- 若柴線 (purple)
| Route | Type | Line color |
|---|---|---|
| 循環ルート 外回り | Bus | black |
| 循環ルート 内回り | Bus | black |
| 南が丘・サプラ線 | Bus | pink |
| 南が丘・サプラ線(竜ヶ崎南高経由) | Bus | pink |
| 佐貫・川原代線 | Bus | red |
| 若柴線 | Bus | purple |
This feed has 196 stops.
List every stop
- 竜ヶ崎駅
- 市役所
- 中曽根
- 文化会館
- 来迎院
- 馴馬
- 馴馬台コミュニティセンター
- 平台２丁目
- 平台入口
- 小柴２丁目
- 小柴４丁目
- サプラ
- ニュータウン中央
- 松葉小学校
- 若柴公園
- 長山中学校
- 長山コミュニティセンター
- 長山４丁目
- 蛇沼公園
- 長山８丁目
- 長山
- 長山第二児童公園
- 長山コミュニティセンター
- 長山中学校
- 若柴公園
- 松葉小学校
- ニュータウン中央
- サプラ
- 小柴４丁目
- 小柴１丁目
- 中根台２丁目
- 中根台中学校
- 中根台５丁目
- 久保台２丁目
- ニュータウン久保台
- 久保台３丁目
- 上貝原塚
- 藤ヶ丘５丁目
- 藤ヶ丘１丁目
- 藤ヶ丘６丁目
- 済生会病院
- 松ヶ丘１丁目
- 松ヶ丘２丁目
- 総合運動公園
- 東部出張所
- 城ノ内１丁目
- 城ノ内２丁目
- 上羽原
- 羽原
- 流通経済大学前
- 竜ヶ崎一高下
- 出し山
- 緑町
- 警察署前
- 城南ショッピングセンター
- 戸張
- 砂町
- 砂町中央
- 砂町西
- 観音前
- 竜ヶ崎二高入口
- 上町辻
- にぎわい広場
- 新町
- 米町
- 米町
- 新町
- にぎわい広場
- 上町辻
- 竜ヶ崎二高入口
- 観音前
- 砂町西
- 砂町中央
- 砂町
- 戸張
- 城南ショッピングセンター
- 警察署前
- 緑町
- 出し山
- 竜ヶ崎一高下
- 流通経済大学前
- 羽原
- 城ノ内２丁目
- 城ノ内１丁目
- 東部出張所
- 松ヶ丘２丁目
- 松ヶ丘１丁目
- 藤ヶ丘６丁目
- 藤ヶ丘１丁目
- 藤ヶ丘５丁目
- 上貝原塚
- 久保台３丁目
- ニュータウン久保台
- 久保台２丁目
- 中根台５丁目
- 中根台中学校
- 中根台２丁目
- 小柴１丁目
- 小柴２丁目
- 平台入口
- 平台２丁目
- 馴馬台コミュニティセンター
- 馴馬
- 来迎院
- 中曽根
- 豊田町根柄
- 羽黒町
- 南が丘１丁目
- 南が丘６丁目
- 南が丘公園
- 北方
- 豊田
- 北文間
- 総合福祉センター
- 道仙田
- 前新田
- 姫宮南
- 姫宮西
- 姫宮東
- 西小学校前
- 西コミュニティセンター前
- 高砂橋
- 栄町
- 新町南
- 水門東
- 第二庁舎
- 奈戸岡
- 富士見住宅
- 中根台
- 中根台
- 富士見住宅
- 奈戸岡
- 第二庁舎
- 水門東
- 新町南
- 栄町
- 高砂橋
- 西コミュニティセンター前
- 西小学校前
- 姫宮東
- 姫宮西
- 前新田
- 道仙田
- 北方
- 羽黒町
- 北方中央
- 竜ヶ崎南高前
- 北方中央
- 龍ケ崎市駅東口
- 佐貫第三児童公園
- 佐貫４丁目
- 佐貫３丁目
- 馴柴小学校北
- 馴柴コミュニティセンター
- 馴柴小学校
- 城西中学校前
- 花丸
- 川原代西
- 紅葉内
- 川原代コミュニティセンター
- 川原代道仙田
- 川原代姫宮
- 六ツ谷
- 六ツ谷橋
- 六ツ谷橋
- 六ツ谷
- 川原代姫宮
- 馴柴小学校
- 馴柴コミュニティセンター
- 馴柴小学校北
- 佐貫３丁目
- 佐貫４丁目
- 佐貫第三児童公園
- 龍ケ崎市駅東口
- 龍ケ崎市駅西口
- 佐貫町南
- 佐貫町中央
- 佐貫町北
- 庄兵衛新田
- マンハイム佐貫前
- 佐貫台
- 文化村公園前
- 龍ケ崎市駅入口
- 佐貫４丁目西
- 佐貫第二児童公園
- 若柴南
- 若柴
- 若柴北
- 星宮神社
- 若柴南
- 佐貫第二児童公園
- 佐貫４丁目西
- 龍ケ崎市駅入口
- 佐貫町北
- 佐貫町中央
- 佐貫町南
Over time
Overall score across the last 2 checks — unchanged since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 77.2 | first check |
| 2026-07-19 | 77.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
8 findings, ordered by severity.
Show every finding
- Warning2583 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)
- Warning196 instances
196 of 196 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)
- Warning61 instances
61 of 61 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)
- Warning45 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)
- Warning26 instances
26 of 61 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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)
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 165 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 165 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 81 / 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 54 / 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/ryugasaki-city-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.