Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
ABQ RIDE
Based on the feed this agency publishes
down 0.4 since 2026-07-08
Ahead of 52% of all tracked agencies and 63% of large agencies. Operates in New Mexico.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.1, validator 8.0.1.
Checked for changes 16 minutes ago; last changed 17 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
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.
Equal shape distance diff coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points
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
1758 of 1758 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
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.
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +8 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.
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.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 11 kinds of issue across 1922 instances (11 error, 1907 warning, 4 informational).
Service data covers the next 57 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (198).
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.
1701 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Wyoming @ Trumbull", "Wyoming @ Zuni", "Wyoming @ Chico", 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.
This agency publishes realtime, but the feed needs an access key we don't have yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (orange)
- 10 (red)
- 140 (blue)
- 141 (purple)
- 155 (orange)
- 157 (green)
- 16 (pink)
- 198 (green)
- 2 (orange)
- 31 (brown)
- 5 (orange)
- 50 (brown)
- 53 (teal)
- 54 (teal)
- 66 (teal)
- 766 (red)
- 777 (green)
- 8 (purple)
- 97 (blue)
- 11 (purple)
- 790 (blue)
- 52 (brown)
| Route | Type | Line color |
|---|---|---|
| 1 Juan Tabo | Bus | orange |
| 10 North 4th St. | Bus | red |
| 140 San Mateo / CNM Work Force | Bus | blue |
| 141 San Mateo | Bus | purple |
| 155 Coors | Bus | orange |
| 157 Cottonwood/Montano/UTC | Bus | green |
| 16 Broadway/University/Gibson | Bus | pink |
| 198 98th / Dennis Chavez | Bus | green |
| 2 Eubank-Ventura | Bus | orange |
| 31 Wyoming | Bus | brown |
| 5 Montgomery/Carlisle | Bus | orange |
| 50 Airport/Downtown | Bus | brown |
| 53 Isleta | Bus | teal |
| 54 Bridge/Westgate | Bus | teal |
| 66 Central Avenue | Bus | teal |
| 766 ART Red Line | Bus | red |
| 777 ART Green Line | Bus | green |
| 8 Menaul | Bus | purple |
| 97 Zuni Express | Bus | blue |
| 11 Lomas | Bus | purple |
| 790 Coors/University | Bus | blue |
| 52 South Broadway-Rio Bravo | Bus | brown |
This feed has 1758 stops.
List every stop
- Wyoming @ Trumbull
- Wyoming @ Zuni
- Wyoming @ Chico
- Wyoming @ Domingo
- Wyoming @ Marquette
- Wyoming @ Lomas
- Wyoming @ Mountain
- Wyoming @ Constitution
- Wyoming @ Constitution
- Wyoming @ Aspen
- Wyoming @ Hannett
- Wyoming @ Indian School
- Wyoming @ Northeastern
- Wyoming @ Apache
- Wyoming @ Menaul
- Wyoming @ Claremont
- Wyoming @ Candelaria
- Wyoming @ La Camila
- Wyoming @ Dellwood
- Wyoming @ Comanche
- Wyoming @ Montgomery
- Wyoming @ Montgomery
- Wyoming @ Gutierrez
- Wyoming @ Northridge
- Wyoming @ Spain
- Wyoming @ Spain
- Wyoming @ Academy
- Wyoming @ Cubero
- Wyoming @ Burlison
- Wyoming @ Harper
- Wyoming @ Harper
- Wyoming @ Curry
- Wyoming @ Loma Del Norte
- Wyoming @ San Francisco
- Wyoming @ Krim (Church P-n-R)
- Wyoming @ Carmel
- Wyoming @ Corona
- Wyoming @ Wilshire
- Wyoming @ Wilshire
- Wyoming @ Holly
- Wyoming @ Paseo Del Norte
- Wyoming @ San Francisco
- Wyoming @ Curry
- Wyoming @ San Antonio
- Wyoming @ San Antonio
- Wyoming @ Burlison
- Wyoming @ Cubero
- Wyoming @ Spain
- Wyoming @ Spain
- Wyoming @ Osuna
- Wyoming @ La Mirada
- Wyoming @ James
- Wyoming @ Comanche
- Wyoming @ Dellwood
- Wyoming @ Candelaria
- Wyoming @ Candelaria
- Wyoming @ Claremont
- Wyoming @ Menaul
- Wyoming @ Apache
- Wyoming @ Northeastern
- Wyoming @ Indian School
- Wyoming @ Aspen
- Wyoming @ Constitution
- Wyoming @ Lomas
- Wyoming @ Marquette
- Wyoming @ Grand
- Wyoming @ Chico
- Wyoming @ Central
- Wyoming @ Central
- Wyoming @ Zuni
- Wyoming @ Trumbull
- Taylor Ranch @ Kachina
- Golf Course @ La Orilla
- Golf Course @ Homestead Circle
- Golf Course @ Homestead Trl.
- Golf Course @ Butterfield
- Golf Course @ Calle Nortena
- Golf Course @ Las Terrazas
- Golf Course @ Shelly Rose
- Golf Course @ Jill Patricia
- Golf Course @ Paradise
- Golf Course @ Congress
- Golf Course @ Country Club Ln.
- Golf Course @ Avocet
- Ellison @ Golf Course
- Ellison @ 7 Bar Loop North
- Ellison @ Cibola Loop West
- Ellison @ Cibola Loop West
- Ellison @ North Seven Bar Loop
- Golf Course @ Cabacillas Arroyo
- Golf Course @ Irving
- Golf Course @ Country Club
- Golf Course @ Paradise
- Golf Course @ Shelly Rose
- Golf Course @ Las Terrazas
- Golf Course @ Calle Nortena
- Golf Course @ Homestead Trail
- Golf Course @ Homestead Cir South
- Golf Course @ Taylor Ranch
- Taylor Ranch @ Kachina
- Lomas @ 4th
- 2nd @ Lomas
- 2nd @ Marquette (Convention Center)
- Martin Luther King @ Broadway
- Martin Luther King @ Elm
- University @ Martin Luther King
- University @ Las Lomas
- Lomas @ University
- Martin Luther King @ University
- Martin Luther King @ Elm
- Martin Luther King @ Broadway
- Coors @ Cottonwood Loop
- 2nd @ Copper
- Lead @ 5th
- 4th @ Santa Fe
- 4th @ Cromwell
- Bridge @ Hartline
- Bridge @ Young Avenue
- Bridge @ Sunset Rd
- Bridge @ Gatewood
- Bridge @ Goff
- Bridge @ Pear
- Bridge @ Anthony
- Bridge @ Atrisco
- Bridge @ Abo
- Bridge @ Foothill
- Old Coors @ Bridge
- Old Coors @ Amalia
- Coors @ Eduardo
- Arenal @ Secret Valley
- Arenal @ Fox Hill
- Sapphire @ Zircon
- Sapphire @ Lucretia
- 86th St. @ Sapphire
- 86th @ Benavides
- Benavides @ 94th
- Benavides @ Del Mastro
- 98th St. @ Westgate Park
- 98th @ Demi Rd
- 98th @ Eucariz
- 98th @ Tower
- 98th @ Westgate Park Plaza
- Benavides @ 98th
- Benavides @ 94th
- 86th @ Benavides
- 86th St. @ Sapphire
- Sapphire @ Corriz
- Sapphire @ 82nd Street
- Arenal @ Unser
- Arenal @ Secret Valley
- Coors @ Arenal
- Coors @ Old Coors
- Old Coors @ Amalia
- Bridge @ Atrisco
- Bridge @ Anthony
- Bridge @ Goff
- Bridge @ Gatewood
- Bridge @ Saavedra
- Av Dolores Huerta @ La Vega
- 4th @ Bridge
- 4th @ Barelas
- 4th @ Santa Fe
- 4th @ Stover
- 4th @ Iron
- Wenonah @ Dorado
- Dorado @ Wenonah
- Dorado @ Dunes Road
- Singing Arrow @ Dorado
- Singing Arrow @ Western Skies
- Singing Arrow @ Parkside
- Singing Arrow @ Fawn Trail
- Juan Tabo @ Cochiti
- Juan Tabo @ Central
- Juan Tabo @ Copper
- Juan Tabo @ Gable Lane
- Juan Tabo @ Lomas
- Juan Tabo @ Lomas
- Juan Tabo @ Mountain Rd
- Juan Tabo @ Constitution
- Juan Tabo @ Princess Jeanne
- Juan Tabo @ Indian School
- Juan Tabo @ Brentwood Hills
- Juan Tabo @ Menaul
- Juan Tabo @ Menaul
- Juan Tabo @ Phoenix
- Juan Tabo @ Lexington
- Juan Tabo @ Candelaria
- Juan Tabo @ Candelaria
- Juan Tabo @ Golden Gate
- Juan Tabo @ Comanche
- Juan Tabo Blvd @ Juan Tabo Place
- Juan Tabo @ Cielito Lindo
- Juan Tabo @ Montgomery
- Juan Tabo @ Baja
- Juan Tabo @ Osuna
- Juan Tabo @ Spain
- Juan Tabo @ Camero
- Juan Tabo @ Burnhamwood
- Juan Tabo @ Malaguena
- Juan Tabo @ Tierra Antigua
- Eubank @ Juan Tabo
- Academy @ Eubank
- Academy @ Rolling Hills
- Academy @ Carruthers
- Academy @ Academy Ridge
- Academy @ Lowell
- Lowell @ Academy
- Lowell @ San Victorio
- Lowell @ Spain
- Spain @ Nugget
- Spain @ Luttrell
- Spain @ Carruthers
- Juan Tabo @ Osuna
- Juan Tabo @ Baja
- Juan Tabo @ Montgomery
- Juan Tabo @ Juan Tabo Place
- Juan Tabo @ Comanche
- Juan Tabo @ Candelaria
- Juan Tabo @ Candelaria
- Juan Tabo @ Claremont
- Juan Tabo @ Phoenix
- Juan Tabo @ Menaul
- Juan Tabo @ Menaul
- Juan Tabo @ Brentwood Hills
- Juan Tabo @ Indian School
- Juan Tabo @ Haines
- Juan Tabo @ Princess Jeanne
- Juan Tabo @ Constitution
- Juan Tabo @ Mountain
- Juan Tabo @ Lomas
- Juan Tabo @ Lomas
- Juan Tabo @ Marquette
- Juan Tabo @ Copper
- Juan Tabo @ Buena Ventura
- Juan Tabo @ Cochiti
- Singing Arrow @ Traiding Post Tr.
- Singing Arrow @ Fawn Trail
- Singing Arrow @ Horseshoe Trail
- Singing Arrow @ Western Skies
- Dorado @ Singing Arrow
- Dorado @ Wenonah
- Dorado @ Cochiti
- Eubank @ Cochiti
- Eubank @ Southern
- Eubank @ Gibson
- Eubank @ La Entrada
- Eubank @ Central
- Eubank @ Buena Ventura
- Eubank @ Chico
- Eubank @ Chico
- and 1508 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 20 checks — down 0.4 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 63.2 | first check |
| 2026-06-20 | 63.2 | no change |
| 2026-06-21 | 63.2 | no change |
| 2026-06-22 | 63.2 | no change |
| 2026-06-23 | 63.2 | no change |
| 2026-06-24 | 63.2 | no change |
| 2026-06-25 | 63.2 | no change |
| 2026-06-26 | 63.2 | no change |
| 2026-06-27 | 63.2 | no change |
| 2026-06-28 | 63.2 | no change |
| 2026-06-29 | 63.2 | no change |
| 2026-06-30 | 63.2 | no change |
| 2026-07-01 | 63.2 | no change |
| 2026-07-02 | 63.2 | no change |
| 2026-07-04 | 63.2 | no change |
| 2026-07-05 | 63.2 | no change |
| 2026-07-06 | 63.2 | no change |
| 2026-07-07 | 62.7 | down 0.5 |
| 2026-07-08 | 62.3 | down 0.4 |
| 2026-07-09 | 61.9 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Error11 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.)
Validator rule: equal_shape_distance_diff_coordinates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1805 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.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1758 instances
1758 of 1758 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)
- Warning60 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)
- Warning35 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)
- Warning2 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.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' 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: missing_feed_contact_email_and_url · Read the fix guide · 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.)
Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' 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 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' 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 13 observed fixes).
Validator rule: big_gap_in_service · 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 with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD certification readiness Needs attention
This feed is close to NTD-ready. 1 validator error to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Ready
- Service data covers the next 57 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 2338 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. 1 validator error to resolve. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 57 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 57 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 11 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
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 39 / 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 95 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 68 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/abq-ride/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.