GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Ono City Ran-Ran Bus (小野市らんらんバス)

Based on the feed this agency publishes

Service mode Bus

70.0 / 100

unchanged since 2026-07-18

Catalogued in Hyogo, Japan.

Covers 255 daysAccessibility gapsRealtime not yet published

Ono City's Ran-Ran community bus in south-central Hyogo.

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

Review the rule documentation for 'location_with_unexpected_stop_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Location with unexpected stop time (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +12 points in its category

Fix 02

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

309 of 309 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 03

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

99 of 99 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.

  1. Review the rule documentation for 'location_with_unexpected_stop_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

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

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

Correctness65.5 / 100

The MobilityData validator flagged 6 kinds of issue across 2690 instances (1 error, 2688 warning, 1 informational).

Freshness100.0 / 100

Service data covers the next 255 days.

Rider experience52.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 published.

Accessibility0 / 100

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

1 accessibility depth signal

  • 4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (らんらんバス・1 北回り循環ルート, らんらんバス・3 河合統合ルート, らんらんバス・7 大開ルート, らんらんバス・9 ひまわりタウンルート).

    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.

FaresLegacy fares

Fares are applied to trips.

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 Ono City Ran-Ran Bus (小野市らんらんバス)'s feed
RouteTypeLine color
らんらんバス・1 北回り循環ルートBusred (no shape in feed)
らんらんバス・10 中谷ルートBuspurple (no shape in feed)
らんらんバス・11 匠台ルートBuswhite (no shape in feed)
らんらんバス・2 南回り循環ルート ロングコースBuspink (no shape in feed)
らんらんバス・2 南回り循環ルート ショートコースBuspink (no shape in feed)
らんらんバス・3 河合統合ルートBusgreen (no shape in feed)
らんらんバス・4 西脇ルートBusyellow (no shape in feed)
らんらんバス・5 鴨池ルートBusteal (no shape in feed)
らんらんバス・6 山田・樫山ルートBusbrown (no shape in feed)
らんらんバス・7 大開ルートBusorange (no shape in feed)
らんらんバス・8 万勝寺ルートBusyellow (no shape in feed)
らんらんバス・9 ひまわりタウンルートBusteal (no shape in feed)

This feed has 309 stops.

List every stop
  • 久保木
  • 久保木
  • 久保木公会堂
  • 久保木公会堂
  • 北古川
  • 北古川
  • 古川
  • 古川
  • 商店街南口
  • 商店街南口
  • 商店街北口
  • 商店街北口
  • 小野郵便局前
  • 小野郵便局前
  • 鹿野
  • 鹿野
  • 広渡廃寺
  • 広渡廃寺
  • 高田
  • 高田
  • アメニティくろかわ
  • アメニティくろかわ
  • ＪＲ市場駅
  • 管理事務所前
  • 管理事務所前
  • 池田公民館前
  • 池田公民館前
  • 池田
  • 池田
  • 北丘町
  • 北丘町
  • 住吉町川南
  • 住吉町川南
  • 広渡西
  • 広渡西
  • 釈迦堂公園前
  • 釈迦堂公園前
  • 敷地公民館前
  • 敷地公民館前
  • 黍田公民館前
  • 黍田公民館前
  • 向山
  • 向山
  • 西山町
  • 土井病院入口
  • 昭和町公民館前
  • 昭和町公民館前
  • グリーンハイツ北
  • グリーンハイツ北
  • グリーンハイツ南
  • グリーンハイツ南
  • 復井南
  • 復井南
  • 王子
  • 王子
  • 粟生
  • 粟生
  • 喜多口
  • 喜多口
  • 来住保育所前
  • 来住保育所前
  • 田園町
  • 下大部
  • ＪＡ市場前
  • ＪＡ市場前
  • 垂井町公民館前
  • 垂井町公民館前
  • 大島
  • 大島
  • 市場
  • 市場
  • 小野消防署前
  • エクラ
  • 浄谷町公民館
  • 浄谷町公民館
  • 河合西駅前
  • 育ヶ丘
  • 育ヶ丘
  • 近津神社前
  • 近津神社前
  • 樫山駅前
  • 福住・小田下西
  • 福住・小田下西
  • コミセンおおべ
  • コミセン下東条
  • コミセン下東条
  • コミセンきすみの
  • コミセンきすみの
  • コミセンいちば
  • 来迎寺
  • 来迎寺
  • 天神東ヶ丘
  • 大部小学校
  • 大部小学校
  • 住吉町上
  • 青野ヶ原駅前
  • 青野ヶ原駅前
  • 図書館前
  • 図書館前
  • 山田東
  • 山田東
  • 匠台
  • 神社前
  • 神社前
  • 中山
  • 中山
  • 大開中
  • 大開中
  • 大開町
  • 大開町
  • 脇本下西山
  • 脇本下西山
  • 小田農協
  • 小田下川南
  • 船木
  • 黒川西
  • 黒川西
  • 北播磨総合医療センター
  • 中町団地
  • 中町団地
  • 天神西
  • 天神西
  • 買野
  • 特別支援学校
  • 特別支援学校
  • 小野商工会議所前
  • 小野商工会議所前
  • 小野大池
  • 小野大池
  • 小野
  • 小野
  • 小野本町一丁目
  • 小野本町一丁目
  • 室山
  • 小野中学校前
  • 小野中学校前
  • テクノプラザ前
  • 舟本
  • 舟本
  • 起生園
  • 流通団地北
  • 匠台１８番地前
  • 匠台１７番地前
  • 榊公園南
  • 匠台３番地前
  • 匠台５番地前
  • 中町
  • 中町
  • 匠台１１番地前
  • 鍬溪温泉前
  • 鍬溪温泉前
  • 小野市役所
  • 敷地南
  • 敷地南
  • 電鉄小野駅
  • 県営小野神明団地
  • 県営小野神明団地
  • 大島中
  • 大島中
  • 浄化センター前
  • 浄化センター前
  • ゆぴか
  • 二葉
  • 二葉
  • 小野ニュータウン東
  • 小野ニュータウン西
  • 山田西
  • 山田西
  • 山田中
  • 山田中
  • 西山
  • 西山
  • 船付
  • 船付
  • 大上
  • 大上
  • 上榊
  • 上榊
  • 下榊
  • 下榊
  • 育ヶ丘南
  • 育ヶ丘南
  • 育ヶ丘西
  • 育ヶ丘西
  • 育ヶ丘東
  • 樫山
  • 樫山
  • 池尻
  • 池尻
  • 下東条小学校
  • 小田上
  • 小田上
  • 脇本谷
  • 脇本谷
  • 脇本新田
  • 脇本新田
  • 四ツ堂
  • 四ツ堂
  • 四ツ堂
  • 四ツ堂
  • 万勝寺新田
  • 万勝寺下池
  • 万勝寺下池
  • 南山稲荷
  • 南山稲荷
  • 万勝寺
  • 万勝寺
  • 万勝寺口
  • 万勝寺口
  • 新開地（共進牧場）
  • 新開地（共進牧場）
  • 新開地（共進牧場）
  • 新開地（共進牧場）
  • 河合西
  • 河合西
  • 浄土寺
  • 浄土寺
  • 浄谷
  • 浄谷
  • 坂下
  • 坂下
  • 坂下
  • 復井
  • 復井
  • 青野ヶ原町
  • 青野ヶ原町
  • 河合中
  • 河合中
  • 新部
  • 新部
  • 住永町
  • 住永町
  • 河合郵便局前
  • 河合郵便局前
  • 粟生駅前
  • 粟生駅前
  • 西脇
  • 西脇北
  • 阿形
  • 来住小学校前
  • 来住小学校前
  • 小野町駅西
  • 小野町駅西
  • うぐいす台
  • 中谷
  • 曽根
  • 曽根
  • 小田下川北
  • 小田下川北
  • 河合小学校前
  • and 59 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 2 checks — unchanged since 2026-07-18.

2026-07-18: 70.02026-07-19: 70.0
Show the numbers
CheckScoreChange
2026-07-1870.0 first check
2026-07-1970.0 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

What changed in this feed

Overall grade and score held steady since 2026-07-18.

Same feed file as 2026-07-18; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

9 findings, ordered by severity.

Show every finding
  • Error1 instance

    Location with unexpected stop time (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'location_with_unexpected_stop_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: location_with_unexpected_stop_time · See MobilityData GTFS Validator rules

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

  • Warning309 instances

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

  • Warning99 instances

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

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

    Unexpected enum value (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Validator rule: unexpected_enum_value · See MobilityData GTFS Validator rules

  • Info1 instance

    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

  • 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. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
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. The feed also carries 1 validator error, the other thing Maps checks at onboarding; the findings below name each fix.

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 66 / 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.

Ono City Ran-Ran Bus (小野市らんらんバス) 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/ono-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.