GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-23

Massachusetts Bay Transportation Authority (MBTA)

Grade F · 59.4 / 100

Down 0.3 points since 2026-08-22 (F to F).

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

  • Correctness no change
  • Freshness down 1.6
  • Rider experience no change
  • Realtime quality no change

Top three things to fix

  1. Re-export with a validity window that reaches at least 60 days out.

    Service data runs out in 13 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

    Effort: One export setting.

  2. Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Same name and description for stop (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

  3. Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Route short name too long (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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 runs out in 13 day(s).
Next action
Re-export with a validity window that reaches at least 60 days out.
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

Ready to send to the agency

Hi Massachusetts Bay Transportation Authority (MBTA) team, Service data runs out in 13 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/massachusetts-bay-transportation-authority-mbta/

Copy this note from the full scorecard.

NTD GTFS readiness: Needs attention

This feed is close to NTD-ready. Service data runs out in 13 days; renew before you certify.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Needs attention
Service data runs out in 13 days; renew before you certify.
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 NTD ID (optional): Different (allowed). Your feed's agency_id is 3, 1; your National Transit Database ID is 10003. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 3, 1 to NTD ID 10003, and keep the feed value stable. Do not change it solely to make the two values equal.

Key facts

Feed URL
https://cdn.mbta.com/MBTA_GTFS.zip
Last checked
2026-08-23
Service window
13 days of service data remain. Last service date 2026-09-05.
Feed version
Summer 2026, 2026-08-19T21:11:39+00:00, version D
Location
Massachusetts

Part of the Massachusetts portfolio: see where this agency sits among the state's feeds before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.