Feed status · checked 2026-08-01
Beaver County Transit Authority
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 1 days ago; last fetch returned HTTP 403.
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 1674 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
234 of 234 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
231 of 231 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 URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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 1674 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
- 234 of 234 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
- 231 of 231 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 URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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 URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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 URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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 1674 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 served from the TransitFeeds archive, which is no longer maintained. The most useful request is publishing the current feed from a live URL, then these fixes. 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 5 kinds of issue across 124 instances (0 error, 124 warning, 0 informational).
Service data ended 1674 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.
1 accessibility depth signal
210 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("9th St at Indiana Ave", "Pennsylvania Ave at 6th St", "79 Wagner Rd (opp. HV Rehab)", 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 234 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.
- 11 (purple)
- 4 (yellow)
- 1 (blue)
- 2 (yellow)
| Route | Type | Line color |
|---|---|---|
| 11 Beaver/BVM | Bus | purple |
| 4 Express 376 | Bus | yellow |
| 1 Ohio River Blvd | Bus | blue |
| 2 Local/Beaver Valley Mall | Bus | yellow |
List every stop
- Duss Ave at Keystone Rd
- 11th St at Ambridge Park and Ride Lot
- Ohio River Blvd at Broad St
- 3rd Ave at 16th St
- Ohio River Blvd at Hazel Ln
- Brodhead Rd at Charity St
- Market St at 5th St (Stop 1)
- 3rd Ave at 12th St
- Duss Ave at 16th St
- Medical Center
- State Ave at Toy St
- Ohio River Blvd at Virginia Ave
- Ohio River Blvd at McKees Rocks Bridge
- State Ave at Dravo St
- 3rd St at Walnut St
- 746 Franklin Ave
- Franklin Ave at Bank St (Police Station)
- State St opp. Phillips St
- 3rd Ave opp. Harvey Run Rd
- Grant St at Oliver Ave
- Monaca Rd at Davis St
- 376 Market St
- Duss Ave at 25th St
- 2950 Duss Ave
- 3rd Ave opp. 5th St
- State St at Johnson Ave
- Monaca Rd at Sheffield
- Shenango Rd at Wallace Run Rd
- Brodhead Rd opp. Main St
- Duss Ave at Beaver Rd
- Main St at 21st St
- 4th Ave opp. 47th St
- Brodhead Rd opp. Charity St
- 7th Ave at 22nd St
- Franklin Ave at Engle St
- 3rd Ave at 12th St
- Mill St at Spring St
- 3rd St at Buffalo St
- 3rd Ave at 16th St
- Township Market Place (Vision Works)
- Northern Lights Shopping Center
- Rochester Transportation Center
- Ohio River Blvd at Camp Horne Rd
- 7th Ave at 17th St
- 810 Merchant St
- State Ave at Dravo St
- 3rd St at Lincoln Ave
- Duss Ave at 16th St
- Duss Ave opp. Legionville Hollow Rd
- Main St at Brodhead Rd
- Friendship Ridge
- 3rd Ave at 6th St
- State St at Johnson Ave
- Main St at 21st St
- Brighton Ave at New York Ave
- Brighton Ave at Jefferson St
- Duss Ave opp. 25th St
- 4th Ave opp. 43rd St
- Mill St at Guy St
- Francis Farmer Apartments
- 3rd St at Insurance St
- Brodhead Rd opp. Lincoln Dr
- Waugaman St at Tyler St
- Northern Lights Shopping Center
- Brodhead Rd at Admiral St (Wendy's)
- 3rd Ave at Harvey Run Rd
- Franklin Ave opp. Pine St
- 3rd St at Beaver St
- Merchant St at 4th St
- Ohio River Blvd at Elizabeth St
- Duss Ave at 14th St
- Mill St opp. Golf Course Rd
- Duss Ave opp. Dearborn St
- 7th Ave at 10th St
- 79 Wagner Rd (HV Rehab)
- 4th St at Park Rd
- Brodhead Rd at Lincoln Dr
- Brighton Ave at Pleasant St
- 3rd Ave at 9th St
- Wagner Road (Target)
- Ohio River Blvd at Hazel Ln
- East Busway (Regional Bus Stop)
- 2973 Duss Ave
- Franklin Ave opp. Kiehl St
- Duss Ave opp. Harmony Rd
- 9th St at Indiana Ave
- Ohio River Blvd at Broad St
- 11th St at Ambridge Police Dept
- Tyler St at Warnock St
- 3531 Brodhead Rd
- Expressway Travel Center
- 9th St at Indiana Ave
- 4th Ave at 36th St
- Franklin Ave (Klenovich's)
- Brodhead Rd opp. Ridgeview Dr
- 3rd St at Beaver St
- 1st Ave at 9th St
- 7th Ave at 13th St
- Merchant St at 11th St
- 3rd Ave at Brightwood Manor
- 7th Ave at 25th St
- Duss Ave at 23rd St
- Brodhead Rd at Ridgeview Dr
- 7th Ave at 6th St
- Bethel Lane at Wykes St
- Monaca Rd opp Sheffield
- Ohio River Blvd at Walnut St
- Pennsylvania Ave at 6th St
- Brodhead Rd at Oak Ln
- Brodhead Rd at Sherwood Dr
- Ohio River Blvd at East Rochester Plaza
- Main St at Brodhead Rd
- Market St Courthouse parking lot entrance
- Brodhead Rd opp. Bonanni Dr
- Brodhead Rd at Hospital Dr
- 4th Ave at 43rd St
- Township Market Place (Texas Roadhouse)
- Brodhead Rd at Bonanni Dr
- 4th Ave at 36th St
- Brodhead Rd at Sheffield Rd
- Duss Ave at 8th St
- Grant St at 4th Ave
- Ohio River Blvd at Willow St
- 3rd Ave at Brightwood Manor
- 7th Ave at 6th St
- Ohio River Blvd at Fisk St
- 719 Merchant St
- Tyler St at Warnock St
- Duss Ave at Dearborn St
- Brodhead Rd at Mt Carmel Drive
- 2011 Sheffield Rd
- Grant St at Liberty Ave (Federal Bldg)
- Ohio River Blvd at Quaker Village Shopping Ctr
- 3rd Ave at 6th St
- State Ave at Tamaqui Dr
- Market St at 5th St (Stop 2)
- 7th Ave at 22nd St
- Ohio River Blvd at Riverview Ave
- 11th St opp. Ambridge Police Dept
- 2011 Sheffield Rd
- Ohio River Blvd opp. McKees Rocks Bridge
- 4th Ave opp. 33rd St
- 1st Ave at 9th St
- Wal-Mart Supercenter
- Brodhead Rd at Center Grange Rd
- Brodhead Rd at Sheffield Rd
- 4th St at Merchant St
- Franklin Ave at Engle St
- Brodhead Rd at Admiral St (Wendy's)
- Ohio River Blvd at Walnut St
- Duss Ave at Harmony Ave
- 3rd St at Chestnut St
- Friendship Circle (Entrance)
- 7th Ave at 17th St
- Green Garden Plaza (Sally's Beauty)
- 7th Ave at 25th St
- 3rd Ave at 9th St
- Wallace Run Rd at Shenango Rd
- Merchant St at 8th St
- Brodhead Rd at Mulberry Ln
- 434 Franklin Ave
- Liberty Ave at Wood St ("T" Station)
- Duss Ave opp. Keystone Rd
- 4th Ave at 47th St
- Brodhead Rd at Caler St
- Brodhead Rd at Main St
- Beaver Valley Mall (Food Court)
- Ohio River Blvd at Monitor Ave
- Liberty Ave at Smithfield St
- Duss Ave at 14th St
- YMCA Dr at 3rd Ave
- Brodhead Rd opp. Village Shops
- Township Market Place (opp. Texas Roadhouse)
- 438 Delaware Ave
- Chippewa Center (Dunham's)
- East Busway (Stop D)
- Merchant St at 6th St
- Ohio River Blvd at Elizabeth St
- Grant St at Strawberry Way
- Grand Ave at Tyler Ave
- 319 Station St
- Liberty Ave opp. Smithfield St
- Duss Ave at 9th St
- Brodhead Rd at North Branch Rd
- Tyler St at Upland St
- State Ave at Locust St
- 7th Ave at 10th St
- Friendship Circle (East)
- Duss Ave at 23rd St
- Ohio River Blvd opp. Quaker Village Shop Ctr
- 3rd Ave opp. 8th St
- Brodhead Rd at Orchard St
- Mill St at Golf Course Rd
- Tyler St at Waugaman St
- 3rd Ave at 5th St
- Wal-Mart Plaza
- CCBC (Middle Lot)
- 3rd St at Lincoln Ave
- Franklin Ave at Orchard St
- Franklin Ave (Municipal Parking Lot)
- 11th St at Maplewood Ave
- 4th Ave at 45th St
- Liberty Ave at William Penn Pl
- State St at Holmes Ave
- Merchant St at 11th St
- 79 Wagner Rd (opp. HV Rehab)
- Brodhead Rd at Center Grange Rd
- Liberty Ave at Market St
- State Ave at Walnut St
- 427 Frankliin Ave
- 4th Ave opp. 45th St
- 3rd St at Insurance St
- 2230 3rd Ave
- Duss Ave at 19th St
- Duss Ave at 19th St
- 437 Delaware Ave
- Tyler St at Upland St
- State St at Phillip St.
- Chippewa Central Square (Giant Eagle)
- Brighton Ave at Jefferson St
- 3rd Ave at 8th St
- Wagner Road (First Commonwealth Bank)
- Liberty Ave at Gateway Center
- Pennsylvania Ave at 6th St
- 4th Ave at 33rd St
- 3rd St at Buffalo St
- 4th St at Park Rd
- Township Market Place (Pier 1 Imports)
- Liberty Ave at 6th St
- 7th Ave at 13th St
- Ohio River Blvd at Riverview Ave
- State St at Holmes Ave
- 11th St at Church St
- Tyler St at Grand Ave
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 45.0 | first check |
| 2026-07-30 | 45.0 | no change |
| 2026-07-31 | 45.0 | no change |
| 2026-08-01 | 45.0 | 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
11 findings, ordered by severity.
Show every finding
- Error1 instance
Service data ended 1674 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)
- Warning234 instances
234 of 234 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)
- Warning231 instances
231 of 231 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)
- Warning117 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · 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
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_route · 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
feed_info.txt is missing its start/end dates (the file itself is absent)
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 · 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 Not ready
Resolve this before you certify on the D-10. Service data expired 1674 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 1674 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 Ready
- All 231 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. Service data expired 1674 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 1674 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 76 / 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/beaver-county-transit-authority/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.