Feed status · checked 2026-11-21

Mountain Metropolitan Transit

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

47.1 / 100

unchanged since 2026-11-20

Cataloged in Colorado.

Feed expiredRealtime not yet published

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

Checked 2026-11-08: the feed URL on file had stopped working, so this record now tracks coloradosprings.gov, the current address Transitland lists for this feed. The agency name and service area in that file match this record. Grades dated before this change came from an older Mobility Database mirror copy.

Top things to fix

Fix 01

Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.Likely your export tool

Service data ended 28 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.

This one is about the feed as a whole, so there is no share of it to count.

⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category

Fix 02

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.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Colorado as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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. Fix 01 · Read the fix guide for scorecard_feed_expired

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. Fix 02 · Read the fix guide for scorecard_no_fare_data

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Fix 03 · Read the fix guide for mixed_case_recommended_field

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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 28 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

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.

About this feed

Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.

Mountain Metropolitan Transit’s published feed lists 32 bus routes, 4,362 scheduled trips and 986 stops. Its service dates run from 2026-03-29 through 2026-10-24. The published file last changed on 2026-11-09.

Score by category

Correctness53.5 / 100

The MobilityData validator flagged 11 kinds of issue across 1885 instances (0 error, 1884 warning, 1 informational).

Freshness0.0 / 100

Service data ended 28 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience75.9 / 100

100% of stops state wheelchair accessibility (0% marked accessible, 100% 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 (0% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (23, 27, 32, 38, 7).

    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.

  • 906 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Fontmore/Mesa", "Colorado/30th", "Robinson/Bott", 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 986 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.

  • 1 (pink)
  • 10 (white)
  • 11 (gray)
  • 12 (brown)
  • 14 (teal)
  • 15 (teal)
  • 16 (pink)
  • 17 (red)
  • 18 (yellow)
  • 19 (yellow)
  • 2 (yellow)
  • 22 (orange)
  • 23 (brown)
  • 24 (pink)
  • 25 (yellow)
  • 27 (gray)
  • 3 (white)
  • 32 (purple)
  • 33 (green)
  • 34 (gray)
  • 35 (brown)
  • 37 (brown)
  • 38 (pink)
  • 39 (teal)
  • 4 (teal)
  • 40 (pink)
  • 5 (red)
  • 6 (teal)
  • 7 (red)
  • 8 (teal)
  • 9 (yellow)
  • ZEB (pink)
Routes in Mountain Metropolitan Transit's feed
RouteTypeLine color
1 Hillside - Hancock PlazaBuspink
10 Hwy 115 - PPSCBuswhite
11 World Arena - PPSCBusgray
12 Palmer Park BlvdBusbrown
14 Chestnut St - G.O.G. RdBusteal
15 FOUNTAIN BLVD -E CHEYENNE MTN BLVDBusteal
16 Brookside - Uintah GardensBuspink
17 19TH STREET/FILLMOREBusred
18 Union BlvdBusyellow
19 WEBER - EAGLE ROCKBusyellow
2 CENTENNIAL BLVD - G.O.G. RdBusyellow
22 SOUTHBOROUGH VIA MURRAY BLVDBusorange
23 Barnes Rd. - Tutt BlvdBusbrown
24 Galley Rd - Tutt BlvdBuspink
25 N. ACADEMY BLVD - VOYAGERBusyellow
27 S. ACADEMY BLVD - PPSCBusgray
3 COLORADO AVE - MANITOUBuswhite
32 SECURITY/WIDEFIELDBuspurple
33 INCLINE/COG SHUTTLEBusgreen
34 GOG/AUSTIN BLUFFS PKWYBusgray
35 LAS VEGAS ST/ PPSCBusbrown
37 Amazon/ AirportBusbrown
38 UNION/ CHILDRENS HOSPITALBuspink
39 CORPORATE DR - VOYAGER PKWYBusteal
4 S. 8th STREET - BROADMOORBusteal
40 VOYAGER - RAMPART PPSCBuspink
5 Boulder - CitadelBusred
6 FILLMORE - CitadelBusteal
7 Pikes Peak Ave. - CitadelBusred
8 Cache La Poudre - CitadelBusteal
9 NEVADA - UCCSBusyellow
ZEB ZEB Downtown ShuttleBuspink
List every stop
  • Fontmore/Mesa
  • 8th/Lower Gold Camp
  • Spruce/St Vrain
  • Spruce/Willamette
  • Spruce/Dale
  • Walnut/Yampa
  • Walnut/Columbia
  • Academy/Hartford
  • Academy/Drennan
  • 3279 Academy
  • Academy/Astrozon
  • Academy/Chelton
  • Academy/Pace
  • Academy/Wentworth
  • Academy/Airport
  • Academy/Pikes Peak
  • Academy/Bijou
  • Academy/Galley
  • Academy/San Miguel
  • Academy/Palmer Park
  • Academy/La Salle
  • Academy/Constitution
  • Academy/Maizeland
  • Academy/Hartstock
  • Academy/Village
  • Academy/Carefree
  • Academy/Half Turn
  • Academy/Meadowland
  • Academy/Flintridge
  • Academy/Union
  • Academy/Montebello
  • Academy/Vickers
  • Academy/Lehman
  • Academy/Dublin
  • Academy/Brookwood
  • Academy/Shrider
  • Academy/Agora
  • Kelly Johnson/Goddard
  • 1155 Kelly Johnson
  • 1070 Kelly Johnson
  • Academy/Kelly Johnson
  • Academy/Goddard
  • Academy/Shrider
  • Academy/York
  • Academy/Dublin
  • Academy/Lehman
  • Academy/Vickers
  • Academy/Anglo
  • Academy/Montebello
  • Academy/Union
  • Academy/Flintridge
  • Academy/Meadowland
  • Academy/Morning Sun
  • Academy/American
  • Academy/Betty
  • Academy/Carefree
  • Academy/Parkmoor Village
  • Academy/Hartsock
  • Academy/Maizeland
  • Academy/Constitution
  • Academy/La Salle
  • Academy/Palmer Park
  • Academy/San Miguel
  • Citadel/Academy
  • Citadel/Portal
  • Academy/Bijou
  • Academy/Pikes Peak
  • Academy/Airport
  • Academy/Early Sun
  • Academy/Fountain
  • Academy/Pace
  • Academy/Chelton
  • Academy/Astrozon
  • Academy/Super Stop
  • Academy/Jet Wing
  • Academy/Hartford
  • Chestnut/Caramillo
  • Chestnut/Fontanero
  • Chestnut/Monroe
  • Chestnut/Van Buren
  • Chestnut/Green Ridge
  • 3211 Chestnut
  • Chestnut/Ellston
  • Chestnut/Edwinstowe
  • Chestnut/Hoorne
  • 4339 Chestnut
  • Holland Park/Edwinstowe
  • Holland Park/Forrest Hill
  • 4103 Centennial
  • Centennial/High Tech
  • Parkside/International
  • 3141 Colorado
  • 4575 CENTENNIAL BLVD
  • Centennial/Pinon Valley OB
  • 30th/Flying W Ranch FS
  • 2151 Garden of the Gods
  • GoG/Centennial
  • 1901 Garden of the Gods
  • 1675 GoG/El Paso County Offices
  • GoG/Centennial
  • GoG/Forrest Hill
  • GoG/Forge
  • GoG/Chestnut
  • GoG/Northpark
  • GoG/Mark Dabling
  • Austin Bluffs/Nevada
  • Austin Bluffs/Mallow EB
  • Austin Bluffs/Regent
  • Austin Bluffs/Goldenrod
  • Austin Bluffs/American
  • Austin Bluffs/Academy
  • Austin Bluffs/Meadowland
  • Austin Bluffs/Goldenrod
  • Austin Bluffs/Union FS
  • Austin Bluffs/Regent
  • Austin Bluffs/Mallow WB
  • GoG/Nevada
  • GoG/Enterprize
  • GoG/Northpark
  • GoG/Chestnut
  • GoG/Forge
  • GoG/Elkton
  • GoG/Forrest Hill
  • 1460 Garden of the Gods
  • 1675 Garden of the Gods
  • 1900 Garden of the Gods
  • 30th/Flying W Ranch
  • 30th/Centauri
  • 5050 Centennial
  • Centennial/List
  • 4710 Centennial
  • Centennial/High Tech
  • Centennial/Creekview
  • Holland Park/Forrest Hill
  • Holland Park/Edwinstone
  • Holland Park/Chestnut
  • Chestnut/Hoorne
  • Chestnut/Darby
  • Chestnut/Edwinstowe
  • Chestnut/Vondel Park
  • 3210 Chestnut
  • Chestnut/Prestonwood
  • Chestnut/Van Buren
  • Chestnut/Monroe
  • Chestnut/Fontanero
  • Chestnut/Caramillo
  • Walnut/Columbia
  • Walnut/Yampa
  • Spruce/Dale
  • Spruce/Willamette
  • Spruce/St Vrain
  • Spruce/Platte
  • 722 Wahsatch
  • Fountain/Corona
  • Fountain/Prospect
  • Fountain/Institute
  • Fountain/Hancock
  • Fountain/Union
  • Fountain/Circle
  • Fountain/Circle
  • Fountain/Hutchinson
  • Fountain/Union
  • Fountain/Fountain
  • Fountain/Cedar
  • Fountain/Institute
  • Fountain/Prospect
  • Fountain/Corona
  • Wahsatch/Rio Grande
  • Academy/Fountain
  • Capulin/Yosemite
  • Capulin/Shasta
  • Capulin/Shenandoah
  • CARMEL/CAPULIN
  • Academy/Austin Bluffs
  • Circle/Janitell E
  • Circle/Janitell W
  • 2945 Las Vegas
  • Maxwell/Corning
  • Maxwell/Glenwood
  • Maxwell/Claiborne
  • Venetucci/Cheyenne Mtn
  • Circle/Janitell E
  • Capulin/Carmel
  • Capulin/Shenandoah
  • Capulin/Shasta
  • Capulin/Yosemite
  • Murray/Edison
  • Murray/Maxwell
  • Murray/Galley
  • Murray/Bijou
  • 2150 Garden of the Gods
  • Murray/Galley
  • Murray/Maxwell
  • Murray/Platte
  • 4110 Tutt
  • Tutt/Barnes
  • Austin Bluffs/Siferd
  • Murray/Pikes Peak
  • Robinson/Bott
  • Barnes/Austin Bluffs
  • Tutt/New Center Pt
  • Uintah/Glenview
  • 2660 Uintah
  • Uintah/24th
  • Uintah/21st
  • 935 N 19th
  • 19th/Koshare
  • King/Tonka
  • King/Friendship
  • King/25th
  • King/Pioneer
  • King/30th
  • Fontanero/30th
  • 902 Fontmore
  • 19th/Koshare
  • 914 N 19th
  • Uintah/20th
  • Uintah/24th
  • 2660 Uintah
  • Uintah/28th
  • 30th/Platte
  • 21st/Skyview
  • Moreno/Communication
  • Lower Gold Camp/21st
  • Murray/Airport
  • Murray/Chapman
  • Murray/Conquista
  • Chelton/Lancaster
  • 2145 Chelton
  • Chelton/Lexington Village
  • Astrozon/Gina
  • Astrozon/Morley
  • 3073 Hancock Expy
  • Colorado/30th
  • Hancock/Monica
  • Fontaine/Widefield
  • Fontaine/Amherst
  • Galley/Space Center
  • Fontaine/Cornell
  • Fontaine/Grinnell
  • Fontaine/Kokomo
  • Fontaine/Drury
  • Galley/5910 Galley
  • Hancock/Monica
  • Hancock/Jet Wing
  • Terminal
  • Murray/Pikes Peak
  • Murray/Bijou
  • Platte/Boulder
  • Fillmore/El Paso
  • and 736 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 13 checks — unchanged since 2026-11-20.

2026-11-09: 47.12026-11-10: 47.12026-11-11: 47.12026-11-12: 47.12026-11-13: 47.12026-11-14: 47.12026-11-15: 47.12026-11-16: 47.12026-11-17: 47.12026-11-18: 47.12026-11-19: 47.12026-11-20: 47.12026-11-21: 47.1
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0947.1 first check
2026-11-1047.1 no change
2026-11-1147.1 no change
2026-11-1247.1 no change
2026-11-1347.1 no change
2026-11-1447.1 no change
2026-11-1547.1 no change
2026-11-1647.1 no change
2026-11-1747.1 no change
2026-11-1847.1 no change
2026-11-1947.1 no change
2026-11-2047.1 no change
2026-11-2147.1 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-09 to 2026-11-21 (13 checks)33df4051cfc02026-10-24Current rubric: see the trend above
2026-10-02 to 2026-11-06 (35 checks)1abb7aaac18b2025-09-27F, 44.3 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-07-25 to 2026-10-01 (65 checks)1abb7aaac18b2025-09-27F, 44.3 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-13 to 2026-07-24 (9 checks)1abb7aaac18b2025-09-27F, 44.3 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-12 (24 checks)1abb7aaac18b2025-09-27F, 44.3 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

Everything we checked

15 findings, ordered by severity.

Show every finding
  • Error1 instance

    Service data ended 28 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. Set feed_end_date in feed_info.txt past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)

    Finding code: scorecard_feed_expired · Read the fix guide for scorecard_feed_expired · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning1848 instances

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

    Finding code: mixed_case_recommended_field · Read the fix guide for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning402 instances

    402 of 4362 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.

    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 for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Warning26 instances

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

    See the linked rule for what this affects.

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

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules 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.)

    Finding code: expired_calendar · Read the fix guide for expired_calendar · 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.)

    Finding code: feed_expiration_date7_days · Read the fix guide for feed_expiration_date7_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Same name and description for stop (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some service calendars have no days of the week switched on.

    Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

    Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)

    Finding code: service_has_no_active_day_of_the_week · Read the fix guide for service_has_no_active_day_of_the_week · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    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 for stop_too_far_from_shape_using_user_distance · 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.)

    Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide for trip_coverage_not_active_for_next7_days · 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.)

    Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)

  • Info1 instance

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Finding code: unknown_file · Read the fix guide for unknown_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Info1 instance

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

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

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

    Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

How we measured this

Checked for changes 18 hours ago; last changed 12 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

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

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. Service data expired 28 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 28 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 4362 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

One requirement remains for this feed to earn the conformance mark. Service data expired 28 days ago.

Valid Met
Passes validation with no errors.
Current Not yet
Service data expired 28 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.

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

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.

A local transit-data support resource is CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers. This resource supports agencies; it is not a scoring authority.

Correctness 54 / 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 0 / 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 76 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the Colorado portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Colorado

Other scorecards in Colorado, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Mountain Metropolitan Transit: GTFS feed quality grade F, 47.1 of 100, checked 2026-11-21. GTFS 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-metropolitan-transit-2356/2026-11-21.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-11-21. 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.