GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

STAR Transit

Based on the feed this agency publishes

Service mode Bus

85.4 / 100

unchanged since 2026-07-31

Catalogued in Texas.

Covers 517 daysAccessibility gapsFlexible serviceRealtime 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 16 hours ago; last changed 41 days ago.

Measured 3 of 4 score categories from the agency's own feed.

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 agency's own URL.

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

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

10 of 10 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 02

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

51 of 136 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 +9 points in its category

Fix 03

Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool

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.

⏱ A review pass in your scheduling software.worth about +8 points in its category

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.

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
10 of 10 trips don't say whether the vehicle is wheelchair accessible.
Next action
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide

    Make the change. 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.

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

    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. Remove retired stops from the export, or add them back to the trips that should serve them. · 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.

    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 517 days.
Published accessibility data
Accessibility information is stated for 62.5% 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 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.

Score by category

Correctness84.0 / 100

The MobilityData validator flagged 5 kinds of issue across 170 instances (0 error, 127 warning, 43 informational).

Freshness100.0 / 100

Service data covers the next 517 days.

Rider experience75.6 / 100

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

Accessibility39.1 / 100

62% of stops state accessibility (61% 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 (101).

    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.

  • 42 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Seagoville Rd @ Peachtree Rd", "Seagoville Rd @ Peachtree Rd", "I 20 Frontage Rd.", and more).

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.

FaresLegacy fares

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 136 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.

  • 101 (green)
Routes in STAR Transit's feed
RouteTypeLine color
101 Balch Springs Midtown ExpressBusgreen
List every stop
  • Peachtree Senior Living Apartments
  • Seagoville Rd @ Peachtree Rd
  • Seagoville Rd @ Peachtree Rd
  • Balch Springs City Hall
  • I 20 Frontage Rd.
  • Twin Oaks Dr. & Seagoville Rd.
  • Spring Oaks Shopping Ctr
  • Seagoville Rd. @ Shepherd Ln.
  • Seagoville Rd. & Ambassador Way
  • Peachtree Rd. & Long St.
  • Peachtree Park Shopping Center
  • Peachtree Rd. & Erich Dr.
  • Bells Better Burgers
  • Beverage Corner
  • Lake June Rd. & Balch Springs Dr.
  • 5 Points Grocery
  • S. Beltline Rd. & Spring Oak Dr.
  • S. Beltline Rd. & Lasater Rd.
  • Pioneer Rd @ Elam Rd
  • Elam Rd @ Loyd Dr
  • Terrell Depot
  • Pleasant Hill Baptist Church
  • Dellis St. @ High St.
  • Baylor Health Center
  • Terrell Senior Citizen Center
  • Riter Hulsey Public Library
  • Town West Plaza
  • Wal-Mart (Terrell)
  • Southwestern Christian College
  • Dollar General (Terrell)
  • Terrell Post Office
  • S. Rockwall Ave. & Hamilton Dr.
  • Terrell Senior Terraces 1
  • Hwy 34 @ Mira Pl.
  • Soulman's Bar-B-Que
  • Terrell Crossing
  • Metro Dr. & Apache Tr.
  • TigerMart
  • Crossroads of Terrell
  • Tanger Outlet Mall
  • Brownstone Apartments
  • Trinity Valley Community College - Terrell Campus
  • Autozone/Maines
  • Airport Rd. and Skyline Dr.
  • Old Castle BuildingEnvelope
  • Lakes Regional MHMR
  • FedEx Home Delivery
  • Hutchins Senior Center
  • York Dr. @ Methodist Charlton Medical Ctr.
  • Wal-Mart (Cedar Hill)
  • Wal-Mart (DeSoto)
  • Wal-Mart (Lancaster)
  • DART UNT Dallas Station
  • Dollar General (Lancaster)
  • Cracker Barrel (DeSoto)
  • The Crossing Shopping Center
  • Crescent Medical Center
  • Fiesta Mart (Lancaster)
  • Cedar Valley College
  • Amazon Fulfillment Center
  • Hutchins Gateway Apartments - North
  • Riverbend Apts
  • The Corner Apts.
  • Windsong Place Apts
  • Pecan Crossing Apts
  • Townsend Square Shopping Ctr.
  • DeSoto Town Hall/Civic Ctr.
  • Creekwood Apts.
  • W. Wintergreen Rd. @ Franklin Park
  • Scotland Dr. @ Bolton Boone Dr.
  • Kohl's eFulfillment Center
  • Wal-Mart Distribution (DeSoto)
  • Solar Turbines Inc.
  • Genesis Center
  • Family Dollar (West) - Hutchins
  • Family Dollar (East) - Hutchins
  • Hutchins Gateway Apts (South)
  • Airport Rd. @ S. Virginia St.
  • Holiday Inn Express (Terrell)
  • Mattress Zone
  • Virginia Anne Apts.
  • Country Manor Club Apts
  • TISD ExCEL Center
  • Bridge St. @ Hwy. 80
  • E. High St. @ Delphine St.
  • Peachtree Rd @ Slater Dr
  • Hickory Tree @ W Bruton Rd
  • Hickory Tree @ Asher Ln
  • Hickory Tree @ Lake June Rd
  • Food Pantry/Senior Center
  • E H Hanby Stadium, Mesquite, TX, USA
  • Lawnview Station, Dallas, TX, USA
  • FedEx Cedardale Rd.
  • Wal-Mart (Lake June)
  • Hickory Tree South of Lake June
  • Quail Drive at Glenshire Drive
  • Glenshire Drive at Home Depot entrance
  • Shepherd Lane at Elam Road
  • Peachtree Senior Living Apartments
  • Ambassador Apartments
  • DART - Buckner Station
  • Hickory Tree South of Lake June
  • Glenshire Drive at Home Depot entrance
  • Shepherd Lane at Elam Road
  • Balch Springs Recreation Center
  • Ambassador Apartments
  • Quail Drive at Glenshire Drive
  • David's Supermarket (E)
  • Kaufman Christian Help Center (E)
  • E. 1st North at Alton St. (E)
  • Washington at E. Hickory Street (E)
  • Texas Health Presbyterian Hospital (W)
  • W. Grove at Shannon (W)
  • Kaufman Square
  • Kaufman County Library
  • Washington at Cates
  • Kings Fort Pkwy at Washington
  • Wal-Mart
  • Washington Square / Cash Store
  • Washington at 7th (Northbound)
  • E. 7th St. and S. Dallas Street
  • E. 4th St. and Wilson
  • Washington at Chestnut
  • Hickory Tree at Municipal Center
  • Hickory Tree at Municipal Center
  • Villas of Seagoville
  • Wal-Mart/Bealls
  • Seagoville City Hall/Library
  • US-175 Frontage Rd @ Creekstone Ct
  • Cedar Point Apartments
  • Kimberly at Creekside
  • Creekside of Seagoville
  • N Hwy 175 @ W. Simonds Rd
  • Seagoville Shopping Ctr.
  • Mathis St @ Howard St.
  • Seagoville Senior Center

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 85.42026-07-30: 85.42026-07-31: 85.42026-08-01: 85.4
Show the numbers
CheckScoreChange
2026-07-2585.4 first check
2026-07-3085.4 no change
2026-07-3185.4 no change
2026-08-0185.4 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-31.

Same feed file as 2026-07-31; 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

8 findings, ordered by severity.

Show every finding
  • Warning117 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

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

  • Warning51 instances

    51 of 136 stops don't say whether a wheelchair user can board there.

    Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

    Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

    Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning10 instances

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

    See the linked rule for what this affects.

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

    Finding code: same_stop_and_agency_url · See MobilityData GTFS Validator rules

  • Warning10 instances

    10 of 10 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible stops, riders need to know the bus itself can take them.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • 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.)

    Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference

  • 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.)

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

  • Info8 instances

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

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

  • Info1 instance

    Some service dates fall outside the date window set in feed_info.txt.

    feed_info.txt should span every day your service runs, so apps know when the data applies.

    Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

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

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).

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 517 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 10 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 is close to the conformance mark. States wheelchair access on 62% 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 517 days.
Accessible Not yet
States wheelchair access on 62% 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.

  • 117 of 136 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.

Clears the Google and Apple Maps four-week coverage bar. This feed has 517 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.

Correctness 84 / 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 76 / 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.

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.

STAR Transit GTFS data quality grade: B

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/star-transit/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. 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.