Feed status · checked 2026-08-23
Via Mobility
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-08-22
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 47 minutes ago; last changed 47 minutes ago.
Measured 4 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
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 '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 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
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 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
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.
⏱ A default or per-trip field in your export.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
- Empty file (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'empty_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- 169 of 169 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
- 397 of 397 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.
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.
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. See this feed's finding-clearance 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.
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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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
- One or more realtime feeds were reachable; live-arrival coverage is not known.
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 6 kinds of issue across 38 instances (1 error, 25 warning, 12 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
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 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 169 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.
- 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 |
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 4 checks — unchanged since 2026-08-22.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 66.7 | first check |
| 2026-08-07 | 64.7 | down 2.0 |
| 2026-08-22 | 66.7 | up 2.0 |
| 2026-08-23 | 66.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-08-22.
The feed file was re-published since 2026-08-22.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
10 findings, ordered by severity.
Show every finding
- 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.)
Finding code: 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. 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)
- 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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 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)
- Warning1 instance
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · 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)
- 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)
- Info4 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · 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. 1 validator error to resolve. Service data runs out in 30 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 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 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, 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 does not meet the conformance requirements yet. Here is what the mark needs: 1 validator error to resolve. 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 Not yet
- 1 validator error to resolve.
- 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.
- 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 200 checks over the last 28 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 30 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
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 73 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 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 45 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers 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 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-2395/2026-08-23.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-23. 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.