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
ECO Transit
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 23% of all tracked agencies and 19% of small 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 4 hours ago; last fetch returned HTTP 403.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1181 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
96 of 96 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
Check the flagged stop times for transposed minutes.
Some scheduled trips move faster between stops than a bus can. Usually a typo'd stop time; riders get arrival times no bus can meet.
⏱ A few minutes per flagged trip.worth about +8 points
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
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. Make this change in whatever tool produces your feed, then re-export.
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. Make this change in whatever tool produces your feed, then re-export.
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.
Check the flagged stop times for transposed minutes. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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 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.
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 9 kinds of issue across 894 instances (0 error, 891 warning, 3 informational).
Service data ended 1181 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- BCX (yellow)
- HY6 (teal)
- LED (green)
- MIN (orange)
- VAL (red)
| Route | Type | Line color |
|---|---|---|
| BCX VAIL/BEAVER CREEK | Bus | yellow |
| HY6 Hwy6 | Bus | teal |
| LED Leadville | Bus | green |
| MIN Minturn | Bus | orange |
| VAL Valley | Bus | red |
This feed has 96 stops.
List every stop
- ECO TRANSIT PARK AND 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
- DONOVAN PARK
- VAIL SKI AND SNOWBOARD ACCADEMY
- SUNNY AVE + JULES DR
- SOUTH FRONTAGE RD and LIONSHEAD
- SOUTH FRONTAGE RD and VAIL RD
- CHAMBERS PARN 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
- 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
- MILLER RANCH RD and 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
- ECO TRANSIT PARK AND 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 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 45.6 | first check |
| 2026-06-20 | 45.6 | no change |
| 2026-06-21 | 45.6 | no change |
| 2026-06-22 | 45.6 | no change |
| 2026-06-23 | 45.6 | no change |
| 2026-06-24 | 45.6 | no change |
| 2026-06-25 | 45.6 | no change |
| 2026-06-26 | 45.6 | no change |
| 2026-06-27 | 45.6 | no change |
| 2026-06-28 | 45.6 | no change |
| 2026-06-29 | 45.6 | no change |
| 2026-06-30 | 45.6 | no change |
| 2026-07-01 | 45.6 | no change |
| 2026-07-02 | 45.6 | no change |
| 2026-07-04 | 45.6 | no change |
| 2026-07-05 | 45.6 | no change |
| 2026-07-06 | 45.6 | no change |
| 2026-07-07 | 45.6 | no change |
| 2026-07-08 | 45.6 | no change |
| 2026-07-09 | 45.6 | 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 1181 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)
- Warning788 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning97 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)
- Warning96 instances
96 of 96 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)
- Warning2 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.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
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)
- 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
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' 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: missing_feed_contact_email_and_url · 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)
- Info63 instances
About 63 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 (e.g. 'Main St & 2nd Ave'). (Often a bulk fix in your scheduling software.)
Validator rule: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2 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)
- Info1 instance
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)
- 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 with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · 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.
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.
76 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.
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 63 changes
For example: ECO TRANSIT PARK AND RIDE -> Eco Transit Park And Ride
Recased shouting route names 1 change
For example: VAIL/BEAVER CREEK -> Vail/beaver Creek
NTD certification readiness Not ready
Resolve this before you certify on the D-10. Service data expired 1181 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 1181 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.
- shapes.txt covers your trips Ready
- All 168 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. Service data expired 1181 days ago. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 1181 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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.
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 63 / 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 58 / 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/eco-transit/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.