Feed status · checked 2026-08-01
RoadRUNNER Transit
Based on the feed this agency publishes
Service mode 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 70 minutes ago; last changed 70 minutes 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
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
312 of 312 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 in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
345 of 345 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
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.
345 of 345 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.
⏱ Usually one value per route pattern in your scheduling source.worth about +15 points in its category
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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
- 312 of 312 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 345 of 345 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- 345 of 345 trips lack rider-facing destination or direction text.
- Next action
- 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.
- 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.
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. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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.
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. · Read the fix guide
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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 is in 30 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% 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 Passio a fix request
This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 31 instances (0 error, 28 warning, 3 informational).
Service data covers the next 30 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Route 6, Route 8).
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.
272 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("17th St. & Hadley", "Alameda @ St. Andrew's Church", "Amador & Chaparro", 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.
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 312 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.
- Blue Aggie Shuttle (blue)
- Green Aggie Shuttle (green)
- Route 1 (orange)
- Route 2 (yellow)
- Route 3 (purple)
- Route 4 (black)
- Route 5 (brown)
- Route 6 (teal)
- Route 7 (green)
- Route 8 (gray)
| Route | Type | Line color |
|---|---|---|
| Blue Aggie Shuttle | Bus | blue |
| Green Aggie Shuttle | Bus | green |
| Route 1 | Bus | orange |
| Route 2 | Bus | yellow |
| Route 3 | Bus | purple |
| Route 4 | Bus | black |
| Route 5 | Bus | brown |
| Route 6 | Bus | teal |
| Route 7 | Bus | green |
| Route 8 | Bus | gray |
List every stop
- 17th St. & Hadley
- Alameda @ St. Andrew's Church
- Amador & Gospel Rescue Mission
- Amador & Chaparro
- Amador & Main St.
- Amador & McSwain
- Amador & Mesilla
- Amador & Tornillo
- Avenida De Mesilla & Calle de Mercado
- Avenida De Mesilla @ United Rentals
- Avenida de Mesilla & Calle de El Paso
- Avenida de Mesilla & Roberts
- Avenida de Mesilla @ Applebees
- Avenida de Mesilla @ Barker Rd.
- Avenida de Mesilla @ Domino's
- Avenida de Mesilla @ Gadsden Plaza
- Avenida de Mesilla @ Rio Grande Prep
- Avenida de Mesilla @ Tierra Verde
- Aveniida de Mesilla & Calle de Santiago
- Bataan East & Mesa Grande
- Bataan East @ Big Daddy's Flea Market
- Bataan East & Porter
- Bataan West & Jornada
- Bataan West & Mesa Grande
- Bataan West & Mesa Road
- Bataan West & Porter
- Bataan West & Sonoma Ranch @ North American Moving & Storage
- Boutz & Calle de Ninos
- Boutz @ Borman Autoplex
- Boutz @ Nissan of Las Cruces
- Boutz @ Las Cruces High School
- Boutz across from Borman Honda
- Boutz across from Las Cruces High School
- Calle Jitas @ DACC (M-F)
- Campo & Arizona
- Campo & Lohman OB
- Church St. & Las Cruces
- Church St. @ Post Office
- Copper Loop @ Tresco
- Del Rey & Engler
- Del Rey & Mars (VA Clinic)
- Del Rey & Mesilla Valley Hospital
- Del Rey & Plaza del Rey (Ashley Furn.)
- Del Rey & Settlers Bend
- Del Rey South past Parkhill
- Divot across from Walmart
- Don Roser & Idaho
- Don Roser & Missouri
- El Paseo @ Albertson's
- El Paseo @ O'Reilly Auto
- El Paseo @ Walgreens
- El Paseo@Sonic
- Elks & Chinook
- Elks & Ellendale
- Elks & Heather Circle
- Elks & Lantana
- Elks & Lenox
- Elks & Rio Bravo
- Engler & Elks
- Espina & Milton
- Espina & Missouri
- Espina & Monte Vista
- Espina & Parkview
- Espina & Plain
- Espina @ Boba Cafe
- Espina across from Boba Cafe
- Evelyn & June
- Evelyn & Juniper
- Evelyn & Louise
- Evelyn & Madrid
- Foothills & Horizon View
- Foothills & Hotel Encanto
- Hadley & Motel
- Hoagland & Carlyle IB
- Hoagland & Del Mar
- Hoagland & Embassy
- Hoagland @ Mayfield High School
- Hoagland before Rose
- Idaho & La Fonda
- Idaho & Stull
- La Fonda & Missouri OB
- Lohman & Mountain View Hospital (M-F)
- Lohman & Esperanza
- Lohman & Olive
- Lohman & Roadrunner
- Lohman @ Bright Star Dental
- Lohman @ Dunkin Donuts
- Lohman @ Kelly Liquors (M-F)
- Lohman @ Kelly's Liquor
- Lohman @ McDonalds
- Lohman @ Mesquite
- Lohman across from Mtn View Hospital (M-F)
- Lohman West across from Ross/Marshalls
- Lohman at Chaparro
- Lohman West & Roadrunner (M-F)
- Lohman West @ Dunkin Donuts (M-F)
- Lohman across from Ross/Marshalls
- Madrid & Alameda IB
- Madrid & Apodaca Park
- Madrid & Desert
- Madrid & Sexton
- Madrid & Solano across from Fiesta Foods
- Madrid @ Alta Tierra Apts.
- Madrid @ Fiesta Foods
- Madrid across from Apodaca Park
- Main & Brown
- Main & Conway
- Main @ Pueblo Plaza
- Main St @ Dairy Queen
- Main St. & Fleming
- Main St. & Gallagher
- Main St. & Greening
- Main St. @ Century 21 Motel (Northbound)
- Main St. @ City Hall
- Main St. @ Coronado Plaza
- Main St. @ Madrid (Fiesta Foods)
- Main St. @ O'Reilly Auto
- Main St. @ Sonic
- Main St. across from Taco Bell
- Main St. across from Viva Kia
- Main St. NE @ Coldwell Banker
- Melendres & El Molino
- Melendres & Main St.
- Melendres & May
- Mesilla Valley Mall (connects w/Route 3)
- Mesquite & Madrid
- Missouri & Alamo
- Missouri & Chaparro
- Missouri & Espina
- Missouri & Locust
- Missouri @ Conlee Elementary
- Missouri @ Pizza Hut
- Missouri @ Solano Square
- Missouri across from Conlee Elementary
- Missouri across from Wok-N-World
- Missouri before Durazno
- Motel & Picacho Plaza
- Motel @ Government Complex
- MVITT
- MVITT (OUTBOUND)
- Mesilla Valley Mall
- MVM (OUTBOUND)
- Picacho & 17th St. IB
- Picacho & 5th St
- Picacho & Mesilla
- Picacho & Reymond
- Picacho & Valley
- Picacho @ ABC Paint
- Picacho @ Diersen Charities
- Picacho @ Lions Park
- Picacho @ Peddlers Pavillion
- Rinconada & Sonoma Ranch
- Rinconada @ Walmart
- Rinconada across from Walmart
- Roadrunner & Calais
- Roadrunner & Camino Coyote
- Roadrunner & Coventry
- Roadrunner & Foothills/Caliches
- Roadrunner & Morning Star
- Roadrunner & Northrise OB
- Roadrunner & Rolling Hills
- Roadrunner & Stagecoach
- Roadrunner @ Camino Real Middle School
- Roadrunner @ Desert Hills Elementary
- Roadrunner @ Solstice Senior Living
- Roadrunner @ Veterans Park
- Roadrunner across Copperstone Apts
- Roadrunner across Cuestas Apts.
- Roadrunner across Veterans Park
- Roarunner @ Copperstone Apts
- Roadrunner & Golf Club
- Solano & Bowman
- Solano & California
- Solano & Court
- Solano & Hadley (LC Aquatic Center)
- Solano & Juniper (Family Dollar)
- Solano & Lohman
- Solano & Madrid
- Solano & Missouri (Fiesta Foods)
- Solano & Montanas Charter School
- Solano & Oasis
- Solano & Panlener (Church of Christ)
- Solano & Pinon
- Solano & Spruce (Health Center)
- Solano @ Newman Center
- Solano @ Washington Elementary
- Solano past Colorado
- Sonoma Ranch and Morning Star (M-F)
- Sonoma Ranch & Rock Springs Rd (M-F) IB
- Sonoma Ranch & Sedona Hills (M-F)
- Sonoma Ranch & Sonora Springs (M-F)
- Sonoma Ranch @ Baatan East
- Sonoma Ranch @ Fire Station 8 (M-F)
- Sonoma Ranch @ Fitness One
- Sonoma Ranch @ Walmart (M-F)
- Sonoma Ranch across from Bella Sierra (M-F)
- Sonoma Ranch across from Walmart (M-F)
- Sonoma Ranch past La Camelia (M-F)
- Sonoma Ranch & Rock Springs Rd. (M-F) OB
- Telshor & Buena Vida Court
- Telshor & Commerce (Starbucks)
- Telshor & Fairway
- Telshor & Hillrise
- Telshor & Missouri
- Telshor & Spruce
- Telshor & Summit Court (Social Security Admin.)
- Telshor @ Doral Court
- Telshor @ Good Samaritan Society
- Foothills @ Hotel Encanto
- Telshor @ Memorial Medical Center
- Telshor @ Planet Fitness
- Telshor @ SunView Imaging
- Telshor @ Telshor Apartments
- Telshor @ Telshor Tower Plaza
- Telshor past Claude Dove
- Telshor South @ Mesilla Valley Mall
- Triviz & Bugatti
- Triviz & John St.
- Triviz @ Omni Apartments
- Triviz & Redwood
- Triviz & Wisconsin
- Triviz @ Lowe's Home Improvement
- Triviz past Madrid
- Union & Oak
- Union & Stewart
- Union @ The Verge Apartments
- University @ Zia Middle School
- University & Avenida de Mesilla OB
- University & Avenida de Mesilla IB
- University & Bowman OB
- University & McDowell Rd
- University & El Paseo
- University & Espina/NMSU Music Building
- University & Haggerty
- University & Jordan
- University & Locust/NMSU Garcia Hall
- University @ IHOP
- University @ Pan Am Plaza
- University @ Solano/NMSU Art Department
- University @ Whataburger
- University @ Pan Am Plaza
- Valley & Aspen St.
- Valley & Amador
- Valley & Avenida De Mesilla
- Valley & Brown
- Valley & Brown St.
- Valley & Hadley
- Valley & McClure
- Valley & Parker
- Valley & Rigby
- and 62 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-31 | 55.7 | first check |
| 2026-08-01 | 55.7 | 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.
The feed file was re-published since 2026-07-31.
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
- Warning345 instances
345 of 345 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning345 instances
345 of 345 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)
- Warning312 instances
312 of 312 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning10 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9 instances
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 (opens the validator rules on an external site)
- Warning7 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 (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.)
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
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 (opens GTFS Best Practices on an external site)
- Info3 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 30 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 30 days; renew before you certify.
- 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 345 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 runs out in 30 days; renew to qualify. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data runs out in 30 days; renew to qualify.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 7 of 312 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 517 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
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 78 / 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 50 / 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 30 / 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/roadrunner-transit-2075/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.