GTFS Scorecard
← All agencies

Feed status · checked 2026-10-07

MetroWest Regional Transit Authority (MWRTA)

Based on the feed source on file; publisher ownership is not verified

Service mode Bus

71.5 / 100

unchanged since 2026-10-06

Cataloged in Massachusetts.

Covers 205 daysAccessibility gapsRealtime not yet published

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.4, validator 8.0.1.

Checked for changes 3 hours ago; last changed 29 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

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 configured feed URL. Publisher ownership of that URL is not verified.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

MetroWest Regional Transit Authority (MWRTA)’s published feed lists 24 bus routes, 1,086 scheduled trips and 125 stops. The published file last changed on 2026-10-06.

Top things to fix

Fix 01

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

125 of 125 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.

Fixing this covers all 125 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

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

1086 of 1086 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers all 1,086 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 03

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.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Massachusetts as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested 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
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.

  1. Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    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.

  2. Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    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.

  3. Fix 03 · Read the fix guide for scorecard_no_fare_data

    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 205 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

Correctness88.0 / 100

The MobilityData validator flagged 3 kinds of issue across 6 instances (0 error, 6 warning, 0 informational).

Freshness85.0 / 100

Service data covers the next 205 days.

Rider experience37.5 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 24 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (RT206, RT306, RT104, RT103, RT203, 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.

  • 38 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Pinewood Dr& Elm St", "Beacon & Fairbanks St", "Arsenal Rd", 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.

Realtime qualityNot yet measured

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 125 stops.

Skip to route and stop data

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.

  • MBCS (red)
  • RT306 (red)
  • RT105 (red)
  • RT305 (red)
  • RT107 (red)
  • RT103 (red)
  • RT304 (red)
  • RT102 (red)
  • RT202 (red)
  • RT201 (red)
  • MWES (red)
  • RT108 (red)
  • RT204 (red)
  • RT302 (red)
  • RT101 (red)
  • NCS (red)
  • RT309 (red)
  • RT207 (red)
  • RT104 (red)
  • MBRS (red)
  • 495C (red)
  • RT301 (red)
  • RT203 (red)
  • RT206 (red)
Routes in MetroWest Regional Transit Authority (MWRTA)'s feed
RouteTypeLine color
MBCS Mass Bay Campus to Campus ShuttleBusred
RT306 Route 306Busred
RT105 Route 105Busred
RT305 Route 305Busred
RT107 Route 107Busred
RT103 Route 103Busred
RT304 Route 304Busred
RT102 Route 102Busred
RT202 Route 202Busred
RT201 Route 201Busred
MWES MathWorks Framingham ShuttleBusred
RT108 Route 108Busred
RT204 Route 204Busred
RT302 Route 302Busred
RT101 Route 101Busred
NCS MathWorks Natick ShuttleBusred
RT309 Route 309Busred
RT207 Route 207Busred
RT104 Route 104Busred
MBRS Mass Bay Riverside ShuttleBusred
495C 495 ConnectorBusred
RT301 Route 301Busred
RT203 Route 203Busred
RT206 Route 206Busred
List every stop
  • Leonard Morse Hospital
  • Maple St / S. Mill St
  • Waverly St. at N 1 Cyclery
  • Birmingham Court
  • Chapel Hill Apartments
  • Natick Common
  • Edmands House
  • Cedar Terrace
  • Wayside Inn Store/ Hager St
  • Ashland Middle School
  • The Green at 9 and 90
  • Target Marlborough
  • Southborough at St Marks
  • Callahan Center
  • Framingham High School
  • McAuliffe Branch Library
  • Framingham MBTA Station
  • Concord St/ Anzio Rd
  • Natick Center MBTA
  • Coolidge Gardens
  • Cedar Gardens
  • Main St at Police Station
  • Union Ave/ Lincoln St.
  • Cross St (Central St/Cross St)
  • Ashland MBTA
  • Campus Drive
  • Downtown Holliston
  • Apex Entertainment
  • Rt 9 East Park & Ride
  • Central St / Cherry St
  • Marlborough Hospital
  • High St & Framingham State
  • Mathworks Lakeside
  • 500 Staples Dr rear Entrance
  • Sherwood Plaza
  • Colonial Rd Capital Rd Housing
  • Framingham Center
  • Babson College
  • Milford Regional Medical Center
  • Maher Court
  • Eagle Rock Apartments
  • Southborough MBTA Station
  • Central St & Route 30
  • Highland Common- Market Basket
  • Newton and Weed St
  • MassBay Wellesley
  • PriceChopper Hopkinton
  • Market Basket
  • Blandin Hub
  • Hannafords Plaza Marlborough
  • 9/27 Shopping Plaza
  • Banana Lot/Intermodal Center
  • Milford Kohls
  • Milford Senior Center
  • Stop and Shop & BJs Wholesale
  • Arsenal Rd
  • Mission Springs
  • New York Ave
  • Rt 9 Park and Ride
  • East Main St Shelter at Beech St
  • Natick Mall - Wegmans
  • Arlington St/Waushakum St
  • Machado House
  • Memorial House (Winthrop & Hollis)
  • Milford Shaws/Wallgreens
  • South Acton MBTA Station
  • Maple St / Walker St
  • Downtown Hudson
  • Hopkinton Center
  • Stop and Shop Temple St
  • Sherwood Village on Mill St.
  • Cirrus Apartments
  • Natick Community Center
  • Forge Park MBTA Station
  • MetroWest Medical Center
  • Buckley Apts/Franklin & Mt. Wayte
  • Shaws Supermarket
  • Babson College (Knight Lot)
  • Water View Village
  • Staples Drive Shelter
  • Bolton St Bus Shelter
  • Spruce St
  • Nobscot Fire Station
  • White Bagley Rd & Boston Rd
  • Milford Crossing
  • Milford Library
  • Homer Ave and Main St
  • Big Y
  • Roche Bros.
  • Kendall Plaza
  • Second St at Rec Center
  • Framingham State University
  • West Natick MBTA on RT 135
  • Kohls
  • Lower Falls (Washington St/Concord St)
  • Oak St
  • Rose Kennedy Lane
  • West Natick MBTA Station
  • Water St & Nicholas Rd
  • Forest and Ames St
  • Farm Road & Route 20
  • Walmart
  • South St & Hayward St
  • Milford Town Hall- Route 14
  • Cloverleaf Mall
  • Kansas St & Route 27
  • Academy Knoll Broad St
  • Hopkinton Center
  • Mathworks Apple Hill RT9
  • Broad St / Lincoln St
  • EMK Community Health
  • Lincoln St & Pleasant St
  • Shoppers World Shelter
  • Main St
  • Normandy Rd
  • Milford High School
  • Market 32
  • Hudson Senior Center
  • Downtown Southborough
  • Milford Target
  • Solomon Pond Mall
  • Woodland MBTA Train Station
  • Bethany Hill
  • Trader Joes Milford
  • Super Stop and Shop
  • 200 Forest St (Hilton)

Over time

Overall score across the last 2 checks — unchanged since 2026-10-06.

2026-10-06: 71.52026-10-07: 71.5
Show the numbers
CheckScoreChange
2026-10-0671.5 first check
2026-10-0771.5 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

CheckedPublished fileService dates throughGrade at the time
2026-10-06 to 2026-10-07 (2 checks)4c5242bfb3c52027-04-30Current rubric: see the trend above
2026-08-06 to 2026-08-07 (2 checks)2289954d19f32026-10-28C, 71.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-01 to 2026-07-10 (9 checks)2289954d19f32026-10-28C, 71.5 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-06-30 (12 checks)e6714044694f2026-07-25F, 56.9 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-10-06.

Same feed file as 2026-10-06; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.

Everything we checked

9 findings, ordered by severity.

Show every finding
  • Warning1086 instances

    1086 of 1086 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference

  • Warning125 instances

    125 of 125 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference

  • Warning4 instances

    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

  • Warning1 instance

    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

  • 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 for missing_recommended_file · See MobilityData GTFS Validator rules

  • 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 for scorecard_missing_feed_info_dates · See MobilityData GTFS Validator rules

  • 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 for scorecard_no_fare_data · See GTFS Best Practices

  • Warning1 instance

    1 of 1086 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.

    When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide for scorecard_missing_headsigns · See GTFS Best Practices

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules

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 205 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 1086 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

One requirement remains for this feed to earn 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 205 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 205 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 85 / 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.

Part of the Massachusetts portfolio: the same scorecards for every feed we track in that group, on one free page.

For programs that support several agencies

This scorecard and the board one-pager for MetroWest Regional Transit Authority (MWRTA) are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.

The report for MetroWest Regional Transit Authority (MWRTA) uses the same numbers as this page: grade C (71.5 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.

One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.

See the program report bundle

See a sample bundle report: a real agency's current grade, with placeholder branding.

A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.

Similar feeds in Massachusetts

Other scorecards in Massachusetts, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

MetroWest Regional Transit Authority (MWRTA): GTFS feed quality grade C, 71.5 of 100, checked 2026-10-07. GTFS 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/metrowest-regional-transit-authority-mwrta/2026-10-07.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-10-07. 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.