Feed status · checked 2026-10-07
Metro-North Railroad
Based on the feed source on file; publisher ownership is not verified
Service mode Rail
unchanged since 2026-10-06
Cataloged in New York.
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 32 minutes ago; last changed 3 hours 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 6 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.
About this feed
Metro-North Railroad’s published feed lists 6 rail routes, 35,990 scheduled trips and 114 stops. It publishes realtime trip updates and service alerts; when we checked, all of them answered. The published file last changed on 2026-10-07.
Top things to fix
Review the rule documentation for 'transfer_with_invalid_trip_and_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Transfer with invalid trip and stop (flagged by the MobilityData validator). See the linked rule for what this affects.
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.
⏱ Varies.worth about +12 points in its category
Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out.
38 of 38 trips scheduled during the sampling window had no live predictions. Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.
This was measured over a realtime sampling window, so it has no feed-wide share.
⏱ A vendor data-mapping question.worth about +41 points in its category
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
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.
This one is about the feed as a whole, so there is no share of it to count.
⏱ Two fields, set once in export settings.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.
- New York as a whole measures moderate 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
- 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.
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. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_rt_trip_coverage
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. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for scorecard_missing_feed_info_dates
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. 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 228 days.
- Published accessibility data
- Accessibility information is stated for 98.2% of stops and 59.3% 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
- 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 6 kinds of issue across 28 instances (1 error, 23 warning, 4 informational).
Service data covers the next 228 days.
98% of stops state wheelchair accessibility (82% marked accessible, 16% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
98% of stops state accessibility (82% 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 (New Haven, New Canaan, Danbury, Waterbury, Hudson).
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.
3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Harlem-125 St", "Yankees-E 153 St", "New Haven-State St").
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.
Sampled 6 times: 2 of 2 configured feeds healthy; 0.0% of scheduled trips had live predictions; predictions ran a median of 60s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 114 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.
- Hudson (green)
- Harlem (blue)
- New Haven (red)
- New Canaan (red)
- Danbury (red)
- Waterbury (red)
| Route | Type | Line color |
|---|---|---|
| Hudson | Rail | green |
| Harlem | Rail | blue |
| New Haven | Rail | red |
| New Canaan | Rail | red |
| Danbury | Rail | red |
| Waterbury | Rail | red |
List every stop
- Grand Central
- University Heights
- Harlem Valley-Wingdale
- Dover Plains
- Mt Vernon East
- Pelham
- New Rochelle
- Marble Hill
- Larchmont
- Mamaroneck
- Harrison
- Rye
- Port Chester
- Greenwich
- Cos Cob
- Riverside
- Old Greenwich
- Stamford
- Noroton Heights
- Darien
- Rowayton
- South Norwalk
- East Norwalk
- Westport
- Green's Farms
- Southport
- Fairfield
- Spuyten Duyvil
- Bridgeport
- Stratford
- Milford
- New Haven
- New Haven-State St
- Glenbrook
- Springdale
- Talmadge Hill
- New Canaan
- Merritt 7
- Riverdale
- Wilton
- Cannondale
- Branchville
- Redding
- Bethel
- Danbury
- Derby-Shelton
- Ansonia
- Seymour
- Ludlow
- Beacon Falls
- Naugatuck
- Waterbury
- Tenmile River
- Wassaic
- Yonkers
- Highbridge Yard
- Fairfield-Black Rock
- Glenwood
- West Haven
- Greystone
- Hastings-on-Hudson
- Dobbs Ferry
- Ardsley-on-Hudson
- Irvington
- Tarrytown
- Philipse Manor
- Scarborough
- Ossining
- Croton-Harmon
- Cortlandt
- Peekskill
- Harlem-125 St
- Manitou
- Garrison
- Cold Spring
- Breakneck Ridge
- Beacon
- New Hamburg
- Poughkeepsie
- Melrose
- Tremont
- Fordham
- Botanical Garden
- Williams Bridge
- Woodlawn
- Wakefield
- Mt Vernon West
- Yankees-E 153 St
- Fleetwood
- Bronxville
- Springdale MW Facility
- Tuckahoe
- Crestwood
- Scarsdale
- Hartsdale
- White Plains
- North White Plains
- Valhalla
- Mt Pleasant
- Hawthorne
- Pleasantville
- Chappaqua
- Mt Kisco
- Bedford Hills
- Katonah
- Goldens Bridge
- Purdy's
- Morris Heights
- Croton Falls
- Brewster
- Southeast
- Patterson
- Pawling
- Appalachian Trail
Over time
Overall score across the last 2 checks — unchanged since 2026-10-06.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-06 | 72.1 | first check |
| 2026-10-07 | 72.1 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality 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-10-07 | ca379465a4f8 | 2027-05-23 | Current rubric: see the trend above |
| 2026-10-06 | aff299c66d7e | 2027-05-23 | Current rubric: see the trend above |
| 2026-08-06 to 2026-08-07 (2 checks) | 81b1bf9580b1 | 2026-11-22 | C, 76.1 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-10 | 06d8561d342b | 2026-12-26 | C, 73.7 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-09 | fbfc9de3155d | 2026-12-26 | C, 73.7 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-08 | bb627ada88d2 | 2026-12-26 | C, 71.5 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-07 | ff5dbfc81eb0 | 2026-12-26 | C, 71.5 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-06 | 57dd3c7cd1f6 | 2026-12-26 | C, 71.5 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-02 to 2026-07-05 (3 checks) | 8860996949fd | 2026-12-26 | C, 71.5 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-01 | bb631ae8e690 | 2026-12-26 | C, 71.5 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-30 | caec6fe352e5 | 2026-12-22 | C, 71.5 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-27 to 2026-06-29 (3 checks) | ff79f06c4a02 | 2026-12-22 | C, 71.5 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
Showing the 12 most recent of 17 periods.
What changed in this feed
Overall grade and score held steady since 2026-10-06.
The feed file was re-published since 2026-10-06 (+2 KB).
Changed counts
- up 38 of 38 trips scheduled during the sampling window had no live predictions. (31 → 38) (scorecard_rt_trip_coverage)
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
12 findings, ordered by severity.
Show every finding
- Error1 instance
Transfer with invalid trip and stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'transfer_with_invalid_trip_and_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: transfer_with_invalid_trip_and_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning14633 instances
14633 of 35990 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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)
- Warning38 instances
38 of 38 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule times labeled as live. Caltrans asks that every trip you run shows up in TripUpdates.
Fix: Ask your AVL vendor to check that every vehicle assignment reaches TripUpdates. School-day and tripper runs are the ones most often left out. (A vendor data-mapping question.)
Finding code: scorecard_rt_trip_coverage · Read the fix guide for scorecard_rt_trip_coverage · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning18 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide for unused_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Single shape point (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'single_shape_point' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: single_shape_point · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
2 of 114 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)
- 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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- 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 (opens GTFS Best Practices on an external site)
- Info3 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)
- Info1 instance
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)
- 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 (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. 1 validator error to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Ready
- Service data covers the next 228 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 35990 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
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 98% of stops and 59% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 228 days.
- Accessible Not yet
- States wheelchair access on 98% of stops and 59% 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 200 checks in the 25 days to 2026-10-07, with 10s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.
Live predictions vs schedule
Arrival predictions ran a median 60s late versus the schedule, and stayed within 240s nine times in ten. They were on time (about a minute early to five late) 94.0% 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 228 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1 validator error, the other thing Maps checks at onboarding; the findings below name each fix.
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 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 71 / 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.
Part of the New York 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 Metro-North Railroad 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 Metro-North Railroad uses the same numbers as this page: grade C (72.1 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 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 New York
Other scorecards in New York, 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.
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/metro-north-railroad/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.