Feed status · checked 2026-11-21
ECO Transit
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
up 22.4 since 2026-11-20 · F → C
Cataloged in Colorado.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://gtfs.coretransit.org/
Watch this feed for free: we email you before it expires or when its grade drops.
Heads-up: The score rose 22 points in one step, from 49 on 2026-11-20 to 71 on 2026-11-21. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-11-21). This can be a brief vendor export glitch; watch the next update before acting.
Top things to fix
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
97 of 97 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.
Fixing this covers all 97 stops in the feed.
⏱ 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
552 of 552 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 552 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Often a bulk fix in your scheduling software.worth about +8 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Colorado as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested 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
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.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
Make the change. Make this change in whatever tool produces your feed, then re-export.
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown
Make the change. Make this change in whatever tool produces your feed, then re-export.
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.
Fix 03 · Read the fix guide for mixed_case_recommended_field
Make the change. Make this change in whatever tool produces your feed, then re-export.
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 140 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
- 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 your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
ECO Transit’s published feed lists 5 bus routes, 552 scheduled trips and 97 stops. Its service dates run from 2026-11-22 through 2027-04-10. The published file last changed on 2026-11-21.
Score by category
The MobilityData validator flagged 7 kinds of issue across 168 instances (0 error, 166 warning, 2 informational).
Service data covers the next 140 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 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 (LED, VAL).
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.
75 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("HARRISON ST and 3RD ST", "HARRISON ST and 8TH ST", "POPLAR ST 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.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 97 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.
- BC X (yellow)
- HY6 (teal)
- LED (green)
- MIN (orange)
- VAL (red)
| Route | Type | Line color |
|---|---|---|
| BC X BEAVER CREEK | Bus | yellow |
| HY6 Hwy 6 | Bus | teal |
| LED SFCHMX to Leadville | Bus | green |
| MIN MINTURN | Bus | orange |
| VAL VALLEY | Bus | red |
List every stop
- LEADVILLE PARK N RIDE
- LINDBERGH DR + COOLEY MESA RD
- COOLEY MESA RD + NAVAJO RD
- HIGHWAY 24 + MEADOW MOUNTAIN BUSINESS PRK
- HIGHWAY 24 + MEADOW MOUNTAIN BUSINESS PRK
- HIGHWAY 24 + 996 MAIN
- HIGHWAY 6 + TRAIL GULCH RD
- HWY6 @ EAGLE RD w
- HIGHWAY 6 + RIVERBEND DR
- HIGHWAY 24 + 472 MAIN
- HWY24 @ TOLEDO ST w
- HIGHWAY 6 + DOWD TRAIL
- POPULAR ST and MOUNTAIN VIEW
- FOREST SERVICE PARK AND RIDE
- SOUTH FRONTAGE RD and CHAMONIX RD
- REDCLIFF - INTOWN
- VAIL SKI AND SNOWBOARD ACCADEMY
- SUNNY AVE + JULES DR
- SOUTH FRONTAGE RD and LIONSHEAD
- SOUTH FRONTAGE RD and VAIL RD
- CHAMBERS PARK AND RIDE
- AVON STATION
- HARRISON ST and 3RD ST
- VAIL TRANSPORTATION CENTER
- DOTSERO TRAILER PARK
- FAWCETT RD + YODER AVE
- SOUTH FRONTAGE RD and CASCADE VILLAGE
- LAKE CREEK BLVD @ HILLCREST
- HIGHWAY 24 + NELSON AVE E
- LINDBERGH DR @ EARHART DR e
- LINDBERGH DR @ EARHART DR w
- HWY6 + RIVERDANCE EAST
- HWY6 + YORKVIEW EAST
- HWY6 + RIVERVIEW EAST
- HWY6 + RIVERDANCE WEST
- HWY6 + YORKVIEW WEST
- HWY6 + RIVERVIEW WEST
- BEAVER CREEK ELK LOT
- WEST VAIL MALL
- WEST VAIL MALL
- BEAVER CREEK VILLAGE
- HIGHWAY 24 + HARRISON AVE
- HIGHWAY 24 + 996 MAIN
- HARRISON ST and 8TH ST
- HARRISON ST and 3RD ST
- LAKE CREEK VILLAGE
- HIGHWAY 6 and EAGLE RIVER VILLAGE
- HIGHWAY 6 and EDWARDS SPUR RD
- HIGHWAY 6 and RIVERWALK
- HIGHWAY 6 and BULL RUN RD
- HIGHWAY 6 and RESERVE RD
- HARRISON ST and 8TH ST
- HWY6 and MILLER RANCH RD e
- HWY6 and ARROWHEAD e
- HIGHWAY 6 and SAWATCH DR
- BEAVER CREEK BEAR LOT e
- HWY6 @ RIVERS EDGE e
- HIGHWAY 6 + EAGLE BEND
- HIGHWAY 6 + STONE BRIDGE DR
- HIGHWAY 6 + EAGLE VAIL RD
- HIGHWAY 6 + STONE CREEK DR
- POPLAR ST and 11TH ST
- HWY6 @ EAGLE RD e
- HIGHWAY 6 + EAGLE VAIL BUSINESS CNTR
- HWY6 @ DOWD PARK BUISNESS CEN e
- FREEDOM PARK
- MOUNTAIN VIEW DR and EAGLES NEST
- HIGHWAY 6 + DOWD PARK BUSINESS CNTR
- HIGHWAY 6 + EAGLE VAIL BUSINESS CENTER
- HIGHWAY 6 + STONE CREEK DR
- HIGHWAY 6 + EAGLE VAIL RD
- HIGHWAY 6 + STONEBRIDGE DR
- HIGHWAY 6 + EAGLEBEND
- HIGHWAY 6 + RIVERSEDGE
- HIGHWAY 6 + W BEAVER CREEK BLVD
- HWY6 @ ARROWHEAD w
- HIGHWAY 6 + MILLER RANCH RD
- HIGHWAY 6 + RESERVE RD
- HIGHWAY 6 + BULL RUN RD
- HWY6 @ RIVERWALK w
- HIGHWAY 6 + EDWARDS SPUR RD
- HIGHWAY 6 + EAGLE RIVER VILLAGE
- HIGHWAY 24 and MOUNTAIN VIEW VILLAGE
- HIGHWAY 6 + TRAIL GULCH RD
- EAGLE VALLEY HIGH SCHOOL
- HIGHWAY 6 + SYLVAN LAKE RD
- 5TH ST + WALL ST
- GYPSUM Park-n-Ride
- SUNNY AVE + JULES DR
- HIGHWAY 24 and WATER STREET
- EAGLE COUNTY AIRPORT
- COOLEY MESA RD + NAVAJO RD
- LINDBERGH DR + COOLEY MESA RD
- LINDBERGH DR + MCGREGOR DR
- 5TH ST + WALL ST
- HWY6 @ SYLVAN LAKE RD w
- LINDBERGH DR + MCGREGOR DR
Over time
Overall score across the last 13 checks — up 22.4 since 2026-11-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-11-09 | 53.3 | first check |
| 2026-11-10 | 52.9 | down 0.4 |
| 2026-11-11 | 52.5 | down 0.4 |
| 2026-11-12 | 52.1 | down 0.4 |
| 2026-11-13 | 51.7 | down 0.4 |
| 2026-11-14 | 51.2 | down 0.5 |
| 2026-11-15 | 50.8 | down 0.4 |
| 2026-11-16 | 50.4 | down 0.4 |
| 2026-11-17 | 50.0 | down 0.4 |
| 2026-11-18 | 49.6 | down 0.4 |
| 2026-11-19 | 49.2 | down 0.4 |
| 2026-11-20 | 48.7 | down 0.5 |
| 2026-11-21 | 71.1 | up 22.4 |
What changed since your last check
- Correctness down 5.0
- Freshness up 98.3
- Rider experience down 0.1
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-21 | cf7fdab38c88 | 2027-04-10 | Current rubric: see the trend above |
| 2026-11-09 to 2026-11-20 (12 checks) | c5b92cc836b7 | 2026-11-21 | Current rubric: see the trend above |
| 2026-10-02 to 2026-11-06 (35 checks) | 90180cbec7f7 | 2023-04-15 | F, 45.6 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-10-01 (65 checks) | 90180cbec7f7 | 2023-04-15 | F, 45.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-13 to 2026-07-24 (10 checks) | 90180cbec7f7 | 2023-04-15 | F, 45.6 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-12 (24 checks) | 90180cbec7f7 | 2023-04-15 | F, 45.6 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed over time
On 2026-11-09 this feed started at grade F. On 2026-11-21 the grade moved from F to C. As of 2026-11-21 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-11-21 Grade went F to C, freshness rose 98 points.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning552 instances
552 of 552 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning160 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning97 instances
97 of 97 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning3 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · 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 for trip_coverage_not_active_for_next7_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide for unused_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info64 instances
About 64 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future feed (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_feed · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
How we measured this
Checked for changes 18 hours ago; last changed 18 hours ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 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.
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.5, validator 8.0.1.
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 140 days.
- 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 552 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
One requirement remains for this feed to earn the conformance mark. 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 Met
- Service data covers the next 140 days.
- 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 139 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
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 75 / 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 100 / 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 43 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the Colorado portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Colorado
Other scorecards in Colorado, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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/eco-transit-2061/2026-11-21.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-11-21. 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.