Feed status · checked 2026-07-23
Mie Kotsu Yokkaichi (三重交通 四日市営業所)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Mie, 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 73 minutes ago; last changed 73 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 9 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
603 of 603 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
1374 of 1374 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 92 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 2041 instances (0 error, 2034 warning, 7 informational).
Service data covers the next 92 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 9 times outside service hours: 3 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
This feed has no route shapes, so the map shows its stops only.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| 桜花台線 | Bus | green (no shape in feed) |
| かわしま線 | Bus | green (no shape in feed) |
| 小杉線 | Bus | green (no shape in feed) |
| 羽津山線 | Bus | green (no shape in feed) |
| 名古屋桜台高速線 | Bus | green (no shape in feed) |
| 三重団地笹川線 | Bus | green (no shape in feed) |
| 泊山医療センター線 | Bus | green (no shape in feed) |
| 美里あがたヶ丘線 | Bus | green (no shape in feed) |
| 水沢線（室山） | Bus | green (no shape in feed) |
| 水沢線（笹川） | Bus | green (no shape in feed) |
| 四日市福王山線 | Bus | green (no shape in feed) |
| 神前高角線 | Bus | green (no shape in feed) |
| 湯の山線 | Bus | green (no shape in feed) |
| 磯津高花平線 | Bus | green (no shape in feed) |
| 東日野四日市港線 | Bus | green (no shape in feed) |
| 四日市平田線 | Bus | green (no shape in feed) |
| こにゅうどうくんライナー | Bus | green (no shape in feed) |
This feed has 603 stops.
List every stop
- 名古屋（名鉄バスセンター）
- 名古屋（名鉄バスセンター）
- 田光
- 福王山
- Ｆ田口南
- ＪＲ四日市
- ＪＲ四日市
- 市役所前（四日市）
- 市役所前（四日市）
- 近鉄四日市
- 近鉄四日市
- 近鉄四日市
- 近鉄四日市
- 近鉄四日市
- 近鉄四日市
- 近鉄四日市
- 近鉄四日市
- 近鉄四日市
- 近鉄四日市
- 鵜の森前
- 鵜の森前
- 十七軒町
- 十七軒町
- 四日市南警察前
- 四日市南警察前
- 中央緑地公園前
- 中央緑地公園前
- 中央緑地公園前
- 日永駅前
- 日永駅前
- 日野口
- 西日野
- 西日野
- 四郷小学校前
- 四郷小学校前
- 室山
- 室山
- 室山西
- 室山西
- 八王子
- 波木道（室山通り）
- 狭間道
- 狭間道
- 高花平口
- 高花平口
- 高花平
- 高花平
- 小林町東
- 小林町東
- 小林町東
- 小林町東
- 小林新田
- 内山道
- 内山道
- 小林町西
- 小林町西
- 神明町
- 小山
- 幸福村口
- 大沢
- 大沢
- 青木
- 茶屋町
- 中谷
- 水沢本町
- 水沢市民センター
- 水沢西条
- 三本松（四日市）
- 林
- 宮妻口
- 丸文前
- 野田
- 大久保
- 椿神社口
- 山本
- 椿大神社
- 高花平小学校前
- 高花平小学校前
- 高花平三丁目
- 高花平三丁目
- 山田（四日市）
- 山田中
- 小山田市民センター前
- 小山田病院
- 笹川三丁目
- 南八王子
- 日永カヨー
- 日永カヨー
- 日永カヨー
- 日永カヨー
- イオンタウン四日市泊
- 泊町
- 泊町
- 追分駅前
- 追分駅前
- 小古曽
- 小古曽
- 森ヶ山
- 森ヶ山
- 小古曽六丁目
- 小古曽六丁目
- 内部駅前
- 内部駅前
- 内部橋
- 内部橋
- 内部橋
- 内部農協前
- 内部農協前
- 内部小学校前
- 内部小学校前
- 古市場
- 貝家
- 貝家
- 小松（四日市）
- 下大久保
- 久間田
- 堀木
- 堀木
- 市立図書館前
- 市立図書館前
- 市立病院（四日市）
- 久保田
- 久保田
- 西伊倉
- 西伊倉
- 大井手
- 大井手
- 川島
- 川島
- 高角
- 高角
- 近鉄湯の山温泉駅
- 近鉄湯の山温泉駅
- 保養所前（菰野）
- 保養所前（菰野）
- 清気橋
- 湯の山温泉・御在所ロープウエイ前
- 諏訪（四日市）
- 諏訪（四日市）
- 生桑道
- 生桑道
- 生桑道
- 生桑道
- 坂部（四日市）
- 坂部（四日市）
- 坂部（四日市）
- 坂部（四日市）
- 坂部口
- 坂部口
- 西坂部
- 西坂部
- 御館
- 御館
- 大池
- 大池
- 下海老町
- 下海老町
- 赤水
- 赤水
- 上海老町
- 上海老町
- 元町（四日市）
- 元町（四日市）
- ファムタウン四日市上海老
- メリノール前
- 四日市橋
- 四日市橋
- 川原町
- 川原町
- 海蔵橋
- 海蔵橋
- 金場町
- 金場町
- 南垂坂
- 南垂坂
- 垂坂
- 阿倉川駅口
- 阿倉川駅口
- 羽津山町
- 羽津山町
- 四日市羽津医療センター
- 四日市羽津医療センター
- 山手中学校前
- 山手中学校前
- 羽津山住宅口
- 羽津山
- 羽津山
- 三ッ谷
- 阿倉川駅前
- 東阿倉川口
- 東阿倉川
- 海蔵神社
- 西阿倉川口
- 西阿倉川
- みゆきヶ丘
- 小杉郵便局前
- 小杉
- 新小杉
- 中尾平
- 中尾平
- 四商前
- 四商前
- 毘沙門前
- 生桑町
- 生桑町
- 新正
- 新正
- 磯津東町
- センター前（四日市）
- センター前（四日市）
- 三重四丁目
- 三重四丁目
- 三重四丁目
- 三重四丁目
- 三重六丁目
- 三重六丁目
- 三重団地
- 神前大日山
- 神前大日山
- 智積口
- 智積口
- 桜台口
- 桜台口
- 桜台二丁目
- 桜台二丁目
- 桜台南
- 桜台南
- 桜台
- 赤堀
- 赤堀
- 常磐農協前
- 常磐農協前
- 城西町
- 城西町
- 常磐小学校前
- 常磐小学校前
- ときわ一丁目
- ときわ一丁目
- 中川原駅前
- 中川原駅前
- 伊倉
- 伊倉
- 南日永
- 南日永
- 日永西
- 日永西
- 笹川中学校
- 笹川中学校
- 笹川東
- 笹川東
- and 353 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
11 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
- Warning1417 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)
- Warning1374 instances
1374 of 1374 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)
- Warning615 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning603 instances
603 of 603 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)
- 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 (opens the validator rules on an external site)
- Warning1 instance
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info32 instances
About 32 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info4 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)
- Info3 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 (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 92 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 9392s 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 92 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 75 / 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 52 / 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.
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/mie-kotsu-yokkaichi/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.