GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Metro-North Railroad

Based on the feed this agency publishes

Service mode Rail

74.7 / 100

down 1.4 since 2026-07-31

Catalogued in New York.

Covers 113 days

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 5 hours ago; last changed 20 hours ago.

Measured 4 of 4 score categories from the agency's own feed.

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

Fix 01

Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.

36 of 36 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

Fix 02

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.

⏱ Two fields, set once in export settings.worth about +15 points in its category

Fix 03

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.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
36 of 36 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
How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. 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.

  2. Add feed_info.txt with feed_start_date and feed_end_date to your export. · 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.

  3. 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. · 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 113 days.
Published accessibility data
Accessibility information is stated for 98.2% of stops and 92.5% 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

Correctness77.0 / 100

The MobilityData validator flagged 7 kinds of issue across 29 instances (0 error, 25 warning, 4 informational).

Freshness85.0 / 100

Service data covers the next 113 days.

Rider experience75.9 / 100

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.

Accessibility96.1 / 100

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.

Realtime quality58.8 / 100

Sampled 6 times: 2 of 2 configured feeds healthy; 0.0% of scheduled trips had live predictions; predictions ran a median of 180s 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.

Skip to route and stop data

The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

  • Hudson (green)
  • Harlem (blue)
  • New Haven (red)
  • New Canaan (red)
  • Danbury (red)
  • Waterbury (red)
Routes in Metro-North Railroad's feed
RouteTypeLine color
HudsonRailgreen
HarlemRailblue
New HavenRailred
New CanaanRailred
DanburyRailred
WaterburyRailred
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 4 checks — down 1.4 since 2026-07-31.

2026-07-25: 76.12026-07-30: 76.12026-07-31: 76.12026-08-01: 74.7
Show the numbers
CheckScoreChange
2026-07-2576.1 first check
2026-07-3076.1 no change
2026-07-3176.1 no change
2026-08-0174.7 down 1.4

What changed since your last check

  • Correctness down 4.0
  • Freshness no change
  • Rider experience down 0.1
  • Realtime quality no change

Everything we checked

13 findings, ordered by severity.

Show every finding
  • Warning2116 instances

    2116 of 28176 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 · See GTFS Schedule reference

  • Warning36 instances

    36 of 36 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

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

  • 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

  • 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 · See GTFS Schedule reference

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

  • Warning1 instance

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no transit vehicle 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

  • Warning1 instance

    Many of the feed's trips don't run at all in the next 7 days.

    It usually means old service periods are still in the export, making the feed bigger and harder to check.

    Fix: Trim past service periods the next time you export. (One setting in most export tools.)

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

  • Warning1 instance

    feed_info.txt is missing its start/end dates (the file itself is absent)

    Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

    Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

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

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

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

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

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

  • 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

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 113 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 28176 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 Awarded

This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.

GTFS conformance mark for Metro-North Railroad

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 113 days.
Accessible Met
States wheelchair access on 98% of stops and 92% of trips.

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.

  • 1 of 114 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.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 9s 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 a median 180s late versus the schedule, and stayed within 900s nine times in ten. They were on time (about a minute early to five late) 74.9% 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 112 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 77 / 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 76 / 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.

Metro-North Railroad GTFS data quality grade: C

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