GTFS Scorecard
← All agencies

Feed status · checked 2026-09-13

Bustang

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

45.1 / 100

down 0.4 since 2026-09-12

Catalogued in Colorado.

Expires in 13 daysAccessibility gapsRealtime not yet published

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 30 hours ago; last changed 2 days 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.

Top things to fix

Fix 01

Re-export with a validity window that reaches at least 60 days out.Likely your export tool

Service data runs out in 13 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

⏱ One export setting.worth about +67 points in its category

Fix 02

Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Foreign key violation (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +24 points in its category

Fix 03

Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Missing required field (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +12 points in its category

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
Service data runs out in 13 day(s).
Next action
Re-export with a validity window that reaches at least 60 days out.
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.

  1. Re-export with a validity window that reaches at least 60 days out. · Read the fix guide for scorecard_feed_expiring_soon

    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. Self-check a feed before you publish.

  2. Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    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. Self-check a feed before you publish.

  3. Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    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. Self-check a feed before you publish.

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 13 days.
Published accessibility data
Accessibility information is stated for 100% 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 v2.
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.

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

Correctness35.2 / 100

The MobilityData validator flagged 9 kinds of issue across 262 instances (221 error, 27 warning, 14 informational).

Freshness21.7 / 100

Service data runs out in 13 day(s). Publish an updated feed soon or riders will lose trip planning.

Rider experience77.5 / 100

100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility62.5 / 100

100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Rams).

    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.

  • 16 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Wewatta St & 17th St", "West Glenwood Park & Ride", "US 36 & Broomfield Station Gate R", 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.

FaresFares v2

Fares are applied to trips.

Realtime qualityNot yet measured

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 58 stops.

Skip to route and stop data

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.

  • Estes (brown)
  • North (green)
  • Pegasus (teal)
  • Rams (green)
  • South (orange)
  • West (teal)
Routes in Bustang's feed
RouteTypeLine color
Estes Bustang to EstesBusbrown
North Bustang North LineBusgreen
Pegasus Bustang PegasusBusteal
Rams Bustang CSU RamsRouteBusgreen
Snow Bustang SnowstangBusteal (no shape in feed)
South Bustang South LineBusorange
West Bustang West LineBusteal
List every stop
  • Broadway & W 14th Ave
  • Lincoln St & 7th Ave
  • 18th St & Stout St
  • 19th St & Stout St
  • Lincoln St & Colfax Ave
  • Broadway & Speer Blvd
  • US 36 & McCaslin Station Gate D
  • US 36 & McCaslin Station Gate A
  • Lyons PnR
  • Lyons PnR
  • US 36 & Sheridan Station Gate D
  • Boulder Junction at Depot Square Station Gate S4
  • Boulder Junction at Depot Square Station Gate S3
  • Wagon Road PnR Gate E
  • Colorado Station Gate E
  • Arapahoe at Village Center Station Gate D
  • Federal Center Station Gate L
  • Union Station Gate B19
  • Union Station Gate B4
  • Union Station
  • Union Station
  • Wewatta St & 17th St
  • US 36 & Broomfield Station Gate P
  • US 36 & Broomfield Station Gate R
  • US 36 & Sheridan Station Gate C
  • Breckenridge Transit Center
  • Colorado Springs Downtown Station
  • Colorado State University
  • Eagle Chambers PnR
  • Fort Collins Downtown Transit Center
  • Frisco Transit Center
  • Grand Junction Regional Airport
  • Harmony Transfer Center
  • Idaho Springs
  • Loveland Ski Area
  • Monument P & R
  • Parachute
  • Rifle
  • Vail Transportation Center
  • West Glenwood Park & Ride
  • Woodmen PnR Northbound
  • Woodmen PnR Southbound
  • Sky Ridge Station
  • Grand Junction Downtown Transfer Facility
  • Avon Station
  • A Basin
  • Copper Mountain
  • Wooly Mammoth PnR
  • Estes Park Visitor Center
  • Rmnp Park & Ride
  • Centerra Loveland Mobility Hub
  • Centerra Loveland Mobility Hub
  • Berthoud Mobility Hub
  • Berthoud Mobility Hub
  • Firestone-Longmont Mobility Hub
  • Firestone-Longmont Mobility Hub
  • Broomfield-Thornton Mobility Hub (Northbound)
  • Broomfield-Thornton Mobility Hub (Southbound)

Over time

Overall score across the last 6 checks — down 0.4 since 2026-09-12.

2026-08-06: 69.62026-08-07: 69.22026-08-10: 68.02026-09-01: 55.32026-09-12: 45.52026-09-13: 45.1
Show the numbers
CheckScoreChange
2026-08-0669.6 first check
2026-08-0769.2 down 0.4
2026-08-1068.0 down 1.2
2026-09-0155.3 down 12.7
2026-09-1245.5 down 9.8
2026-09-1345.1 down 0.4

What changed since your last check

  • Correctness no change
  • Freshness down 1.6
  • Rider experience no change

What changed over time

On 2026-08-06 this feed started at grade D. On 2026-09-01 the grade moved from D to F. As of 2026-09-13 it holds grade F.

A plain-language history of this feed, newest first.

  • 2026-09-12 Score fell 10 points, freshness fell 18 points.
  • 2026-09-01 Grade went D to F, freshness fell 37 points.

Everything we checked

12 findings, ordered by severity.

Show every finding
  • Error219 instances

    Foreign key violation (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: foreign_key_violation · See MobilityData GTFS Validator rules

  • Error2 instances

    Missing required field (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'missing_required_field' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: missing_required_field · See MobilityData GTFS Validator rules

  • Warning258 instances

    258 of 258 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

  • Warning12 instances

    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

  • Warning7 instances

    Same route and agency url (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'same_route_and_agency_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: same_route_and_agency_url · See MobilityData GTFS Validator rules

  • Warning5 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 for stop_without_stop_time · See MobilityData GTFS Validator rules

  • Warning1 instance

    This feed's service calendar runs out within the next 30 days.

    If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.

    Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)

    Finding code: feed_expiration_date30_days · Read the fix guide for feed_expiration_date30_days · See MobilityData GTFS Validator rules

  • 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

  • Warning1 instance

    Some route colors don't contrast with their text color.

    Route badges get hard to read, most of all for riders with low vision.

    Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)

    Finding code: route_color_contrast · Read the fix guide for route_color_contrast · See MobilityData GTFS Validator rules

  • Warning1 instance

    Service data runs out in 13 day(s).

    When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

    Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)

    Finding code: scorecard_feed_expiring_soon · Read the fix guide for scorecard_feed_expiring_soon · See GTFS Best Practices

  • Info14 instances

    Platform without parent station (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: platform_without_parent_station · See MobilityData GTFS Validator rules

  • 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

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

  • The feed lists fare products but has no rider_categories.txt to say who each fare is for.

    Consider: Add rider_categories.txt for the fares you already offer. Then point your fare products at those categories.

NTD GTFS readiness Needs attention

This feed is close to NTD-ready. 2 validator errors to resolve. Service data runs out in 13 days; renew before you certify.

Published Ready
Published at a public URL.
Valid Needs attention
2 validator errors to resolve.
Current Needs attention
Service data runs out in 13 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 258 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: 2 validator errors to resolve. Service data runs out in 13 days; renew to qualify. States wheelchair access on 100% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
2 validator errors to resolve.
Current Not yet
Service data runs out in 13 days; renew to qualify.
Accessible Not yet
States wheelchair access on 100% 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.

  • 5 of 58 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.

At risk for the Google and Apple Maps four-week coverage bar. This feed has 11 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar. The feed also carries 221 validator errors, 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 35 / 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 22 / 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 78 / 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.

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.

Bustang GTFS data quality grade: F

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/regional-transportation-district-rtd-2280/2026-09-13.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-09-13. 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.