Feed status · checked 2026-07-19
Fukutsu Mini-Bus (ふくつミニバス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Fukuoka, 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 8 hours ago; last changed 8 hours ago.
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
241 of 241 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
44 of 44 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 3 kinds of issue across 1870 instances (0 error, 1868 warning, 2 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
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.
- ふくつミニバス １福間周回線 (orange)
- ふくつミニバス ２津屋崎線 (teal)
- ふくつミニバス ３上西郷線 (red)
- ふくつミニバス ４勝浦線 (green)
- ふくつミニバス ５東福間・若木台線 (purple)
- ふくつ乗合タクシー (yellow)
| Route | Type | Line color |
|---|---|---|
| ふくつミニバス １福間周回線 | Bus | orange |
| ふくつミニバス ２津屋崎線 | Bus | teal |
| ふくつミニバス ３上西郷線 | Bus | red |
| ふくつミニバス ４勝浦線 | Bus | green |
| ふくつミニバス ５東福間・若木台線 | Bus | purple |
| ふくつ乗合タクシー | Bus | yellow |
This feed has 241 stops.
List every stop
- 東福間３丁目１
- 花見市営住宅前
- 花見市営住宅前
- 花見公民館前
- 花見公民館前
- ふくまりん前
- ふくまりん前
- 福間小入口
- 福間小入口
- グリーンタウン入口
- グリーンタウン入口
- 手光南１
- 手光南２（ふくとぴあ南）
- 手光公民館前
- 手光公民館前
- 八竜神社前
- 八竜神社前
- 花見の里３丁目
- 花見の里３丁目
- 福間南５丁目
- 福間南５丁目
- 有弥の里２
- 有弥の里２
- 宮司５丁目
- 宮司５丁目
- 上田医院前
- 上田医院前
- 戸井手
- 戸井手
- 本木入口
- 畦町
- 朝日ヶ丘団地
- ゆめマート津屋崎前
- ゆめマート津屋崎前
- 津屋崎小学校前
- 津屋崎小学校前
- 名糖前
- 名糖前
- 五反田
- 五反田
- あけぼの
- あけぼの
- 桜川
- 桜川
- 東福間５丁目
- 東福間２丁目
- 高平公民館前
- 東福間３丁目２
- 勝浦局前
- 勝浦局前
- 松原
- 松原
- 原町１区２
- 原町１区２
- 百田公園前
- 百田公園前
- 末広橋
- 末広橋
- 魚センター前
- 魚センター前
- 渡公民館
- 渡公民館
- 田ノ浦
- 田ノ浦
- 池尻
- 池尻
- 末広
- 末広
- 大石下
- 津屋崎
- 津屋崎
- なまずの郷
- なまずの郷
- けんじえん前
- けんじえん前
- 原町２区
- 原町２区
- 福津市文化会館前
- 福津市文化会館前
- 格納庫前
- 格納庫前
- 有弥の里１
- 有弥の里１
- 粟島神社前
- 粟島神社前
- 原町公民館東口
- 原町公民館東口
- 原町１区１
- 原町１区１
- 宮城病院前
- ふくとぴあ
- 総合病院前
- 総合病院前
- 四角
- 四角
- 教安寺前
- 教安寺前
- 堅川入口
- 新海
- カメリアステージ
- 東町
- 東町
- 宮地浜
- 宮地浜
- 宮司コミュニティセンター
- 宮司コミュニティセンター
- 宮司４丁目
- 宮司４丁目
- 福津市役所前
- 福津市役所前
- 宮地岳宮前
- 宮地岳宮前
- 宮司３丁目
- 宮司３丁目
- 若木台６丁目１
- 若木台６丁目１
- 八並北口
- 八並北口
- 本木中
- 立石
- 畦町公民館前
- 畦町入口
- 第２朝日ヶ丘団地
- 内殿公民館前
- JR福間駅みやじ口
- 内殿
- 内殿
- 上西郷
- 上西郷
- 板見坂集会所前
- 板見坂集会所前
- ふれあい広場ふくま
- 鞍掛
- 鞍掛
- イオンモール福津
- 光陽台２丁目
- 光陽台２丁目
- 光陽台３丁目
- 光陽台３丁目
- 手光
- 手光
- 図書館前
- 図書館前
- 本町
- 本町
- 光陽台１丁目
- 光陽台１丁目
- 末広東
- 塩浜口
- 塩浜口
- 塩浜公民館前
- 塩浜公民館前
- 新町
- 新町
- 奴山口
- 奴山口
- 勝浦クリニック前
- 勝浦クリニック前
- 勝浦小学校前
- 東
- 東
- 勝浦浜
- 緑町公民館前
- 緑町公民館前
- あんずの里
- 練原
- 練原
- 津屋崎園前
- 津屋崎園前
- 奴山公民館前
- 昭和学園前（新原奴山古墳群前）
- 昭和学園前（新原奴山古墳群前）
- 生家サンドリーム前
- 生家サンドリーム前
- 大石
- 大石
- 須多田公民館前
- 須多田公民館前
- 在自
- 在自
- 星ヶ丘市営住宅前
- 星ヶ丘市営住宅前
- 西福間３丁目１
- 西福間３丁目１
- 星ヶ丘公民館前
- 星ヶ丘公民館前
- 星ヶ丘入口
- 星ヶ丘入口
- 宮司ヶ丘
- 宮司ヶ丘
- 宮司ヶ丘入口
- 宮司ヶ丘入口
- 太郎丸
- 太郎丸
- 大和町
- 大和町
- JR東福間駅若木台口
- 若木台１丁目
- 若木台１丁目
- 若木台幼稚園前
- 若木台幼稚園前
- 若木台５丁目１
- 若木台５丁目１
- 西福間３丁目２
- 西福間３丁目２
- 小田ノ裏
- 小田ノ裏
- 山中
- 山中
- 吉原
- 吉原
- 若木台６丁目２
- 若木台６丁目２
- 若木台６丁目３
- 若木台６丁目３
- 若木台５丁目２
- 若木台５丁目２
- 若木台４丁目
- 若木台４丁目
- 若木台３丁目１
- 若木台３丁目１
- 若木台３丁目２
- 若木台３丁目２
- 若木台２丁目１
- 若木台２丁目１
- 南町公民館前
- 南町公民館前
- 若木台２丁目２
- 若木台２丁目２
- 東福間病院前
- 東福間病院前
- JR東福間駅東福間口
- 東福間郵便局前
- 東福間公民館前
- 神興幼稚園前
- 東福間８丁目１
- 東福間８丁目２
- 東福間団地集会所前
- 東福間７丁目
- 花見が浜
- 花見が浜
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
5 findings, ordered by severity.
Show every finding
- Warning1811 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)
- Warning241 instances
241 of 241 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)
- Warning57 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)
- Warning44 instances
44 of 44 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)
- Info2 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 84 / 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/fukutsu-city-mini-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.