Feed status · checked 2026-07-19
Tokai City Ran-Ran Bus (東海市らんらんバス)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Aichi, 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
250 of 250 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
140 of 140 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 6 kinds of issue across 3908 instances (0 error, 3904 warning, 4 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
12 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (名和線（平日）【系統１】, 名和線（休日）【系統１】, 名和線（平日）【系統２】, 名和線（休日）【系統２】, 荒尾線（平日）【系統３】, and more).
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)
- 名和線（休日）【系統１】 (orange)
- 名和線（平日）【系統２】 (orange)
- 名和線（休日）【系統２】 (orange)
- 荒尾線（平日）【系統３】 (pink)
- 荒尾線（休日）【系統３】 (pink)
- 荒尾線（平日）【系統４】 (pink)
- 荒尾線（休日）【系統４】 (pink)
- 富木島線（平日）【系統５】 (green)
- 富木島線（休日）【系統５】 (green)
- 富木島線（平日）【系統６】 (green)
- 富木島線（休日）【系統６】 (green)
- 加木屋線（平日）【系統７】 (purple)
- 加木屋線（休日）【系統７】 (purple)
- 加木屋線（平日）【系統８】 (purple)
- 加木屋線（休日）【系統８】 (purple)
- 横須賀線（平日）【系統９】 (teal)
- 横須賀線（休日）【系統９】 (teal)
- 横須賀線（平日）【系統１０】 (teal)
- 横須賀線（休日）【系統１０】 (teal)
- 横須賀線（平日）【系統１１】 (teal)
| Route | Type | Line color |
|---|---|---|
| 名和線（平日）【系統１】 | Bus | orange |
| 名和線（休日）【系統１】 | Bus | orange |
| 名和線（平日）【系統２】 | Bus | orange |
| 名和線（休日）【系統２】 | Bus | orange |
| 荒尾線（平日）【系統３】 | Bus | pink |
| 荒尾線（休日）【系統３】 | Bus | pink |
| 荒尾線（平日）【系統４】 | Bus | pink |
| 荒尾線（休日）【系統４】 | Bus | pink |
| 富木島線（平日）【系統５】 | Bus | green |
| 富木島線（休日）【系統５】 | Bus | green |
| 富木島線（平日）【系統６】 | Bus | green |
| 富木島線（休日）【系統６】 | Bus | green |
| 加木屋線（平日）【系統７】 | Bus | purple |
| 加木屋線（休日）【系統７】 | Bus | purple |
| 加木屋線（平日）【系統８】 | Bus | purple |
| 加木屋線（休日）【系統８】 | Bus | purple |
| 横須賀線（平日）【系統９】 | Bus | teal |
| 横須賀線（休日）【系統９】 | Bus | teal |
| 横須賀線（平日）【系統１０】 | Bus | teal |
| 横須賀線（休日）【系統１０】 | Bus | teal |
| 横須賀線（平日）【系統１１】 | Bus | teal |
This feed has 250 stops.
List every stop
- しあわせ村
- 元浜公園東
- 元浜公園東
- 南堀畑
- 南堀畑
- 一ノ割
- 一ノ割
- 尾張横須賀駅前
- 仲新田
- 仲新田
- 南加木屋駅西
- 南加木屋駅西
- 寺ノ前南
- 寺ノ前南
- 中平地
- 中平地
- 大清水
- 大清水
- 加木屋南公園
- 加木屋南公園
- 知北平和公園前
- 加木屋デイサービスセンター
- 東海市役所
- 東大堀
- 東大堀東
- 大堀保育園北
- 加木屋南小学校前
- 加木屋南小学校前
- 南加木屋駅東
- 南加木屋駅東
- 鎌吉良根
- 鎌吉良根
- 三ツ池小学校西
- 三ツ池小学校西
- 中部安全衛生技術センター東
- 中部安全衛生技術センター東
- 東海市消防署南出張所前
- 東海市消防署南出張所前
- 水深
- 水深
- 清水団地東
- 清水団地東
- 明倫小学校西
- 明倫小学校西
- 東海市消防署北出張所前
- 東海市消防署北出張所前
- 後山
- 後山
- 洞ケ山
- 洞ケ山
- 荒尾住宅
- 荒尾住宅
- 渡内
- 渡内
- 聚楽園駅前
- 浜須賀
- 浜須賀
- アピタ荒尾店北
- アピタ荒尾店北
- 北脇
- 北脇
- 一番畑
- 一番畑
- 名和駅前
- 名和駅東
- 名和駅東
- トドメキ
- トドメキ
- 緑陽小学校東
- 緑陽小学校東
- 大廻間池
- 大廻間池
- 緑陽台
- 緑陽台
- 八幡東
- 八幡東
- 東海町七丁目
- 東海町七丁目
- 新池
- 新池
- 長生
- 長生
- 平地公園
- 平地公園
- 新上野ケ丘
- 新上野ケ丘
- 秋葉
- 秋葉
- 二反表
- 二反表
- 石塚
- 石塚
- 濁池
- 濁池
- 第一上野ケ丘
- 第一上野ケ丘
- 加家公民館前
- 加家公民館前
- 北之山
- 北之山
- 上野中学校前
- 上野中学校前
- 東海北郵便局前
- 東海北郵便局前
- 星城大学東
- 星城大学東
- 平洲小学校北
- 平洲小学校北
- 荒尾
- 荒尾
- 寺中
- 寺中
- 新日鉄前駅前
- 岡前
- 岡前
- 名和保育園北
- 名和保育園北
- アピタ荒尾店前
- アピタ荒尾店前
- 富貴ノ台三丁目
- 富貴ノ台三丁目
- 伏見一丁目
- 伏見一丁目
- 富木島中学校前
- 富木島中学校前
- 新石根
- 新石根
- 昇録公園前
- 昇録公園前
- 富木島小学校前
- 富木島小学校前
- 東山保育園北
- 東山保育園北
- バロー上野台店南
- バロー上野台店南
- 上野台
- 上野台
- 上野台口
- 上野台口
- 藤塚
- 藤塚
- 上野台公園
- 上野台公園
- 山中団地前
- 山中団地前
- 富田
- 富田
- 姫島
- 姫島
- 伏見三丁目
- 伏見三丁目
- 白拍子橋東
- 白拍子橋東
- 白拍子
- 白拍子
- 西知多総合病院
- 中ノ池住宅口
- 中ノ池住宅口
- 高横須賀駅前
- 太田川駅前
- 太田川駅前
- 横須賀小学校北
- 横須賀小学校北
- 中ノ池六丁目
- 中ノ池六丁目
- 城之腰
- 城之腰
- 大田町公民館前
- 大田町公民館前
- 御洲浜
- 御洲浜
- 加木屋市民館前
- 加木屋市民館前
- 加木屋車庫
- 加木屋石塚
- 加木屋石塚
- 加木屋町一丁目南
- 加木屋町一丁目南
- 加木屋南市民館西
- 加木屋南市民館西
- 家下
- 家下
- 寄亀
- 寄亀
- 元浜南
- 元浜南
- 向田
- 向田
- 荒尾住宅東
- 荒尾住宅東
- 高横須賀町五丁目
- 高横須賀町五丁目
- 細田
- 細田
- 三ツ池
- 三ツ池
- 三ツ池保育園前
- 三ツ池保育園前
- 寺徳
- 寺徳
- 若宮
- 若宮
- 大池公園前
- 大池公園前
- 大田小学校入口
- 大田小学校入口
- 中ノ池二丁目
- 中ノ池二丁目
- 的場
- 的場
- 東海市リサイクルセンター前
- 東海市リサイクルセンター前
- 東海市消防本部前
- 東海市消防本部前
- 東海市創造の杜交流館南
- 東海市創造の杜交流館南
- 東海市民体育館前
- 東海市民体育館前
- 東海市立中央図書館前
- 東海市立中央図書館前
- 東海南高校前
- 東岨
- 東岨
- 東畑
- 東畑
- 南三ケ月
- 南三ケ月
- 南鹿持
- 南鹿持
- 南神田
- 南神田
- 八幡新田駅東
- 浜新田東
- 浜新田東
- 富貴ノ台六丁目
- 富貴ノ台六丁目
- 伏見一丁目南
- 伏見一丁目南
- 伏見四丁目
- 伏見四丁目
- 平洲記念館前
- 平洲記念館前
- 泡池
- 泡池
- 北鹿持
- 北鹿持
- 北社山
- 養父町三丁目
- 養父町三丁目
- アクアマリンプラザ
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
9 findings, ordered by severity.
Show every finding
- Warning3881 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)
- Warning250 instances
250 of 250 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)
- Warning140 instances
140 of 140 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)
- Warning21 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)
- 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
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)
- Info2 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.)
Validator rule: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules 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)
- 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 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 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 52 / 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/tokai-city-ranran-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.