Feed status · checked 2026-11-21
Middletown Area Transit (MAT)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-11-20
Cataloged in Connecticut.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://data.trilliumtransit.com/gtfs/ninetown-connecticut-us/ninetown-connecticut-us.zip
Watch this feed for free: we email you before it expires or when its grade drops.
Heads-up: Days until the service window ends dropped by 27 between 2026-11-13 and 2026-11-14, but only 1 day(s) passed. The feed's calendar appears to have moved backward, which can happen when an older export is republished. Worth confirming the latest export is the one being served. (checked 2026-11-14). This can be a brief vendor export glitch; watch the next update before acting.
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
825 of 842 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 825 of 842 stops, about 98% of them.
⏱ 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
906 of 906 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 906 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Often a bulk fix in your scheduling software.worth about +8 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.
- Connecticut 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-11-02.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- 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
- Finding
- Fix 02 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
- Finding
- Fix 03 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.
Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for mixed_case_recommended_field
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. See this feed's finding-clearance log.
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 374 days.
- Published accessibility data
- Accessibility information is stated for 2% 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.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
Middletown Area Transit (MAT)’s published feed lists 17 bus routes, 906 scheduled trips and 842 stops. Its service dates run from 2026-11-18 through 2027-11-30. The published file last changed on 2026-11-19.
Score by category
The MobilityData validator flagged 8 kinds of issue across 162 instances (0 error, 113 warning, 49 informational).
Service data covers the next 374 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.
460 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 842 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)
- 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 (no shape in feed) |
| 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
- Berlin & Willowbrook
- Marino Manner Outbound
- Stop & Shop Middletown - Installed
- Downtown Terminal
- Main Street Market
- Middletown Plaza @ Washington Street
- Camp & Broad
- Main & College
- DSS / DCF
- Hammonassett Campgrounds
- Hammonasset Camp Ground
- Madison Center -Wall Street
- Hammonasset Beach Campground
- Chester Donovan Park
- East Lyme Commons
- Flanders & Boston Post Road
- Brooks Plaza
- Silver & Walnut St
- 201 West High Street Plaza
- Shoprite Clinton Eastbound
- Shoprite @ Route 1 & Meadow Road
- Stop & Shop & Dunkin
- Walgreens & Stop & Shop Clinton
- High & William Street
- Stop & Shop Cromwell Inbound
- Marino Manor Inbound
- 123 Elm Street Plaza
- Research Parkway South
- Research Parkway Center
- Research Parkway & Mill Rock Road
- Mystic Market
- Main Street & Maple Ave Outbound
- Maple & Soundview Ave
- Maple Ave & Cricket Ct
- Maple Ave & Otis Street
- Maple Ave & George Drive
- Maple Ave & Summerfield Road
- Knollwood Beach South
- Knollwood Beach North
- Fenwick Private Beach
- Maple & Wilson Ave
- Fenwick Golf Club
- Harbor One Marina
- Saybrook Point Resort & Marina
- Fort Saybrook Monument Park
- College Street & North Cove Road
- Soundview Bus Shelter
- Ridge & Randolph Road - Installed
- Melilli Plaza Parking Lot
- Arcade Lot
- Middlesex Corporate Parking Garage
- Middletown Police Department
- Woodrow Wilson Apartments
- Big Y Middletown Outbound
- Big Y Middletown Inbound
- Kirtland Commons @ Spring St
- Spring St & Spring Hill
- Union & Spring St
- Silgan Plastics
- Bridge & Main St
- Big Y Clinton
- Clinton Crossing Mall @ Route 81
- FedEx @ Middle St
- Main & William St
- DeKoven Dr & Dr. MLK Jr Way
- Union Green @ Main St
- YMCA Middletown @ Union St
- Beit Paley Center
- Main St Ext & Crescent St
- Hubbard Park
- Main St Ext & Cooley Ave Outbound
- Main St Ext & Cooley Ave Inbound
- Main & West Silver St
- Silver & Elm St
- Middletown Post Office
- Silver & Wall St
- Silver St & Frissell Ter
- Silver & Allison St
- Silver St & Holmes Dr
- The Connection @ Silver St
- CT Juvenile Training School
- CVS @ East Main St
- CVS @ Main St Ext
- East Main & Baer St
- Stop & Shop Middletown Inbound
- Children's Neurology Services
- Bow Ln & Opp Dennison Rd
- Bow Ln & Dennison Rd
- Standpipe & Bow Ln Inbound
- Standpipe & Bow Ln Outbound
- 400 Saybrook Rd Medical Center Inbound
- 400 Saybrook Road Medical Center Outbound
- Middlesex Orthopedic and Spine
- 530 Saybrook Rd Medical Complex
- 534 Saybrook Medical Complex @ Saybrook Rd
- 535 Saybrook Road Plaza
- Saybrook Rd & Windy Hill Dr
- Benchmark @ South Farms
- Tradewinds Plaza
- Saybrook & Randolph Rd
- Forge Outbound
- Summerhill Apartments @ Woodbury Cir
- Summerhill Apartments @ Bartholomew Rd
- Bartholomew Rd Northbound
- CT State Middlesex
- Reservoir & Bartholomew Rd
- Middlesex Hospital @ South Main St
- Opp Middlesex Hospital @ South Main St
- South Main & Glynn Ave
- South Main & Cottage St
- Opp Wilcox Apartments
- Wilcox Apartments
- Dominos Middletown
- Opp Dominos
- Senior Center @ Durant St
- Huntinghill & Francis Ave
- Woodrow Wilson Apartments
- Opp South Main & Ward
- South Main & Ward St
- South Main Street Plaza
- Opp South Main Street Plaza
- Charton Place Apartments
- Opp Charton Place Apartments
- Apple Rehab Middletown
- Randolph Rd & Highland Ave
- Randolph & Farm Hill Rd
- Grace Covenant Church
- Clover & Lewis St
- Randolph Rd & Guarino Dr
- Randolph Rd & Jack English Dr
- Randolph & Long Hill Rd
- Mercy Highschool Inbound
- Mercy Highschool Outbound
- Laurel Grove Rd & Red Bud St Outbound
- Laurel Grove Rd & Red Bud St Inbound
- Vinal Highschool Inbound
- Vinal Highschool Outbound
- Long Hill & Yellow Rd Outbound
- Long Hill & Yellow Rd Inbound
- Ridgely 2 @ Long Hill Rd Outbound
- Ridgely 2 @ Long Hill Rd Inbound
- Ridgely 1 @ Long Hill Rd Outbound
- Ridgely 1 @ Long Hill Rd Inbound
- Blue & Blue Meadow Rd Inbound
- Blue & Blue Meadow Rd Outbound
- Blue Rd & Blue Bell Ln Outbound
- Blue Rd & Blue Bell Ln Inbound
- Wesleyan Hill & Blue Rd Outbound
- Wesleyan Hills & Blue Rd Inbound
- South Main St & Trigo Dr
- South Main St & Round Hill Rd
- Traverse Square Apartments
- Russell Library @ Court St
- Court Street Apartments
- Washington & Pearl St
- Usdan Campus Center
- Center for Film Studies
- High & William St Southbound
- Olin Library
- Excely Science Center @ Chruch St
- Fauver Apartments Outbound
- Fauver Apartments Inbound
- Freeman Athletic Center Inbound
- Freeman Athletic Center Outbound
- Wesleyan Practice Fields @ Cross St
- Long Ln & Fairview Ave
- Smith Field Inbound
- Smith Field Outbound
- Long Lane Farm Outbound
- Long Lane Farm Inbound
- Santangelo Circle @ long Ln
- Long Ln & Clarence Ct
- Cubeta & Daddario Rd
- Snow School Outbound
- Snow School Inbound
- Zion Church Outbound
- and 592 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 13 checks — unchanged since 2026-11-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-11-09 | 59.0 | first check |
| 2026-11-10 | 58.6 | down 0.4 |
| 2026-11-11 | 74.5 | up 15.9 |
| 2026-11-12 | 74.5 | no change |
| 2026-11-13 | 74.5 | no change |
| 2026-11-14 | 74.5 | no change |
| 2026-11-15 | 74.5 | no change |
| 2026-11-16 | 74.5 | no change |
| 2026-11-17 | 74.5 | no change |
| 2026-11-18 | 74.5 | no change |
| 2026-11-19 | 76.0 | up 1.5 |
| 2026-11-20 | 76.0 | no change |
| 2026-11-21 | 76.0 | 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.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-19 to 2026-11-21 (3 checks) | 7fce26817c67 | 2027-11-30 | Current rubric: see the trend above |
| 2026-11-14 to 2026-11-18 (5 checks) | 2b660f9a28d3 | 2027-11-04 | Current rubric: see the trend above |
| 2026-11-11 to 2026-11-13 (3 checks) | d4fbfb5fa822 | 2027-11-30 | Current rubric: see the trend above |
| 2026-11-09 to 2026-11-10 (2 checks) | ca7401343dc5 | 2026-11-30 | Current rubric: see the trend above |
| 2026-10-26 to 2026-11-06 (12 checks) | 8afcb6489f8f | 2027-05-27 | C, 77.8 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-10-02 to 2026-10-25 (24 checks) | b339237ffe8b | 2026-10-01 | F, 51.3 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-18 to 2026-10-01 (14 checks) | b339237ffe8b | 2026-10-01 | F, 51.3 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-09-01 to 2026-09-13 (13 checks) | 713d0c0902a5 | 2027-03-27 | C, 77.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-08-05 to 2026-08-31 (27 checks) | ce8803c45010 | 2027-05-27 | C, 77.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-08-04 | 775fa9c360fa | 2026-08-10 | F, 53.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-08-03 (10 checks) | 291e8977fb00 | 2027-05-27 | C, 77.9 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-14 to 2026-07-24 (8 checks) | 291e8977fb00 | 2027-05-27 | C, 77.7 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
Showing the 12 most recent of 13 periods.
What changed over time
On 2026-11-09 this feed started at grade F. On 2026-11-11 the grade moved from F to C. As of 2026-11-21 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-11-11 Grade went F to C, freshness rose 67 points.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Warning906 instances
906 of 906 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 (opens the GTFS Schedule reference on an external site)
- Warning825 instances
825 of 842 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 (opens the GTFS Schedule reference on an external site)
- Warning79 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning26 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 for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning7 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide for stop_too_far_from_shape_using_user_distance · 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 for route_color_contrast · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed offers flexible service that riders book ahead, but it has no booking_rules.txt.
Riders can see the service area but not how or when to book a trip. Without that, they can't 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 for scorecard_flex_no_booking_rules · 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 for unknown_column · 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 for unknown_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info6 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 for service_window_outside_feed_period · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide for big_gap_in_service · 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).
How we measured this
Checked for changes 18 hours ago; last changed 2 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.
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.5, validator 8.0.1.
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 374 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 906 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 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 374 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.
- 26 of 842 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 373 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 73 / 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.
Part of the Connecticut portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in Connecticut
Other scorecards in Connecticut, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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-11-21.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-11-21. 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.