← All agencies

Feed status · checked 2026-10-15

Tsukubane-go (つくばね号)

Based on the official feed source on file

Service mode Bus

FDCBA

76.3 / 100

unchanged since 2026-10-14

Cataloged in Ibaraki, Japan.

Covers 350 daysAccessibility gapsRealtime not yet published

Source feed: https://api.gtfs-data.jp/v2/organizations/tsukubacity/feeds/TSUKUBANEGO/files/feed.zip?rid=current

Tsukuba City's Tsukubane-go community bus serving the northern part of the city; counted separately from the excluded Tsuku Bus archive.

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 official feed URL on file.

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

Tsukubane-go (つくばね号)’s published feed lists 1 bus route and 65 stops. Its service dates run from 2026-10-01 through 2027-09-30. The published file last changed on 2026-09-30.

Top things to fix

Fix 01

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

Missing required file (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

Fix 02

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

Missing calendar and calendar date files (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

Fix 03

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

65 of 65 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 65 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 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

Agency: Tsukubane-go (つくばね号)
Finding: missing_required_file
Feed evidence: Missing required file (flagged by the MobilityData validator).
Why it matters: See the linked rule for what this affects.
Requested change: Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Recheck: Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Evidence: https://gtfsscorecard.org/agency/tsukubane-go/?finding=missing_required_file#finding-handoff

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

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 350 days.
Published accessibility data: Accessibility information is stated for 0% of stops; trip coverage is not known. 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.

Hi,

Our GTFS feed (Tsukubane-go (つくばね号)) scored C (76.3 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
   What: Missing required file (flagged by the MobilityData validator).
   Finding code: missing_required_file

2. Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
   What: Missing calendar and calendar date files (flagged by the MobilityData validator).
   Finding code: missing_calendar_and_calendar_date_files

3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 65 of 65 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

Full scorecard: https://gtfsscorecard.org/agency/tsukubane-go/

Score by category

Correctness71.2 / 100

The MobilityData validator flagged 4 kinds of issue across 13 instances (3 error, 3 warning, 7 informational).

Freshness100.0 / 100

Service data covers the next 350 days.

Rider experience64.3 / 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.

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.

This feed has 65 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.

Routes in Tsukubane-go (つくばね号)'s feed
Route	Type	Line color
つくばね号	Bus	green (no shape in feed)

List every stop

筑波中央病院
筑波交流センター
カスミ筑波店
北条
北条仲町
筑波山ゲートパーク入口
北条新町
北条大池・運動公園入口
市民研修センター
山口
不動峠入口
平沢東
平沢中央
平沢官衙西入口
北条横町北
つくば田井郵便局
神郡南
神郡
神郡東
館
六所
立野東
立野西
臼井入口
臼井
飯名神社入口
沼田東
沼田中坪
筑波山口
沼田上坪
二十三夜前
筑波山神社入口
筑波山郵便局入口
東山入口
筑波ふれあいの里入口（つくば湯）
東山入口
筑波山郵便局入口
筑波山神社入口
二十三夜前
沼田上坪
沼田中坪
沼田東
飯名神社入口
臼井
臼井入口
立野西
立野東
六所
神郡東
神郡
神郡南
つくば田井郵便局
北条横町北
平沢官衙西入口
平沢中央
平沢東
不動峠入口
山口
市民研修センター
北条大池・運動公園入口
北条新町
筑波山ゲートパーク入口
北条仲町
北条
カスミ筑波店

Over time

Overall score across the last 14 checks — unchanged since 2026-10-14.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	76.3	first check
2026-10-03	76.3	no change
2026-10-04	76.2	down 0.1
2026-10-05	76.3	up 0.1
2026-10-06	76.3	no change
2026-10-07	76.3	no change
2026-10-08	76.3	no change
2026-10-09	76.3	no change
2026-10-10	76.3	no change
2026-10-11	76.3	no change
2026-10-12	76.3	no change
2026-10-13	76.3	no change
2026-10-14	76.3	no change
2026-10-15	76.3	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.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-02 to 2026-10-15 (14 checks)	`1f25bac0809e`	2027-09-30	Current rubric: see the trend above
2026-09-30 to 2026-10-01 (2 checks)	`1f25bac0809e`	2027-09-30	C, 76.3 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-09-29 (63 checks)	`0624286e512e`	2026-12-31	B, 80.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-23 to 2026-07-24 (2 checks)	`0624286e512e`	2026-12-31	B, 80.1 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade

Everything we checked

5 findings, ordered by severity.

Show every finding

Error2 instances
Missing required file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_required_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Error1 instance
Missing calendar and calendar date files (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_calendar_and_calendar_date_files · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning65 instances
65 of 65 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)
Warning3 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)
Info7 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. 2 validator errors to resolve. Accessibility completeness has not been measured.

Valid Not yet: 2 validator errors to resolve.
Current Met: Service data covers the next 350 days.
Accessible Not yet: Accessibility completeness has not been measured.

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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

65 of 65 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 349 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 3 validator errors, 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 71 / 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 64 / 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 Ibaraki

Other scorecards in Ibaraki, 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.

Badge HTML

<a href="https://gtfsscorecard.org/agency/tsukubane-go/"><img src="https://gtfsscorecard.org/agency/tsukubane-go/badge.svg" width="320" height="58" alt="Tsukubane-go (つくばね号): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Tsukubane-go (つくばね号): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/tsukubane-go/badge.svg)](https://gtfsscorecard.org/agency/tsukubane-go/)

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/tsukubane-go/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.

GTFS Scorecard. (2026). Tsukubane-go (つくばね号) GTFS feed-quality record, dated 2026-10-15 (grade C (76.3/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 1f25bac0809e…). https://gtfsscorecard.org/data/artifacts/tsukubane-go/2026-10-15.json

@misc{gtfsscorecard-tsukubane-go-2026-10-15,
  title        = {Tsukubane-go (つくばね号) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/tsukubane-go/2026-10-15.json}},
  note         = {Checked 2026-10-15; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade C (76.3/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.