Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Mountain Line Transit
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 73% of all tracked agencies and 71% of mid-size agencies. Operates in Arizona.
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 14 minutes ago; last changed 19 hours ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
176 of 176 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
1336 of 1336 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).
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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points
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.
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. See this feed's dated fix log.
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. See this feed's dated fix log.
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. · 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. See this feed's dated fix log.
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 5 kinds of issue across 190 instances (0 error, 187 warning, 3 informational).
Service data covers the next 174 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Sampled 9 times outside service hours: 3 of 3 feeds healthy.
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.
- 2 (blue)
- 3 (green)
- 4 (orange)
- 5 (orange)
- R14 (brown)
- 7 (purple)
- R10 (red)
- 66 (red)
- 8 (teal)
| Route | Type | Line color |
|---|---|---|
| 2 Route 02 - Blue | Bus | blue |
| 3 Route 03 - Green | Bus | green |
| 4 Route 04 - Gold | Bus | orange |
| 5 Route 05 - Orange | Bus | orange |
| R14 Route 14 - Brown | Bus | brown |
| 7 Route 07 - Purple | Bus | purple |
| R10 Route 10 - Maroon | Bus | red |
| 66 Route 66 - Red | Bus | red |
| 8 Route 8 to Woody Mountain Road | Bus | teal |
This feed has 176 stops.
List every stop
- Route 66 / Thompson St (Mavrik) WB
- Route 66 / Railroad Springs Blvd WB
- Route 66 / Northwestern St (Hidden Hollow) WB
- Rt. 66 / Northwestern St. (Wildwood Hills)
- Beulah Blvd. / University (Roundabout)
- Beulah Blvd./ University Av. (Roundabout) NB
- Route 66 / Railroad Springs Blvd. (Kit Carson)
- (Temp) Woody Mt Rd / Patio Del Presidio
- Pine Cliff
- Gemini Rd.
- Kaspar (NAIPTA) WB
- Lockett / Fanning WB
- Lockett / Manor
- Lockett / Alta Vista WB
- Lockett / King WB
- Cedar Plaza WB
- Cedar / West WB
- Cedar / Gemini SB
- Forest / Turquoise WB
- Beaver (FMC) SB
- Beaver / Hunt
- Beaver / Birch
- Downtown Connection Center
- San Francisco / Birch
- San Francisco / Elm
- Desilva Ave/Beaver St
- Beaver (FMC) NB
- Forest / Turquoise EB
- Cedar / Gemini NB
- Cedar / West EB
- Cedar / Aris EB
- Lockett / King EB
- Lockett / Alta Vista EB
- Lockett / Fanning EB
- Kaspar (NAIPTA) EB
- Lynch (FUTS Trail)
- Flagstaff Mall Connection Ctr
- Cummings / Lynch
- Soliere / Country Club
- Soliere (Timberline) WB
- Soliere (Butterfield) WB
- Soliere / Elk Run WB
- Soliere / Foxlair (East) WB
- Soliere / Foxlair (West) WB
- Foxglenn / Butler SB
- Butler (Black Barts)
- Butler / Lucky WB
- Butler (Golden Eagle) WB
- Butler WB (L&W Supply)
- Butler / Sawmill WB
- Butler / Elden WB
- Butler / San Francisco WB
- Kendrick / Benton
- Butler / San Francisco EB
- Butler / Elden EB
- Butler / Cambridge EB
- Butler EB (Marathon)
- Butler (Napa)
- Butler (Filiberto's)
- Butler (Little America)
- Foxglenn / Butler NB
- Soliere / Foxlair (West) EB
- Soliere / Foxlair (East ) EB
- Soliere / Elk Run EB
- Soliere (Butterfield) EB
- Soliere (Timberline) EB
- Country Club (B of A)
- Route 66 / Country Club
- Milton (Taco Bell)
- Milton / University
- Beulah (Wal-Mart)
- Lake Mary / I-17
- Lake Mary / High Country
- Lake Mary / Mohawk
- Walapai/Lake Mary
- Walapai / Yaqui (North)
- Zuni / Kofa
- Lone Tree (CCC)
- Lone Tree / Pine Knoll
- Lone Tree / Brannen
- Lone Tree / Franklin
- Fort Valley / Winding Brook
- Fort Valley / Valley Crest
- Peak View / Mountain
- Peak View / Cooper
- Peak View / Fremont
- Fremont / Lynette
- Fremont (Cheshire Park)
- Fremont (FALA)
- Fort Valley (Museum of N. AZ)
- Fort Valley / Stevanna
- Fort Valley / Meade SB
- Fort Valley / Whipple
- Thorpe / Bonito WB
- Thorpe (Clark Homes) WB
- Thorpe (Ball Fields) SB
- Thorpe (Adult Center) SB
- Santa Fe / Park EB
- Aspen (City Hall) EB
- Beaver / Phoenix
- Lone Tree / Franklin
- Lone Tree / Brannen
- Lone Tree / Pine
- Lone Tree (CCC)
- Zuni / Kofa
- Walapai / South Yaqui
- Walapai / Lake Mary
- Lake Mary / Mohawk
- Lake Mary / Hi Cntry
- Lake Mary / Beulah
- Beulah / McConnell
- Milton / University (Target)
- Milton / Plaza Way
- Milton Rd. / Butler Av. (NAU)
- Aspen (City Hall) WB
- Santa Fe / Park WB
- Thorpe (Adult Center) NB
- Thorpe (Ball Fields) NB
- Thorpe (Clark Homes) EB
- Thorpe / Bonito EB
- Fort Valley / Forest
- Fort Valley / Meade NB
- Fort Valley (Pioneer Museum)
- Sixth / Third WB
- Sixth / First WB
- Sixth / West WB
- West / Felice NB
- Fourth / Felice SB
- Fourth at Route 66 SB
- Fourth / Huntington SB
- Huntington (Walmart) WB
- Route 66 / Riordan Rd. (The Standard)
- Route 66 / Pinnacle
- Thompson St
- University Av. / Forest Meadows St. (True North Dentistry)
- Woodlands Village Blvd. / University Av.
- Route 66 / Woodlands Village Blvd. (Doubletree)
- Route 66 / Metz Walk
- Huntington Dr. / Grant St. EB
- Huntington (Walmart) EB
- Fourth / Huntington NB
- Fourth NB (Walgreens)
- Huntington Dr. / Grant St. WB
- Beaver / Franklin SB
- Beaver (Gillenwater)
- University (Wilson)
- Knoles (Campus Heights) SB
- McConnell (SBS) WB
- Forest Meadows (Shell)
- Forest Meadows (Apts.)
- Woodlands Village
- McConnell (SBS) EB
- Knoles (Campus Heights) NB
- University (Reilly)
- Beaver (NAU Bookstore)
- Beaver / Franklin NB
- Route 66 / Fanning WB
- Route 66 / Steves WB
- Route 66 / Fourth WB
- Route 66 / Arrowhead WB
- Route 66 / Ponderosa WB
- Route 66 / Switzer WB
- Route 66 / San Francisco
- Route 66 / Switzer EB
- Route 66 / Ponderosa EB
- Route 66 / Arrowhead EB
- Route 66 / Fourth EB
- Route 66 / Steves EB
- Route 66 / Fanning EB
- Highway 89 / Smokerise
- Christmas Tree / Snowflake
- Winter / Christmas Tree
- Gemini / Pine Cliff (BASIS) EB
- Fourth / Sparrow (NPA) SB
- Fourth / Sparrow (NPA) NB
- Fourth / Cedar SB
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 76.6 | first check |
| 2026-06-20 | 75.9 | down 0.7 |
| 2026-06-21 | 75.6 | down 0.3 |
| 2026-06-22 | 76.6 | up 1.0 |
| 2026-06-23 | 75.4 | down 1.2 |
| 2026-06-24 | 76.6 | up 1.2 |
| 2026-06-25 | 76.6 | no change |
| 2026-06-26 | 76.6 | no change |
| 2026-06-27 | 74.9 | down 1.7 |
| 2026-06-28 | 76.6 | up 1.7 |
| 2026-06-29 | 76.6 | no change |
| 2026-06-30 | 76.6 | no change |
| 2026-07-01 | 75.6 | down 1.0 |
| 2026-07-02 | 76.6 | up 1.0 |
| 2026-07-04 | 76.6 | no change |
| 2026-07-05 | 76.6 | no change |
| 2026-07-06 | 76.6 | no change |
| 2026-07-07 | 76.6 | no change |
| 2026-07-08 | 76.6 | no change |
| 2026-07-09 | 76.6 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality 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.
Everything we checked
- Warning1336 instances
1336 of 1336 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)
- Warning386 instances
386 of 1336 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)
- Warning176 instances
176 of 176 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)
- Warning168 instances
Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_distance_exceeds_shape_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9 instances
Equal shape distance same coordinates (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: equal_shape_distance_same_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' 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: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
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
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)
- Info3 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)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (4, 5, 66).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
125 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Route 66 / Thompson St (Mavrik) WB", "Route 66 / Railroad Springs Blvd WB", "Route 66 / Northwestern St (Hidden Hollow) WB", 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 5 changes
For example: 'stop_name': 'Rt. 66 / Northwestern St. (Wildwood Hills) ' -> 'Rt. 66 / Northwestern St. (Wildwood Hills)'
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
NTD certification readiness Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 174 days.
- 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 1336 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. 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 174 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.
Realtime reliability
The realtime feed responded on 100.0% of 105 checks over the last 16 days, with 0s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 174 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
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 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 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 41 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality 100 / 100
- 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/mountain-line-transit/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.