Feed status · checked 2026-08-01
Berks Area Regional Transportation Authority (BARTA)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Pennsylvania.
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 81 minutes ago; last changed 22 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
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
904 of 904 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 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
2578 of 2578 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
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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 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
- 904 of 904 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- 2578 of 2578 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
- Feed evidence
- The feed contains no fare information.
- Next action
- 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.
- 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.
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.
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.
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. 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.
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. · Read the fix guide
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 155 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
- 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.
Score by category
The MobilityData validator flagged 6 kinds of issue across 825 instances (0 error, 825 warning, 0 informational).
Service data covers the next 155 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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (4, 7, 8, 10, 12, and more).
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.
838 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Macarthur Rd & Barco Industries Entrance", "State & 2nd St. Farside Eb", "State & 3rd St. Nearside Eb", 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.
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 904 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.
- 1 (red)
- 10 (orange)
- 11 (blue)
- 12 (gray)
- 14 (gray)
- 15 (teal)
- 16 (green)
- 17 (green)
- 18 (pink)
- 19c (purple)
- 19r (purple)
- 2 (green)
- 20 (yellow)
- 22 (red)
- 3 (pink)
- 4 (green)
- 5 (purple)
- 7 (red)
- 8 (teal)
- 9 (red)
| Route | Type | Line color |
|---|---|---|
| 1 Temple via 5th Street | Bus | red |
| 10 Brookline | Bus | orange |
| 11 Mohnton via Shillington | Bus | blue |
| 12 Lincoln Park via Reading Hospital | Bus | gray |
| 14 Wernersville via Sinking Spring | Bus | gray |
| 15 Berkshire Mall | Bus | teal |
| 16 Broadcasting Square | Bus | green |
| 17 Glenside/Airport/Berks Heim | Bus | green |
| 18 Schuylkill Ave. | Bus | pink |
| 19c Cotton Street via BTC | Bus | purple |
| 19r Riverside/First Energy Stadium | Bus | purple |
| 2 Fairgrounds Sq. Market | Bus | green |
| 20 Route 61/Hamburg | Bus | yellow |
| 22 Lyon Station/East Penn DEKA | Bus | red |
| 3 Temple via Kutztown Rd. | Bus | pink |
| 4 10th / 11th Streets | Bus | green |
| 5 Albright College | Bus | purple |
| 7 Pennside | Bus | red |
| 8 Reiffton/Shelbourne/Birdsboro | Bus | teal |
| 9 Grill via Kenhorst | Bus | red |
List every stop
- Macarthur Rd & Barco Industries Entrance
- State & 2nd St. Farside Eb
- State & 3rd St. Nearside Eb
- 3rd & Pine St. Nearside Sb
- 4th & Pine St. Nea Side Eb
- 4th & Windsor Castle Rd. Nearside Sb
- 4th & Arch St. Nearside Sb
- 4th & Maple St. Nearside Sb
- Route 61 & Cougles Entrance Nearside Sb
- Route 61 & Balthaser St. Farside Sb
- Route 61 & Schappell Rd. Farside Sb
- 5th St. & Walnut St. Farside Nb
- Route 61 & Zions Church Rd. Farside Sb
- Route 61 & Tom Schaffer's Rv Entrance
- Route 61 & Bellvue Ave. Farside Sb
- Route 61 & Boyer's Market Entrance
- Route 61 & 9th St. Nearside Sb
- Route 61 & Route 662 Farside Sb
- Route 61 & Glen Gery Entrnce Nearside Sb
- Route 61 & Birch Hill Rd. Nearside Sb
- Route 61 & Eb Consulting Entrance
- Route 61 & Mohrsville Rd. Farside Sb
- 5th St. & Elm St. Farside Nb
- Route 61 & Bellmans Chrch Rd. Farside Sb
- Route 61 & Wall St. Farside Sb
- Route 61 & Peach St. Farside Eb
- Route 61 & Schneider Electric Entrance
- Route 61 & Route 73 Nearside Sb
- Route 61 & Berkley Park Rd. Farside Sb
- Route 61 & Snyder Rd. Farside Sb
- Route 61 & Energy Ln. Farside Sb
- Route 61 & Cross Keys Rd. Nearside Sb
- 5th St. & Madison Ave. Farside Nb
- Route 61 & Crossrds Blvd. Farside Sb
- Route 61 & Tuckerton Rd. Farside Sb
- Muhlenberg Indust Mall East Farside Sb
- Route 61 & Reading Crest Ave.farside Sb
- Centre & Bellevue Ave. Nearside Sb
- Centre Ave. & George St. Farside Sb
- Centre Ave. & Cathedral St. Farside Sb
- Centre Ave. & Bern St. Nearside Sb
- Centre Ave. & Bern St. Farside Sb
- Centre Ave. & Exeter St. Farside Sb
- 5th St. Hwy At Bojangles Nearside Nb
- Centre Ave. & Evans St. Nearside Sb
- Centre Ave. & Pike St. Nearside Sb
- Centre Ave. & Robeson St. Nearside Sb
- Centre Ave. & Spring St. Farside Sb
- Centre Ave. & Windsor St. Farside Sb
- Centre Ave. & Douglass St. Farside Sb
- Centre Ave. & Oley St. Farside Sb
- 4th St. & Greenwich St. Farside Sb
- Court & 5th St. Farside Eb
- 5th St. Hwy At Plaza 222 Farside Nb
- Court And Reed St. Farside Eb
- Court And 8th St. Nearside Eb
- 5th St. Hwy & Elizabeth Ave. Farsidenb
- 5th St. Hwy Walmart
- Hampden Blvd. & Robeson St. Far Side Nb
- Hampden Blvd. & Marion St. Far Side Nb
- Hampden Blvd. & Exeter St. Far Side Nb
- 8th St. & Penn St. Farside Sb
- Hampden Blvd. & College Ave. Far Side Nb
- Hampdn Blvd. & Deer Path Rd. Far Side Wb
- Reservor Rd. & Hampdn Blvd. Near Side Eb
- Kutztown Rd. & Exeter St. Far Side Nb
- Kutztown Rd. & Bellvue Ave. Far Side-Nb
- Route 222 & Park Rd. Far Side Eb
- Park Rd. & Brl Grocery Far Side Eb
- Park Rd. & Route 73 Far Side Eb
- 9th St. & Penn St. Farside-Nb
- Park Rd. & Golden Dr. Mid-Block Eb
- Park Rd. & Walnuttown Rd. Far Side Eb
- Main St. & Route 662 S. Far Side Eb
- Main St. & Route 662 N. Far Side Eb
- Fleetwood Lyons Rd At Weaver's Hardware
- Deka/epenn Main Entrance Guard Booth
- Deka Stop 3
- Deka Stop 4
- 9th St. & Washington St. Farside-Nb
- Deka Stop 5
- Deka Stop 6
- Deka Stop 7
- Main St. & Route 662 N. Far Side Wb
- Main St. & Route 662 S. Far Side Wb
- Park Rd. & Walnuttown Rd. Far Side Wb
- Park Rd. & Golden Rd. Mid-Block Wb
- Park Rd. & Route 73 Far Side Wb
- Park Rd. & Dries Rd. Far Side Wb
- Park Rd. & Route 222 Far Side Wb
- 9th St. & Walnut St. Nearside-Nb
- Kutztown Rd. & Mt. Laurel Rd.far Side-Sb
- Kutztown Rd. & Hay Rd. Far Side-Sb
- Kutztwn Rd. & E. Belvue Ave.-Far Side-Sb
- Kutztwn Rd. & Elizabeth Ave. Far Side-Sb
- Kutztown Rd. & Emerson Ave. Far Side-Sb
- Kutztown Rd. & Girard Ave.-Far Side-Sb
- Kutztown Rd. & Monroe St. Far Side-Sb
- Kutztown Rd. & Exeter St. Far Side S B
- 9th St. & Elm St. Farside-Nb
- 9th St. & Perry St. Far Side-Sb
- 3rd & Washington St. - Far Side - Wb
- 2nd & Washington St. - Far Side - Wb
- Front & Washington St. - Far Side - Nb
- Front & Walnut St. - Far Side - Nb
- Front & Elm St. - Far Side - Nb
- Front & Buttonwood St. - Far Side - Nb
- Front & Green St. - Far Side - Nb
- Front & Greenwich St. - Far Side - Nb
- Front & Oley St. - Far Side - Nb
- 9th St. & Buttonwood St. Farside-Nb
- Front & Douglass St. - Far Side - Nb
- Front & Windsor St. - Far Side - Wb
- Windsor & Weiser St. - Far Side - Wb
- Windsor & Lincoln St. - Far Side - Wb
- Windsor St. & Sch Ave. Near Side Wb
- Schuylkill & Blair Ave. - Far Side - Nb
- Schuylkill Ave. & Avenue B Near Side Nb
- Sch Ave. & Avenue A - Far Side - Nb
- Route 183 & Lackawanna St. Near Side Nb
- Route 183 & Mercer St. - Near Side - Nb
- 9th St. & Green St. Farside-Nb
- Route 183 & S Tulpehocken Rd Nearside Nb
- Route 183 & Barlow Ave. - Near Side - Nb
- Route 183 & Martin Ave. - Near Side - Nb
- Route 183 & Boeing Ave. - Near Side - Nb
- Route 183 & Reading Airport Far Side Nb
- St. Joesph Hospital
- Route 183 & Reading Airport Far Side Sb
- Route 183 & Boeing Ave. - Far Side - Sb
- Route 183 & Martin Ave. - Far Side - Sb
- 9th St. & Greenwich St. Farside-Nb
- Route 183 & Morrison Rd. - Far Side - Sb
- Route 183 & N Tulpehocken Rd Nearside Sb
- Route 183 & S Tulpehocken Rd Nearside Sb
- Route 183 & Mercer St. - Far Side - Sb
- Route 183 & Lackawanna St Near Side Sb
- Lackawanna & Chester St - Near Side - Nb
- Schuylkill Av & Lackawanna St Farside Sb
- Schuylkill Ave & Lehigh St Nearside Sb
- 9th St. & Oley St. Farside-Nb
- Schuylkill & Blair Ave. - Near Side - Sb
- Schuylkill Ave & Windsor St Far Side Sb
- Schuylkill Ave & Douglass St Far Side Sb
- Schuylkill Ave & Oley St - Far Side - Sb
- Schuylkill Ave & Greenwich St Farside Sb
- Schykill Ave & Buttonwood St Far Side Sb
- Schuylkill Ave & Elm St - Near Side - Sb
- Front & Walnut St. - Near Side - Eastb
- Front & Washington St. - Near Side - Sb
- 9th St. & Douglass St. Farside-Nb
- 2nd & Court St. - Far Side - Eastb
- 3rd & Court St. - Far Side - Eastb
- 4th & Court St. - Far Side - Eastb
- 5th & Court St. - Far Side - Eastb
- 6th & Court St. - Near Side - Eastb
- 8th & Court St. - Near Side - Eastb
- Penn Ave & Park Rd Far Side East Bound
- Rt 183 At Macarthur Rd
- 9th St. & Windsor St. Farside-Nb
- Walmart North Reading Plaza
- 4th And Walnut Farside Southbound
- 5th St & Spring St Far Side West Bound
- Van Reed
- Granite Point
- Keiser
- Bti Midblock
- 9th St. & Spring St. Farside-Nb
- Ridgewood
- Berkshire Blvd
- Berkshire Mall Outbound
- 9th St. & Robeson St. Farside-Nb
- 9th St. & Marion St. Farside-Nb
- 9th St. & Perry St. Farside-Nb
- 9th St. & Pike St. Farside-Nb
- 9th St. & Amity St. Farside-Nb
- 9th St. & Union St. Farside-Nb
- Kutztown Rd. & Rockland St. Farside-Nb
- Kutztown Rd. & Delta Ave. Nearside-Nb
- Fairgrounds Market-Sb
- Kutztown Rd. & Delta Ave. Nearside Sb
- Rockland Plaza Mid Block Sb
- Barta Main Office 1700 N. 11th St.
- 10th St. & Union St. Farside Sb
- 10th St. & Amity St. Farside Sb
- 10th St. & Perry St. Farside Sb
- 10th St. & Robeson St. Farside Sb
- 10th St. & Spring St. Farside Sb
- 10th St. & Windsor St. Farside Sb
- 10th St. & Greenwich St. Farside Sb
- 10th St. & Green St. Farside Sb
- 10th St. & Elm St. Farside Sb
- 10th St. & Walnut St. Farside Sb
- 10th St. & Washington St. Nearside Sb
- 10th St. & Penn St. Nearside Sb
- 9th St. & Penn St. Nearside Wb
- 8th St. & Walnut St. Nearside-Sb
- 9th St. & Penn St. Nearside-Nb
- 10th St. & Penn St. Farside Eb
- 11th St. & Penn St. Farside-Nb
- Hampden Blvd. & Rockland St. Sb
- Hampden Blvd. & City Line Ave. Sb
- Berkshire Mall Main Entrance
- Berkshire Mall Sears Entrance
- Penn Ave. & 4th Ave. Mid Block Wb
- Penn Ave. & 3rd Ave. Mid Block Wb
- Weiser St. & Douglass St. Nearside Sb
- Penn Ave. & 4th Ave. Farside Eb
- Penn Ave. & 2nd Ave. Mid Block Eb
- 11th St. & Penn St. Nearside Eb
- Perkiomen Ave. & Franklin St.nearside Eb
- Perkiomen Ave. & Chestnut St.nearside Eb
- Perkiomen Ave. & 14th St. Nearside Eb
- Perkiomen Ave. & 15th St. Farside Eb
- Perkiomen Ave. & 16th St. Farside Eb
- Perkiomen Ave. & 17th St. Farside Eb
- Perkiomen Ave. & 18th St. Nearside Eb
- Perkiomen Ave. & 20th St. Nearside Eb
- Perkiomen Ave. & 22nd St. Nearside Eb
- Richard Delp(stony Creek) Town Houses
- 22nd St. & Perkiomen Ave. Nearside Wb
- Perkiomen Ave. & 19th St. Farside Wb
- Perkiomen Ave & 18th St Farside Wb
- Perkiomen Ave. & 17th St. Farside Wb
- Perkiomen Ave. & 16th St. Farside Wb
- Perkiomen Ave. & 15th St. Farside Wb
- Perkiomen Ave. & 14th St. Farside Wb
- Perkiomen Ave. & Spruce St. Farside Wb
- Perkiomen Ave. & Min Spring Nearsidewb
- Perkiomen Ave. & Franklin St Nearside Wb
- 11th St. & Penn St. Farside Wb
- 10th St. & Penn St. Nearside Wb
- Walmart In Exeter
- Rte 345 & East Main St. Farside Eb
- Cheatnut St. & East 1st St.
- East 5th St. & Chestnut St. Farside Wb
- East 5th St. & Union St. Farside Wb
- Union St. & Hopewell St. Farside Wb
- Hopewell St. & Hay Creek Rd. Farside Wb
- 4th St. & Cherry St. Farside Sb
- 4th St. & Chestnut St. Farside Sb
- 4th St. & Spruce St. Farside Sb
- 4th St. & Pine St. Farside Sb
- Redner's At Kenhorst Plaza
- 5th St. & Laurel St. Farside Nb
- 5th St. & Bingaman St. Farside Nb
- 5th St. & Spruce St. Farside Nb
- 5th St. & Chestnut St. Farside Nb
- 5th St. & Franklin St. Farside Eb
- Lanc Ave. & Morgantown Rd. Farside Wb
- and 654 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 63.8 | first check |
| 2026-07-30 | 63.8 | no change |
| 2026-07-31 | 63.8 | no change |
| 2026-08-01 | 63.8 | 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
10 findings, ordered by severity.
Show every finding
- Warning2578 instances
2578 of 2578 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 (opens the GTFS Schedule reference on an external site)
- Warning904 instances
904 of 904 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 (opens the GTFS Schedule reference on an external site)
- Warning597 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.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning178 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning23 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning16 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning10 instances
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators 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.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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 155 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 2578 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 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 155 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 155 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 62 / 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 38 / 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.
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/berks-area-regional-transportation-authority-barta-2064/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.