Feed status · checked 2026-08-01
Rio Metro Regional Transit District
Based on the feed this agency publishes
Service mode Rail + Bus
unchanged since 2026-07-31
Catalogued 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.3, validator 8.0.1.
Checked for changes 9 hours ago; last changed 41 days ago.
Measured 3 of 4 score categories from the agency's own feed.
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 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
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 823 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the transit vehicles 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 in its category
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no transit vehicle is scheduled to arrive.
⏱ A review pass in your scheduling software.worth about +6 points in its category
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 +6 points in its category
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
- Service data ended 823 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service 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
- Feed evidence
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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
- Feed evidence
- Some service calendars in the feed have already ended.
- Next action
- Remove past service periods the next time you export the 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.
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.
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.
Remove retired stops from the export, or add them back to the trips that should serve them. · Read the fix guide
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.
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.
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 823 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
- Fare information is published using GTFS Fares v1.
- 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.
Score by category
The MobilityData validator flagged 7 kinds of issue across 40 instances (0 error, 37 warning, 3 informational).
Service data ended 823 day(s) ago. Trip planners have likely already dropped this feed.
100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
101 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Los Ranchos/Journal Center Rail Runner Station", "Santa Fe County/N.M. 599 Rail Runner Station", "Sandoval County/U.S. 550 Rail Runner Station", 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.
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.
This feed has 151 stops.
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.
- 201 (green)
- 202 (green)
- 204 (green)
- 206 (green)
- 208 (green)
- 209 (green)
- 210 (green)
- 366 (green)
- 505 (green)
- 8 (green)
- NMRX (black)
| Route | Type | Line color |
|---|---|---|
| 201 Bernalillo / Enchanted Hills | Bus | green |
| 202 | Bus | green |
| 204 Bernalillo / Jemez Springs | Bus | green |
| 206 | Bus | green |
| 208 | Bus | green |
| 209 | Bus | green |
| 210 | Bus | green |
| 366 | Bus | green |
| 505 Sandoval County / US 550 to Albuquerque | Bus | green |
| 8 Bernalillo / Cuba | Bus | green |
| NMRX | Rail | black |
List every stop
- West Reinken Avenue @ 10th Street
- West Reinken Avenue @ 10th Street
- Fresnius Dialysis
- Sandsage and Los Morros
- NM 6 & Valencia
- Start EB
- NM 6 & Luna
- NM 6 & Los Cerritos
- NM 6 & Los Lentes
- NM 6 and Carson Dr
- NM 6 & Luna
- NM 6 & Camelot
- NM 6 & Los Lentes
- NM 6 & Los Cerritos
- NM 6 & Hunning Ranch Loop
- NM6 & Desert Willow
- NM 6 & Valencia
- NM 6 & Carson
- NM 6 & Emilio Lopez
- Los Morros & Wallmart Distribution Center
- N 3rd Street @ W Reinken Avenue
- N 3rd Street @ W Reinken Avenue
- Central/Unser (C.U.T.C. Bay A)
- A.T.C. (Bay N)
- Downtown Albuquerque Rail Runner Station
- Algodones
- Alvarado Transportation Center
- Bearhead Canon
- Bearhead Canon
- Belen Rail Runner Station
- Bernalillo High School
- Bernalillo County Rail Runner Station
- Canal Boulevard @ Blue Bench Inlet
- Canal Boulevard @ Blue Bench Inlet
- NM 47 @ Esperanza Rd. (Bosque Farms)
- NM 47 @ Esperanza Rd. (Bosque Farms)
- Cañon Senior Center
- Rt. 66 Casino
- Huning Ranch Loop @ Chisholm Avenue
- Valencia Dr @ Cibola Dr
- Cibola Dr @ Valencia Dr
- Cochiti Elementary
- Town of Cochiti Lake
- Cochiti Pueblo
- Jager Way @ Carr Way
- Jager Way @ Picabo St
- Crestview Drive @ Empty Lot
- Crestview Drive @ Empty Lot
- Cuba Elementary School
- Cuba High School
- Cuba High School
- Cuba Middle School
- Cuba Municipal Complex
- S Mesa Road @ W Delgado Avenue
- S Mesa Road @ W Delgado Avenue
- Desert Lily Avenue @ Lone Star Street
- Main Street @ Don Pasqual
- Main Street @ Don Pasqual
- Downtown Bernalillo Rail Runner Station
- S Mesa Road @ Edith Drive
- S Mesa Road @ Edith Drive
- Canal Boulevard @ Encantada Apartments
- Canal Boulevard @ Encantada Apartments
- Entrada Drive @ Camelot Blvd.
- Entrada Drive @ Camelot Blvd.
- Lonestar Street @ Fire Wheel Avenue
- S Mesa Road @ Gilbert Avenue
- S Mesa Road @ Gilbert Avenue
- Golden Gate Drive @ Camelot Blvd.
- Golden Gate Drive @ Camelot Blvd.
- Grayson Hills Dr @ Brighton Hills Dr
- Grayson Hills Dr @ Brighton Hills Dr
- Hillside Drive @ Crestview Drive
- Crestview Drive @ Hillside Drive
- Safelite (Sprint) Blvd @ Home Depot
- Safelite (Sprint) Blvd @ Home Depot
- Huning Ranch Loop @ Sundance Street
- Canal Boulevard @ Inlet across House #611
- Canal Boulevard @ Inlet across House #611
- Isleta Pueblo Rail Runner Station
- Jemez Pueblo Trail House
- Jemez School
- Jemez School
- Jemez Pueblo Civic Center
- Jemez Pueblo Civic Center
- Jemez Springs Village Complex
- Kewa Rail Runner Station
- Camino de Llano @ Christopher Dr (Westside Apartments)
- Camino del Llano @ S Mesa Road
- Los Ranchos/Journal Center Rail Runner Station
- Los Lunas Rail Runner Station
- Los Lunas Rail Runner Station
- Mackenzie Drive @ Dara Drive
- Mackenzie Drive @ Dara Drive
- NM 6 @ NM 47
- NM 6 @ NM 47
- Main St. @ Camino del Llano
- Main St. @ Camino del Llano
- McDonald's / Circle K
- McDonald's / Circle K
- S Mesa Road @ Michael Don Avenue
- S Mesa Road @ Michael Don Avenue
- Montaño Rail Runner Station
- NM 47 @ N. El Cerro Lp.
- NM 47 @ N. El Cerro Lp.
- Jager Way @ Albertsons
- Jager Way @ NM State Offices
- Otero Street @ Crosswalk
- Panada Drive @ Camelot Boulevard
- Panada Drive @ Camelot Boulevard
- Pena Blanca
- Pena Blanca
- NM 47 @ Molina Rd. (Peralta)
- NM 47 @ Molina Rd. (Peralta)
- Red Mesa @ Sundance Street
- Red Stand @ Walatowa Center
- Red Stand @ Walatowa Center
- NM 4 @ Redwood Grove
- West Reinken Avenue @ Main Street
- West Reinken Avenue @ Main Street
- NM 147 east of Rio Grande Bridge
- Sandia Pueblo Rail Runner Station
- Sandoval County/U.S. 550 Rail Runner Station
- Sandoval County Court House - Bernalillo
- Sandoval County Govt. Complex
- Sandoval County/U.S. 550 Station Bus
- Santa Ana Pueblo Tribal Office
- Santa Domingo Elementary
- Santa Domingo Head Start/Health Center
- Santa Domingo Tribal Office
- San Ysidro Village Office
- NM 4 @ Sawmill
- NM 4 @ Sawmill
- Santa Fe Depot Rail Runner Station
- Santa Fe County/N.M. 599 Rail Runner Station
- Lonestar Street @ Silver Sage Avenue
- South Capitol Rail Runner Station
- Solitude @ Sundance Street
- Stanley Dr @ Safelite Building
- Stanley Dr @ Safelite Building
- Fulcrum Way @ Tri-State Generation
- Fulcrum Way @ Tri-State Generation
- Fulcrum Way @ Tri-State Generation
- U.N.M. Valencia
- Valley View Drive @ Camelot Boulevard
- Valley View Drive @ Camelot Boulevard
- Wal-Mart
- West Aragon @ N 11th Street
- West Aragon @ N 11th Street
- Capitol Square Drive
- Zia Road Rail Runner Station
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 63.0 | first check |
| 2026-07-30 | 63.0 | no change |
| 2026-07-31 | 63.0 | no change |
| 2026-08-01 | 63.0 | 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
9 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 823 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the transit vehicles 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.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning19 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no transit vehicle 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 (opens the validator rules on an external site)
- Warning11 instances
11 of 221 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 (opens GTFS Best Practices on an external site)
- Warning8 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 (opens the validator rules on an external site)
- Warning8 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 · 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 · 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Platform without parent station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the transit vehicle ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Finding code: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 823 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 823 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 221 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. Service data expired 823 days ago.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 823 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.
- 19 of 151 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
How this agency maps to the standards
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 73 / 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 99 / 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.
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/rio-metro-regional-transit-district/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.