GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Mountain Line

Based on the feed this agency publishes

Service mode Bus

28.6 / 100

unchanged since 2026-07-31

Catalogued in Arizona.

Feed expiredRealtime not yet published

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.3, validator 8.0.1.

Checked for changes 72 minutes ago; last fetch returned HTTP 403.

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

Fix 01

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

Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +18 points in its category

Fix 02

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

Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +18 points in its category

Fix 03

Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool

Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

⏱ Usually an export-tool fix, not hand editing.worth about +18 points in its category

This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.

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.

Feed evidence
Trip distance exceeds shape distance (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'trip_distance_exceeds_shape_distance' 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.
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.

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

    Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.

    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. Self-check a feed before you publish.

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

    Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.

    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. Self-check a feed before you publish.

  3. Re-generate shape distances in your export; flag to your vendor if it persists.

    Make the change. This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.

    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. Self-check a feed before you publish.

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 was 216 days ago.
Published accessibility data
Accessibility information is stated for 100% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
No fare information is published in the feed.
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

This feed is served from the TransitFeeds archive, which is no longer maintained. The most useful request is publishing the current feed from a live URL, then these fixes. Each fix names the validator notice and a guide link.

Score by category

Correctness0.0 / 100

The MobilityData validator flagged 19 kinds of issue across 785 instances (117 error, 117 warning, 551 informational).

Freshness35.0 / 100

This feed's calendar reached a scheduled service boundary 216 day(s) ago. Confirm your next service period is published so riders can keep planning trips.

Rider experience63.6 / 100

100% of stops state wheelchair accessibility (65% marked accessible, 35% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility100 / 100

100% of stops state accessibility (65% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (R005, R008, R066).

    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.

  • 124 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Beaver / Phoenix", "Beaver / Franklin SB", "Beulah / McConnell", and more).

    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.

Realtime qualityNot yet measured

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

Skip to route and stop data

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.

  • R010 (red)
  • R014 (brown)
  • R002 (blue)
  • R003 (green)
  • R004 (yellow)
  • R005 (orange)
  • R066 (red)
  • R007 (purple)
  • R008 (teal)
  • MTEX (brown)
Routes in Mountain Line's feed
RouteTypeLine color
R010 Route 10Busred
R014 Route 14Busbrown
R002 Route 2Busblue
R003 Route 3Busgreen
R004 Route 4Busyellow
R005 Route 5Busorange
R066 Route 66Busred
R007 Route 7Buspurple
R008 Route 8Busteal
MTEX Mountain ExpressBusbrown
List every stop
  • Beaver / Phoenix
  • Forest Meadows (Apts.)
  • Kendrick / Benton
  • Milton / University
  • Milton / Forest Meadows
  • 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
  • Lone Tree / Wood
  • Lone Tree / Brannen
  • Lone Tree / Franklin
  • Aspen (City Hall) EB
  • Santa Fe / Park WB
  • Woodlands Village
  • Fort Valley (Pioneer Museum)
  • Fort Valley / Winding Brook
  • Fort Valley / Valley Crest
  • Beulah / McConnell
  • Peak View / Mountain
  • Peak View / Cooper
  • Peak View / Fremont
  • Fremont / Lynette
  • Fort Valley / Meade SB
  • Fort Valley / Whipple
  • McConnell (SBS) EB
  • Thorpe / Bonito WB
  • Thorpe (Clark Homes) WB
  • Thorpe (Ball Fields) SB
  • Thorpe (Adult Center) SB
  • Route 66 (The Standard)
  • Aspen (City Hall) WB
  • Woodlands Village / University
  • Knoles (Campus Heights) NB
  • Route 66 / Pinnacle
  • Thompson Drive
  • Univ / Forest Meadows
  • Route 66 / Metz Walk
  • Milton / Northern Arizona Univ
  • University (Reilly)
  • Santa Fe / Park EB
  • Huntington (Walmart) EB
  • Fourth / Huntington NB
  • Fourth (Walgreens)
  • Sixth / Third
  • Sixth / First
  • Sixth / West
  • West / Felice
  • Beaver (NAU Bookstore)
  • Fourth / Cedar
  • Fourth / Felice
  • Fourth and Route 66
  • Fourth / Huntington SB
  • Huntington (Walmart) WB
  • Huntington Dr. / Grant St. EB
  • Huntington Dr. / Grant St. WB
  • Beaver / Franklin NB
  • Route 66 / Woodlands Village
  • Thorpe (Adult Center) NB
  • Thorpe (Ball Fields) NB
  • San Francisco / Benton
  • Thorpe (Clark Homes) EB
  • Thorpe / Bonito EB
  • Fort Valley / Stevanna
  • Fort Valley / Forest
  • Fremont (FALA)
  • Fremont (Cheshire Park)
  • Beaver (Flag Medical Ctr) NB
  • Fort Valley / Meade NB
  • Fort Valley (Museum of N. AZ)
  • Milton (Taco Bell)
  • Cherry / Leroux
  • 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
  • Milton / Forest Meadows
  • Milton / University
  • Milton / Plaza Way
  • Sawmill (Grove)
  • Gemini / Pine Cliff (BASIS)
  • Gemini / Pine Cliff (BASIS)
  • Downtown Connection Center
  • Fourth / Sparrow (NPA) SB
  • Fourth / Sparrow (NPA) NB
  • Route 66 / Switzer
  • Highway 180 / Snowbowl Rd.
  • Hart Prairie Lodge
  • Flag High Park and Ride
  • Desilva Ave/Beaver St
  • Route 66 / Ponderosa EB
  • Route 66 / Arrowhead EB
  • Route 66 / Fourth EB
  • Route 66 / Steves
  • Beaver / Franklin SB
  • Route 66 / Fanning
  • Route 66 / Country Club
  • Highway 89 / Smokerise
  • Christmas Tree / Snowflake
  • Winter / Christmas Tree
  • Flagstaff Mall Connection Ctr
  • Route 66 / Fanning
  • Route 66 / Steves
  • Route 66 / Fourth WB
  • Route 66 / Arrowhead WB
  • Beaver (Gillenwater)
  • Route 66 / Ponderosa WB
  • Route 66 / Switzer
  • Route 66 / San Francisco
  • San Francisco / Birch
  • San Francisco / Elm
  • Forest / Turquoise EB
  • Cedar / Gemini NB
  • Cedar / West EB
  • University (Wilson)
  • Cedar / Aris
  • Lockett / King EB
  • Lockett / Alta Vista EB
  • University Dr/S. Knoles Dr.
  • University Dr./S. Knoles Dr.
  • Lockett / Fanning EB
  • Kaspar (NAIPTA) EB
  • Lynch (FUTS Trail)
  • Cummings / Lynch
  • Kaspar (NAIPTA) WB
  • Lockett / Fanning WB
  • Knoles (Campus Heights) SB
  • Lockett / Manor
  • Lockett / Alta Vista WB
  • Lockett / King WB
  • Cedar / Fourth
  • Cedar / West WB
  • Cedar / Gemini SB
  • Forest / Turquoise WB
  • Beaver (Flagstaff Med Ctr) SB
  • Beaver / Hunt
  • Beaver / Birch
  • McConnell (SBS) WB
  • Butler / San Francisco EB
  • Butler / Elden EB
  • Butler / Cambridge
  • Butler (Marathon)
  • Butler (Napa)
  • Butler (Filiberto's)
  • Butler (Little America)
  • Foxglenn / Butler NB
  • Soliere / Foxlair (West) EB
  • Beulah (Wal-Mart)
  • Soliere / Foxlair (East ) EB
  • Soliere / Elk Run EB
  • Soliere (Butterfield) EB
  • Soliere (Timberline) EB
  • Country Club (B of A)
  • Soliere / Country Club
  • Soliere (Timberline) WB
  • Soliere (Butterfield) WB
  • Soliere / Elk Run WB
  • Forest Meadows (Shell)
  • Soliere / Foxlair (East) WB
  • Fairgrounds
  • Soliere / Foxlair (West) WB
  • Foxglenn / Butler SB
  • Butler (Black Barts)
  • Butler / Lucky WB
  • Butler Ave and Ponderosa Parkway
  • Butler
  • Butler / Sawmill
  • Butler / Elden WB
  • Butler / San Francisco WB
  • NAU
  • No stop

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 28.62026-07-30: 28.62026-07-31: 28.62026-08-01: 28.6
Show the numbers
CheckScoreChange
2026-07-2528.6 first check
2026-07-3028.6 no change
2026-07-3128.6 no change
2026-08-0128.6 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-31.

Same feed file as 2026-07-31; 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

24 findings, ordered by severity.

Show every finding
  • Error34 instances

    Trip distance exceeds shape distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules

  • Error30 instances

    Duplicate key (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: duplicate_key · See MobilityData GTFS Validator rules

  • Error22 instances

    Some trips have stop times whose distances along the route go backwards.

    Apps can show buses jumping backwards or mis-order stops.

    Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)

    Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules

  • Error17 instances

    Block trips with overlapping stop times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules

  • Error10 instances

    Stop time with arrival before previous departure time (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: stop_time_with_arrival_before_previous_departure_time · See MobilityData GTFS Validator rules

  • Error4 instances

    Equal shape distance diff coordinates (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: equal_shape_distance_diff_coordinates · See MobilityData GTFS Validator rules

  • Warning510 instances

    510 of 551 trips lack rider-facing destination or direction text.

    When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices

  • Warning43 instances

    The feed contains route shapes no trip uses.

    Harmless to riders, but it bloats the feed and suggests stale export data.

    Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

    Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning26 instances

    Some stops sit far from the route line, going by the feed's own distance values.

    Trip planners may draw the route down the wrong streets or point riders to the wrong corner.

    Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)

    Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning19 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 · See MobilityData GTFS Validator rules

  • Warning11 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.)

    Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning10 instances

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

    Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning3 instances

    On some trips the stop distances run a little past the end of the route line.

    The stop and shape distance values don't quite line up, so any math that uses them can drift.

    Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)

    Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

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

    Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    A file GTFS asks for (usually feed_info.txt) is missing.

    feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.

    Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)

    Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    Some stops sit far from the route line they belong to.

    Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

    Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    On some trips the stops fall along the route line in a different order than the schedule lists.

    Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.

    Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)

    Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules

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

    Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    The published calendar ended 216 day(s) ago at a boundary between the feed's own scheduled service periods.

    The calendar encodes distinct service periods (like academic terms), so this looks like a planned transition rather than a lapse — but trip planners still show nothing until the next period is published.

    Fix: Confirm your next service period is published: export its calendar and set feed_info feed_end_date past it. (One export when the next period's schedule is set.)

    Finding code: scorecard_planned_service_boundary

  • Warning1 instance

    feed_info.txt is missing its start/end dates (the file itself is absent)

    Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

    Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

    Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules

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

    Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • Info550 instances

    Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules

  • Info1 instance

    Unsorted stop times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. 6 validator errors to resolve. Service data expired 216 days ago, so FTA would find the link out of date.

Published Ready
Published at a public URL.
Valid Needs attention
6 validator errors to resolve.
Current Not ready
Service data expired 216 days ago, so FTA would find the link out of date.
agency_id provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
agency_id equals your NTD ID (optional) Not checked yet
This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
shapes.txt covers your trips Ready
All 551 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, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

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). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also 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. 6 validator errors to resolve. Service data expired 216 days ago.

Valid Not yet
6 validator errors to resolve.
Current Not yet
Service data expired 216 days ago.
Accessible Met
States wheelchair access on 100% of stops and 100% of trips.

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.

  • 11 of 181 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. The feed also carries 117 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, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

Correctness 0 / 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. FTA NTD readiness also checks that the published feed is valid.
Freshness 35 / 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. FTA NTD readiness also checks that the published feed is current.
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.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Mountain Line GTFS data quality grade: F

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-1148/2026-08-01.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-08-01. 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.