Feed status · checked 2026-07-23
Kaetsuno Route Bus (加越能バス 一般路線)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
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.
Checked for changes 75 minutes ago; last changed 75 minutes ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 6 snapshots.
- 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
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
The realtime feed's last update was about 2 hours old when sampled. A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
⏱ A vendor support ticket; treat it as a feed outage.worth about +50 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
697 of 697 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
499 of 499 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.
Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish.
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 251 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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 4 kinds of issue across 63761 instances (0 error, 63761 warning, 0 informational).
Service data covers the next 251 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.
Sampled 6 times outside service hours: 2 of 2 configured feeds healthy; vehicle position plausibility was not measurable.
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)
- アウトレットシャトル (green)
- アウトレットシャトル (green)
- 中田町線 (green)
- 中田町線 (green)
- 仏生寺経由 氷見線 (green)
- 仏生寺経由 氷見線 (green)
- 伏木駅経由 氷見 (green)
- 伏木駅経由 氷見線 (green)
- 加越線 (green)
- 加越線 (green)
- 南波岡線 (green)
- 南波岡線 (green)
- 南砺・金沢線 (green)
- 南砺・金沢線 (green)
- 南砺・金沢線 (green)
- 南砺・金沢線 (green)
- 国吉線 (green)
- 国吉線 (green)
- 富大高岡循環線 (green)
- 富山高専線(※高専指定日のみ運行) (green)
- 富山高専線(※高専指定日のみ運行) (green)
- 小牧線 (green)
- 小牧線 (green)
- 小牧線 (green)
- 小牧線 (green)
- 市内②-③系統 (green)
- 市内③系統 (green)
- 市内④-①系統 (green)
- 市内④系統 (green)
- 庄川町線 (green)
- 庄川町線 (green)
- 庄川町線 (green)
- 庄川町線 (green)
- 庄川町線 (green)
- 庄川町線 (green)
- 戸出東部小学校線(※学校指定日のみ運行) (green)
- 戸出東部小学校線(※学校指定日のみ運行) (green)
- 東回り伏木循環線 (green)
- 氷見高校線 (green)
- 灘浦海岸・守山経由氷見線 (green)
- 灘浦海岸・守山経由氷見線 (green)
- 灘浦海岸・守山経由氷見線 (green)
- 灘浦海岸・守山経由氷見線 (green)
- 石動OL福岡町線 (green)
- 石動OL福岡町線 (green)
- 石動OL福岡町線 (green)
- 石動OL福岡町線 (green)
- 石堤循環線 (green)
- 砺波総合病院線 (green)
- 砺波総合病院線 (green)
- 砺波総合運動公園線 (green)
- 砺波総合運動公園線 (green)
- 第一高校線(※学校指定日のみ運行) (green)
- 第一高校線(※学校指定日のみ運行) (green)
- 脇・氷見線 (green)
- 若林線 (green)
- 若林線 (green)
- 西回り伏木循環線 (green)
- 西回り伏木循環線 (green)
- 西回り伏木循環線 (green)
- 西回り伏木循環線 (green)
- 西回り伏木循環線(矢田止) (green)
- 高岡法科大学線 (green)
- 高岡法科大学線 (green)
- 高岡法科大学線 (green)
- 高岡駅南口~新高岡駅 (green)
- 高岡駅南口~新高岡駅 (green)
- 高岡駅南口~済生会高岡病院 (green)
- 高岡駅南口~済生会高岡病院 (green)
| Route | Type | Line color |
|---|---|---|
| ふしき病院経由 氷見線 | Bus | green |
| ふしき病院経由 氷見線 | Bus | green |
| アウトレットシャトル | Bus | green |
| アウトレットシャトル | Bus | green |
| 中田町線 | Bus | green |
| 中田町線 | Bus | green |
| 仏生寺経由 氷見線 | Bus | green |
| 仏生寺経由 氷見線 | Bus | green |
| 伏木駅経由 氷見 | Bus | green |
| 伏木駅経由 氷見線 | Bus | green |
| 加越線 | Bus | green |
| 加越線 | Bus | green |
| 南波岡線 | Bus | green |
| 南波岡線 | Bus | green |
| 南砺・金沢線 | Bus | green |
| 南砺・金沢線 | Bus | green |
| 南砺・金沢線 | Bus | green |
| 南砺・金沢線 | Bus | green |
| 国吉線 | Bus | green |
| 国吉線 | Bus | green |
| 富大高岡循環線 | Bus | green |
| 富山高専線(※高専指定日のみ運行) | Bus | green |
| 富山高専線(※高専指定日のみ運行) | Bus | green |
| 小牧線 | Bus | green |
| 小牧線 | Bus | green |
| 小牧線 | Bus | green |
| 小牧線 | Bus | green |
| 市内②-③系統 | Bus | green |
| 市内③系統 | Bus | green |
| 市内④-①系統 | Bus | green |
| 市内④系統 | Bus | green |
| 庄川町線 | Bus | green |
| 庄川町線 | Bus | green |
| 庄川町線 | Bus | green |
| 庄川町線 | Bus | green |
| 庄川町線 | Bus | green |
| 庄川町線 | Bus | green |
| 戸出東部小学校線(※学校指定日のみ運行) | Bus | green |
| 戸出東部小学校線(※学校指定日のみ運行) | Bus | green |
| 東回り伏木循環線 | Bus | green |
| 氷見高校線 | Bus | green |
| 灘浦海岸・守山経由氷見線 | Bus | green |
| 灘浦海岸・守山経由氷見線 | Bus | green |
| 灘浦海岸・守山経由氷見線 | Bus | green |
| 灘浦海岸・守山経由氷見線 | Bus | green |
| 石動OL福岡町線 | Bus | green |
| 石動OL福岡町線 | Bus | green |
| 石動OL福岡町線 | Bus | green |
| 石動OL福岡町線 | Bus | green |
| 石堤循環線 | Bus | green |
| 砺波総合病院線 | Bus | green |
| 砺波総合病院線 | Bus | green |
| 砺波総合運動公園線 | Bus | green |
| 砺波総合運動公園線 | Bus | green |
| 第一高校線(※学校指定日のみ運行) | Bus | green |
| 第一高校線(※学校指定日のみ運行) | Bus | green |
| 脇・氷見線 | Bus | green |
| 若林線 | Bus | green |
| 若林線 | Bus | green |
| 西回り伏木循環線 | Bus | green |
| 西回り伏木循環線 | Bus | green |
| 西回り伏木循環線 | Bus | green |
| 西回り伏木循環線 | Bus | green |
| 西回り伏木循環線(矢田止) | Bus | green |
| 高岡法科大学線 | Bus | green |
| 高岡法科大学線 | Bus | green |
| 高岡法科大学線 | Bus | green |
| 高岡駅南口~新高岡駅 | Bus | green |
| 高岡駅南口~新高岡駅 | Bus | green |
| 高岡駅南口~済生会高岡病院 | Bus | green |
| 高岡駅南口~済生会高岡病院 | Bus | green |
This feed has 697 stops.
List every stop
- 高岡駅前3番のりば
- 高岡駅前4番のりば
- 高岡駅前5番のりば
- 高岡駅前
- 末広町3番のりば
- 末広町4番のりば
- 末広町
- 片原町
- 片原町
- 坂下町
- 坂下町
- 急患医療センター前
- 急患医療センター前
- 広小路
- 広小路
- 広小路
- 大坪町
- 大坪町
- 縄手中町
- 縄手中町
- 内免
- 内免
- 西大路
- 西大路
- 四ツ屋
- 四ツ屋
- 長慶寺住宅前
- 長慶寺住宅前
- 長慶寺
- 長慶寺
- 長慶寺工場前
- 長慶寺工場前
- 新守山
- 新守山
- 海老坂
- 海老坂
- 小竹
- 小竹
- 国泰寺前
- 国泰寺前
- 下田子
- 下田子
- 上泉
- 上泉
- 柳田(守山経由)
- 柳田(守山経由)
- 本江口
- 柳田口(守山経由)
- 柳田口(守山経由)
- 本町(砺波)
- 本町(砺波)
- 佐加野新町
- 佐加野新町
- 岩坪西
- 高岡支援学校前
- 高岡支援学校前
- 清水
- 太田小学校前
- 太田小学校前
- 窪
- 窪
- ハローワーク小矢部前
- ハローワーク小矢部前
- イオンモールとなみ
- イオンモールとなみ
- 砺波総合病院前
- 窪中央
- 窪中央
- 工芸高校前
- 工芸高校前
- 文化の森前
- 文化の森前
- 伊勢大町
- 伊勢大町
- 氷見駅口
- 氷見駅口
- 中村記念病院前
- 中村記念病院前
- 氷見駅前
- 柴野
- 伏木錦町
- 伏木錦町
- 高岡ふしき病院
- 南大町口
- 南大町口
- 二上町
- 富大高岡キャンパス
- 氷見本町
- 氷見本町
- 比美町
- 比美町
- 砺波総合運動公園前
- 下麻生北
- 下麻生北
- 氷見中央(1)
- 氷見中央(1)
- 常国団地
- 常国団地
- 常国西
- 常国西
- 加納神社前
- 加納神社前
- 豊町
- 豊町
- スポーツコア
- スポーツコア
- 氷見高校前
- 柳田南
- 柳田南
- 泊 民宿磯波風
- 泊 民宿磯波風
- 北大町(道の駅氷見)
- 北大町(道の駅氷見)
- 池田浜
- 池田浜
- 下麻生
- 下麻生
- 鎮守の森公園前
- 伏木旭町
- 伏木旭町
- 小竹北
- 小竹北
- 氷見栄町
- 氷見栄町
- 下関公民館口
- 下関公民館口
- 瑞龍寺口
- 瑞龍寺口
- 京田
- 京田
- 間島
- 間島
- 高岡オフィスパーク
- 高岡オフィスパーク
- 阿尾
- 阿尾
- 北阿尾
- 北阿尾
- ひみ阿尾の浦温泉
- ひみ阿尾の浦温泉
- 薮田
- 薮田
- 小杉
- 小杉
- 中泊
- 中泊
- 岩井戸温泉
- 岩井戸温泉
- 宇波
- 宇波
- 脇方
- 脇方
- 小境
- 小境
- 大境
- 大境
- 九殿浜温泉ひみのはな
- 九殿浜温泉ひみのはな
- 砺波駅南
- 姿
- 姿
- 中田口
- 中田口
- 中田
- 中田
- 女子口
- 女子口
- 中波
- 中波
- 田中
- 田中
- 脇
- 脇
- 堀内
- 三郎丸
- 三郎丸
- 東部小学校前
- 東部小学校前
- 秋元
- 秋元
- 東開発
- 東開発
- となみ野大橋詰
- となみ野大橋詰
- 北明太子堂
- 農協庄東支店前
- 庄東センター
- ユニクロ前
- ユニクロ前
- 太郎丸三丁目
- 太郎丸三丁目
- 本町中央
- 本町中央
- 新富町南
- 新富町南
- 寿町
- 寿町
- 志貴野中学校前
- 志貴野中学校前
- ハローワーク高岡前
- ハローワーク高岡前
- 江尻
- 江尻
- 旭ヶ丘
- 旭ヶ丘
- 荻布
- 荻布
- 新能町
- 新能町
- 米島口
- 米島口
- 米島
- 米島
- 高美町
- 高美町
- 矢田
- 矢田
- 串岡
- 串岡
- 古府口 東亞合成高岡工場前
- 古府口 東亞合成高岡工場前
- 伏木駅前
- 伏木駅前
- 伏木中央町
- 伏木中央町
- 玉川
- 玉川
- 国分港
- 国分港
- 国分
- 国分
- 国分口
- 国分口
- 岩崎口
- 岩崎口
- 岩崎(道の駅雨晴)
- 岩崎(道の駅雨晴)
- 大島分庁舎前
- 大島分庁舎前
- 雨晴駅前
- 雨晴駅前
- 雨晴
- 雨晴
- 辰の口
- 辰の口
- 松太枝浜
- 松太枝浜
- 太田(伏木)
- 太田(伏木)
- 伊勢領(氷見)
- and 447 more (see the full list on the map or in the GeoJSON)
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
7 findings, ordered by severity.
Show every finding
- Error1 instance
The realtime feed's last update was about 2 hours old when sampled.
A realtime feed this far behind has effectively stopped. Riders see buses that already left, or apps quietly fall back to the schedule while still showing a live label.
Fix: Ask your AVL vendor why the feed stopped advancing; the GTFS-Realtime header timestamp should move forward on every publish. (A vendor support ticket; treat it as a feed outage.)
Validator rule: scorecard_rt_feed_lapsed
- Warning63142 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)
- Warning697 instances
697 of 697 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)
- Warning573 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)
- Warning499 instances
499 of 499 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)
- Warning37 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)
- Warning9 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_short_name_too_long · 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 251 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.
Realtime reliability
The realtime feed responded on 100.0% of 1 checks, with 7779s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 251 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 72 / 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 50 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
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/kaetsuno-route-bus/2026-07-23.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-23. 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.