Feed status · checked 2026-09-05
Keifuku Bus (京福バス)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Fukui, 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.3, validator 8.0.1.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
1535 of 1535 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
1382 of 1382 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
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
- 1535 of 1535 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
- Feed evidence
- 1382 of 1382 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Feed evidence
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- 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.
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 268 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 4 kinds of issue across 106815 instances (0 error, 106796 warning, 19 informational).
Service data covers the next 268 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
2 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.
This feed has 1535 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.
- すまいるバス南ルート (brown)
- すまいるバス東ルート (teal)
- すまいるバス北ルート (red)
- すまいるバス西ルート (green)
- もりたんバス (brown)
- 25 エンゼルランド線 (brown)
- OKABO 北回り系統 (brown)
- OKABO 南回り系統 (brown)
- 62 一乗谷東郷線 (brown)
- 48 三国丸岡線 (brown)
- 82 丸岡永平寺線 (brown)
- 31 丸岡線（田原町経由） (brown)
- 32 丸岡線（町屋町経由） (brown)
- 46 勝山大野線 (brown)
- 44 勝山大野線 (brown)
- 39 大和田丸岡線 (brown)
- 38 大和田大学病院線 (brown)
- 83 大学病院松岡線 (brown)
- 11 大安寺線 (brown)
- 55 大野線 (brown)
- 59 大野線 (brown)
- 12 学園線 (brown)
- 18 学園線（快） (brown)
- 小松空港線 (brown)
- 16 川西三国線 (brown)
- 20 幾久・新田塚線（幾久先回り） (brown)
- 21 幾久・新田塚線（福井大学前先回り） (brown)
- 恐竜バス (brown)
- 95 新保米納津線 (brown)
- 日新さんさんバス (brown)
- 47 春江丸岡線 (brown)
- 朝倉・永平寺ダイレクトバス (teal)
- 84 東尋坊線 (brown)
- 85 東尋坊線 (brown)
- 96 東尋坊線 (brown)
- 97 東尋坊線 (brown)
- 13 桜ヶ丘団地線 (brown)
- 40 森田線 (brown)
- 永平寺ライナー (brown)
- 88 永平寺線 (brown)
- 81 池見線 (brown)
- 98 海岸線 (brown)
- 74 清水グリーンライン (brown)
- 73 清水グリーンライン (brown)
- 75 清水グリーンライン (brown)
- 51 済生会問屋団地線 (brown)
- 52 済生会問屋団地線 (brown)
- 36 県立病院丸岡線 (brown)
- 26 福井総合病院線 (brown)
- 60 羽水高校線 (brown)
- 87 芦原丸岡永平寺線 (brown)
- 86 芦原丸岡永平寺線（長屋経由） (brown)
- 10 越前海岸ブルーライン (brown)
- 15 越前海岸ブルーライン (brown)
- 14 越前海岸ブルーライン (brown)
- 19 越前海岸ブルーライン (brown)
- 71 運動公園線（ベル前先回り） (brown)
- 70 運動公園線（道守高校先回り） (brown)
- 28 運転者教育センター線 (brown)
- 酒生いきいきバス (brown)
- 91 金津本荘線 (brown)
- 89 金津高校線 (brown)
- 30 高木線 (brown)
- 名古屋線 (brown)
- 80 鶉三国線 (brown)
| Route | Type | Line color |
|---|---|---|
| すまいるバス南ルート | Bus | brown |
| すまいるバス東ルート | Bus | teal |
| すまいるバス北ルート | Bus | red |
| すまいるバス西ルート | Bus | green |
| もりたんバス | Bus | brown |
| 25 エンゼルランド線 | Bus | brown |
| OKABO 北回り系統 | Bus | brown |
| OKABO 南回り系統 | Bus | brown |
| 62 一乗谷東郷線 | Bus | brown |
| 48 三国丸岡線 | Bus | brown |
| 82 丸岡永平寺線 | Bus | brown |
| 31 丸岡線（田原町経由） | Bus | brown |
| 32 丸岡線（町屋町経由） | Bus | brown |
| 46 勝山大野線 | Bus | brown |
| 44 勝山大野線 | Bus | brown |
| 39 大和田丸岡線 | Bus | brown |
| 38 大和田大学病院線 | Bus | brown |
| 83 大学病院松岡線 | Bus | brown |
| 11 大安寺線 | Bus | brown |
| 55 大野線 | Bus | brown |
| 59 大野線 | Bus | brown |
| 12 学園線 | Bus | brown |
| 18 学園線（快） | Bus | brown |
| 小松空港線 | Bus | brown |
| 16 川西三国線 | Bus | brown |
| 20 幾久・新田塚線（幾久先回り） | Bus | brown |
| 21 幾久・新田塚線（福井大学前先回り） | Bus | brown |
| 恐竜バス | Bus | brown |
| 95 新保米納津線 | Bus | brown |
| 日新さんさんバス | Bus | brown |
| 47 春江丸岡線 | Bus | brown |
| 朝倉・永平寺ダイレクトバス | Bus | teal |
| 84 東尋坊線 | Bus | brown |
| 85 東尋坊線 | Bus | brown |
| 96 東尋坊線 | Bus | brown |
| 97 東尋坊線 | Bus | brown |
| 13 桜ヶ丘団地線 | Bus | brown |
| 40 森田線 | Bus | brown |
| 永平寺ライナー | Bus | brown |
| 88 永平寺線 | Bus | brown |
| 81 池見線 | Bus | brown |
| 法恩寺リゾート線 | Bus | brown (no shape in feed) |
| 98 海岸線 | Bus | brown |
| 74 清水グリーンライン | Bus | brown |
| 73 清水グリーンライン | Bus | brown |
| 75 清水グリーンライン | Bus | brown |
| 51 済生会問屋団地線 | Bus | brown |
| 52 済生会問屋団地線 | Bus | brown |
| 36 県立病院丸岡線 | Bus | brown |
| 26 福井総合病院線 | Bus | brown |
| 60 羽水高校線 | Bus | brown |
| 芝政ワールド線 | Bus | brown (no shape in feed) |
| 87 芦原丸岡永平寺線 | Bus | brown |
| 86 芦原丸岡永平寺線（長屋経由） | Bus | brown |
| 10 越前海岸ブルーライン | Bus | brown |
| 15 越前海岸ブルーライン | Bus | brown |
| 14 越前海岸ブルーライン | Bus | brown |
| 19 越前海岸ブルーライン | Bus | brown |
| 71 運動公園線（ベル前先回り） | Bus | brown |
| 70 運動公園線（道守高校先回り） | Bus | brown |
| 28 運転者教育センター線 | Bus | brown |
| 酒生いきいきバス | Bus | brown |
| 91 金津本荘線 | Bus | brown |
| 89 金津高校線 | Bus | brown |
| 30 高木線 | Bus | brown |
| 名古屋線 | Bus | brown |
| 80 鶉三国線 | Bus | brown |
List every stop
- ＮＴＴ勝山前
- ＮＴＴ勝山前
- 立石交差点
- 立石交差点
- 南校前
- 南校前
- 毛屋
- 毛屋
- 北市
- 北市
- 若猪野
- 若猪野
- 猪野口
- 猪野口
- 大渡
- 大渡
- 下荒井
- 下荒井
- あっ宝んど
- 新在家
- 新在家
- 南新在家
- 南新在家
- 自動車学校前
- 自動車学校前
- 中津川
- 中津川
- 東中津川
- 東中津川
- 東中野
- 東中野
- 中野
- 中野
- 大野口
- 大野口
- 重藤公園口
- 重藤公園口
- 護国神社口
- 護国神社口
- 藤島高校前
- 藤島高校前
- 市立図書館前
- 市立図書館前
- 明道中学校前
- 明道中学校前
- 田原町
- 田原町
- 県立大学
- グリーンセンター口
- グリーンセンター口
- グリーンセンター
- 体育館前
- 西松本
- 西松本
- 久保町
- 久保町
- 仁愛女子高校
- 平章小学校前
- 平章小学校前
- 霞町
- 霞町
- 三国南校
- 三国南校
- 錦四丁目
- 錦四丁目
- 裁判所前
- 裁判所前
- 称名寺前
- 称名寺前
- 大名町
- 大名町
- 雄島
- 郷土歴史博物館
- 城町
- 城町
- 養浩館口江戸上町
- 養浩館口江戸上町
- 有楽町
- 有楽町
- 二の宮
- 二の宮
- 二の宮四丁目
- 二の宮四丁目
- 新田塚町
- 新田塚町
- 福大附属特別支援学校
- 福大附属特別支援学校
- 松本二丁目
- 松本二丁目
- 堀ノ宮第２
- 堀ノ宮第２
- 三郎丸団地
- 三郎丸団地
- 武道館前
- 武道館前
- 剣大谷
- 剣大谷
- 鷹巣公民館前
- 鷹巣公民館前
- 松本三丁目
- 松本三丁目
- 木田さざんか児童館
- 木田さざんか児童館
- 木田小学校前
- 木田小学校前
- 木田町
- 木田町
- 県職員住宅前
- 県職員住宅前
- 南木田
- 南木田
- 板垣五丁目
- 板垣五丁目
- 羽水高校前
- 羽水高校前
- 羽水二丁目
- 羽水二丁目
- 町屋町
- 町屋町
- 松本小学校前
- 松本小学校前
- 医師会館口
- 医師会館口
- 二の宮三丁目
- 二の宮三丁目
- 二の宮三丁目第２
- 二の宮三丁目第２
- 二の宮郵便局前
- 二の宮郵便局前
- 幾久
- 幾久
- アピタ・エルパ前
- 幾代二丁目
- 幾代二丁目
- 二の宮二丁目
- 二の宮二丁目
- 県立歴史博物館前
- 県立歴史博物館前
- 有楽町本町
- 有楽町本町
- 計石第２
- 計石第２
- 川上
- 川上
- 下丁
- 下丁
- 犬山
- 犬山
- 大野市休日急患診療所前
- 大野市休日急患診療所前
- 糸魚町
- 糸魚町
- 宮前町
- 宮前町
- 河増団地
- 河増団地
- 幾久公園
- 幾久公園
- 福井総合病院
- 福井医療大学
- あさくら水の駅
- あさくら水の駅
- 安波賀第２
- 安波賀第２
- 啓蒙小学校口
- 啓蒙小学校口
- 開発口
- 開発口
- 五万堂
- 五万堂
- 明里町
- 明里町
- 明里町
- 自治会館前
- 自治会館前
- 高木中央
- 高木中央
- 高木中央二丁目
- 高木中央二丁目
- 県立病院
- 新米松
- 新米松
- 八幡神社前
- 八幡神社前
- 福井競輪場前
- 福井競輪場前
- 四ツ井本町
- 四ツ井本町
- 日之出小学校前
- 日之出小学校前
- パリオ前
- パリオ前
- 南四ツ居
- 南四ツ居
- 自動車学校入口
- 自動車学校入口
- 上北野
- 上北野
- 東安居団地入口
- 加茂河原二丁目
- 加茂河原二丁目
- 西学園町
- 飯塚町
- 問屋団地西口
- 問屋団地西口
- 成和公園
- 成和公園
- 土木事務所前
- 加茂河原三丁目
- 加茂河原三丁目
- 高木北
- 北前公園前
- スキージャム勝山
- 小幡町藤田医院
- 小幡町藤田医院
- Ｃ・ネットふくい
- 休暇村越前三国
- けやき台
- けやき台
- 桜ケ丘第２
- 桜ケ丘第３
- ふくい鮮いちば口
- ふくい鮮いちば口
- 卸売市場前
- 卸売市場前
- 卸売市場前
- 安川病院前
- 安川病院前
- フェアモール福井
- フェアモール福井
- 大和田町
- 大和田町
- 堂島町
- 堂島町
- 泉田
- 泉田
- 北野上町
- 北野上町
- 團助本店前
- 團助本店前
- 志比南小学校前
- 志比南小学校前
- 勝見二丁目
- 勝見二丁目
- 豊島東公園口
- 豊島東公園口
- 花月新町
- 花月新町
- 渡団地入口
- 渡団地入口
- and 1285 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
6 findings, ordered by severity.
Show every finding
- Warning105492 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)
- Warning1535 instances
1535 of 1535 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 (opens the GTFS Schedule reference on an external site)
- Warning1382 instances
1382 of 1382 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 (opens the GTFS Schedule reference on an external site)
- Warning1290 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 (opens the validator rules on an external site)
- Warning14 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info19 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 268 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 14 of 1535 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 268 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 77 / 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/keifuku-bus/2026-09-05.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-05. 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.