GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

東北町町民バス

Based on the feed this agency publishes

Service mode Bus

71.9 / 100

First scorecard for this agency

Catalogued in Aomori, Japan.

Covers 251 daysAccessibility gapsRealtime not yet published

東北町町民バス is the public schedule named by the repository. This registry item represents one feed record.

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

Fix 01

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

320 of 320 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

Fix 02

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

34 of 34 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

Fix 03

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.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.

  1. 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.

  2. 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.

  3. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · 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
No fare information is published in the feed.
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

Correctness80.5 / 100

The MobilityData validator flagged 6 kinds of issue across 1042 instances (0 error, 1036 warning, 6 informational).

Freshness100.0 / 100

Service data covers the next 251 days.

Rider experience37.4 / 100

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 not published.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

1 accessibility depth signal

  • 1 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.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and stops

This feed has no route shapes, so the map shows its stops only.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

Routes in 東北町町民バス's feed
RouteTypeLine color
町民バス　新舘線Busorange (no shape in feed)
町民バス　虫神線Busgray (no shape in feed)
町民バス　宇道坂線Busgreen (no shape in feed)
町民バス　塔ノ沢線Busyellow (no shape in feed)
町民バス　柵線Busbrown (no shape in feed)
町民バス　細津線Busblack (no shape in feed)
町民バス　豊瀬線Busyellow (no shape in feed)
町民バス　浜台線Busred (no shape in feed)
買い物バス　乙供行Buspink (no shape in feed)
買い物バス　上北行Buspink (no shape in feed)
通勤通学バス　乙供駅・甲地・中村線Buspink (no shape in feed)
通勤通学バス　乙供駅・甲地・鶴ヶ崎線Buspink (no shape in feed)
通勤通学バス　乙供駅・保戸沢・中村線Buspink (no shape in feed)

This feed has 320 stops.

List every stop
  • 萠出
  • 萠出
  • 輝ヶ丘（東）
  • 輝ヶ丘（東）
  • 輝ヶ丘（北）
  • 輝ヶ丘（北）
  • 枋木
  • 枋木
  • 輝ヶ丘（枋木入口）
  • 輝ヶ丘（枋木入口）
  • 寒水（北）
  • 寒水（北）
  • 寒水学習センター
  • 寒水学習センター
  • 乙部
  • 乙部
  • 保戸沢
  • 保戸沢
  • 保戸沢（西）
  • 保戸沢（西）
  • 大洞
  • 大洞
  • 外蛯沢（西）
  • 外蛯沢（西）
  • Ａコープ
  • Ａコープ
  • 豊瀬集会所
  • 豊瀬集会所
  • 豊瀬（東）
  • 豊瀬（東）
  • 豊前（北）
  • 豊前（北）
  • 豊前（南）
  • 豊前（南）
  • 五十嵐（北）
  • 五十嵐（北）
  • 五十嵐（南）
  • 五十嵐（南）
  • 大池
  • 大池
  • 中村
  • 中村
  • 才市田
  • 才市田
  • 水喰
  • 水喰
  • 切左坂
  • 切左坂
  • 野田頭
  • 野田頭
  • 豊栄
  • 豊栄
  • 滝沢
  • 滝沢
  • 巴蘭（北）
  • 巴蘭（北）
  • 巴蘭（南）
  • 巴蘭（南）
  • 蒼前
  • 蒼前
  • ゆうき青森農協
  • 漆玉
  • 漆玉
  • 境ノ沢
  • 境ノ沢
  • 御料
  • 御料
  • 狼ノ沢
  • 狼ノ沢
  • 旭
  • 旭
  • 浜台（北）
  • 浜台（北）
  • 浜台（南）
  • 浜台（南）
  • 田ノ沢
  • 田ノ沢
  • 鶴ヶ崎
  • 舟ヶ沢
  • 舟ヶ沢
  • 徳万舘
  • 徳万舘
  • 新山
  • 新山
  • 土橋
  • 土橋
  • 蓼内
  • 長久保
  • 長久保
  • 甲地（南）
  • 甲地（南）
  • 甲地
  • 甲地
  • 甲地（西）
  • 外蛯沢（東）
  • 外蛯沢（東）
  • 公園団地
  • 公園団地
  • 内蛯沢（東）
  • 内蛯沢（東）
  • 内蛯沢（西）
  • 内蛯沢（西）
  • 北新山
  • 北新山
  • 緑町
  • 緑町
  • 乙供駅
  • 外蛯沢（南）
  • 外蛯沢（南）
  • サンデー・薬王堂乙供店
  • サンデー・薬王堂乙供店
  • 乙供郵便局
  • 乙供郵便局
  • 南総合運動公園
  • 南総合運動公園
  • 甲地郵便局前
  • 甲地郵便局前
  • かんぶん・ユニバース
  • かんぶん・ユニバース
  • 旭町グラウンド
  • 旭町グラウンド
  • 本村十字路
  • 本村十字路
  • 新南町
  • 新南町
  • 青森銀行上北町支店
  • 青森銀行上北町支店
  • 薬王堂上北北店
  • 薬王堂上北北店
  • 東北町役場通り
  • 東北町役場通り
  • 向平（南）
  • 向平（南）
  • 小川原（南２）
  • 小川原（南２）
  • 上北小学校
  • 上北小学校
  • 豊瀬（西）
  • 豊瀬（西）
  • 甲地（北）
  • 甲地（北）
  • 北総合運動公園入口
  • 北総合運動公園入口
  • 北総合運動公園通
  • 北総合運動公園通
  • 甲地小学校前
  • 甲地小学校前
  • 蓼内入口
  • 蓼内入口
  • 長久保東口
  • 長久保東口
  • 長崎
  • 長崎
  • 上野
  • 上野
  • 上北保健福祉センター
  • 役場
  • 役場
  • 新舘
  • 新舘
  • 中央通り
  • 中央通り
  • 上北町駅前
  • 上北町駅前
  • 南町
  • 南町
  • 旭町（上）
  • 旭町（上）
  • 旭町集会所
  • 旭町集会所
  • 旭町（下）
  • 旭町（下）
  • 小川原湖公園キャンプ場
  • 小川原湖公園キャンプ場
  • 宝湖館
  • 道の駅
  • 虫神
  • 虫神
  • 戸舘
  • 戸舘
  • 菩提寺
  • 菩提寺
  • 小川原（南１）
  • 小川原（南１）
  • 小川原（南３）
  • 小川原（南３）
  • 向山
  • 小川原駅バス停
  • 小川原駅バス停
  • 下沼崎
  • 下沼崎
  • 本村集会所
  • 栄沼
  • ワークショップ小笠原
  • 豊田
  • 八幡
  • 八幡
  • 花向町集会所入口
  • 花向踏切東口
  • 花向踏切東口
  • 丘ノ上団地
  • 丘ノ上団地
  • 宇道坂
  • 宇道坂
  • 添ノ沢（西）
  • 添ノ沢（西）
  • 添ノ沢（東）
  • 添ノ沢（東）
  • 上清水目
  • 上清水目
  • 清水目学習センター
  • 清水目学習センター
  • 下清水目
  • 下清水目
  • 石坂（湯沢）
  • 石坂（湯沢）
  • 赤平
  • 赤平
  • 千曳学供センター
  • 千曳学供センター
  • 下板橋
  • 向平（北）
  • 向平（北）
  • 上板橋（西）
  • 上板橋（東）
  • 南平集会所
  • 南平集会所
  • 南平（中央）
  • 南平（中央）
  • 南平（南）
  • 南平（南）
  • 朝日団地
  • 朝日団地
  • 馬込
  • 馬込
  • 西大浦
  • 西大浦
  • 坂下町
  • 吉田内科医院
  • 吉田内科医院
  • 東北町老人福祉センター
  • 乙供元町
  • 乙供元町
  • マエダストア乙供店
  • マエダストア乙供店
  • 旧分庁舎前
  • 旧分庁舎前
  • コミセン前
  • 東北小学校
  • 東北小学校
  • and 70 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

10 findings, ordered by severity.

Show every finding
  • Warning1010 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

  • Warning320 instances

    320 of 320 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

  • Warning34 instances

    34 of 34 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

  • Warning25 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

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

    Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • Info3 instances

    Some trip headsigns name a stop along the way, not the final destination.

    The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.

    Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)

    Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules

  • 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

  • Info1 instance

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

    Validator rule: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

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.

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 80 / 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 37 / 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.

東北町町民バス GTFS data quality grade: C

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/tohokutown-tohoku-town-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.