GTFS Scorecard
← All agencies

Feed status · checked 2026-10-07

Southeastern Pennsylvania Transportation Authority (SEPTA) Rail

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

Service mode Rail

87.3 / 100

down 0.2 since 2026-10-06

Cataloged in Pennsylvania.

Covers 45 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.4, validator 8.0.1.

Checked for changes 32 minutes ago; last changed 27 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 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.

About this feed

Southeastern Pennsylvania Transportation Authority (SEPTA) Rail’s published feed lists 13 rail routes, 2,340 scheduled trips and 156 stops. Its service dates run from 2026-09-27 through 2026-11-21. It publishes realtime trip updates, vehicle positions and service alerts; when we checked, all of them answered. The published file last changed on 2026-10-06.

Top things to fix

Fix 01

Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.

47 of 134 sampled vehicle positions were far from their assigned route (worst: 32565 m). A transit vehicle shown off its route usually means a wrong trip assignment; riders watch their transit vehicle drive the wrong path.

This was measured over a realtime sampling window, so it has no feed-wide share.

⏱ A vendor support ticket with the trip ids attached.worth about +5 points in its category

Fix 02

Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.Likely your export tool

Some stops sit far from the route line they belong to. Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.

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.

⏱ A few minutes per flagged stop.worth about +4 points in its category

Fix 03

Add feed_contact_email or feed_contact_url to feed_info.txt.Likely your export tool

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.

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.

⏱ One field, set once in export settings.worth about +4 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.
  • Pennsylvania 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-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
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

    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 stop_too_far_from_shape

    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 missing_feed_contact_email_and_url

    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 45 days.
Published accessibility data
Accessibility information is stated for 100% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v2.
Realtime information
Live-arrival data covered 100% 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

Correctness86.5 / 100

The MobilityData validator flagged 6 kinds of issue across 12 instances (0 error, 7 warning, 5 informational).

Freshness75.0 / 100

Service data covers the next 45 days.

Rider experience92.5 / 100

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

Accessibility100 / 100

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

1 accessibility depth signal

  • 14 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Gray 30th St Station", "49th St", "9th St Lansdale", 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.

FaresFares v2

Fares are applied to trips.

Realtime quality94.7 / 100

Sampled 9 times: 3 of 3 configured feeds healthy; 100.0% of scheduled trips had live predictions; 64.9% of vehicles on their route; predictions ran a median of 360s behind schedule.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 156 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.

  • AIR (gray)
  • CHE (gray)
  • CHW (gray)
  • CYN (gray)
  • FOX (gray)
  • LAN (gray)
  • MED (gray)
  • NOR (gray)
  • PAO (gray)
  • TRE (gray)
  • WAR (gray)
  • WIL (gray)
  • WTR (gray)
Routes in Southeastern Pennsylvania Transportation Authority (SEPTA) Rail's feed
RouteTypeLine color
AIR Airport LineRailgray
CHE Chestnut Hill East LineRailgray
CHW Chestnut Hill West LineRailgray
CYN Cynwyd LineRailgray
FOX Fox Chase LineRailgray
LAN Lansdale/Doylestown LineRailgray
MED Media/Wawa LineRailgray
NOR Manayunk/Norristown LineRailgray
PAO Paoli/Thorndale LineRailgray
TRE Trenton LineRailgray
WAR Warminster LineRailgray
WIL Wilmington/Newark LineRailgray
WTR West Trenton LineRailgray
List every stop
  • Cynwyd
  • Bala
  • Wynnefield Av
  • Gray 30th St Station
  • Suburban Station
  • Jefferson Station
  • Temple University
  • North Broad
  • Wayne Junction
  • Newark DE
  • Churchman's Crossing
  • Wilmington
  • Claymont Transit Center
  • Marcus Hook
  • Highland Av
  • Chester Transit Center
  • Eddystone
  • Crum Lynne
  • Ridley Park
  • Prospect Park
  • Norwood
  • Glenolden
  • Folcroft
  • Sharon Hill
  • Curtis Park
  • Darby
  • Allegheny
  • East Falls
  • Wissahickon
  • Manayunk
  • Ivy Ridge
  • Miquon
  • Spring Mill
  • Conshohocken
  • Norristown Transit Center
  • Main St
  • Norristown Elm Street
  • Wawa
  • Elwyn
  • Media
  • Moylan-Rose Valley
  • Wallingford
  • Swarthmore
  • Morton
  • Secane
  • Primos
  • Clifton-Aldan
  • Gladstone
  • Lansdowne
  • Fernwood-Yeadon
  • Angora
  • 49th St
  • Noble
  • Rydal
  • Meadowbrook
  • Bethayres
  • Philmont
  • Forest Hills
  • Somerton
  • Trevose
  • Neshaminy Falls
  • Langhorne
  • Woodbourne
  • Yardley
  • West Trenton
  • Airport Terminals E & F
  • Airport Terminals C & D
  • Airport Terminal B
  • Airport Terminal A
  • Eastwick
  • Penn Medicine Station
  • Fern Rock Transit Center
  • Melrose Park
  • Elkins Park
  • Jenkintown-Wyncote
  • Glenside
  • Ardsley
  • Roslyn
  • Crestmont
  • Willow Grove
  • Hatboro
  • Warminster
  • Thorndale
  • Downingtown
  • Whitford
  • Exton
  • Malvern
  • Paoli
  • Daylesford
  • Berwyn
  • Devon
  • Strafford
  • Wayne
  • St. Davids
  • Radnor
  • Villanova
  • Rosemont
  • Bryn Mawr
  • Haverford
  • Ardmore
  • Wynnewood
  • Narberth
  • Merion
  • Overbrook
  • North Hills
  • Oreland
  • Fort Washington
  • Ambler
  • Penllyn
  • Gwynedd Valley
  • North Wales
  • Pennbrook
  • Lansdale
  • Fortuna
  • Colmar
  • Link Belt
  • Chalfont
  • New Britain
  • Delaware Valley University
  • Doylestown
  • 9th St Lansdale
  • Trenton Transit Center
  • Levittown
  • Bristol
  • Croydon
  • Eddington
  • Cornwells Heights
  • Torresdale
  • Holmesburg Junction
  • Tacony
  • Bridesburg
  • North Philadelphia Amtrak
  • Wister
  • Germantown
  • Washington Ln
  • Stenton
  • Sedgwick
  • Mount Airy
  • Wyndmoor
  • Gravers
  • Chestnut Hill East
  • Chestnut Hill West
  • Highland
  • St. Martins
  • Richard Allen Ln
  • Carpenter
  • Upsal
  • Tulpehocken
  • Chelten Av
  • Queen Ln
  • North Philadelphia Septa
  • Olney
  • Lawndale
  • Cheltenham
  • Ryers
  • Fox Chase

Over time

Overall score across the last 2 checks — down 0.2 since 2026-10-06.

2026-10-06: 87.52026-10-07: 87.3
Show the numbers
CheckScoreChange
2026-10-0687.5 first check
2026-10-0787.3 down 0.2

What changed since your last check

  • Correctness no change
  • Freshness down 1.7
  • Rider experience no change
  • Realtime quality up 0.6

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.

CheckedPublished fileService dates throughGrade at the time
2026-10-06 to 2026-10-07 (2 checks)c908d0f0e8092026-11-21Current rubric: see the trend above
2026-09-13f437e84a5d022026-10-17B, 81.6 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-09-01bb69978e27682026-10-17B, 86.3 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-08-06 to 2026-08-07 (2 checks)cbe382f776f82026-08-29C, 76.3 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-03 to 2026-07-10 (8 checks)81576cc0ccb92026-07-25C, 73.7 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade
2026-06-29 to 2026-07-02 (4 checks)a987607066352026-07-25C, 71.7 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-06-28 (10 checks)df3b58a5579f2026-06-27D, 68.3 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall score fell 0.2 points since 2026-10-06.

Same feed file as 2026-10-06; the published zip did not change.

New since 2026-10-06 (1 finding)

  • Warning53 instances

    Some live predictions are more than 30 minutes away from the schedule.

    Finding code: scorecard_rt_predictions_implausible

Changed counts

  • up 47 of 134 sampled vehicle positions were far from their assigned route (worst: 32565 m). (41 → 47) (scorecard_rt_vehicles_off_route)

No longer reported since 2026-10-06 (1 finding)

  • 1 of 30 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage)

This records the later feed state. It does not establish who made a change or why.

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
  • Warning53 instances

    Some live predictions are more than 30 minutes away from the schedule.

    Differences that large usually mean predictions are keyed to the wrong trips, not that transit vehicles are that late.

    Fix: Spot-check the flagged predictions against what transit vehicles actually did; raise trip-matching with your AVL vendor. (A vendor data-mapping question.)

    Finding code: scorecard_rt_predictions_implausible

  • Warning47 instances

    47 of 134 sampled vehicle positions were far from their assigned route (worst: 32565 m).

    A transit vehicle shown off its route usually means a wrong trip assignment; riders watch their transit vehicle drive the wrong path.

    Fix: Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips. (A vendor support ticket with the trip ids attached.)

    Finding code: scorecard_rt_vehicles_off_route

  • Warning5 instances

    Some stops sit far from the route line they belong to.

    Trip planners may draw the transit vehicle route through the wrong path or point riders to the wrong boarding location.

    Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

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

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

  • Warning1 instance

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules

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

  • Info2 instances

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

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

  • Info1 instance

    The feed has a stretch of two weeks or more with no service running.

    A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

    Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

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

  • 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

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 45 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 2340 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 Southeastern Pennsylvania Transportation Authority (SEPTA) Rail

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 45 days.
Accessible Met
States wheelchair access on 100% of stops and 100% 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.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks in the 25 days to 2026-10-07, with 24s 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 360s late versus the schedule, and stayed within 2160s nine times in ten. They were on time (about a minute early to five late) 43.4% of the time. 64.9% of reported vehicle positions sat on or near the published route shape.

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 45 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 86 / 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 75 / 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 92 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 95 / 100
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the Pennsylvania 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 Southeastern Pennsylvania Transportation Authority (SEPTA) Rail 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 Southeastern Pennsylvania Transportation Authority (SEPTA) Rail uses the same numbers as this page: grade B (87.3 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 the program report bundle

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 Pennsylvania

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

Southeastern Pennsylvania Transportation Authority (SEPTA) Rail: GTFS feed quality grade B, 87.3 of 100, checked 2026-10-07. 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/southeastern-pennsylvania-transportation-authority-septa-503/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.