Feed status · checked 2026-10-07
El Paso Transportation Authority
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-10-06
Cataloged in Texas.
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.4, validator 8.0.1.
Checked for changes 62 minutes ago; last changed 95 days ago.
Measured 4 of 4 score categories from the feed URL on file (publisher not verified).
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 6 snapshots.
- 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.
About this feed
El Paso Transportation Authority’s published feed lists 6 bus routes, 143 scheduled trips and 195 stops. It publishes realtime trip updates and vehicle positions; when we checked, all of them answered. The published file last changed on 2026-07-04.
Top things to fix
Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out.
12 of 12 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.
This was measured over a realtime sampling window, so it has no feed-wide share.
⏱ A vendor data-mapping question.worth about +41 points in its category
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
195 of 195 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 195 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
143 of 143 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 143 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 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.
- Texas 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-10-05.
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_rt_trip_coverage
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.
Fix 02 · 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. Self-check a feed before you publish.
Fix 03 · 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. 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 205 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
- No fare information is published in the feed.
- Realtime information
- Live-arrival data covered 0% of scheduled trips in the sampled window.
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.
Score by category
The MobilityData validator flagged 1 kind of issue across 2 instances (0 error, 2 warning, 0 informational).
Service data covers the next 205 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 not 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 (Rte10, Rte30).
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.
178 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Socorro Rd @ Gonzales St", "Socorro Rd @ Southside Rd", "Socorro Rd @ Gaspar", 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.
Sampled 6 times: 2 of 2 configured feeds healthy; 0.0% of scheduled trips had live predictions; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 195 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.
- Rte50 (purple)
- Rte10 (blue)
- Rte20 (red)
- Rte30 (orange)
- Rte31 (brown)
- Rte40 (yellow)
| Route | Type | Line color |
|---|---|---|
| Rte50 Rte 50 - MVTC - Mission Trail | Bus | purple |
| Rte10 Rte 10 - WTC - Anthony/Canutillo | Bus | blue |
| Rte20 Rte 20 - UETC - Montana Vista | Bus | red |
| Rte30 Rte 30 - MVTC - Horizon | Bus | orange |
| Rte31 Rte 31 - MVTC - Eastlake | Bus | brown |
| Rte40 Rte 40 - MVTC - Fabens - Tornillo | Bus | yellow |
List every stop
- Montana - Tierra Este
- Agua Clara - El Rosio
- Alameda Ave. & Zepplin Dr.
- Alameda Ave. & Bufford Rd.
- Eastlake Blvd.& Peyton Dr.
- Banker Rd. & Tom Mays Rd.
- Westway Blvd & De Alva Dr.
- Franklin St. & S Eight St.
- Eastlake Blvd.& Rojas Dr (NB)
- Doniphan Dr. & Talbot Ave. (NB)
- De Alva Dr. & Gallardo Rd.
- Mark Jason Dr. & Marvin Ln.
- Horizon Blvd. & Thea Smith Dr.
- Horizon Bl Vd. & Nancy Dr.
- Doniphan Dr & Graphite Dr
- 5500 Doniphan Dr & McCutcheon Ln
- Socorro Rd @ Passmore Rd
- Doniphan Dr & Redd Rd (NB)
- Horizon Blvd.& Ascencion St.
- 13071 Socorro Rd
- Eastlake Blvd.& Peyton Dr.
- Doniphan Dr. & El Chanate Rd. (NB)
- Clint Rd @ Alameda Ave
- Mission Del Paso @ E.P.C.C
- Alameda Ave. & San Elizario Rd.
- Doniphan Dr. & La Mesa Ave. (NB)
- Montana - Krag
- Horizon Blvd. & Desert Mesa St.
- Fabens St. & Camp St.
- Darrington Rd. & Horizon Blvd. (Side Of Walmart Off Darrington)
- Doniphan Dr & Montoya Dr (NB)
- Licons Dairy Azaderos, 11951 Glorietta Rd
- Fabens St & San Eli Supermarket
- Socorro Rd @ Lisa Diane Rd
- Darrington & Desierto Lindo Ave.
- Socorro Rd @ Passmore Rd
- Montana Ave. & Tierra Este Rd. (Justice St.)
- Horizon Blvd. & Stockyard Rd.
- Doniphan Dr & Mcclintock Dr (NB)
- Alameda Ave. & Fortaleza Rd.
- Peyton Rd. & Bret Harte Dr.
- Eastlake Blvd. & Darrington Rd.
- Doniphan Dr & Park Ridge Ct
- Doniphan Dr. & Park Ave. (NB)
- Socorro - Bovee
- Alameda Ave. & N Rio Vista Rd. (Socorro Hs)
- Socorro Rd @ Buford Rd
- FM 1110/San Elizario Rd @ Rio Negro Dr
- Alameda Ave. & N Rio Vista Rd. (Socorro Hs)
- Socorro Rd @ San Antonio Ave
- Mission Valley Transfer Center
- Peyton Rd. & Trollope Dr.
- Alameda Ave @ Velasco Way
- Tornillo & OT Smith
- Socorro Rd @ Jericho Dr
- Socorro - Jericho
- N Mesa St & Osborne Dr
- Franklin St. & S 2Nd St.
- Socorro Rd @ Caribe Cir
- San Elizario - Camino de la Rosa
- Westside Transfer Center
- Montana - Las Casitas
- Antionio St. & Luisa St.
- 6161 Doniphan Dr & Rio Valley Estates (NB)
- Doniphan Dr. & Mcarthur St. (NB)
- 5320 Doniphan Dr & JJ Mexican Restaurant
- Socorro Rd @ Buford Rd
- Socorro Rd @ Bovee Rd
- Desert Meadows Rd. & Montana Ave.
- Horizon Blvd. & Rodman Dr
- Socorro Rd @ Yaya Ln
- Alameda Ave @ Americas Ave
- Socorro Rd @ Paseo Del Convento (Presido Chapel)
- Doniphan Dr & Borderland Road (NB)
- Doniphan Dr & Borderland Road (SB)
- Socorro Rd @ Gonzales St
- Oleary Dr. & Newell Heights
- Socorro Entertainment Center
- Eastlake Blvd. & Darrington Rd.
- FM 1110/San Elizario Rd @ Hansard Dr
- Eastlake Blvd. & Gateway Blvd
- Socorro Rd @ Borrego Rd
- Socorro - Cabribe
- Antonio St. & Wildcat Dr.
- Eastlake Blvd. & Emerald Park Dr.
- Doniphan Dr. & Vinton Rd. (SB)
- Doniphan Dr. & La Mesa Ave. (SB)
- Oleary Dr. & Marsha Rd.
- Montana Ave. & Square Dance Rd.
- Horizon Blvd. & Darrington Rd. (Horizon City Pw)
- Alameda Ave @ Americas Ave
- Westway Blvd. & Tom Mays Rd.
- Upper Eastside Transfer Center
- Greg Dr. & Mark Jason Dr.
- Bowdoin - Horizon
- Alameda Ave. & Denton Rd.
- Doniphan Dr. & Mcarthur St. (SB)
- Doniphan Dr. & El Chanate Rd. (SB)
- Doniphan Dr. & Park Ave. (SB)
- Doniphan Dr. & Talbot Ave. (SB)
- Doniphan Dr. & Crystal Marie Rd. (SB)
- Doniphan Dr & Viramontes St (SB)
- Doniphan Dr & Rio Valley Estates (SB)
- Doniphan Dr & Montoya Dr (SB)
- Doniphan Dr & Coates Dr (SB)
- Doniphan Dr & West Green Dr (SB)
- Doniphan Dr & Redd Rd (SB)
- Doniphan Dr & Mulberry Ave
- Doniphan Dr & Mcclintock Dr (SB)
- 7845 N Mesa St & Osborne Dr
- 7575 N Mesa & 1St Remcon Cir
- 7411 Remcon Cir & N Mesa St
- Doniphan Dr & West Green Dr (NB)
- Doniphan Dr & Coates Dr (NB)
- Doniphan Dr & Viramontes St (NB)
- Doniphan Dr. & Crystal Marie Rd. (NB)
- Edgemere\Tierra Paso
- Edgemere\Tierra Angel
- Edgemere\Tierra Nevada
- 12401 Edgemere\Tierra Este
- Montana Ave. & Rich Beem Blvd.
- Montana Ave. & N Zaragoza Rd.
- Montana Ave. & Square Dance Rd.
- Montana Ave. & N Zaragoza Rd.
- Las Casitas Dr. & George Dickens Pl
- Big John Dr. & Vanderveer Dr.
- Oleary Rd. & Patsy Pl.
- Montana Ave. & Turf Rd.
- Tierra Este Rd & Montana Ave (Walmart)
- Tierra Este Rd & Tierra Laguna Dr
- Rc Poe Rd & Pablo Sanchez Pl
- Rc Poe Rd & Sammy Reece Pl
- Rc Poe Rd & Tierra Este Rd
- Rc Poe Rd & Tierra Inca Dr
- Rc Poe Rd & Tierra Aurora Dr
- Alameda Ave @ Presa Pl
- Alameda Ave @ Presa Pl
- Alameda Ave @ Carnes Rd
- Alameda Ave @ Carnes Rd
- Alameda Ave @ Ivey Rd
- Alameda Ave @ Rafael Septian Ln
- Horizon Blvd. & Montevideo St.
- Horizon Blvd @ Montevideo St
- Horizon Blvd @ Monte Alto Dr
- Horizon Blvd @ Across Horizon Bakery
- Horizon Blvd @ Robin Rd
- Horizon Blvd. & Elsworth Dr.
- Horizon Blvd. & Elsworth Dr.
- Horizon Blvd. At Walmart
- Darrington Rd. & Scobey Dr.
- Darrington Rd. & Alder Wood Manor Dr.
- Darrington Dr. & Horizon Blvd. (Hrzn City Mpal. Ct)
- Darrington & Horizon Blvd.
- Horizon Blvd. & Howard Lowe
- Darrington Rd. & Rosyln Dr.
- Eastlake Blvd. & Emerald Sands Ave.
- Eastlake Blvd. & Gateway Blvd. W (Sisd)
- Alameda Ave @ Cananea Ln
- Alameda Ave @ Cananea Ln
- Alameda Ave @ Horizon Blvd
- Alameda Ave @ Place Rd
- Alameda Ave @ Vineyard Rd
- Alameda Ave @ Passmore Rd
- Alameda Ave @ Melton Rd
- Alameda Ave @ Camino De La Rosa Rd
- Alameda Ave @ Jeff Jones Dr
- Fabens St. & Ne I Ave. Rd.
- Alameda Ave. & 4Th St.
- Alameda Ave. & 4Th St. TCP
- Alameda Ave. & Oil Mill Rd.
- Alameda Ave. & Denton Rd.
- Alameda Ave. & River Hondo
- Alameda Ave. & Fortaleza Rd.
- Socorro Rd @ Southside Rd
- Socorro Rd @ Gaspar
- Socorro Rd @ Zenaida
- 601 Tiwa Rd
- Socorro Rd @ Thompson Rd
- FM 1110/San Elizario Rd @ Campo Bello Dr
- FM 1110/San Elizario Rd @ Camino Barrial
- Socorro Rd @ Thompson Rd
- Socorro Rd @ Brisa Del Valle Dr
- Socorro Rd @ F E Jackson Rd
- Socorro Rd @ Anahi
- Socorro Rd @ Holguin Rd
- Socorro Rd @ Moon Rd
- Socorro Rd @ Winn Rd (Lady Caf)
- Socorro Rd @ Isaiah Dr
- Socorro Rd @ Oscar Alvarez Ct
- Alameda Ave. & Bufford Rd
- Horizon Blvd @ Patti Jo Dr
- Montana & Flager St
- Montana Ave. & Mark Avizio
- Stacey Anne Dr. & Mark Jason Dr
- Mark Jason Dr. & Karl Ct.
Over time
Overall score across the last 2 checks — unchanged since 2026-10-06.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-06 | 72.8 | first check |
| 2026-10-07 | 72.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
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-10-06 to 2026-10-07 (2 checks) | db45e5ce8290 | 2027-04-30 | Current rubric: see the trend above |
| 2026-08-06 to 2026-09-13 (4 checks) | db45e5ce8290 | 2027-04-30 | C, 72.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-04 to 2026-07-10 (7 checks) | db45e5ce8290 | 2027-04-30 | C, 77.7 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-01 to 2026-07-02 (2 checks) | bb67a276c413 | 2027-04-30 | C, 78.2 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-06-30 (12 checks) | f27262ba24f4 | 2027-04-30 | C, 78.6 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall grade and score held steady since 2026-10-06.
Same feed file as 2026-10-06; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
7 findings, ordered by severity.
Show every finding
- Warning195 instances
195 of 195 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)
- Warning143 instances
143 of 143 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)
- Warning30 instances
30 of 143 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning12 instances
12 of 12 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.
Fix: Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide for scorecard_rt_trip_coverage · See GTFS-Realtime reference (opens the GTFS-Realtime 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.)
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 is missing its start/end dates
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
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 205 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 143 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 205 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.
Realtime reliability
The realtime feed responded on 100.0% of 200 checks in the 25 days to 2026-10-07, with 9s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
Clears the Google and Apple Maps four-week coverage bar. This feed has 205 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 96 / 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 85 / 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 42 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 59 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Part of the Texas portfolio: the same scorecards for every feed we track in that group, on one free page.
For programs that support several agencies
This scorecard and the board one-pager for El Paso Transportation Authority are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.
The report for El Paso Transportation Authority uses the same numbers as this page: grade C (72.8 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.
One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.
See a sample bundle report: a real agency's current grade, with placeholder branding.
A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.
Similar feeds in Texas
Other scorecards in Texas, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/el-paso-transportation-authority/2026-10-07.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-10-07. 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.