Feed status · checked 2026-10-15
Takeya Kotsu (タケヤ交通)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-10-14
Cataloged in Miyagi, Japan.
Source feed: https://api.gtfs-data.jp/v2/organizations/takeyakoutu/feeds/takeyakotsu/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 6 hours ago; last changed 15 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
About this feed
Takeya Kotsu (タケヤ交通)’s published feed lists 5 bus routes, 83 scheduled trips and 83 stops. Its service dates run from 2026-10-01 through 2027-03-31. The published file last changed on 2026-09-30.
Top things to fix
Review the rule documentation for 'number_out_of_range' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Number out of range (flagged by the MobilityData validator). See the linked rule for what this affects.
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.
⏱ Varies.worth about +12 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
83 of 83 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 83 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 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.
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 planned ID change, not a quick text cleanup.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.
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_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.
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 167 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 83.1% 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 8 kinds of issue across 1478 instances (1 error, 1459 warning, 18 informational).
Service data covers the next 167 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
2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("KUKKA with Flower&Cafe", "KYOU BAR LOUNGE & INN前").
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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.
This feed has 83 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.
- 仙台西部ライナー (purple)
- 白石蔵王山麓循環線 (purple)
- せんだい海手線ループバス (purple)
- 川崎仙南ライナー (purple)
- 秋保ループバス (purple)
| Route | Type | Line color |
|---|---|---|
| 仙台西部ライナー | Bus | purple |
| 白石蔵王山麓循環線 | Bus | purple |
| せんだい海手線ループバス | Bus | purple |
| 川崎仙南ライナー | Bus | purple |
| 秋保ループバス | Bus | purple |
List every stop
- グランドホテル前
- 界 秋保前
- 木の家前
- 佐勘前
- 秋保・里センター
- 仙台市天文台
- 地下鉄広瀬通駅
- 仙台駅前
- ＪＲ白石蔵王駅
- ＪＲ白石駅
- タケヤ交通本社前
- 城下広場
- 鎌先温泉
- 弥治郎こけし村
- 蔵王キツネ村
- 荒井駅
- 鐘崎総本店笹かま館
- 三井アウトレットパーク仙台港
- 震災遺構荒浜小
- 深沼海岸
- 深沼うみのひろば
- かわさきまち
- ＪＲフルーツパーク
- 海岸公園馬術場
- 海岸公園冒険広場
- アクアイグニス仙台
- かわまちてらす閖上
- ゆりあげ港朝市
- エコキャンプ入口前
- ホテル佐勘前
- ホテルクレセント
- 佐々木美術館
- KOMOREBI
- KUKKA with Flower&Cafe
- KYOU BAR LOUNGE & INN前
- 湯向中央公園前
- 秋保ワイナリー
- グレートデーンブリューイング
- みちのく公園
- ホテル瑞鳳前
- ホテル緑水亭
- 万華鏡美術館
- 秋保ヴィレッジ
- 野上
- 第二小前
- 第二小前
- 立野
- 立野
- 川崎病院前
- 川崎病院前
- 川崎校前
- 川崎校前
- 川崎町役場前
- 川崎町役場前
- 里山地区入口
- 川崎仲町
- 川崎仲町
- 北向
- 北向
- 音無入口
- 音無
- 音無
- 谷山温泉入口
- 道の駅村田前
- 道の駅村田前
- 村田工業団地
- 村田工業団地
- 関場
- 関場
- 橋本
- 橋本
- 県南中核病院
- 蘭亭前
- 大河原郵便局前
- 大河原郵便局前
- 大河原町役場前
- 大河原町役場前
- 大河原産業高校前
- 大河原産業高校前
- 大河原駅前
- 秋保工芸の里
- 緑水亭前
- 瑞鳳前
Over time
Overall score across the last 14 checks — unchanged since 2026-10-14.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 75.5 | first check |
| 2026-10-03 | 75.5 | no change |
| 2026-10-04 | 75.5 | no change |
| 2026-10-05 | 75.5 | no change |
| 2026-10-06 | 75.5 | no change |
| 2026-10-07 | 75.5 | no change |
| 2026-10-08 | 75.5 | no change |
| 2026-10-09 | 75.5 | no change |
| 2026-10-10 | 75.5 | no change |
| 2026-10-11 | 75.5 | no change |
| 2026-10-12 | 75.5 | no change |
| 2026-10-13 | 75.5 | no change |
| 2026-10-14 | 75.5 | no change |
| 2026-10-15 | 75.5 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
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-02 to 2026-10-15 (14 checks) | 3a410624aeef | 2027-03-31 | Current rubric: see the trend above |
| 2026-09-30 to 2026-10-01 (2 checks) | 3a410624aeef | 2027-03-31 | C, 75.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-01 to 2026-09-29 (25 checks) | 6722ffa45272 | 2027-03-31 | B, 82.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-08-31 (38 checks) | 524322eb1f07 | 2027-03-31 | B, 81.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-23 to 2026-07-24 (2 checks) | 524322eb1f07 | 2027-03-31 | B, 81.9 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-18 to 2026-07-19 (2 checks) | 7fb03498b83f | 2026-09-30 | B, 83.3 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
Everything we checked
11 findings, ordered by severity.
Show every finding
- Error1 instance
Number out of range (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'number_out_of_range' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: number_out_of_range · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1440 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning83 instances
83 of 83 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)
- Warning14 instances
14 of 83 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)
- Warning12 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)
- Warning5 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info13 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide for service_window_outside_feed_period · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5 instances
About 5 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.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info3 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)
- Info2 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)
Conformance mark Not yet
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 83% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 167 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 83% 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 166 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 64 / 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 72 / 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.
Part of the Japan portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Miyagi
Other scorecards in Miyagi, 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/takeya-kotsu/2026-10-15.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-15. 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.