Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Via Mobility
Based on the feed this agency publishes
up 2.8 since 2026-07-08 · D → D
Ahead of 56% of all tracked agencies and 53% of mid-size agencies. Operates 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.1, validator 8.0.1.
Checked for changes 11 minutes ago; last changed 11 minutes ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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 with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 29 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +51 points
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Review the rule documentation for 'empty_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Empty file (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 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
169 of 169 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
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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.
Re-export with a validity window that reaches at least 60 days out. · 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Review the rule documentation for 'empty_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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.
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 37 instances (1 error, 26 warning, 10 informational).
Service data runs out in 29 day(s). Publish an updated feed soon or riders will lose trip planning.
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
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (ELDO, GHC, HOPCW, LF).
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.
68 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("11th St & Pearl St", "14th Canyon & Arapahoe", "20th St & Baseline Rd", 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.
Sampled 9 times outside service hours: 3 of 3 feeds healthy.
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.
- HOPCW (orange)
- HOPCCW (black)
- LF (teal)
- GHC (orange)
- MR (brown)
- ELDO (green)
- P2P (gray)
- SH (white)
- NL (gray)
| Route | Type | Line color |
|---|---|---|
| HOPCW HOP Clockwise | Bus | orange |
| HOPCCW HOP Counterclockwise | Bus | black |
| LF Lyons Flyer | Bus | teal |
| GHC Gold Hill Climb | Bus | orange |
| MR Mountain Rides | Bus | brown |
| ELDO Eldo Shuttle | Bus | green |
| P2P Park to Park | Bus | gray |
| SH Shelter | Bus | white |
| NL Nederland | Bus | gray |
This feed has 169 stops.
List every stop
- Walnut St & 11th St
- 9th Street and Boulder Creek
- 9th Street and University Avenue NB
- 9th Street and University Avenue SB
- 9th Street and Walnut Street NB
- 9th Street and Walnut Street SB
- Broadway and 20th Avenue
- Broadway & Canyon SB
- UMC
- Broadway and College Avenue
- Broadway & Regent Dr NB
- Broadway and University Avenue
- Pearl Street and 10th Street WB
- Spruce St & Broadway
- Pearl Street and 18th Street EB
- College Avenue and 9th Street EB
- Pearl Street West of 26th Street WB
- Pearl Street and 23rd Street EB
- Euclid Avenue and 18th Street
- Pearl Street and 20th Street EB
- College Avenue and 11th Street EB
- Folsom Street and Taft Drive SB
- Pearl Street East of 26th Street WB
- Folsom Street and Colorado Avenue
- Pearl Street and Folsom Street EB
- 14th Street and College Avenue
- Folsom Street and Arapahoe Avenue NB
- 2100 Block 30th Street
- Folsom Street and Arapahoe Avenue SB
- Colorado Avenue and Folsom Street EB
- College Avenue and 9th Street NB
- Canyon Boulevard and 28th Street WB
- Folsom Street and Canyon Boulevard
- Pearl Street and 15th Street EB
- College Avenue and 13th Street WB
- College Avenue and 11th Street WB
- Pearl Street and 29th Street EB
- 29th Street and Canyon Boulevard
- Folsom Street and Goss Street
- Canyon Boulevard and 28th Street EB
- Buffalo Folsom Field Plaza
- Euclid Avenue and 14th Street
- Pearl Street and 23rd Street WB
- Pearl Street and 28th Street EB
- Pearl Street and 29th Street WB
- 9th Street and Arapahoe Road NB
- 30th Street and Walnut Street
- Pearl Street and 18th Street WB
- Pearl Street and 10th Street EB
- Pearl Street and 15th Street WB
- Folsom Street and Taft Drive NB
- Pearl Street and 20th Street
- Pearl Street and 30th Street WB
- 18th Street and Euclid Avenue (Telcom)
- 29th Street and Walnut Street
- Walnut Street and 30th Street EB
- Colorado Avenue and 18th Street
- Walnut Street and 30th Street WB
- Colorado Avenue and Folsom Street WB
- Walnut St & 14th St (Boulder Station)
- 20th St & Baseline Rd
- Gold Hill Inn
- Gold Hill School
- Salina School House
- Logan Mill
- Poorman
- 200 Pearl Street
- 14th Canyon & Arapahoe
- 200 Pearl Street
- 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 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
- 4200 Ute Hwy (Circle K) WB
- US 36 & 2nd NS
- Food Box
- Old Depot
- Community Center
- RTD
- B&F Grocery
- Melt Coffee
- Guercio Field/Grahn Housing
- New Vista High School
- Pearl St & 2nd Street
- Regent Parking Lot
- Table Mesa & Broadway EB
- Superior PNR WB
- Marshal WB
- Eldorado Park Entrance EB
- Eldorado Park Entrance WB
- Eldorado Park Visitor Center
- Marshal EB
- Superior PNR EB
- 16th and Broadway
- Trolly Stop West
- Ranger Cottage
- Mud Lake
- 9th Street and Arapahoe Road SB
- Shelter
- 11th St & Pearl St
- Broadway & Pleasant St SB
- Broadway and Baseline (NB)
- Broadway & 27th Way NB
- Broadway & Rayleigh NB
- Broadway and Dartmouth (NB)
- Table Mesa PNR WB
- Eldorado Pool WB
- Dowdy Draw WB
- Table Mesa PNR EB
- Broadway & Dartmouth SB
- Broadway & Rayleigh SB
- Broadway & 27th Way SB
- Broadway and Baseline (SB)
- Table Mesa & Broadway WB
- US 36 & Lake Ridge Trail FS NB
- Broadway & Spruce NB
- US 36 & US 66 FS NB
- Canyon Blvd West
- Canyon Blvd East
- Point View Drive NB
- Point View Drive SB
- Magnolia
- Boulder Falls
- Nederland High School
- Pearl Street and 30th Street EB
- Junction Place & Pearl Street SB
- 32nd Street & Walnut Street SB
- 32nd Street & Walnut Street NB
- Junction Place & Pearl Street NB
- Pearl Street & Junction Place
- Jeffco Government Center
- Matthews/Winter Park
- Martin G Lockley Discovery Center
- Red Rocks Trading Post
- Morrison Natural History Museum
- Broadway & Regent Dr SB
- Baseline & Broadway
- Eldorado Pool EB
- Dowdy Draw EB
- Erie High School
- Powers & Ambrose
Over time
Overall score across the last 21 checks — up 2.8 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 67.4 | first check |
| 2026-06-20 | 70.9 | up 3.5 |
| 2026-06-21 | 70.7 | down 0.2 |
| 2026-06-22 | 69.0 | down 1.7 |
| 2026-06-23 | 69.1 | up 0.1 |
| 2026-06-24 | 68.6 | down 0.5 |
| 2026-06-25 | 70.7 | up 2.1 |
| 2026-06-26 | 70.7 | no change |
| 2026-06-27 | 70.7 | no change |
| 2026-06-28 | 70.9 | up 0.2 |
| 2026-06-29 | 69.7 | down 1.2 |
| 2026-06-30 | 69.1 | down 0.6 |
| 2026-07-01 | 69.6 | up 0.5 |
| 2026-07-02 | 70.0 | up 0.4 |
| 2026-07-03 | 70.8 | up 0.8 |
| 2026-07-04 | 63.3 | down 7.5 |
| 2026-07-05 | 66.2 | up 2.9 |
| 2026-07-06 | 63.2 | down 3.0 |
| 2026-07-07 | 63.1 | down 0.1 |
| 2026-07-08 | 62.2 | down 0.9 |
| 2026-07-09 | 65.0 | up 2.8 |
What changed since your last check
- Correctness down 4.0
- Freshness down 1.7
- Rider experience no change
- Realtime quality up 22.5
What changed in this feed
Overall score rose 2.8 points since 2026-07-08.
The feed file was re-published since 2026-07-08.
New since 2026-07-08 (2 findings)
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Service data runs out in 29 day(s).
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Resolved since 2026-07-08 (1 finding)
- 8 of 13 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-06-19 this feed started at grade D. On 2026-06-20 the grade moved from D to C. On 2026-06-22 the grade moved from C to D. On 2026-06-25 the grade moved from D to C. As of 2026-07-09 it holds grade D.
A plain-language history of this feed, newest first.
- 2026-07-06 Score fell 3 points, realtime fell 15 points.
- 2026-07-04 Grade went C to D, realtime fell 16 points.
- 2026-07-02 Grade went D to C.
- 2026-06-29 Grade went C to D, realtime fell 6 points.
- 2026-06-25 Grade went D to C, realtime rose 11 points.
- 2026-06-22 Grade went C to D, realtime fell 8 points.
- 2026-06-20 Grade went D to C, realtime rose 18 points.
Everything we checked
- Error1 instance
Empty file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'empty_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: empty_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning397 instances
397 of 397 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning169 instances
169 of 169 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)
- Warning21 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.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 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)
- Warning2 instances
2 of 397 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 24 observed fixes).
Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Route long name contains short name (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Service data runs out in 29 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info7 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)
- Info3 instances
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)
NTD certification readiness Needs attention
This feed is close to NTD-ready. 1 validator error to resolve. Service data runs out in 29 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Needs attention
- Service data runs out in 29 days; renew before you certify.
- 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 397 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. Service data runs out in 29 days; renew to qualify. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data runs out in 29 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.
- 21 of 169 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.
Realtime reliability
The realtime feed responded on 100.0% of 105 checks over the last 16 days, with 3s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 540 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1 validator error, 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.
Your state runs a transit-data program that can help: CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers. Your state publishes no quality rubric of its own, so the closest published bars a program can hold this feed to are the federal and industry ones below; the score maps to those.
- Correctness 69 / 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 48 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 45 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality 100 / 100
- 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/via-mobility-2395/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.