Feed status · checked 2026-07-19
Nemuro Kotsu (根室交通)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-18
Catalogued in Hokkaido, 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.
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
331 of 331 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
175 of 175 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 310 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 2 kinds of issue across 15959 instances (0 error, 15959 warning, 0 informational).
Service data covers the next 310 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.
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.
- ①公住循環線 (white)
- ②公住循環線 (white)
- 中標津空港線 (white)
- 厚床線 (white)
- 札幌根室線 (white)
- 根高線成央回り登校 (white)
- 根高線望洋回り登校 (white)
- 納沙布線 (white)
- 花咲線 (white)
- 落石線 (white)
- 西浜線 (white)
- 釧路根室線 (white)
| Route | Type | Line color |
|---|---|---|
| ①公住循環線 | Bus | white |
| ②公住循環線 | Bus | white |
| 中標津空港線 | Bus | white |
| 厚床線 | Bus | white |
| 札幌根室線 | Bus | white |
| 根高線成央回り登校 | Bus | white |
| 根高線望洋回り登校 | Bus | white |
| 納沙布線 | Bus | white |
| 花咲線 | Bus | white |
| 落石線 | Bus | white |
| 西浜線 | Bus | white |
| 釧路根室線 | Bus | white |
This feed has 331 stops.
List every stop
- 東梅
- 東梅
- ペンケ東梅
- ペンケ東梅
- 道の駅スワン44ねむろ
- 基線
- 基線
- 川口
- 川口
- 湖南西口
- 湖南西口
- 湖南中央
- 湖南中央
- 厚床小中学校前
- 厚床小中学校前
- すずらん学園前
- 厚床駅前
- 厚床駅前
- 厚床駅前
- 琴平町2丁目
- 琴平町2丁目
- 落石港
- 落石港
- 風連
- 風連
- 奥行
- 奥行
- 矢臼別橋
- 矢臼別橋
- 合同庁舎前
- 合同庁舎前
- 落石西
- 落石西
- 落石神社前
- 落石神社前
- 落石中学校前
- 落石中学校前
- 落石駅前
- 落石駅前
- 浜松
- 浜松
- 汐見町
- 汐見町
- 浜松駐車公園
- 浜松駐車公園
- 町立別海病院
- 昆布盛
- 昆布盛
- 別海町交流館ぷらと前
- 常盤
- 常盤
- 宮舞
- 宮舞
- 平糸
- 平糸
- 公住前
- 公住前
- 中春別
- 中春別
- 長節
- 千島町
- 千島町
- 西和田
- 西和田
- 根室高校
- 根室交通営業所
- 厚岸入口
- 北陽高校前
- テラジマ前
- テラジマ前
- 中標津高校前
- 中標津高校前
- 中標津バスターミナル
- 市立病院前
- 市立病院前
- 松本町1丁目
- 松本町1丁目
- 隣保院前
- 隣保院前
- 常惺寺前
- 常惺寺前
- 根室別院前
- 根室別院前
- 朝日町
- 朝日町
- 明郷伊藤牧場前
- 明郷伊藤牧場前
- 宝町1丁目
- 宝町1丁目
- 中標津町役場前
- 中標津町役場前
- ゆめの森公園入口
- ゆめの森公園入口
- 中標津空港
- 中標津空港
- 花咲町2丁目
- 花咲町2丁目
- 姉別
- 姉別
- 浜中
- 浜中
- 茶内
- 茶内
- 場外馬券場
- 場外馬券場
- イオン釧路店
- イオン釧路店
- 市立釧路病院
- 市立釧路病院
- 三慈会病院
- 三慈会病院
- 十字街
- 十字街
- 釧路駅前
- 東北海道病院
- 東北海道病院
- 弥栄町1丁目
- 弥栄町1丁目
- 新川町
- 新川町
- 日赤病院
- 日赤病院
- 釧路労災病院
- 孝仁会記念病院
- くしろバス本社
- 大谷地バスセンター
- 大通バスセンター
- 大通バスセンター
- 北都交通本社前
- 札幌駅前
- 中標津トーヨーグランドホテル
- 市役所前
- 市役所前
- 光洋町3丁目
- 光洋町4丁目
- 公住南
- 公住東
- 公住北
- 自衛隊前
- 光洋町南
- 光洋町西
- 光洋町西
- 光洋町2丁目
- 光洋町2丁目
- 緑町1丁目
- 駅前ターミナル
- 駅前ターミナル
- 西浜町9丁目
- 西浜町9丁目
- 別海高校
- 振興局前
- 振興局前
- 中学分岐点
- 中学分岐点
- 有磯営業所前
- 有磯営業所前
- 緑ヶ岡団地入口
- 緑ヶ岡団地入口
- 宝林町4丁目
- 宝林町4丁目
- 建設管理部前
- 建設管理部前
- オワッタラウス
- オワッタラウス
- 月岡町2丁目
- 月岡町2丁目
- 老人ホーム入口
- 老人ホーム入口
- 車石入口
- 車石入口
- 花咲港
- 花咲港
- 花咲港中央
- 花咲港中央
- 花咲港西
- 花咲港西
- 栄町
- 栄町
- 公住入口
- 光洋中学校前
- 光洋中学校前
- 無線前
- 無線前
- 月ヶ丘分岐点
- 月ヶ丘分岐点
- 曙町
- 曙町
- 文化会館前
- 文化会館前
- 明治町1丁目
- 明治町1丁目
- 商工会館前
- 商工会館前
- 本町5丁目
- 本町5丁目
- 郵便局前
- 郵便局前
- 市営ゲートボール場前
- 市営ゲートボール場前
- 梅ヶ枝町
- 梅ヶ枝町
- 弥生町1丁目
- 弥生町1丁目
- 弥生町2丁目
- 弥生町2丁目
- 緑町2丁目
- 緑町2丁目
- 駅前信金前
- 北斗小学校前
- 北斗小学校前
- 北斗小学校前
- 清隆寺前
- 清隆寺前
- セレモニーホール平和前
- セレモニーホール平和前
- 定基町1丁目
- 定基町1丁目
- 岬町3丁目
- 岬町3丁目
- 駒場町入口
- 駒場町入口
- 共立病院前
- 共立病院前
- 花園町
- 花園町
- 敷島町2丁目
- 敷島町2丁目
- 光和公園前
- 光和公園前
- 光和町3丁目
- 光和町3丁目
- 市営住宅前
- 市営住宅前
- 宝林町3丁目
- 宝林町3丁目
- 昭和町
- 昭和町
- 成央小学校前
- 成央小学校前
- 光洋町1丁目
- 光洋町1丁目
- 駒場町2丁目
- 駒場町2丁目
- 明治町3丁目
- 明治町3丁目
- 根室高校前
- 根室高校前
- 教員住宅前
- 教員住宅前
- 新茶屋前
- and 81 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.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 80.5 | first check |
| 2026-07-19 | 80.5 | 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
4 findings, ordered by severity.
Show every finding
- Warning15733 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)
- Warning331 instances
331 of 331 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)
- Warning226 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)
- Warning175 instances
175 of 175 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)
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 310 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 310 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 84 / 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 60 / 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/nemuro-kotsu/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.