Feed status · checked 2026-10-21
Mie Kotsu Matsusaka (三重交通 松阪営業所)
Based on the official feed source on file
Service mode Bus
down 1.0 since 2026-10-20
Cataloged in Mie, Japan.
Source feed: https://api.gtfs-data.jp/v2/organizations/mie-kotsu/feeds/sancomatsusaka/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 35 minutes ago; last changed 35 minutes 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 9 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
Mie Kotsu Matsusaka (三重交通 松阪営業所)’s published feed lists 11 bus routes, 356 scheduled trips and 370 stops. Its service dates run from 2026-10-01 through 2027-01-22. It publishes realtime trip updates, vehicle positions and service alerts; when we checked, all of them answered. The published file last changed on 2026-10-21.
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
370 of 370 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 370 stops in the feed.
⏱ 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
356 of 356 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 356 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Review the flagged fields and fill in the ones your riders would use.
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.
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.
⏱ A field at a time; not urgent.worth about +8 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.
Fix 01 · 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.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_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.
Fix 03 · Read the fix guide for missing_recommended_field
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 93 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
- Live-arrival data covered 88.9% of scheduled trips in the sampled window.
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 5 kinds of issue across 1126 instances (0 error, 1119 warning, 7 informational).
Service data covers the next 93 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: 3 of 3 configured feeds healthy; 88.9% of scheduled trips had live predictions; vehicle position plausibility was not measurable; predictions ran a median of 70s behind schedule.
Routes and stops
This feed has no route shapes, so the map shows its stops only.
This feed has 370 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.
| 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) |
List every stop
- 松阪駅前
- 松阪駅前
- 松阪駅前
- 愛宕町
- 愛宕町
- 茶与町
- 茶与町
- 春日町
- 春日町
- 大黒田小林
- 大黒田小林
- 新黒田町
- 新黒田町
- 黒田新田
- 黒田新田
- 小黒田
- 小黒田
- 田村
- 田村
- 中部中学校口
- 中部中学校口
- 立野
- 立野
- 松尾小学校口
- 松尾小学校口
- 丹生寺
- 丹生寺
- 桂瀬
- 桂瀬
- 寺井
- 寺井
- 大河内小学校前
- 大河内小学校前
- 広坂
- 広坂
- 大河内
- 大河内
- 脇谷
- 脇谷
- 辻原
- 辻原
- 辻原
- 瀬戸
- 瀬戸
- 六呂木
- 六呂木
- 小片野
- 小片野
- 南小学校前
- 南小学校前
- 大石
- 不動前
- 大石幼稚園前
- 大石幼稚園前
- 大石本郷
- 東村
- 東村
- 深野
- 深野
- 柿野学校前
- 柿野学校前
- 柿野
- 赤滝
- 赤滝
- 千才橋
- 畑井
- 畑井
- 粥見神社前
- 粥見神社前
- 飯南地域振興局
- 飯南地域振興局
- 伊勢寺
- 観音前
- 観音前
- 飯南高校前
- 飯南高校前
- 柏野（松阪）
- 虻野
- 虻野
- 堀出
- 堀出
- 東出（松阪）
- 宮前学校前
- 宮前学校前
- 宮前車庫前
- 宮前車庫前
- 国分寺
- 野々口
- 野々口
- 作滝
- 作滝
- 向赤桶
- 向赤桶
- 赤桶
- 赤桶
- 片栗子
- 片栗子
- 田引口
- 田引口
- 田引
- 田引
- 九十九曲
- 九十九曲
- 粟野
- 粟野
- 向粟野
- 向粟野
- 粟野農協前
- 川俣橋
- 富永（松阪）
- 富永（松阪）
- 大谷橋
- 杢原
- 七日市
- 上り
- 森深野
- 森
- 森
- 横滝口
- 家野
- 木屋切
- 多気中学校前
- 多気中学校前
- シャープ正門前
- シャープ南
- シャープ南
- 相可台公園前
- 相可台公園前
- 多気町役場前
- 多気町役場前
- 多気町役場前
- 仁田
- 仁田
- ツヅラ又橋
- 上辻原
- 阪内御所
- 不動橋
- 阪内
- 阪内
- 細野
- 柚原
- 駅部田
- 駅部田
- 御殿山口
- 御殿山口
- 篠田山
- 篠田山
- 厚生病院前
- 厚生病院前
- 蛸路
- 蛸路
- 蛸路
- 蛸路
- 八太
- 八太
- 八太
- 射和
- 相可一区
- 相鹿上神社前
- 相鹿上神社前
- 五桂口
- 五桂口
- 佐奈
- 佐奈
- 平谷
- 平谷
- 前村
- 前村
- 井戸谷
- 井戸谷
- おきん茶屋
- おきん茶屋
- 栃原駅口
- 栃原駅口
- 栃原
- 栃原
- 神瀬
- 神瀬
- 楠ヶ野
- 楠ヶ野
- 下楠
- 下楠
- 川添
- 川添
- 粟生頭首湖前
- 粟生頭首湖前
- 粟生
- 粟生
- 高奈
- 高奈
- 下三瀬
- 下三瀬
- 上三瀬
- 上三瀬
- 上三瀬西
- 上三瀬西
- 三瀬谷
- 道の駅奥伊勢おおだい
- VISON （ヴィソン）
- VISON （ヴィソン）
- 上蛸路
- 上蛸路
- 大台厚生病院
- 阿波曽
- 庄
- 庄
- 射和幼稚園前
- 射和幼稚園前
- 本郷（松阪）
- 本郷（松阪）
- 御麻生薗
- 御麻生薗
- 広瀬
- 広瀬
- 下茅原
- 下茅原
- つばな保育園前
- つばな保育園前
- 上茅原
- 上茅原
- 上出江口
- 下蛸路
- 平生町
- 平生町
- 相可高校前
- 相可高校前
- 相可高校南
- 三重高校前
- 三重高校前
- 南郊町
- 南郊町
- 岡寺前
- 岡寺前
- 本町（松阪）
- 本町（松阪）
- 市民病院前
- 市民病院前
- 中大坪
- 中大坪
- 松阪高校前
- 花田
- 花田
- 松阪中央病院
- 西之庄
- 西之庄
- 川井町二丁目
- 川井町二丁目
- 五曲り
- 五曲り
- 西井村
- and 120 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 20 checks — down 1.0 since 2026-10-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 78.7 | first check |
| 2026-10-03 | 80.8 | up 2.1 |
| 2026-10-04 | 80.8 | no change |
| 2026-10-05 | 80.8 | no change |
| 2026-10-06 | 80.8 | no change |
| 2026-10-07 | 80.8 | no change |
| 2026-10-08 | 80.8 | no change |
| 2026-10-09 | 78.7 | down 2.1 |
| 2026-10-10 | 80.8 | up 2.1 |
| 2026-10-11 | 80.8 | no change |
| 2026-10-12 | 80.8 | no change |
| 2026-10-13 | 80.8 | no change |
| 2026-10-14 | 80.8 | no change |
| 2026-10-15 | 80.0 | down 0.8 |
| 2026-10-16 | 80.8 | up 0.8 |
| 2026-10-17 | 80.8 | no change |
| 2026-10-18 | 80.8 | no change |
| 2026-10-19 | 80.8 | no change |
| 2026-10-20 | 80.8 | no change |
| 2026-10-21 | 79.8 | down 1.0 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality down 4.6
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-21 | fb219eb6e95a | 2027-01-22 | Current rubric: see the trend above |
| 2026-10-20 | e11649a257d5 | 2027-01-21 | Current rubric: see the trend above |
| 2026-10-19 | aff80e9f216b | 2027-01-20 | Current rubric: see the trend above |
| 2026-10-18 | aae2e5d13203 | 2027-01-19 | Current rubric: see the trend above |
| 2026-10-17 | 4f101b0339bb | 2027-01-18 | Current rubric: see the trend above |
| 2026-10-16 | d163804f862a | 2027-01-17 | Current rubric: see the trend above |
| 2026-10-15 | ba6a5b6d31a6 | 2027-01-16 | Current rubric: see the trend above |
| 2026-10-14 | 6f96a5893a9e | 2027-01-15 | Current rubric: see the trend above |
| 2026-10-13 | f460af580589 | 2027-01-14 | Current rubric: see the trend above |
| 2026-10-12 | 7d73cb19d35e | 2027-01-13 | Current rubric: see the trend above |
| 2026-10-11 | f05a66a9b638 | 2027-01-12 | Current rubric: see the trend above |
| 2026-10-10 | a63a026fb894 | 2027-01-11 | Current rubric: see the trend above |
Showing the 12 most recent of 85 periods.
What changed in this feed
Grade dropped from B to C since 2026-10-20.
The feed file was re-published since 2026-10-20.
What changed inside the export
- Service now runs through 2027-01-22 (was 2027-01-21).
Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.
New since 2026-10-20 (1 finding)
- Warning1 instance
1 of 9 trips scheduled during the sampling window had no live predictions.
Finding code: scorecard_rt_trip_coverage · Read the fix guide for scorecard_rt_trip_coverage · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-10-02 this feed started at grade C. On 2026-10-03 the grade moved from C to B. On 2026-10-09 the grade moved from B to C. On 2026-10-10 the grade moved from C to B. As of 2026-10-21 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-10-21 Grade went B to C, realtime fell 5 points.
- 2026-10-10 Grade went C to B, realtime rose 10 points.
- 2026-10-09 Grade went B to C, realtime fell 10 points.
- 2026-10-03 Grade went C to B, realtime rose 10 points.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning733 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.)
Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning385 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)
- Warning370 instances
370 of 370 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)
- Warning356 instances
356 of 356 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)
- 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.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
1 of 9 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.
Fix: Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide for scorecard_rt_trip_coverage · See GTFS-Realtime reference (opens the GTFS-Realtime reference 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.)
Finding code: unknown_column · Read the fix guide for unknown_column · 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.)
Finding code: unknown_file · Read the fix guide for unknown_file · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · 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 93 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-21, with 46s 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.
Live predictions vs schedule
Arrival predictions ran a median 70s late versus the schedule, and stayed within 166s nine times in ten. They were on time (about a minute early to five late) 100.0% of the time.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 93 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 79 / 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 95 / 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 Mie
Other scorecards in Mie, 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/mie-kotsu-matsusaka/2026-10-21.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-21. 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.