Feed status · checked 2026-11-21

Metra

Based on the feed source on file; publisher ownership is not verified

Service mode Rail

68.7 / 100

down 0.4 since 2026-11-20

Cataloged in Illinois.

Covers 40 daysAccessibility gapsRealtime not yet published

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

Top things to fix

Fix 01

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

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

Fixing this covers all 3,371 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 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.

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

Fix 03

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

45 of 241 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 45 of 241 stops, about 19% of them.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +5 points in its category

Riders and need behind these fixes

  • No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
  • Illinois 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.

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
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. Fix 01 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    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.

  2. Fix 02 · 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.

  3. Fix 03 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    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 40 days.
Published accessibility data
Accessibility information is stated for 81.3% 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 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.

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.

Metra’s published feed lists 11 rail routes, 3,371 scheduled trips and 241 stops. The published file last changed on 2026-11-14.

Score by category

Correctness75.5 / 100

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

Freshness51.7 / 100

Service data covers the next 40 days.

Rider experience72.8 / 100

81% of stops state wheelchair accessibility (81% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.

Accessibility50.8 / 100

81% of stops state accessibility (81% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (MD-N, ME, NCS).

    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.

  • 53 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("College Ave", "Fairview Ave.", "Stone Ave.", 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.

FaresLegacy fares

Fares are applied to trips.

Realtime qualityNot yet measured

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

  • BNSF (green)
  • HC (black)
  • MD-N (orange)
  • MD-W (yellow)
  • ME (orange)
  • NCS (gray)
  • RI (red)
  • SWS (blue)
  • UP-N (green)
  • UP-NW (yellow)
  • UP-W (pink)
Routes in Metra's feed
RouteTypeLine color
BNSF Burlington NorthernRailgreen
HC Heritage CorridorRailblack
MD-N Milwaukee NorthRailorange
MD-W Milwaukee WestRailyellow
ME Metra ElectricRailorange
NCS North Central ServiceRailgray
RI Rock IslandRailred
SWS Southwest ServiceRailblue
UP-N Union Pacific NorthRailgreen
UP-NW Union Pacific NorthwestRailyellow
UP-W Union Pacific WestRailpink
List every stop
  • 103rd St. - Beverly Hills
  • 103rd St. (Rosemoor)
  • 107th St. - Beverly Hills
  • 107th St.
  • 111th St. - Morgan Park
  • 111th St. (Pullman)
  • 115th St. - Morgan Park
  • 119th St.
  • 123rd St.
  • Orland Park 143rd
  • 147th St.
  • Orland Park 153rd
  • Orland Park 179th
  • 18th St.
  • 211th St.
  • 27th St.
  • 35th St. - Lou Jones
  • 47th St. (Kenwood)
  • 51st/53rd St. (Hyde Park)
  • 55th - 56th - 57th St.
  • 59th St. (U. of Chicago)
  • 63rd St.
  • 75th St. (Grand Crossing)
  • Cheltenham (79th St.)
  • 79th St. (Chatham)
  • 83rd St.
  • 83rd St. (Avalon Park)
  • 87th St.
  • 87th St. (Woodruff)
  • 91st St. - Beverly Hills
  • 91st St.
  • South Chicago (93rd)
  • 95th St. - Beverly Hills
  • 95th St.
  • 99th St. - Beverly Hills
  • Antioch
  • Arlington Heights
  • Arlington Park
  • Ashburn
  • Ashland
  • Aurora
  • Barrington
  • Bartlett
  • Bellwood
  • Belmont
  • Bensenville
  • Berkeley
  • Berwyn
  • Big Timber
  • Blue Island
  • Western Avenue
  • Braeside
  • Brainerd
  • Brookfield
  • Bryn Mawr
  • Buffalo Grove
  • Burr Oak
  • Calumet
  • Cary
  • Central St.
  • Chicago Ridge
  • Cicero
  • Clarendon Hills
  • Clybourn
  • College Ave
  • Congress Park
  • Crystal Lake
  • Cumberland
  • Chicago Union Station
  • Deerfield
  • Dee Road
  • Des Plaines
  • Edgebrook
  • Edison Park
  • Elburn
  • Elgin
  • Elmhurst
  • Elmwood Park
  • Evanston (Davis St.)
  • Fairview Ave.
  • Flossmoor
  • Forest Glen
  • Fox Lake
  • Fox River Grove
  • Franklin Park
  • Franklin Pk
  • Fort Sheridan
  • Galewood
  • Geneva
  • Gladstone Park
  • Glencoe
  • Glen Ellyn
  • Glenview
  • Golf
  • Grand/Cicero
  • Grayland
  • Grayslake
  • Gresham
  • Great Lakes
  • Halsted Street
  • Hanover Park
  • Hanson Park
  • Harlem Ave.
  • Harvard
  • Harvey
  • Hazel Crest
  • Healy
  • Hickory Creek
  • Highland Park
  • Highlands
  • Highwood
  • Hinsdale
  • Hollywood
  • Homewood
  • Hubbard Woods
  • Indian Hill
  • Ingleside
  • Irving Park
  • Itasca
  • Ivanhoe
  • Jefferson Park
  • Joliet
  • Kedzie
  • Kenilworth
  • Kenosha
  • Kensington
  • La Fox
  • LaGrange Road
  • Lake Bluff
  • Lake-Cook
  • Lake Forest
  • Lake Villa
  • Laraway Road
  • Lavergne
  • Lemont
  • Libertyville
  • Lisle
  • Lake Forest.
  • Lockport
  • Lombard
  • Long Lake
  • 95th St.-Longwood
  • LaSalle Street
  • Main St.
  • Downers Grove
  • Manhattan
  • Mannheim
  • Mars
  • Matteson
  • Mayfair
  • Maywood
  • McCormick Place
  • McHenry
  • Medinah
  • Melrose Park
  • Midlothian
  • Millennium Station
  • Mokena
  • Mont Clare
  • Morton Grove
  • Mt. Prospect
  • Mundelein
  • Museum Campus/11th St.
  • Naperville
  • National St
  • Northbrook
  • North Chicago
  • Washington St (Grayslake)
  • New Lenox
  • Glen/N. Glenview
  • Norwood Park
  • Oak Forest
  • Oak Lawn Patriot
  • Oak Park
  • O'Hare Transfer
  • Olympia Fields
  • Chicago OTC
  • Palatine
  • Palos Heights
  • Palos Park
  • Park Ridge
  • Peterson/Ridge
  • Pingree Road
  • Prairie Crossing.
  • Prairie St.
  • Prairie View
  • Prairie Crossing
  • Prospect Hts
  • Racine
  • Ravenswood
  • Ravinia
  • Ravinia Park
  • Richton Park
  • Riverdale
  • River Grove
  • Riverside
  • River Forest
  • Robbins
  • Rogers Park
  • Romeoville
  • Roselle
  • Rosemont
  • Round Lake
  • Round Lake Beach
  • Route 59
  • Schaumburg
  • Schiller Park
  • South Shore
  • State St.
  • Stewart Ridge
  • Stone Ave.
  • Stony Island
  • Summit
  • Tinley-80th
  • Tinley Park
  • University Park
  • Van Buren St.
  • Blue Island-Vermont
  • Vernon Hills
  • Villa Park
  • 103rd St.-Washington Hts.
  • Waukegan
  • West Chicago
  • Western Ave
  • Westmont
  • Western Springs
  • Wheaton
  • Wheeling
  • West Hinsdale
  • Willow Springs
  • Wilmette
  • Windsor Park
  • Winfield
  • Winnetka
  • Winthrop Harbor
  • Wood Dale
  • Woodstock
  • Worth
  • West Pullman
  • Wrightwood
  • Zion

Over time

Overall score across the last 13 checks — down 0.4 since 2026-11-20.

2026-11-09: 73.72026-11-10: 73.32026-11-11: 72.92026-11-12: 72.52026-11-13: 72.02026-11-14: 71.62026-11-15: 71.22026-11-16: 70.82026-11-17: 70.42026-11-18: 70.02026-11-19: 69.52026-11-20: 69.12026-11-21: 68.7
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0973.7 first check
2026-11-1073.3 down 0.4
2026-11-1172.9 down 0.4
2026-11-1272.5 down 0.4
2026-11-1372.0 down 0.5
2026-11-1471.6 down 0.4
2026-11-1571.2 down 0.4
2026-11-1670.8 down 0.4
2026-11-1770.4 down 0.4
2026-11-1870.0 down 0.4
2026-11-1969.5 down 0.5
2026-11-2069.1 down 0.4
2026-11-2168.7 down 0.4

What changed since your last check

  • Correctness no change
  • Freshness down 1.6
  • 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.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-14 to 2026-11-21 (8 checks)f2230b96e4112026-12-31Current rubric: see the trend above
2026-11-09 to 2026-11-13 (5 checks)71792ebd99bc2026-12-31Current rubric: see the trend above
2026-10-22 to 2026-11-06 (16 checks)71792ebd99bcnot recordedF, 37.7 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-10-03 to 2026-10-21 (18 checks)06b6f940e9f9not recordedF, 37.7 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-10-02dab6ab536c1bnot recordedF, 37.7 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-09-23 to 2026-10-01 (9 checks)dab6ab536c1bnot recordedF, 37.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-22436aad1e3950not recordedF, 37.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-18 to 2026-09-21 (4 checks)14f345e7ae0fnot recordedF, 37.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-09 to 2026-09-13 (5 checks)94c69691466bnot recordedF, 37.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-22 to 2026-09-08 (17 checks)1a949b3a3636not recordedF, 37.5 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-18 to 2026-08-21 (2 checks)d47341a5ec44not recordedF, 36.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-12 to 2026-08-16 (5 checks)4266d3bab1fcnot recordedF, 37.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade

Showing the 12 most recent of 18 periods.

What changed over time

On 2026-11-09 this feed started at grade C. On 2026-11-19 the grade moved from C to D. As of 2026-11-21 it holds grade D.

A plain-language history of this feed, newest first.

  • 2026-11-19 Grade went C to D.

Everything we checked

11 findings, ordered by severity.

Show every finding
  • Warning3371 instances

    3371 of 3371 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)

  • Warning45 instances

    45 of 241 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)

  • Warning5 instances

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

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

    Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning3 instances

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

    Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning2 instances

    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 for stop_without_stop_time · See MobilityData GTFS Validator rules (opens the validator rules 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

    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)

  • Warning1 instance

    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)

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

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

    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)

How we measured this

Checked for changes 18 hours ago; last changed 7 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 40 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) Different (allowed)
Your feed's agency_id is METRA; your National Transit Database ID is 50118. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id METRA to NTD ID 50118, and keep the feed value stable. Do not change it solely to make the two values equal.
shapes.txt covers your trips Ready
All 3371 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 81% 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 40 days.
Accessible Not yet
States wheelchair access on 81% 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.

  • 2 of 241 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 39 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 76 / 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 52 / 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 73 / 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 Illinois portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Illinois

Other scorecards in Illinois, 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.

Metra: GTFS feed quality grade D, 68.7 of 100, checked 2026-11-21. GTFS 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/metra-2854/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.