Feed status · checked 2026-08-01
Via Mobility
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Colorado.
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 16 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 518 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.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
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
210 of 210 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
419 of 419 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
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 518 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
- 210 of 210 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
- 419 of 419 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
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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_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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 518 days ago.
- 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
- 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 Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names 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 8 kinds of issue across 137 instances (0 error, 87 warning, 50 informational).
Service data ended 518 day(s) ago. Trip planners have likely already dropped this feed.
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
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (HOP Clockwise, Gold Hill Climb).
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.
56 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Broadway & Pleasant (SB)", "Pearl Street and 23rd Street", "University Ave and 11th St", 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.
This feed has 210 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.
- HOP Counter Clockwise (black)
- Gold Hill Climb (orange)
- Eldorado Park Shuttle (red)
- HOP Clockwise (orange)
- Park to Park Shuttle (red)
- Lyons Flyer (teal)
- Mountain Rides (brown)
| Route | Type | Line color |
|---|---|---|
| HOP Counter Clockwise | Bus | black |
| Gold Hill Climb | Bus | orange |
| Eldorado Park Shuttle | Bus | red |
| HOP Clockwise | Bus | orange |
| Park to Park Shuttle | Bus | red |
| Lyons Flyer | Bus | teal |
| Mountain Rides | Bus | brown |
List every stop
- 11th Street and Tom's Way
- Walnut Street and 11th Street
- 30th Street and Colorado Avenue
- 30th Street and Colorado
- 9th Street and Arapahoe Avenue
- 9th Street and Boulder Creek
- 9th Street and University Avenue
- 9th Street and University Avenue
- 9th Street and Walnut Street
- 9th Street and Walnut Street
- Baseline Road and Broadway
- Bear Creek
- Broadway and 20th Avenue
- Broadway and 27th Way NB
- Broadway and 27th Way SB
- Broadway and Baseline Road
- Broadway and Boulder Creek Path
- Broadway and Canyon Boulevard (SB)
- Broadway and College - The Hill
- Broadway and College Avenue
- Broadway and Euclid Avenue
- Broadway and Rayleigh Road
- Broadway and Rayleigh Road
- Broadway and Regent Drive
- Broadway & Pleasant (SB)
- Regent Drive (Center for Community)
- Discovery Learning Center
- Pearl Street and 10th Street
- Pearl Street Mall and 15th Street
- S Broadway and Dartmouth Avenue SB
- Spruce Street and Broadway
- Table Mesa Drive and 39th Street
- Table Mesa and Tantra Drive
- 18th Street (UMC)
- Williams Village
- College Avenue and 9th Street
- 9th Street and Aurora Avenue
- 10th Street and Baseline Road
- 17th Street and Baseline Road
- NVHS
- 22nd Street and Baseline Road
- 17th Street and Baseline Road
- 10th Street and Baseline Road
- 9th Street and Aurora Avenue
- 13th Street and Walnut Street
- Pearl Street and 18th Street
- College Avenue and 9th Street
- Pearl Street West of 26th Street
- Pearl Street and 24th Place
- Euclid Avenue and 18th Street
- Pearl Street and 20th Steet
- College Avenue and 11th Street
- Folsom Street and Taft Drive
- Pearl Street East of 26th Street
- Folsom Street and Colorado Avenue
- Pearl Street and Folsom Street
- 14th Street and College Avenue
- Folsom Street and Arapahoe Avenue
- 2100 Block 30th Street
- Folsom Street and Arapahoe Avenue
- Colorado Avenue and Folsom Street
- College Avenue and 9th Street
- Canyon Boulevard and 28th Street
- Canyon Boulevard and Folsom Street
- Folsom Street and Canyon Boulevard
- Pearl Street and 15th Street
- College Avenue and 13th Street
- College Avenue and 11th Street
- Pearl Street and 29th Street
- 16th Street and Broadway
- 29th Street and Canyon Boulevard
- Folsom Street and Goss Street
- Canyon Boulevard and 28th Street
- Buffalo Folsom Field Plaza
- Euclid Avenue and 14th Street
- Pearl Street and 23rd Street
- Pearl Street and 28th Street
- Pearl Street and 29th Street
- 9th Street and Arapahoe Road
- 30th Street and Walnut Street
- Pearl Street and 18th Street
- Pearl Street and 10th Street
- Pearl Street and 15th Street
- Folsom Street and Taft Drive
- Pearl Street and 20th Street
- Pearl Street and 30th Street
- 18th Street and Euclid Avenue (Telcom)
- 29th Street and Walnut Street
- Walnut Street and 30th Street
- Colorado Avenue and 18th Street
- Walnut Street and 30th Street
- Colorado Avenue and Folsom Street
- Walnut Street and 14th Street (Boulder Station)
- Folsom Street and Pine Street
- 28th Street and Spruce Street
- Folsom Street and Walnut Street
- Folsom Street and Walnut Street
- 20th Street and Baseline Road
- University Ave and 11th St
- Canyon Blvd and 9th St
- Gold Hill Inn
- Gold Hill School
- Salina School House
- Logan Mill
- Poorman
- 200 Pearl Street
- 14th Canyon & Arapahoe
- Switzerland Trail
- 200 Pearl Street
- Nederland Park-n-Ride
- Hessie Trailhead
- Regent parking lot
- Broadway and Table Mesa SB
- SH 170 & SH 93 WB
- ECSP Visitor Center
- ECSP Entrance station EB
- ECSP Entrance station WB
- SH 93 & SH 170 NB
- Broadway and Table Mesa NB
- S Broadway and Dartmouth Avenue NB
- Walnut Street and 16th Street EB
- Walnut Street and 15th Street WB
- Walnut Street and 18th Street WB
- Walnut Street and 20th Street WB
- Walnut Street and 18th Street EB
- Walnut Street and 20th Street EB
- Theater-29th St Mall
- 18th St and Broadway
- Nederland High School
- Park & Ride - Superior
- Marshall Lot WB
- Hwy 93 & El Dorado
- 11th Street and Pearl Street
- 11th Street and Pearl Street
- Walnut Street & 9th Street
- Canyon Boulevard & 11th Street
- US 36 & McCaslin Park-n-Ride
- Broadway and Baseline Rd SB
- Doudy Draw Trailhead
- New Vista School WB
- Trolly WB
- Trolly EB
- US 36 & Old Main WB
- 4th & Main NS
- High & 5th Lyons
- 4th & Railroad
- US 36 and Broadway EB
- RTD PnR Hwy 36 2nd Ave EB FS
- US 36 & McConnell Dr. NS EB
- 4206 Ute Hwy EB
- US 36 & US 66 FS SB
- US 36 & Lake Ridge Trail FS SB
- US 36 & Lefthand Canyon FS SB
- US 36 & Longhorn Dr. NS SB
- Broadway & Yarmouth NS SB
- Broadway & Quince ave SB
- Broadway & Iris SB
- Broadway & Alpine SB
- Broadway & Spruce SB
- Broadway & Walnut SB
- Broadway & Arapahoe SB
- Broadway Euclid EB
- Broadway & 20th SB
- Broadway & Euclid Ave (NB)
- Broadway & Pleasant St NB
- Broadway & University NB
- Broadway & Arapahoe NB
- Broadway & Canyon NB
- Broadway & Walnut NB
- Broadway & Alpine NB
- Broadway & Iris NB
- Broadway & Quince NB
- Broadway & Yarmouth NB
- Hwy 36 & Longhorn NB
- Hwy 36 & Lefthand Canyon NB
- Hwy 36 & Hwy 66 WB
- 4200 Ute Hwy (Circle K) WB
- US 36 & 2nd NS
- Brighton, CO, USA
- Niwot, CO, USA
- Boulder, CO, USA
- Lafayette, CO, USA
- Longmont, CO, USA
- Estes Park, CO, USA
- Lyons, CO, USA
- Watkins, CO, USA
- Aurora, CO, USA
- Westminster, CO, USA
- Frederick, CO, USA
- Boulder County, CO, USA
- Denver, CO, USA
- Nederland, CO, USA
- Superior Park & Ride WB
- Superior Park & Ride EB
- Eldorado Pool WB
- Eldorado Pool EB
- Dowdy Draw EB
- Marshal Lot EB
- Table Mesa RTD Park & Ride EB
- Table Mesa RTD Park & Ride WB
- Table Mesa & 41st St. WB
- Food Box
- Old Depot
- Mud Lake Openspace
- Community Center
- RTD
- B&F Grocery
- Melt Coffee
- Guercio Field/Grahn Housing
- Ranger Cottage
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 50.0 | first check |
| 2026-07-30 | 50.0 | no change |
| 2026-07-31 | 50.0 | no change |
| 2026-08-01 | 50.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
13 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 518 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, 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)
- Warning419 instances
419 of 419 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)
- Warning210 instances
210 of 210 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)
- Warning73 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)
- Warning14 instances
14 of 419 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)
- Warning4 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)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 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)
- Info8 instances
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 518 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 518 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 419 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 518 days ago. 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 expired 518 days ago.
- 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.
- 73 of 210 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.
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 72 / 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 59 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Access needed to measure
- 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/via-mobility/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.