Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Via Mobility
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 34% of all tracked agencies and 31% 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 8 days ago.
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 495 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
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).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.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
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.
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 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send 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 495 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.
Fares are applied to trips.
This agency publishes realtime, but the feed needs an access key we don't have yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 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 |
This feed has 210 stops.
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 10 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 50.0 | first check |
| 2026-07-01 | 50.0 | no change |
| 2026-07-02 | 50.0 | no change |
| 2026-07-03 | 50.0 | no change |
| 2026-07-04 | 50.0 | no change |
| 2026-07-05 | 50.0 | no change |
| 2026-07-06 | 50.0 | no change |
| 2026-07-07 | 50.0 | no change |
| 2026-07-08 | 50.0 | no change |
| 2026-07-09 | 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-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Error1 instance
Service data ended 495 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.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: 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 (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)
- 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.)
Validator rule: 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.)
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)
- Warning14 instances
14 of 419 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)
- Warning8 instances
Some service calendars in the feed have already expired.
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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: 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.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: 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.)
Validator rule: 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.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 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)
- Info8 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: 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).
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.
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Recased shouting stop names 1 change
For example: NVHS -> Nvhs
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 495 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 495 days ago, so FTA would find the link out of date.
- 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.
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. Service data expired 495 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 495 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
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 72 / 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 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 59 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/via-mobility-180/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.