Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Rail
Based on the feed this agency publishes
down 0.3 since 2026-07-08
Ahead of 67% of all tracked agencies and 65% of mid-size agencies. Operates in Pennsylvania.
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.1, validator 8.0.1.
Checked for changes 14 minutes ago; last changed 6 days ago.
Top things to fix
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 16 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +64 points
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
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 bus route through the wrong streets or point riders to the wrong corner.
⏱ A few minutes per flagged stop.worth about +6 points
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.
1 of 7 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 +5 points
Agencies here usually clear this within about 1 week (based on 84 observed fixes).
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Re-export with a validity window that reaches at least 60 days out. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 7 kinds of issue across 51 instances (0 error, 39 warning, 12 informational).
Service data runs out in 16 day(s). Publish an updated feed soon or riders will lose trip planning.
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.
100% of stops state accessibility (49% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
Sampled 9 times: 3 of 3 feeds healthy; 85.7% of scheduled trips had live predictions; 88.5% of vehicles on their route; predictions ran a median of 660s behind schedule.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: 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)
| Route | Type | Line color |
|---|---|---|
| AIR Airport Line | Rail | gray |
| CHE Chestnut Hill East Line | Rail | gray |
| CHW Chestnut Hill West Line | Rail | gray |
| CYN Cynwyd Line | Rail | gray |
| FOX Fox Chase Line | Rail | gray |
| LAN Lansdale/Doylestown Line | Rail | gray |
| MED Media/Wawa Line | Rail | gray |
| NOR Manayunk/Norristown Line | Rail | gray |
| PAO Paoli/Thorndale Line | Rail | gray |
| TRE Trenton Line | Rail | gray |
| WAR Warminster Line | Rail | gray |
| WIL Wilmington/Newark Line | Rail | gray |
| WTR West Trenton Line | Rail | gray |
This feed has 156 stops.
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 21 checks — down 0.3 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 72.5 | first check |
| 2026-06-20 | 70.9 | down 1.6 |
| 2026-06-21 | 69.8 | down 1.1 |
| 2026-06-22 | 69.4 | down 0.4 |
| 2026-06-23 | 69.6 | up 0.2 |
| 2026-06-24 | 69.6 | no change |
| 2026-06-25 | 69.3 | down 0.3 |
| 2026-06-26 | 68.9 | down 0.4 |
| 2026-06-27 | 68.4 | down 0.5 |
| 2026-06-28 | 68.3 | down 0.1 |
| 2026-06-29 | 72.7 | up 4.4 |
| 2026-06-30 | 72.4 | down 0.3 |
| 2026-07-01 | 72.1 | down 0.3 |
| 2026-07-02 | 71.7 | down 0.4 |
| 2026-07-03 | 76.0 | up 4.3 |
| 2026-07-04 | 75.7 | down 0.3 |
| 2026-07-05 | 75.3 | down 0.4 |
| 2026-07-06 | 75.0 | down 0.3 |
| 2026-07-07 | 74.7 | down 0.3 |
| 2026-07-08 | 74.3 | down 0.4 |
| 2026-07-09 | 74.0 | down 0.3 |
What changed since your last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall score fell 0.3 points since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-06-19 this feed started at grade C. On 2026-06-21 the grade moved from C to D. On 2026-06-29 the grade moved from D to C. On 2026-06-27 feed expired. As of 2026-07-09 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-07-03 Score rose 4 points, correctness rose 14 points.
- 2026-06-29 Grade went D to C, freshness rose 43 points.
- 2026-06-27 Feed expired.
- 2026-06-21 Grade went C to D, realtime fell 4 points.
Everything we checked
- Warning33 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
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.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning11 instances
Some live predictions disagree with the schedule by more than 30 minutes.
Differences that large usually mean predictions are keyed to the wrong trips, not that buses are that late.
Fix: Spot-check the flagged predictions against what buses actually did; raise trip-matching with your AVL vendor. (A vendor data-mapping question.)
Agencies here usually clear this within about 1 week (based on 27 observed fixes).
Validator rule: scorecard_rt_predictions_implausible
- Warning4 instances
4 of 26 sampled vehicle positions were far from their assigned route (worst: 11579 m).
A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.
Fix: Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips. (A vendor support ticket with the trip ids attached.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: scorecard_rt_vehicles_off_route
- Warning3 instances
Some service calendars in the feed have already expired.
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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 24 observed fixes).
Validator rule: feed_expiration_date30_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Route long name contains short name (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Service data runs out in 16 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
1 of 7 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.)
Agencies here usually clear this within about 1 week (based on 84 observed fixes).
Validator rule: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Info10 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · Read the fix guide · 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 with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
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.
NTD certification readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 16 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 16 days; renew before you certify.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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
This feed is close to the conformance mark. Service data runs out in 16 days; renew to qualify.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data runs out in 16 days; renew to qualify.
- 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 106 checks over the last 16 days, with 25s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Prediction accuracy
Arrival predictions ran a median 660s late versus the schedule, and stayed within 2040s nine times in ten. They were on time (about a minute early to five late) 27.3% of the time. 88.5% 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.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 23 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 77 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 27 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 92 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality 93 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/southeastern-pennsylvania-transportation-authority-septa-503/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.