Feed status · checked 2026-07-19
Imizu City Kitokito Bus (射水市きときとバス)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Toyama, 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
383 of 383 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
124 of 124 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 5 kinds of issue across 4044 instances (0 error, 4040 warning, 4 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.
1 accessibility depth signal
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar ((15)歌の森小学校線, (2)新湊・本江線, (2)新湊・本江線, (2)新湊・本江線, (5)新湊・越中大門駅線, 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.
- (12)小杉駅・金山線 (yellow)
- (12)小杉駅・金山線 (yellow)
- (13)小杉駅・池多線 (red)
- (13)小杉駅・池多線 (red)
- (13)小杉駅・池多線 (red)
- (14)小杉駅・太閤山循環線 (pink)
- (14)小杉駅・太閤山循環線 (pink)
- (15)歌の森小学校線 (gray)
- (16)小杉駅・下経由足洗線（北系統・大江） (white)
- (16)小杉駅・下経由足洗線（北系統・大江） (white)
- (16)小杉駅・下経由足洗線（南系統・白石） (white)
- (16)小杉駅・下経由足洗線（南系統・白石） (white)
- (16)小杉駅・下経由足洗線（南系統・白石） (white)
- (17)堀岡・片口経由小杉駅線 (green)
- (17)堀岡・片口経由小杉駅線 (green)
- (17)堀岡・片口経由小杉駅線 (green)
- (2)新湊・本江線 (red)
- (2)新湊・本江線 (red)
- (2)新湊・本江線 (red)
- (4)新湊南部中学校線 (red)
- (5)新湊・越中大門駅線 (teal)
- (5)新湊・越中大門駅線 (teal)
- (5)新湊・越中大門駅線 (teal)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (7)新湊・小杉線 (blue)
- (8)小杉駅・大島中央循環線 (red)
- (8)小杉駅・大島中央循環線 (red)
- (9)大門循環線 (orange)
- (9)大門循環線 (orange)
- (9)大門循環線 (orange)
- (9)大門循環線 (orange)
- (9)大門循環線 (orange)
- (9)大門循環線 (orange)
| Route | Type | Line color |
|---|---|---|
| (12)小杉駅・金山線 | Bus | yellow |
| (12)小杉駅・金山線 | Bus | yellow |
| (13)小杉駅・池多線 | Bus | red |
| (13)小杉駅・池多線 | Bus | red |
| (13)小杉駅・池多線 | Bus | red |
| (14)小杉駅・太閤山循環線 | Bus | pink |
| (14)小杉駅・太閤山循環線 | Bus | pink |
| (15)歌の森小学校線 | Bus | gray |
| (16)小杉駅・下経由足洗線（北系統・大江） | Bus | white |
| (16)小杉駅・下経由足洗線（北系統・大江） | Bus | white |
| (16)小杉駅・下経由足洗線（南系統・白石） | Bus | white |
| (16)小杉駅・下経由足洗線（南系統・白石） | Bus | white |
| (16)小杉駅・下経由足洗線（南系統・白石） | Bus | white |
| (17)堀岡・片口経由小杉駅線 | Bus | green |
| (17)堀岡・片口経由小杉駅線 | Bus | green |
| (17)堀岡・片口経由小杉駅線 | Bus | green |
| (2)新湊・本江線 | Bus | red |
| (2)新湊・本江線 | Bus | red |
| (2)新湊・本江線 | Bus | red |
| (4)新湊南部中学校線 | Bus | red |
| (5)新湊・越中大門駅線 | Bus | teal |
| (5)新湊・越中大門駅線 | Bus | teal |
| (5)新湊・越中大門駅線 | Bus | teal |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (7)新湊・小杉線 | Bus | blue |
| (8)小杉駅・大島中央循環線 | Bus | red |
| (8)小杉駅・大島中央循環線 | Bus | red |
| (9)大門循環線 | Bus | orange |
| (9)大門循環線 | Bus | orange |
| (9)大門循環線 | Bus | orange |
| (9)大門循環線 | Bus | orange |
| (9)大門循環線 | Bus | orange |
| (9)大門循環線 | Bus | orange |
This feed has 383 stops.
List every stop
- 柳瀬公民館前
- 柳瀬公民館前
- 二十六町公民館前
- 二十六町公民館前
- 七美工業団地口
- 七美工業団地口
- リサイクルプラザ前
- リサイクルプラザ前
- 古高場
- 古高場
- 東津幡江公民館前
- 東津幡江公民館前
- 西津幡江口
- 西津幡江口
- 作道小学校前
- 作道小学校前
- 野村
- 小杉駅南口
- 小杉駅南口
- 新湊南部中学校前
- 新湊南部中学校前
- 鏡宮公民館前
- 殿村口
- 殿村公民館前
- 殿村公民館前
- 今井南口
- 沖塚原西口
- 寺塚原公民館前
- 寺塚原西口
- 寺塚原西口
- 松木北口
- 松木北口
- 松木
- 松木
- タカギセイコー
- タカギセイコー
- 坂東
- 坂東
- 大島北野
- 大島北野
- JAいみず野東部支店前
- JAいみず野東部支店前
- 加茂コミュニティ施設前
- 加茂中部西
- 倉垣小杉口
- 白石神社前
- 白石神社前
- 白石口
- 今井公民館前
- 今開発北
- 今開発北
- 一番町
- 一番町
- 若杉北
- 小島西
- 小島西
- 小杉中学校口
- 小杉中学校口
- いみずのショッピングタウン前
- 小杉高校前
- 小杉高校前
- 下条新
- 下条新
- 真生会富山病院前
- 本田
- 本田
- 赤井口
- 赤井口
- ほたる野ヴィレッジ
- 上条団地公民館前
- 浅井コミュニティセンター口
- 浅井コミュニティセンター口
- 今開発
- 南荒町
- 南荒町
- 新港の森
- 新港の森
- 二ノ井公民館前
- 橋下条コミュニティセンター前
- 若林
- 若林
- 小杉中学校前
- 小杉中学校前
- 一番町南
- 伊勢領
- 太閤山北口
- 太閤山北口
- 五歩一
- 宿屋
- 青井谷公民館前
- 金山小学校前
- 金山小学校前
- 新屋敷
- 新屋敷
- 三野
- 三野
- 野手
- 野手
- 林寺
- 林寺
- 上浄土寺
- 上浄土寺
- 小杉カントリー口
- 小杉カントリー口
- 太閤山団地口
- 太閤山団地口
- 浄土寺公民館前
- 浄土寺公民館前
- 上野
- 上野
- 南太閤山14丁目
- 南太閤山14丁目
- 環境科学センター前
- 環境科学センター前
- アルビス太閤山店前
- アルビス太閤山店前
- 中太閤山小学校前
- 中太閤山小学校前
- 小杉南中学校前
- 小杉南中学校前
- 太閤山コミュニティセンター前
- 天池公園前
- 南太閤山12丁目
- 太閤山10丁目
- 太閤山9丁目
- 太閤山相撲場前
- 富山県立大学前
- 富山県立大学前
- 中太閤山3丁目
- 中太閤山4丁目
- 中太閤山7丁目
- 中太閤山9丁目
- 薬勝寺池南公園前
- 花園公園前
- 平野
- 山本新
- 山本新公民館前
- 太閤山ランド前
- 太閤山ランド前
- 池多コミュニティセンター前
- 北野会館前
- 東太閤山4丁目
- 東太閤山3丁目
- 東太閤山北
- 黒河5区
- 黒河1区
- 黒河2区
- 練合東口
- 練合東口
- 兜山公園前
- 駅南通り1丁目
- 駅南通り1丁目
- 千成商店街
- 千成商店街
- 練合
- 練合
- 救急薬品市民交流プラザ前
- 新町
- 高寺
- 小杉小学校前
- 西楠町
- アルビス小杉総合体育センター前
- アルビス小杉総合体育センター前
- 手崎北
- 手崎北
- 鷲塚北
- 鷲塚北
- 小杉白石西
- 小杉白石
- 海老江中町
- 海老江中町
- 小杉白石東
- 加茂東部公民館前
- 下村三箇口
- 三ケ北
- 三ケ北
- 高寺北
- 高寺北
- 愛宕
- 稲積
- 大江北
- 大江
- 大江苑前
- 浜開
- 西高木
- 八講
- 摺出寺コミュニティセンター前
- 下村パークゴルフ場口
- 中新湊駅前
- 中新湊駅前
- クロスベイ新湊
- クロスベイ新湊
- 新湊高校前
- 新湊高校前
- 射北中学校前
- 射北中学校前
- 本町3丁目
- 本町3丁目
- 新湊信用金庫前
- 新湊信用金庫前
- 富山銀行前
- 富山銀行前
- 善光寺西口
- 善光寺西口
- 善光寺交差点
- 善光寺交差点
- 堀岡中町
- かぐら橋口
- かぐら橋口
- あゆの風センター
- あゆの風センター
- 牧野北口
- 牧野北口
- 牧野
- 牧野
- 新港東口
- 新港東口
- 金屋古志野神社前
- 金屋古志野神社前
- 姫野口
- 姫野口
- 市役所前
- 小杉高校北
- 小杉高校北
- 太閤山１丁目
- 稲積口
- 稲積口
- 高場南
- 久々江口
- 下村コミュニティセンター前
- 下村コミュニティセンター前
- 針原北
- 針原南
- 中央図書館口
- 中太閤山6丁目
- 薬勝寺池公園前
- 水上谷口
- 石畑池前
- 五官野
- 土代公民館前
- 富山情報ビジネス専門学校前
- 富山情報ビジネス専門学校前
- 太閤山3丁目
- 太閤山3丁目
- 堀岡コミュニティセンター前
- 射水町
- 北電社宅前
- 椎土
- 椎土
- 中太閤山16丁目
- and 133 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 | 75.8 | first check |
| 2026-07-19 | 75.8 | 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
7 findings, ordered by severity.
Show every finding
- Warning3820 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)
- Warning383 instances
383 of 383 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)
- Warning189 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)
- Warning124 instances
124 of 124 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)
- Warning30 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
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info4 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)
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 74 / 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/imizu-city-kitokito-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.