Feed status · checked 2026-08-01
Berkshire Regional Transit Authority (BRTA)
Based on the feed this agency publishes
Service mode Bus
down 0.4 since 2026-07-31
Catalogued in Massachusetts.
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 41 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
194 of 208 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 +23 points in its category
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no bus is scheduled to arrive.
⏱ A review pass in your scheduling software.worth about +6 points in its category
Remove past service periods the next time you export the feed.Likely your export tool
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.
⏱ One setting in most export tools.worth about +4 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- 194 of 208 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
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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
- Some service calendars in the feed have already ended.
- Next action
- Remove past service periods the next time you export the feed.
- 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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Remove retired stops from the export, or add them back to the trips that should serve them. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Remove past service periods the next time you export the feed. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 31 days.
- Published accessibility data
- Accessibility information is stated for 6.7% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 85 instances (0 error, 39 warning, 46 informational).
Service data covers the next 31 days.
7% of stops state wheelchair accessibility (7% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
7% of stops state accessibility (7% 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 (921, 5A).
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.
91 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Tyler St @ Courtland Pl", "North Adams Stop & Shop", "BMC Wahconah St", 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.
Fares are applied to trips.
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 208 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 (blue)
- 11 (yellow)
- 12 (yellow)
- 14 (purple)
- 15 (brown)
- 2 (red)
- 21 (green)
- 3 (purple)
- 34 (yellow)
- 4 (purple)
- 5A (red)
- 5B (red)
- 901 (green)
- 903 (green)
- 904 (green)
- 921 (teal)
| Route | Type | Line color |
|---|---|---|
| 1 Pittsfield, North Adams | Bus | blue |
| 11 Berkshire Community College | Bus | yellow |
| 12 Pittsfield Southeast Loop | Bus | yellow |
| 14 Pittsfield Southeast Loop | Bus | purple |
| 15 West Pittsfield, Lebanon Ave | Bus | brown |
| 2 Pittsfield, Lee | Bus | red |
| 21 Lee, Great Barrington | Bus | green |
| 3 North Adams, Williamstown | Bus | purple |
| 34 North Adams Loop | Bus | yellow |
| 4 Pittsfield, Dalton, Hinsdale | Bus | purple |
| 5A Pittsfield, Lanesborough | Bus | red |
| 5B Pittsfield, Lanesborough | Bus | red |
| 901 Pittsfield / North Adams | Bus | green |
| 903 North Adams / Greenfield | Bus | green |
| 904 Pittsfield / Northampton | Bus | green |
| 921 Express Pittsfield/Great Barrington | Bus | teal |
List every stop
- Massachusetts College of Liberal Arts (MCLA)
- Big Y
- Rite Aid Adams S
- Rite Aid Adams N
- Goodwill Pittsfield Tyler
- Tyler St @ Courtland Pl
- Lee Mobil Station
- Lenoxdale Post Office
- Lenoxdale Post Office
- Big Y Lee
- North Adams Stop & Shop
- BMC Wahconah St
- Housatonic South
- Flagrock
- Flagrock
- Blue Hill Rd
- Blue Hill Rd
- Great Barrington Cemetary
- Great Barrington Fire Department
- Railroad St South
- Railroad St North
- BCC Great Barrington
- People's Pantry
- CVS Great Barrington
- Great Barrington West Ave
- Great Barrington West Ave
- West & Maple Great Barrington
- Beachtree Commons South
- Beachtree Commons North
- Brookside Great Barrington
- Fairview Hospital
- Lanesborough Post Office
- West Street and Salisbury Court
- West Street and Sherwood Drive
- BCC Paterson Field House (in)
- Crane Ave (in)
- 510 North St (Out)
- East St and E Center St (in)
- St. Joseph's Church (out)
- Cumberland Farms
- Lanesborough Mobil Station
- East & Elm (Fenn)
- MCLA on Ashland St (in)
- Big Y Market Pittsfield (in)
- Crane Ave (out)
- Allendale Plaza on Cheshire Rd (out)
- North St and Linden St (in)
- Cumberland Farms
- Williams College at Hopkins Hall
- Williamstown Rotary
- Williamstown Hist. Museum
- Meadowvale Apartments
- Highland Ave and Pecks Rd
- Linden St and Dewey Ave (Inbound)
- Wayfair at Clocktower
- East St and Frederico Drive
- 703 W Housatonic
- Simon's Rock
- Tyler St & Plunkett St
- Tyler St & Plunkett St
- Pecks Rd and Valentine Rd
- Linden St and Dewey Ave (Outbound)
- West Street and Onota Street
- Dalton Ave & Connecticut Ave
- Dalton Ave & Thorndyke Ave
- Greylock Valley Apartments
- Greylock Valley Apartments
- Park Ave & High St
- Park Ave & High St
- Callahan Drive
- Clapp Park
- Clapp Park
- MoCA
- North St & Cromwell Ave
- North St & Cromwell Ave
- East St. and Newell St. (Outbound)
- BCC Temporary Stop #1
- BCC Temporary Stop #2
- BCC Temporary Stop #3
- Walmart North Adams (in front of Garden Center)
- Berkshire Medical Center (Charles St)
- Maplewood Ave
- Maplewood Ave (in)
- Rose Manor Apartments (Elberon Ave)
- American Legion Drive near Whitneys Beverage Shop
- Pittsfield ITC
- Columbia St / Valley St (S)
- Ashfield Center (E)
- Savoy Center (E)
- Plainfield Center (E)
- Charlemont Park & Ride
- JWO Transit Center Greenfield
- Ashfield Center (W)
- Plainfield Center (W)
- Savoy Center (W)
- Columbia St / Valley St (N)
- Dalton Center (E)
- Windsor Center (E)
- Cummington Center (E)
- Goshen Center
- Williamsburg Center (E)
- Academy of Music
- Northampton Amtrak
- Main St / Court House (W)
- Main St / Masonic St (W)
- Williamsburg Center (W)
- Cummington Center (W)
- Windsor Center (W)
- Dalton Center (W)
- Adams Center (E)
- Allendale Plaza – DCR Rail Trail
- Dalton Division Rd. and April Lane
- Barrington Plaza
- Berkshire Community College (BCC)
- Pittsfield Walmart
- Berkshire Mall (North Mall Entrance)
- Berkshire Medical Center
- Center St. (Adams)
- Cheshire Post Office
- Curtis Ave. and Main St., Dalton
- Dalton Division Rd. and Hubbard Ave.
- Downing Industrial Park
- East St. and Center St.
- East St. and Elm St.
- East St. and Newell St. (Inbound)
- Elm St. and Holmes Rd.
- Fairgrounds Plaza
- Fairview Hospital
- Glendale Post Office
- Hillcrest Campus (Berkshire Medical Center)
- Hinsdale Post Office
- Housatonic (Front St. and Depot St.)
- Intermodal Center
- Lakeway Dr. and Valentine Rd.
- Lanesborough Post Office
- Lebanon Ave and Housatonic St.
- Lee Center (Main St. and Park. St.)
- Lenox
- Lenox (Walker St. at Rt. 7)
- Lenoxdale (Crystal St. and Mill St.)
- North Adams Center
- Merrill Rd. at Stop & Shop
- Mohawk Forest
- Newell St. and Elm St.
- Berkshire Medical North Adams
- North St. and Tyler St. (Berkshire Medical Center)
- Onota St. and Linden St.
- Park Square
- Pittsfield Plaza
- Plastics Ave. at General Electric
- Lanesborough Police Department
- Price Chopper
- Lee Premium Outlets
- Proprietors Fields
- Great Barrington Library
- Rose Manor
- Rt. 8 at Farnams Rd. (Cheshire Hills)
- Claire Teague Senior Center
- Berkshire Innovation Center
- Stockbridge Center (Main St.)
- North Adams Stop & Shop
- Stop and Shop Dan Fox Dr
- Tyler St. and Woodlawn Ave.
- Wahconah St. at Pecks Rd.
- North Adams Walmart
- West St. and Valentine Rd.
- Williams St. and Dalton Division Rd. (Burgner's)
- William Street Plaza
- Williams Inn
- Ocean State Job Lot (Curran Highway)
- The Clark
- Park St. (at Paresky Center)
- Brayton Hill Elementary
- Route 2 at Phelps Ave.
- Route 2 at Wild Oats Market
- North St. and Wahconah St. (Berkshire Medical Center)
- Tyler St. and Woodlawn Ave.
- Plastics Ave. at General Electric
- Panera Bread Plaza on Merrill Rd
- Rt. 8 at Farnams Rd. (Cheshire Hills)
- Elm St. and Holmes Rd.
- East St. and Elm St.
- Williams St. and Dalton Division Rd. (Burgner's)
- Dalton Division Rd. and April Lane
- Dalton Division Rd. and Hubbard Ave.
- Lenoxdale (Crystal St. and Mill St.)
- Lenox
- East St. and Center St.
- Lee Center (Main St. and Park. St.)
- Stockbridge Center (Main St.)
- Glendale Post Office
- Housatonic (Front St. and Depot St.)
- Rite Aid (Main St. and Rosseter St.)
- Proprietors Fields
- West St. and Valentine Rd.
- Onota St. and Linden St.
- Lakeway Dr. and Valentine Rd.
- Hancock Rd. and Route 7 (Main St.)
- Wahconah St. at Pecks Rd.
- Route 2 at Phelps Ave.
- Route 2 at Wild Oats Market
- Center St. (Adams)
- Cheshire Post Office
- Park St. (at Paresky Center)
- Curtis Ave. and Main St., Dalton
- The Clark
- William Street Plaza
- Pittsfield Plaza
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 78.3 | first check |
| 2026-07-30 | 76.2 | down 2.1 |
| 2026-07-31 | 75.8 | down 0.4 |
| 2026-08-01 | 75.4 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points 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
7 findings, ordered by severity.
Show every finding
- Warning194 instances
194 of 208 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)
- Warning37 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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 describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info4 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 31 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 538 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 7% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 31 days.
- Accessible Not yet
- States wheelchair access on 7% of stops and 100% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 37 of 208 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 31 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 88 / 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 52 / 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 77 / 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/berkshire-regional-transit-authority-brta/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.