Feed status · checked 2026-08-23
Norwalk Transit District
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-08-22
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 51 minutes ago; last changed 51 days ago.
Measured 4 of 4 score categories from the feed URL on file (publisher not verified).
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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.
Top things to fix
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
20 of 20 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
⏱ A vendor data-mapping question.worth about +41 points in its category
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
252 of 252 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 +25 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
943 of 943 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
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
- 20 of 20 trips scheduled during the sampling window had no live predictions.
- Next action
- Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
- 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
- 252 of 252 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
- 943 of 943 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
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.
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. · Read the fix guide
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.
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. 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.
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. 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 1351 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
- Fare information is published using GTFS Fares v1.
- Realtime information
- Live-arrival data covered 0% of scheduled trips in the sampled window.
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
The MobilityData validator flagged 5 kinds of issue across 68 instances (0 error, 65 warning, 3 informational).
Service data covers the next 1351 days.
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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 4, 6, 8, 9).
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.
160 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("380 Main Ave S", "Van Zant & Fort Point", "South Main & Monroe", 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.
Sampled 9 times: 3 of 3 configured feeds healthy; 0.0% of scheduled trips had live predictions; vehicle position plausibility was not measurable; predictions ran a median of 0s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 252 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 (yellow)
- 2 (teal)
- 3 (red)
- 4 (red)
- 5 (purple)
- 6 (green)
- 7 (gray)
- 8 (teal)
- 9 (pink)
| Route | Type | Line color |
|---|---|---|
| 1 Route 1: NCC - East Norwalk Station | Bus | yellow |
| 2 Route 2: NCC - Woodward Ave/Dock | Bus | teal |
| 3 Route 3: Wal*Mart - SoNo Station | Bus | red |
| 4 Route 4: Norwalk HS - SoNo Station | Bus | red |
| 5 Route 5: Highland Ave - Burnell Blvd/Wal | Bus | purple |
| 6 Route 6: Ponus Ave - Westport Ave | Bus | green |
| 7 Route 7: Wilton Center - SoNo Station | Bus | gray |
| 8 Coastal Link | Bus | teal |
| 9 Greenwich Shuttle - Central Loop | Bus | pink |
List every stop
- SoNo Station
- T.J Maxx
- 380 Main Ave S
- Nathan Hale S
- 25 Van Zant W
- Van Zant & Fort Point
- South Main & Monroe
- Lowe & MLK S
- Cliff & Soundview
- Soundview & Hadik
- Kohl's
- Highland & Knollwood
- Highland & Charcoal
- Lowe & MLK N
- South Main & Washington
- East & Saint Paul
- Stuart & Grandview
- Ponus & Ellis
- New Canaan & Silvermine
- New Canaan & Bartlett
- Norwalk Hospital
- Ponus & Cornwall
- Calf Pasture Beach
- Maple & Van Buren
- East & Park Hill
- Naramake Elementary N
- Norwalk High N
- Strawberry Hill & Wstpt
- Norwalk High S
- Naramake Elementary S
- White Oaks N
- Target
- Wilton Hills N
- 187 Danbury
- Danbury & Ridgefield
- Old Ridgefield & Godfrey
- Stop & Shop Wilton
- Wolfpit Park & Ride Lot
- Wilton Hills S
- Brien McMahon
- Post & Lois
- Roton Middle School
- Riverview Apartments
- Post & Sherwood
- Post & Buckely E
- Fairfield RR
- Fairfield & Brewster E
- Stew Leonard's OB
- State & Park E
- Stratford & Central E
- Kendall School
- Ponus Ridge School
- Bpt & Naugatuck E
- Bowlero
- Spring Hill & Ponus
- Milford RR E
- Milford Plaza E
- Milford Plaza W
- Milford RR W
- Bpt & Naugatuck W
- Barnum & Veterans W
- Stratford RR W
- Connecticut & Central W
- Wspt & County
- Raymour & Flannigan
- Andrew's Field
- Fairfield & Brestwer W
- Fairfield RR W
- Post & Buckley W
- 50 Danbury / ASML
- Wspt & George W
- 10/20 Westport
- Wilton Town Hall
- Golf Galaxy
- Wilton Center
- Post & Compo
- Dick's Sporting Goods
- Fairfield Circle
- GBT Bus Terminal
- CVS on Conn Ave
- Milford Green E
- Conn Post Mall
- Milford Green W
- Roodner Court
- Conn Ave & Fairfield Ave
- Maple & Van Buren
- Post & Compo W
- Greenwich Station
- Soundview & Fieldpoint
- Greenwich Town Hall
- Fort Point & Putnam
- Lafayette & Putnam
- Greenwich Hospital
- Mason & Amogerone
- Norwalk Community College
- CVS on West Ave
- Main & Broad
- North Main & Ann
- Veterans Park
- 25 Van Zant E
- Marvin Elementary School S
- Wspt & Wolfpit
- Silver Star Diner
- Stuart & Maple
- Wspt & East
- Arch St
- Wspt & George
- Conn Ave & Scribner
- Belden Avenue
- Glover & Grist Mill
- Gateway Shopping
- White Oaks S
- Post & Main
- State & Fairfield E
- Stratford & Surf E
- Stratford & Main E
- Leonard St
- Milford Hospital E
- Oak Knoll Condos
- John & Park W
- Fairfield & State W
- Sherwood Diner W
- Stop & Shop 1
- Merwin St
- East Ave & Gregory Blvd
- St. Thomas Church
- Lowe & MLK
- City Market
- Water & Hanford
- Woodward & Baxter
- Raymond Terrace
- Ely & Testa
- Ely & Duke
- East Avenue
- Ward & Aiken
- Norwalk DMV
- 201/301 Merritt 7
- Stevens & Stuart
- Wall Street
- Route 7 Connector
- Glover & Grist IB
- Main & Burnell
- Ponus & Bartlett
- Dock Shopping Center
- Barnum & Veterans E
- Milford Hospital W
- Stratford & Main W
- East Town Rd
- John St @ Broad St
- St. Thomas Family Services
- 60 Danbury Rd
- Main Ave (Across Walmart)
- Walmart on Main Ave
- Highland & Soundview N
- Monroe & Chestnut
- Chestnut & Henry
- Post & Sylvan Rd S
- Post & Sylvan Rd N
- Post & Lacey E
- Post & Lacey W
- Stop & Shop 2
- Stratford & Surf W
- Moose Home
- Post & Hills Point E
- Post & Crescent
- Fairfield & Albion
- Fairfield & Orland
- State & Iranistan
- Fairfield & Iranistan
- Stratford & Connecticut E
- Burritt & Water
- Stew Leonard's IB
- W Cedar St
- Stratford & Connecticut W
- NHS Maple & Prospect
- N Taylor & Chipping
- N Taylor & Benedict
- Benedict & Glenwood
- East Wall Street & East Avenue
- Roger Square
- Lowe & Cleveland N
- Lowe and Hamilton N
- Morton & Taylor
- Lowe & Hamilton S
- Lowe & Cleveland S
- City Hall S
- Norwalk Housing Authority
- South Main & Hanford
- East Norwalk RR
- The Dock
- Burritt & Woodward
- Lexington Ave
- Lexington & Austin
- Lexington & Hemlock
- Lexington & Knapp
- Taylor & Hillside W
- Ely & Crestline
- Ely Avenue
- Taylor & Hillside E
- Arch St
- Wilson & Grey Rock
- First Student Transit
- South Main & Meadow
- South Main & Novak
- South Main & Grove
- South Main & Merritt
- South Main & Concord
- South Main & Raymond
- South Main & Haviland
- Norwalk Art Space
- Conn Ave & Stuart Ave
- West & Maple
- Main & Cross
- Main & School
- Main & West Main
- Union & Eclipse
- Union Ave Senior Court
- Norwalk Transit Office
- Main & Maplewood
- Diamond Shopping Plaza
- Health Park
- Conn Ave & Clinton Ave
- Briggs High School
- Merritt On the River
- 20 Glover Ave
- North Seven
- Washington & North Main
- West & Butler
- 401/501 Merritt 7
- 801 Merritt 7
- Main Avenue (Across from Briggs High)
- City Hall N
- Watershed Hotel
- CVS on Main Avenue
- Main & Union
- Ward & Main S
- Ward & Thames
- CVS on West Ave
- West & Arch
- 370 West Ave
- West & Garner
- IVE Apartments
- Burnell Blvd Hub
- Stop & Shop
- 99 Washington St
- Merritt 7 RR
- Fort Point & Liberty
- Walmart Shopping Center
- The Marvin
- 101 Merritt 7
- and 2 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — unchanged since 2026-08-22.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-22 | 72.0 | first check |
| 2026-08-23 | 72.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-08-22.
Same feed file as 2026-08-22; 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
- Warning943 instances
943 of 943 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)
- Warning252 instances
252 of 252 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)
- Warning54 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning20 instances
20 of 20 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning9 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 (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · 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)
- Info3 instances
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 1351 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 943 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 1351 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.
Realtime reliability
The realtime feed responded on 100.0% of 115 checks over the last 15 days, with 17s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran right on the schedule, and stayed within 45s nine times in ten. They were on time (about a minute early to five late) 95.7% of the time.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 1351 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 52 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 59 / 100
- 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/norwalk-transit-system-nts-2242/2026-08-23.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-23. 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.