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
Navajo Transit System
Based on the feed this agency publishes
up 0.1 since 2026-07-08 · F → F
Ahead of 46% of all tracked agencies and 43% of mid-size agencies. Operates in New Mexico.
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 8 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 1985 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
153 of 167 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 +23 points
Remove past service periods the next time you export the feed.Likely your export tool
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.
⏱ One setting in most export tools.worth about +4 points
Agencies here usually clear this within about 1 week (based on 61 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.
Remove past service periods the next time you export the feed. · 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 25 instances (0 error, 11 warning, 14 informational).
Service data ended 1985 day(s) ago. Trip planners have likely already dropped this feed.
8% of stops state wheelchair accessibility (8% marked accessible, 1% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
8% of stops state accessibility (8% 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.
- 1 (green)
- 10 (green)
- 13 (green)
- 14 (green)
- 15 (green)
- 16 (green)
- 18 (green)
- 3 (green)
- 5 (green)
- 6 (green)
- 7A/B (green)
- 8 (green)
- 9 (green)
| Route | Type | Line color |
|---|---|---|
| 1 Tuba City / Fort Defiance | Bus | green |
| 10 Pinon / Chinle / Tsaile | Bus | green |
| 13 Fort Defiance / Crownpoint / Gallup | Bus | green |
| 14 Shiprock / Fort Defiance | Bus | green |
| 15 Sanders / Window Rock | Bus | green |
| 16 Aneth / Bluff / Blanding | Bus | green |
| 18 Shiprock | Bus | green |
| 3 Kayenta / Fort Defiance | Bus | green |
| 5 Fort Defiance / Gallup | Bus | green |
| 6 Crystal / Gallup | Bus | green |
| 7A/B Newcomb/Farmingon/Shiprock/Fort Defiance | Bus | green |
| 8 Chinle / Ganado / Tsaile | Bus | green |
| 9 Dilkon / Fort Defiance | Bus | green |
This feed has 167 stops.
List every stop
- Holbrook Junction - Road Stop
- Burnside - Lok'aah Ni Teel Shopping Center
- Dinnebito Junction - Road Stop
- Cross Canyon - Road Stop
- Keams Canyon - Hopi Police Department
- Hopi Cultural Center - Road Stop
- Kykotsmovi - Road Stop
- Hotevilla - Road Stop
- Keams Canyon - Trading Post
- Kinlichee Junction - Road Stop
- Polacca - Circle M Market
- St. Michaels - Karigan Complex
- Polacca - Hopi Health Care Center
- Second Mesa - Road Stop
- St. Michaels - Denny's Restaurant
- Jeddito Wash - Road Stop
- Tuba City - I.H.S. (Out-Patient)
- Coalmine - Community Road Stop
- Ganado - Post Office
- Pinon - Bashas Parking Lot
- Pinon - IHS
- Whippoorwilll
- Blue Gap - Store
- Tselani - Cottonwood Chapter House
- Nahatadziil - Chapter House
- Sanders - Conoco Store
- Sanders - Ortegas Indian Ruins
- Allentown Indian City Chee's Store
- Lupton - Chapter House
- Aspen Canyon Road South - Road Stop
- Oakspring - Chapter House
- Hunters Point MP 17 - Road stop
- St. Michaels - I.H.S. Administration
- Tse Bonito - Family Dollars
- Window Rock - Museum / Parks
- Window Rock - Quality Inn
- Ft.Defiance - Workforce/Fieldhouse
- Crownpoint - NTU - Campus bus stop
- Crownpoint - Police Department
- Shiprock - B.I.A. Building
- Shiprock - Chapter House
- Tsaile - IHS
- Window Rock - DES Office
- Pinedale - Chapter House
- Shiprock - Across East 7/11 Store
- Gamerco - Navajo Shopping Road Stop
- Wheatfields Lake - Pull Out
- Coyote Canyon - Chapter House
- Shiprock - I.H.S. Hospital Road Stop
- Tuba City - Bashas Parking Lot
- Smith Lake Chapter
- Mariano Lake - Chapter House
- Window Rock - Admin 1 & 2 temporary
- Gallup - Fire Rock Casino
- Yatahey T&R Market
- Gallup - R&M Rent to Own
- Buffalo Springs - DOT Yard
- Shiprock - City Market
- Littlewater - Gas Station
- Burnham - Shell Gas Station
- Newcomb - Firestation
- Sheepspring - Gas Station
- Naschitti - Road Stop
- Naschitti - Road Stop(opposite)
- Yatahey - Red Mesa Store
- Window Rock - Bashas Parking Lot
- Shiprock - East 7/11 Store
- Shiprock - Fleet Management
- Shiprock - Navajo Police Department
- Chinle - South Giant Store
- Round Rock - Chapter House
- Lukachukai - Giant Store
- Pinesprings - Road Stop
- Red Mesa Chapter House
- Bluff - K & C Store
- Bluff - Twin Rock Cafe
- Steamboat Canyon - Express Store
- Steamboat Deer Standing - Road Stop
- Blanding - White Mesa Travel Center
- Blanding - Clark's Market
- Blanding - Blue Mountain Hospital
- Blanding - Utah State University / Greyhound
- Blanding - Canyon Country
- Blanding - Visitor Center
- Blanding - State of Utah Offices
- Montezuma Creek - Red Mesa Express
- Aneth - Red Mesa Express
- Aneth - Chapter House
- Window Rock - Department of Justice
- Window Rock - Fleet Management
- Window Rock - Census Office
- Window Rock - Education Building
- Window Rock - Police Department
- Chilchinbito - Estates Housing
- Del Muerto - Church MP 7
- Many Farms - Giant Store
- Rough Rock Junction - N.Rt. 59
- Chinle - I.H.S. Hospital
- Chinle - Pic-N-Run Store
- Chinle - Chevron Gas Station
- North NHA Main Office
- Wells Fargo Bank
- Dine College South Campus
- Tse Bit'a'i Jr High
- Nataani Nez Restaurant
- Kayenta - Police Department
- Kayenta - Shell Store
- Tsaile - Dine College Campus
- Wheatfields - Chapter House
- Wheatfields Lake - Pull Out
- Navajo Pine - Shopping Center
- Ft.Defiance - Navajo Transit Building
- Kayenta - Junction Hwy 160/Rt.59
- Chinle - Community Center
- Chinle - Transit Sub-Station
- Twin Lakes - Old Chapter House
- Crownpoint - Bashas
- Crownpoint - Land Office
- Crownpoint - Trading Post
- Ft.Defiance - N.T.U.A.
- Ft.Defiance - Water Development
- Ft.Defiance - Facilities Maintenance
- Ft.Defiance - Tsehootsooi Medical Center
- Gallup - Walmart
- Gallup - Rainbow Bread Co. Stop
- Gallup - Amtrak Depot
- Gallup - Zecca Plaza
- Gallup - Pinon Plaza Stop
- Gallup - UNM Campus
- Gallup - GIMC Hospital
- Tse Bonito - Family Dollars
- Ft.Defiance - Old P.H.S. (Hospital)
- Ft.Defiance - Conoco Gas Station
- Ft.Defiance - Post Office
- Farmington - Walmart Super Center parking lot
- Tohatchi - Navajo Petroleum
- Kirtland - Central Center
- Kirtland - Monster Slayer (AM)
- Farmington - O'Reilly Road Stop
- Harper Hills - 7/11 Store
- Shiprock - I.H.S. Hospital
- Ganado - Chapter / Apache County
- Nazlini Junction - Road Stop
- Pinon Junction - Road Stop
- Chinle - Fleet Management
- Cornfields Junction - Road Stop
- Greasewood - NHA Housing #1
- Tse Bonito - Navajo DOT Facilities
- Dilkon - Bashas Parking Lot
- Indian Wells - N.H.A. Roadstop
- Indian Wells - HHH Road Stop - MP72
- Greasewood - NHA Housing #2
- St. Michaels - Post Office
- Chinle - Holiday Inn Road Stop
- Chinle - MP 454 Road Stop
- Chinle - Bashas Parking Lot
- Chinle - Chapter House
- Standing Rock - Housing Road Stop
- Coyote Canyon Rehab - Road Stop
- Coyote Canyon - Dibe' Licheii Housing
- Coyote Canyon - Dibe' Licheii Housing(opposite)
- Ft.Defiance - Forestry
- Tsaile - Alon Store
- Crystal - Chapter House
- Crystal - Old Chapter House
- Chinle - Canyon De Chelly & N Rt7
- Tsaile - MP 16.4 Road Stop
Over time
Overall score across the last 9 checks — up 0.1 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 56.5 | first check |
| 2026-07-01 | 56.5 | no change |
| 2026-07-02 | 56.5 | no change |
| 2026-07-04 | 56.5 | no change |
| 2026-07-05 | 56.6 | up 0.1 |
| 2026-07-06 | 56.6 | no change |
| 2026-07-07 | 56.5 | down 0.1 |
| 2026-07-08 | 56.5 | no change |
| 2026-07-09 | 56.6 | up 0.1 |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall score rose 0.1 points 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.
Everything we checked
- Error1 instance
Service data ended 1985 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)
- Warning153 instances
153 of 167 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)
- Warning4 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)
- Warning2 instances
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)
- Warning2 instances
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' 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 5 observed fixes).
Validator rule: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
2 of 38 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)
- 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
Leading or trailing whitespaces (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: leading_or_trailing_whitespaces · 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)
- Info13 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)
- Info1 instance
Feed valid beyond total service window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' 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 7 observed fixes).
Validator rule: feed_valid_beyond_total_service_window · 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.
26 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Blanding - Utah State University / Greyhound", "Bluff - K & C Store", "Chinle - Canyon De Chelly & N Rt7", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Trimmed surrounding whitespace 1 change
For example: 'stop_name': 'Dine College South Campus ' -> 'Dine College South Campus'
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 1985 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 1985 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 38 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 1985 days ago. States wheelchair access on 8% of stops and 95% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 1985 days ago.
- Accessible Not yet
- States wheelchair access on 8% of stops and 95% 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.
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.
- Correctness 75 / 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 76 / 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/navajo-transit-system-157/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.