Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Kayak Transit (CTUIR)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 27% of all tracked agencies and 26% of mid-size agencies. Operates in Oregon.
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.1, validator 8.0.1.
Checked for changes 6 hours ago; last fetch returned HTTP 404.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 374 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
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
137 of 137 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
39 of 39 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 8 kinds of issue across 68 instances (0 error, 23 warning, 45 informational).
Service data ended 374 day(s) ago. Trip planners have likely already dropped this feed.
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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
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.
- Hermiston Hopper (teal)
- La Grande Arrow (brown)
- Mission Metro (gray)
- Walla Walla Whistler (gray)
- Hermiston Hart (yellow)
- Milton - Freewater (teal)
- Rocket-Tripper (pink)
| Route | Type | Line color |
|---|---|---|
| Hermiston Hopper | Bus | teal |
| La Grande Arrow | Bus | brown |
| Mission Metro | Bus | gray |
| Walla Walla Whistler | Bus | gray |
| Hermiston Hart | Bus | yellow |
| Milton - Freewater | Bus | teal |
| Rocket-Tripper | Bus | pink |
This feed has 137 stops.
List every stop
- Grocery Outlet
- NE 6th St & E Montana Ave (Hermiston)
- NE Aspen Dr - The Aspens (Hermiston)
- Good Shepherd Medical Center (Hermiston)
- W Elm Ave - Butte Park (Hermiston)
- NE 4th St & E Dogwood Ave (Hermiston)
- NW 11th St & W Hartley Ave (Hermiston)
- W Ridgeway Ave & NW 11th St (Hermiston)
- W Ridgeway Ave & NW Butte Dr (Hermiston)
- City Hall (Hermiston)
- NE 4th St & Gladys Ave (Hermiston)
- E Main St & NE 7th St (Hermiston)
- NE 13th St & NE Madrona Dr - Highland Park (Hermiston)
- W Orchard Ave & SW 10th St (Hermiston)
- W Orchard Ave & SW 7th St (Hermiston)
- SW 11th St & W Division Ave (Hermiston)
- SW 11th St & W Joseph Ave (Hermiston)
- SW 9th St & W Johns Ave (Hermiston)
- Hermiston Plaza
- E Highland Ave & SE 5th St (Hermiston)
- SE Columbia Dr (Hermiston)
- NE 4th St & E Oregon Ave (Hermiston)
- SW 3rd Street & W Orchard Avenue (Hermiston)
- City Hall (Hermiston)
- E Main St & NE 7th St (Hermiston)
- NE 13th St & NE Madrona Dr - Highland Park (Hermiston)
- E Highland Ave & SE 5th St (Hermiston)
- NE 4th St & Gladys Ave (Hermiston)
- NE 4th St & E Dogwood Ave (Hermiston)
- NE 4th St & E Oregon Ave (Hermiston)
- NW 11th St & W Hartley Ave (Hermiston)
- W Orchard Ave & SW 10th St (Hermiston)
- W Ridgeway Ave & NW 11th St (Hermiston)
- SW 11th St & W Division Ave (Hermiston)
- SW 9th St & W Johns Ave (Hermiston)
- W Orchard Ave & SW 7th St (Hermiston)
- U.S. Bank (Court Ave and SW 1st Street)
- Riverfront Plaza - SW 4th St & SW Court Ave (Pendleton)
- B St & Cayuse Rd (Mission)
- Sinclair Station (Milton-Freewater)
- 6th St & Yerxa Ave (Umatilla)
- City Park (Echo)
- Pendleton Convention Center
- CAPECO (SW Isaac Avenue, at May Park sign)
- First Stop Mart (2316 SE Court Ave)
- Pilot Rock Community Pavilion
- Blue Mountain Community College (Hermiston)
- 6th & B Street (Umatilla)
- Hwy 730 & S 1st St Bus Shelter (Irrigon)
- Eastern Oregon Cancer Center (1713 SW 24th/sidewalk after driveway)
- Circle K (335 Court Ave)
- Sam's Stop & Shop
- Fire Station / S Mill St at SE 9th Av
- Library / City Hall
- Safeway
- N Elizabeth S at NE 6th Ct
- NE 8th Av at Crowl St
- Neighborhood Market: NW 8th Av / Vining St
- Lamb St. Between NW 8th Av & NW 10th Av
- North Main St at NW 11th Av
- Elk's Lodge / N Main St at NW 6th Av
- Community Center
- Post Office
- Farmland Road
- College Place Walmart
- NE 10th & Diagonal
- NE Diagonal & Ridgeway
- NE Diagonal & Ridgeway
- NE 10th & Diagonal
- Best Road/Motanic Road
- TAJ Food Mart
- Safeway (Columbus)
- NW 10th & Ridgeway Ave.
- NW 10th & Ridgeway Ave.
- SW Locust & 2nd
- SW Locust & 2nd
- Milton-Freewater Fry's True Value (Bus shelter)
- Post Office (Adams)
- Arrowhead Travel Plaza
- Century Link across Post Office (Athena)
- Best Rd & Marsh Hawk Ln (Tutuilla)
- Blue Mountain College (Pendleton)
- Cayuse Technologies
- City Hall - Library (Pendleton)
- College Ave across Andy's Laundromat (Walla Walla)
- Andy's Laundromat (Walla Walla)
- Easy St & Short Mile Rd (Mission)
- Post Office (Irrigon)
- July Grounds - Tribal Services Building (Mission)
- Kirkpatrick Rd & McKinley Ln (Mission)
- LaGrande Transit Hub
- Lavadour Ln (Mission)
- McNary Market
- Mission Creek Subdivision (MCS) - Cedar St & Aspen Way
- Mission Creek Subdivision (MCS) - Cedar St & Short Mile Rd
- Mission Market - Cayuse Rd & Hwy 331
- Mission Market - Cayuse Rd & Hwy 331
- Kayak Transit Hub (behind Nixyaawii Governance Center )
- Old West Federal Credit Union (Pendleton)
- Post Office (Pilot Rock)
- Pilot Truck Center (Stanfield)
- Roy Raley Park (Pendleton)
- Mission Senior Center
- Shenandoah Estates (Tutuilla)
- Stateline Community Church (Milton-Freewater)
- Til Taylor Park (Pendleton)
- Post Office (Umatilla)
- Walla Walla Transfer Center
- Walmart (Hermiston)
- Walmart (Pendleton)
- Main Street and Franklin Street (Weston Post Office)
- Whirlwind Turnout (Mission)
- Wildhorse Resort and Casino
- Eastern Oregon University
- St. Anthony Hospital (Pendleton)
- Recycling Depot (Umatilla)
- City Hall - Village Square (Umatilla)
- Post Office (Athena)
- Post Office (Adams)
- Stafford Hansell Government Center (Hermiston)
- 1000 S.W. Dorion (Old PGG bldg)
- Interpath Lab (SW Perkins Ave)
- SE Nye Ave near Social Security Office (Pendleton)
- Cayuse Rd & Parr Ln (Mission)
- SW 3rd Street & W Orchard Avenue (Hermiston)
- Pendleton Market
- 2500 SE Court Ave (Pendleton)
- Corwin Ln (Meacham)
- Loka Dr (Meacham)
- Meacham Store
- Adams Ave & 2nd St (LaGrande)
- Northwest Farm Supply (Hermiston)
- KIE Supply Corporation (Hermiston)
- Glendening St & E Taft Ave (Stanfield)
- Elizabethan Manor (Pendleton)
- Smith's Frozen Foods (Weston)
- College Place Walmart (Walla Walla)
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 46.7 | first check |
| 2026-06-20 | 46.7 | no change |
| 2026-06-21 | 46.7 | no change |
| 2026-06-22 | 46.7 | no change |
| 2026-06-23 | 46.7 | no change |
| 2026-06-24 | 46.7 | no change |
| 2026-06-25 | 46.7 | no change |
| 2026-06-26 | 46.7 | no change |
| 2026-06-27 | 46.7 | no change |
| 2026-06-28 | 46.7 | no change |
| 2026-06-29 | 46.7 | no change |
| 2026-06-30 | 46.7 | no change |
| 2026-07-01 | 46.7 | no change |
| 2026-07-02 | 46.7 | no change |
| 2026-07-04 | 46.7 | no change |
| 2026-07-05 | 46.7 | no change |
| 2026-07-06 | 46.7 | no change |
| 2026-07-07 | 46.7 | no change |
| 2026-07-08 | 46.7 | no change |
| 2026-07-09 | 46.7 | 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-08.
Same feed file as 2026-07-08; 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.
What changed over time
On 2026-06-19 this feed started at grade F. On 2026-06-30 feed expired. As of 2026-07-09 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-06-30 Feed expired.
Everything we checked
- Error1 instance
Service data ended 374 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning137 instances
137 of 137 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)
- Warning39 instances
39 of 39 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning17 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
5 of 39 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning3 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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Validator rule: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 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)
- Info8 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
78 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("NE 6th St & E Montana Ave (Hermiston)", "NE Aspen Dr - The Aspens (Hermiston)", "W Elm Ave - Butte Park (Hermiston)", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 374 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 374 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
- shapes.txt covers your trips Ready
- All 39 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. Service data expired 374 days ago. 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 Not yet
- Service data expired 374 days ago.
- 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 17 of 137 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
Your state runs a transit-data program that can help: Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS. Your state publishes no quality rubric of its own, so the closest published bars a program can hold this feed to are the federal and industry ones below; the score maps to those.
- Correctness 76 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 43 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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/kayak-transit-ctuir/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.