Feed status · checked 2026-10-15
Toyama Chitetsu Bus (富山地方鉄道バス)
Based on the official feed source on file
Service mode Bus
unchanged since 2026-10-14
Cataloged in Toyama, Japan.
Source feed: https://api.gtfs-data.jp/v2/organizations/chitetsu/feeds/chitetsubus/files/feed.zip?rid=current
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.4, validator 8.0.1.
Checked for changes 3 hours ago; last changed 14 days ago.
Measured 4 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
Toyama Chitetsu Bus (富山地方鉄道バス)’s published feed lists 178 bus routes, 1,360 scheduled trips and 1,043 stops. Its service dates run from 2026-10-01 through 2027-09-30. It publishes realtime trip updates and vehicle positions; when we checked, all of them answered. The published file last changed on 2026-10-01.
Top things to fix
Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Varies.worth about +24 points in its category
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ 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
1043 of 1043 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.
Fixing this covers all 1,043 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- The served-area need overlays cover the United States and Canada, so none of them applies to this feed.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- 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.
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.
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.
Fix 03 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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 350 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 6 kinds of issue across 99939 instances (1062 error, 98877 warning, 0 informational).
Service data covers the next 350 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.
This feed has 1043 stops.
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.
- 01 新幹線市街地線 (green)
- 01 新幹線市街地線 (green)
- 01 新幹線市街地線 (green)
- 01 新幹線市街地線 (green)
- 01 新幹線市街地線 (green)
- 01 新幹線市街地線 (green)
- 01 生地循環線 (green)
- 01 生地循環線 (green)
- 01 生地循環線 (green)
- 05 池尻線 (green)
- 05 池尻線 (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)
- 堤防・熊野経由八尾・萩の島循環線 (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)
- 布目経由・新湊線 (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)
- 西の番・大場・流杉線 (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)
| Route | Type | Line color |
|---|---|---|
| 01 新幹線市街地線 | Bus | green |
| 01 新幹線市街地線 | Bus | green |
| 01 新幹線市街地線 | Bus | green |
| 01 新幹線市街地線 | Bus | green |
| 01 新幹線市街地線 | Bus | green |
| 01 新幹線市街地線 | Bus | green |
| 01 生地循環線 | Bus | green |
| 01 生地循環線 | Bus | green |
| 01 生地循環線 | Bus | green |
| 05 池尻線 | Bus | green |
| 05 池尻線 | 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 |
| 堤防・熊野経由八尾・萩の島循環線 | 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 |
| 布目経由・新湊線 | 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 |
| 西の番・大場・流杉線 | 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 |
List every stop
- 奥田中学校前
- 奥田中学校前
- 牛島新町
- 牛島新町
- 北日本放送会館前
- 北日本放送会館前
- 湊入船町
- 湊入船町
- 双葉町
- 双葉町
- 奥田町
- 奥田町
- 奥田本町
- 奥田本町
- 千代田町
- 千代田町
- 奥田北小学校前
- 興人団地
- 下新北町３区
- 富山駅北口
- 富山駅北口
- 富山駅北口
- 富山県美術館
- 富山県美術館
- 富山駅前
- 富山駅前
- 富山駅前
- 富山駅前
- 富山駅前
- 富山駅前
- 富山駅前
- 富山駅前
- 富山市役所前
- 富山市役所前
- 富山市役所前
- 富山市役所前
- 富山市役所前
- 富山市役所前
- 富山市役所前
- 富山市役所前
- 城址公園前
- 城址公園前
- 城址公園前
- 城址公園前
- 城址公園前
- 城址公園前
- 荒町
- 荒町
- 北新町
- 北新町
- 北新町
- 東町（富山）
- 東町（富山）
- 舘出
- 舘出
- 双代町
- 双代町
- 新田中
- 新田中
- 新荒川
- 新荒川
- 東荒川
- 新庄新町
- 新庄新町
- 中新庄富山銀行前
- 中新庄富山銀行前
- 向新庄口
- 向新庄口
- 機械工業センター
- 機械工業センター
- 鶴ケ丘
- 鶴ケ丘
- 金泉寺
- 金泉寺
- 針原新町
- 針原新町
- 針原小学校前
- 針原小学校前
- 宮成口
- 宮成口
- 町袋宮条
- 町袋宮条
- 芝草口
- 芝草口
- 藤の木北口
- 藤の木小学校前
- 藤の木団地前
- 藤の木新町
- 金代
- 新金代
- 開
- 藤代町
- 町新
- 東布施口
- 田家新
- 前沢口
- 前沢口
- 雄山中学校前
- 雄山中学校前
- 貫田
- 八ツ屋口
- 大清水
- 大清水
- 東大森
- 公民館前（大森）
- 西大森
- 大橋
- 三ツ塚
- 一夜泊
- 西大森口
- 富山東高校前
- 富山東高校前
- 東富山駅口
- 東富山駅口
- 中田二丁目
- 中田二丁目
- 千原崎
- 草島
- 草島
- 荒屋（四方）
- 荒屋（四方）
- 南町
- 南町
- ちてつ四方
- 四方町
- 四方神明町
- 荒屋南部
- 荒屋南部
- 射北中学校前
- 射北中学校前
- 古明神
- 古明神
- 堀岡局前
- 堀岡局前
- 堀岡中町
- 堀岡中町
- 新港東口
- クロスベイ新湊
- 新湊きっときと市場
- 浜開
- 浜開
- 西海老江
- 西海老江
- 海老江
- 海老江
- 海老江口
- 海老江口
- 槍ケ崎口
- 槍ケ崎口
- 練合
- 練合
- 練合東口
- 練合東口
- 足洗潟公園口
- 足洗潟公園口
- 足洗西口
- 足洗西口
- 足洗
- 足洗
- 打出
- 打出
- 新出町
- 新出町
- 本江（新湊）
- 本江（新湊）
- 川の駅新湊
- 川の駅新湊
- 氷見漁港前
- ひみ番屋街
- 海王丸パーク
- 岩崎（雨晴海岸）
- 五番町
- 五番町
- 大泉町一丁目
- 大泉町一丁目
- 西大泉
- 西大泉
- 法蓮寺橋
- 法蓮寺橋
- 西公文名
- 西公文名
- 大泉中学校前
- 大泉中学校前
- 大泉駅前
- 大泉駅前
- 青葉町
- 青葉町
- 大町南部
- 大町南部
- 大町南部口
- 大町南部口
- 下堀
- 下堀
- 朝菜町六丁目
- 朝菜町駅前
- 朝菜町三丁目
- 新堀町
- 新堀町
- 上堀町
- 上堀町
- 上堀町
- 堀町中央
- 堀（高専）
- 堀（高専）
- 清住町口
- 西本郷（高専）
- 国立高専前
- 本郷四区
- 本郷町五区
- 本郷新
- 上堀駅前
- 上堀駅前
- 小杉口（福沢）
- 小杉口（福沢）
- 布市
- 布市
- 藤塚（月岡）
- 藤塚（月岡）
- 開発駅前
- 焼野
- 月岡小学校前
- 月岡小学校前
- 月岡中学校前
- 月岡中学校前
- 中布目
- 中布目
- 上今町
- 上今町
- 福沢口
- 福沢口
- 東福沢三区
- 東福沢三区
- 福沢
- 研修所前
- 研修所前
- 月岡団地
- 月岡団地
- 富山国際大学
- 月見町五丁目
- 月見町二丁目
- 月見町二丁目
- 月岡西緑町
- 南富山駅前
- 南富山駅前
- 堀川南大町
- 堀川南大町
- 富山市農協前
- 富山市農協前
- 南堀川
- 南堀川
- and 793 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 14 checks — unchanged since 2026-10-14.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 66.1 | first check |
| 2026-10-03 | 56.1 | down 10.0 |
| 2026-10-04 | 56.1 | no change |
| 2026-10-05 | 66.1 | up 10.0 |
| 2026-10-06 | 66.1 | no change |
| 2026-10-07 | 66.1 | no change |
| 2026-10-08 | 66.1 | no change |
| 2026-10-09 | 66.1 | no change |
| 2026-10-10 | 66.1 | no change |
| 2026-10-11 | 66.1 | no change |
| 2026-10-12 | 66.1 | no change |
| 2026-10-13 | 66.1 | no change |
| 2026-10-14 | 66.1 | no change |
| 2026-10-15 | 66.1 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-02 to 2026-10-15 (14 checks) | 7ae160f4501c | 2027-09-30 | Current rubric: see the trend above |
| 2026-10-01 | 7ae160f4501c | 2027-09-30 | D, 66.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-30 | 4c8996c4a4ad | 2027-09-30 | F, 54.4 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-09-29 (63 checks) | 04541ea9dfae | 2027-05-25 | C, 74.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-23 to 2026-07-24 (2 checks) | 04541ea9dfae | 2027-05-25 | C, 74.3 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
What changed over time
On 2026-10-02 this feed started at grade D. On 2026-10-03 the grade moved from D to F. On 2026-10-05 the grade moved from F to D. As of 2026-10-15 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-10-05 Grade went F to D, realtime rose 50 points.
- 2026-10-03 Grade went D to F, realtime fell 50 points.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Error1060 instances
Foreign key violation (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: foreign_key_violation · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error2 instances
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.)
Finding code: duplicate_key · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning97199 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1492 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1360 instances
1360 of 1360 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1043 instances
1043 of 1043 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning128 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.)
Finding code: duplicate_route_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning58 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.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
Two requirements remain for this feed to earn the conformance mark. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 350 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 200 checks in the 25 days to 2026-10-15, with 13s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
Clears the Google and Apple Maps four-week coverage bar. This feed has 349 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1062 validator errors, 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 32 / 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 100 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the Japan portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Toyama
Other scorecards in Toyama, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/toyama-chitetsu-bus/2026-10-15.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-10-15. 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.