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 9 hours ago; last fetch returned HTTP 404.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 1309 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points 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
911 of 911 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
2538 of 2538 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
This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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 ended 1309 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service 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
- Feed evidence
- 911 of 911 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
- 2538 of 2538 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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_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. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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 was 1309 days ago.
- 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
This feed is published from a code repository. Forward this to whoever maintains that repository; the fix happens in the source data, then a fresh export is committed. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 7 kinds of issue across 27 instances (0 error, 23 warning, 4 informational).
Service data ended 1309 day(s) ago. Trip planners have likely already dropped this feed.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is 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.
850 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("5th St. & Walnut St. Farside Nb", "5th St. & Elm St. Farside Nb", "5th St. & Madison Ave. Farside Nb", 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
This feed has no route shapes, so the map shows its stops only.
This feed has 911 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.
| Route | Type | Line color |
|---|---|---|
| 2 Fairgrounds Square Market | Bus | green (no shape in feed) |
| 3 Temple Via Kutztown Road | Bus | pink (no shape in feed) |
| 12 Lincoln Park Via Reading Hospital | Bus | gray (no shape in feed) |
| 20 Route 61-Hamburg | Bus | yellow (no shape in feed) |
| 9 Grill Via Kenhorst | Bus | red (no shape in feed) |
| 11 Mohnton Via Shillington | Bus | blue (no shape in feed) |
| 17 Glenside-Airport-Berks Heim | Bus | green (no shape in feed) |
| 7 Pennside | Bus | red (no shape in feed) |
| 8 Reiffton_shelbourne_square_birdsboro | Bus | teal (no shape in feed) |
| 16 Broadcasting Square | Bus | green (no shape in feed) |
| 15 Berkshire Mall | Bus | teal (no shape in feed) |
| 5 Albright College | Bus | purple (no shape in feed) |
| 10 Brookline | Bus | orange (no shape in feed) |
| 19c Cotton Street | Bus | purple (no shape in feed) |
| 19r Riverside | Bus | purple (no shape in feed) |
| 1 Temple Via 5th Street | Bus | red (no shape in feed) |
| 4 10th-11th Street | Bus | green (no shape in feed) |
| 18 Schuylkill Avenue | Bus | pink (no shape in feed) |
| 14 Wernersville Via Sinking Spring | Bus | gray (no shape in feed) |
| 22 Lyon Station-Deka | Bus | red (no shape in feed) |
List every stop
- 8th St. & Penn St. Farside Sb
- Perkiomen Ave. & 17th St. Farside Eb
- Park Rd. & Route 73 Far Side Eb
- 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 1
- Deka Stop 2
- Deka Stop 3
- Perkiomen Ave. & 18th St. Nearside Eb
- Deka Stop 4
- 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
- Perkiomen Ave. & 20th St. Nearside Eb
- Park Rd. & Route 222 Far Side Wb
- 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
- Perkiomen Ave. & 22nd St. Nearside Eb
- Kutztown Rd. & Exeter St. Far Side S B
- 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
- Richard Delp(stony Creek) Town Houses
- Front & Oley St. - Far Side - 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
- 22nd St. & Perkiomen Ave. Nearside Wb
- Route 183 & Mercer St. - Near Side - 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
- 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
- Perkiomen Ave. & 19th St. Farside Wb
- Schuylkill Ave & Lehigh St Nearside Sb
- 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
- Schuylkill Ave & Green St Near Side Sb
- Schykill Ave & Buttonwood St Far Side Sb
- Schuylkill Ave & Elm St - Near Side - Sb
- Front & Walnut St. - Near Side - Eastb
- Perkiomen Ave & 18th St Farside Wb
- Front & Washington St. - Near Side - Sb
- 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
- Kvp
- Perkiomen Ave. & 17th St. Farside Wb
- Rt 183 At Macarthur Rd
- Walmart North Reading Plaza
- 4th And Walnut Farside Southbound
- 5th St & Spring St Far Side West Bound
- Van Reed
- Granite Point
- Keiser
- 9th St. & Penn St. Farside-Nb
- Perkiomen Ave. & 16th St. Farside Wb
- Bti Midblock
- Ridgewood
- Berkshire Blvd
- Berkshire Mall Outbound
- 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
- 9th St. & Washington St. Farside-Nb
- 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
- 9th St. & Walnut St. Nearside-Nb
- 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
- Lanc Ave. & Carroll St. Farside Wb
- Lanc Ave. & Grace St. Farside Wb
- Lanc Ave. & Noble St. Farside Wb
- 9th St. & Elm St. Farside-Nb
- Lanc Ave. & Angelica St. Farside Wb
- Lanc Ave. & Rt 625 Farside Wb
- Lanc Ave. & Hancock Blvd. Farside Wb
- Wyomissing Blvd. & Margrt St. Farside Eb
- Lancaster Ave. & Rt 625 Mid-Block Eb
- Lancaster Ave. & Noble St. Farside Eb
- Lancaster Ave. & Carroll St. Farside Eb
- Lanc Ave. & Morgantown Rd. Nearsideeb
- Lanc Ave. & Wyomissing Ave. Farsidewb
- Lancaster Ave. & Museum Rd. Nearside Wb
- 9th St. & Buttonwood St. Farside-Nb
- Ollie's Outlet Mall Shillington
- South Church St. & Front St. Mid-Block
- Cherry St. & 6th St. Nearside Wb
- Cambridge Ave. & Parkview Pl. Farside Sb
- The Highlands Parking Lot
- K-Mart Main Entrance
- Springtowne Center (lowes/giant)
- Berkshire Hills Circle
- 9th St. & Green St. Farside-Nb
- Penn St. & 5th St. Farside Eb
- 5th St. & Penn St. Farside Wb
- 4th St. & Penn St. Farside Wb
- 3rd St. & Penn St. Farside Wb
- 2nd St. & Penn St. Nearside Wb
- 2nd Ave. & Penn Ave. Nearside Wb
- 3rd Ave. & Penn Ave. Mid-Block Wb
- 5th Ave. & Penn Ave. Farside Wb
- 6th Ave. & Penn Ave. Mid-Block Wb
- 8th Ave. & Penn Ave. Farside Wb
- 9th St. & Greenwich St. Farside-Nb
- Penn Ave. & Reading Ave. Farside Wb
- Redners At Sinking Spring
- W Penn Ave. & Sportsman Rd. Farside Wb
- Main St. & Parkside Dr At State Hospital
- Rt 422 & Rt 419 Mcdonalds
- Penn Ave. & Park Ave. Farside Eb
- Penn Ave. & Lynne Ave. Farside Eb
- Penn Ave. & Trent Ave. Farside Eb
- Penn Ave. & Fairview Ave. Nearside Eb
- Penn Ave. & 8th Ave. Farside Eb
- 9th St. & Oley St. Farside-Nb
- Penn Ave. & 6th Ave. Farside Eb
- Penn Ave. & 2nd Ave. Nearside Eb
- Penn St. & 2nd St. Farside Eb
- Penn St. & 3rd St. Farside Eb
- Penn St. & 4th St. Nearside Eb
- Penn St. & 5th St. Farside Eb
- Penn St. & 6th St. Nearside Eb
- Wal-Mart At Berkshire Square Mall
- 9th St. & Douglass St. Farside-Nb
- Spring St. & Crossing Dr. Nearside Nb
- Giant At Van Reed Rd
- 5th & Penn St. Mid Block Nb
- 5th & Washington St. Farside Nb
- 5th & Buttonwood St. Farside Nb
- 5th & Centre St. Farside Nb
- 5th St. & Walnut St. Farside Nb
- 9th St. & Windsor St. Farside-Nb
- Macarthur Rd & Barco Industries Entrance
- Macarthur Rd & Vist Financial Operations
- Macarthur Rd. & Phillips Van Heusen
- Macarthur Rd. & Direct Link Tech Center
- Berks Heim 2nd Stop
- 4th & Elm St. Farside Sb
- 4th & Washington St. Farside Sb
- 19th St & Cotton St Farside Wb
- Price-Rite Market At Outer Station
- Park-N-Ride Lot At First Energy Stadium
- 9th St. & Spring St. Farside-Nb
- Leesport Park And Ride (redners)
- Ashley Plant Entrance
- Fleetwood Fixtures Entrance
- Route 61 & Woodland Rd. Farside Eb
- Hamburg Park And Ride (redners)
- Jetson Dr. & Route 61 Mid Block Eb
- Iwcodirect Entrance
- Barta Transportation Center
- 6th St. & Cherry St. Mid Block Wb
- 9th St. & Robeson St. Farside-Nb
- 5th St. & Washington St. Farside Nb
- 5th St. & Buttonwood St. Farside Nb
- 5th St. &woodward St. Farside Nb
- 5th St. & Greenwich St. Farside Nb
- 5th St. & Oley St. Farside Nb
- 5th St. & Douglass St. Farside Nb
- 5th S.t & Windsor St. Farside Nb
- 5th St. & Spring St. Farside Nb
- 5th St. & Robeson St. Farside Nb
- 5th St. & Marion St. Farside Nb
- 9th St. & Marion St. Farside-Nb
- 5th St. & Perry St. Farside Nb
- 5th St. & Pike St. Farside Nb
- 5th St. & Bern St. Farside Nb
- 5th St. & Richmond St. Farside Nb
- 5th St. & Crescent St. Farside Nb
- 5th & Delta St. /ramada Inn Nearside Nb
- Boscov's North At Fairgrounds Mall
- 5th St. Hwy & Bellevue Ave. Farside Nb
- 5th St. & South Temple Blvd. Farsidenb
- 5th St. & Northtemple Blvd. Farside Nb
- 9th St. & Perry St. Farside-Nb
- 5th St. Hwy & Water St. Farside Nb
- 5th St. Hwy & Euclid Ave. Farside Nb
- 5th St. Hwy & Tuckerton Rd. Farside Nb
- 5th St. Hwy & San Mateo Lane Farside Nb
- 5th St. Hwy & 8th Ave. Nearside Nb
- 5th St. Hwy & Leesport Ave. Farside Nb
- 5th St. Hwy & Leesport Ave. Farside Sb
- 5th St. Hwy & 8th Ave. Farside Sb
- 5th St. Hwy & Tuckerton Rd. Farside Sb
- 5th St. Hwy & Euclid St. Farside Sb
- and 661 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 | 45.4 | first check |
| 2026-07-30 | 45.4 | no change |
| 2026-07-31 | 45.4 | no change |
| 2026-08-01 | 45.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
12 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1309 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning2538 instances
2538 of 2538 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)
- Warning911 instances
911 of 911 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)
- Warning16 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)
- Warning4 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · 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
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · 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)
- Info3 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 (opens the validator rules on an external site)
- Info1 instance
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
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 Not ready
Resolve this before you certify on the D-10. Service data expired 1309 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 1309 days ago, so FTA would find the link out of date.
- 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 Not ready
- No trips in this feed have a shape_id linked to a row in shapes.txt. Add shapes.txt with a shape_id for each trip's path, and set trips.shape_id to match. Reduced, Rural, and Tribal NTD reporters need this in their published GTFS starting Report Year 2026; Full Reporters needed it in Report Year 2025.
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. Service data expired 1309 days ago. 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 Not yet
- Service data expired 1309 days ago.
- 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
How this agency maps to the standards
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 77 / 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 0 / 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/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.