Feed status · checked 2026-08-01
Middletown Area Transit (MAT)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Connecticut.
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 73 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
778 of 795 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 +24 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
564 of 564 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
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
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
- 778 of 795 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
- 564 of 564 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
- 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
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.
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. 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.
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 299 days.
- Published accessibility data
- Accessibility information is stated for 2.1% of stops and 0% 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 7 kinds of issue across 114 instances (0 error, 65 warning, 49 informational).
Service data covers the next 299 days.
2% of stops state wheelchair accessibility (2% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
2% of stops state accessibility (2% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (641 B, 641 A, 582, 584-585).
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.
560 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Killingworth Village, Killingworth, CT, USA", "Route 81 & Route 154 Higganum", "Route 81 & Route 154 Higganum", 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 795 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.
- 645 (yellow)
- Clinton Trolley (teal)
- 581 (blue)
- 582 (green)
- 583 (yellow)
- 584 (red)
- 585 (orange)
- 584-585 (gray)
- 590 (black)
- 586 (pink)
- 642 (black)
- 643 (red)
- 644 (purple)
- 640 (orange)
- 581-582 Saybrook Rd/Wesleyan Hills (pink)
- 641 B (green)
- 641 A (green)
| Route | Type | Line color |
|---|---|---|
| 645 Madison - Middletown | Bus | yellow |
| Clinton Trolley | Bus | teal |
| 581 Saybrook Road | Bus | blue |
| 582 Wesleyan Hills | Bus | green |
| 583 Washington Street | Bus | yellow |
| 584 Newfield Street | Bus | red |
| 585 Westlake Drive | Bus | orange |
| 584-585 Newfield/Westlake | Bus | gray |
| 590 Meriden - Middletown Flyer | Bus | black |
| 586 Portland/East Hampton | Bus | pink |
| 642 Old Saybrook - Chester | Bus | black |
| 643 Old Saybrook - New London | Bus | red |
| 644 Old Saybrook - Middletown | Bus | purple |
| 640 Old Saybrook Loop | Bus | orange |
| 581-582 Saybrook Rd/Wesleyan Hills | Bus | pink |
| 641 B Old Saybrook - Madison | Bus | green |
| 641 A Old Saybrook - Madison | Bus | green |
List every stop
- Killingworth Village, Killingworth, CT, USA
- Route 81 & Route 154 Higganum
- Route 81 & Route 154 Higganum
- Route 81 & Route 80, Killingworth
- Route 81 & Killingworth Village
- Route 81 & Route 154 Higganum
- Route 81 & Lake Ave, Higganum
- Route 81 & Skinner Rd, Higganum
- 415 Killingworth Rd, Haddam, CT, USA
- Route 81 & Little City Rd, Higganum
- Route 81 & Soobitsky Rd, Higganum
- Route 81 & Ivy Rd, Higganum
- Route 81 & Woods Rd, Higganum
- Route 81 & Burr Rd, Higganum
- Route 81 & Brault Hill Rd, Higganum
- Route 81 & Hidden Lake Rd, Higganum
- Route 81 & N Parker Hill, Killingworth
- Route 81 & Route 148, Killingworth
- Route 81 & HK Middle School, Killingworth
- Route 81 & Lovers Ln, Killingworth
- Route 81 & Beechwood Rd, Killingworth
- Route 81 & Killingworth Town Hall
- Route 81 & Killingworth Library
- Route 81 & Hemlock Dr, Killingworth
- Route 81 & Chittenden Rd, Killingworth
- Route 81 & Stevens Rd, Killingworth
- Route 81 & Sherwood Forest, Killingworth
- Route 81 & Roast Meat Hill, Clinton
- Route 81 & Silver Birch Ln, Clinton
- Route 81 & Hemlock Hill Rd, Clinton
- Route 81 & Evergreen, Clinton
- Route 81 & Egypt Ln, Clinton
- Route 81 & Rock Ledge, Clinton
- Route 81 & Margo Ln, Clinton
- Route 81 & Woodland Dr, Clinton
- Route 81 & Walnut Hill Rd, Clinton
- Route 81 & Walnut Hill Rd, Clinton
- Route 81 & Morgan High School, Clinton
- Route 81 & Hurd Bridge Rd, Clinton
- Route 81 & Indian River Rec Complex, Clinton
- Route 81 & Evergreen, Clinton
- Route 81 & Hemlock Hill Rd, Clinton
- Route 81 & Silver Birch Ln, Clinton
- Route 81 & Roast Meat Hill, Clinton
- Route 81 & Sherwood Forest, Killingworth
- Route 81 & Stevens Rd, Killingworth
- Route 81 & Chittenden Rd, Killingworth
- Route 81 & Route 80, Killingworth
- Route 81 & Hemlock Dr, Killingworth
- Route 81 & Killingworth Library, Killingworth
- Route 81 & Killingworth Town Hall
- Route 81 & Beechwood Dr
- Route 81 & Lovers Ln, Killingworth
- Route 81 & HK Middle School
- Route 81 & Route 148, Killingworth
- Route 81 & N Parker Hill Rd, Killingworth
- Route 81 & Old Country Rd, Higganum
- Route 81 & Parker Hill Rd, Higganum
- Route 81 & Barman Rd, Higganum
- Route 81 & Soobitsky Rd, Higganum
- Route 81 & Ponsett Rd, Higganum
- 415 Killingworth Rd, Higganum
- Route 81 & Morris Hubbard Rd, Higganum
- Route 81 & Lake Rd, Higganum
- Route 81 & Route 154, Higganum
- E Main St & Downtown Clinton (Clinton Arts District)
- 288 Flanders Rd, East Lyme, CT, USA
- Clinton Town Docks
- Pilot's Point Marina
- Lobster Landing
- Hammonasset Beach
- Madison Park and Ride
- Stop & Shop Commons
- Route 1 & Pearl Street
- Blue & Wesleyan Hills
- Randolph & Highland
- Washington Plaza
- Smith & Middle St
- Meriden RailRoad Station
- William & High Street
- Westlake Dr & Trolley Crossing
- Washington & High St
- Daddario Rd / Cubeta Rd
- Greystone Manor
- Portland Convalescent
- Price Rite
- Wal-Mart
- FedEx
- Westlake Dr & East St
- Berlin & Willowbrook
- Newfield / Washington Streets
- Middletown High Bus Stop Inbound
- Cromwell Square Plaza
- Newfield & Tuttle Outbound
- Middletown High Bus Stop Outbound
- Newfield Towers
- High / Grand Street
- North Main Street
- Pearl Street
- Price Chopper
- Sagamore Hills
- West & Wadsworth
- Wesleyan University
- Sbona Towers
- Metro Square
- Long Hill & Blue
- Marino Manner
- Main & Pleasant
- CVH / Silver St
- 534 Saybrook Road Medical Center
- Saybrook Rd / Reservoir Rd
- Middlesex Community College
- Summer Hill Road & Woodbury Circle
- Stop & Shop Middletown
- Middlesex Hospital
- Downtown Terminal
- Main Street Market
- Main & Ferry
- Main & Rapallo
- N Main & Free CTR
- N Main & Pease Ave
- N Main & High St
- High & Stack St
- High & Spring Street
- Grand & Prospect
- Liberty & Berlin
- Charton Terrace
- Stonycrest Towers
- Newfield & Condon St
- Newfield & Mile Lane
- Ghezzi's
- Dunkin Donuts
- Mcdonalds
- Newfield & Tuttle Rd
- Newfield & Mile ln Inbound
- Newfield & Stonycrest Dr Inbound
- Newfield Towers Inbound
- Washington & Veterans Way
- Washington & Broad
- Westlake Drive & Russett Ln
- Westlake Drive & Rising Trail Dr
- Westlake Drive & Northwoods Ln
- Westlake Drive & Town Ridge
- West Lake Drive & Carriage Crossing
- Westlake Drive & Carriage Crossing Ln
- Westlake Drive & Smith St
- Smith & Industrial Park Rd
- Middle & Timber Ridge Rd
- Main & Mill St
- West St & Cromwell Hills Dr
- Main St Extension & Cooley Ave
- Main St Extension & Mill St
- Summerhill Apartments Stop 2
- 400 Saybrook Rd
- Standpipe Rd & Bow Ln
- Saybrook Road @ Stop & Shop
- Silver & Wall
- Dekoven & Union
- Middletown Plaza @ Washington Street
- Pratt & Miller
- Pratt & Center
- Camp & Broad
- E Main & Pratt
- Main & College
- South Main & Church
- South Main & Loveland
- South Main & Glynn
- South Main & Warwick
- South Main & Pameacha
- South Main & Ward Street
- Randolph & South Main
- Cubeta & Kieft
- Long Hill & Yellow
- Long Hill & Long Hill
- DSS / DCF
- South Main & Highland
- High & Freestone
- High & Marlborough
- Adams Market
- Solano Inn
- W High Cobalt Center
- Portland-Cobalt & Gospel
- High & Church
- Cross St Freeman Athletic Center
- Cross & Long
- West & Aresco
- West & Rogers
- George & Washington
- Washington & West
- East Main & Baer
- Silver & Elm
- Cubeta & Daddario
- South Main & Ward
- South Main & Crescent inbound
- Dekoven Dr & MLK
- Main & Marlborough
- Community Health Center
- Main & Liberty
- Russell Library
- Wesleyan University
- William & Broad
- Main St Ext & W Silver St
- Silver St & McKenzie St
- Silver St & Mullaney Way
- Silver St & Flood Dr
- Middlesex Health Care Center
- Cafferys Plaza
- Best Cleaners
- U-haul
- Bestway Inn
- CVS
- Middle St & Bysiewicz Dr
- Middle St & Winsupply
- Randolph Rd & Farm Hill
- Randolph Rd & E Ridge Rd
- Pine Street & Randolph Road, Middletown, CT, USA
- Clinton Train Station
- Hammonassett Campgrounds
- Clinton Train Station Central Ave
- Hammonasset Camp Ground
- Madison Center -Wall Street
- Portland Quick Mart
- Rt 66 & Gospel Ln Portland
- Hammonasset Beach Campground
- Chester Donovan Park
- Amazing Grace Food Pantry
- Grand & Pearl Street
- Community Heath Center @ Grand Street
- Prospect & Liberty Street
- Grand Street & Woodward Ave
- Grand & High Street
- High & Spring Street Northbound
- Opp Lowe's
- River Grace Plaza
- West Street & Berlin Road
- Stop & Shop @ West Street
- Wesleyan LoRise Housing
- Traverse Square
- East Lyme Commons
- Flanders & Boston Post Road
- Brooks Plaza
- Connecticut Valley Hospital
- Silver & Allison Street
- Silver & Walnut Street
- Middletown Post Office
- CVS @ East Main Street
- The Village at South Farms
- Tradewinds Plaza
- CVS @ Main Street Extension
- Sanseer Mill
- and 545 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 | 77.9 | first check |
| 2026-07-30 | 77.9 | no change |
| 2026-07-31 | 77.9 | no change |
| 2026-08-01 | 77.9 | 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
10 findings, ordered by severity.
Show every finding
- Warning778 instances
778 of 795 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)
- Warning564 instances
564 of 564 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)
- Warning36 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)
- Warning27 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: 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. (Varies.)
Finding code: same_name_and_description_for_stop · 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)
- Info7 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 299 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 564 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 2% 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 299 days.
- Accessible Not yet
- States wheelchair access on 2% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 36 of 795 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 299 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 78 / 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 100 / 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 60 / 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/middletown-area-transit-mat/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.