Feed status · checked 2026-08-01
New Jersey Transit (NJ Transit) Rail
Based on the feed this agency publishes
Service mode Tram + Rail
unchanged since 2026-07-31
Catalogued in New Jersey.
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 72 minutes ago; last changed 1 days ago.
Measured 3 of 4 score categories from the agency's own feed.
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 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
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool
Some trips have stop times whose distances along the route go backwards. Apps can show transit vehicles jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +24 points in its category
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
231 of 231 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 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
- Block trips with overlapping stop times (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Feed evidence
- Some trips have stop times whose distances along the route go backwards.
- Next action
- Re-generate shape distances in your export; flag to your vendor if it persists.
- 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
- Feed evidence
- 231 of 231 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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.
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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.
Re-generate shape distances in your export; flag to your vendor if it persists.
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.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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 176 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% 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
- 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.
Score by category
The MobilityData validator flagged 5 kinds of issue across 3331 instances (507 error, 2824 warning, 0 informational).
Service data covers the next 176 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (ATLC, HBLR, PASC, RVLN).
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.
11 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("30TH ST. PHL.", "NEWARK BROAD ST", "PRINCETON JCT.", 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.
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 231 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- ATLC (teal)
- NEC (red)
- NJCL (teal)
- NJCLL (teal)
- NLR (teal)
- PASC (purple)
- PRIN (red)
- RARV (yellow)
- RVLN (blue)
- BNTN (pink)
- BNTNM (pink)
- HBLR (teal)
- MNBN (yellow)
- MNBNP (yellow)
- MNE (green)
- MNEG (gray)
- MRL (gray)
| Route | Type | Line color |
|---|---|---|
| ATLC Atlantic City Rail Line | Rail | teal |
| NEC Northeast Corridor | Rail | red |
| NJCL North Jersey Coast Line | Rail | teal |
| NJCLL North Jersey Coast Line | Rail | teal |
| NLR Newark Light Rail | Tram / light rail | teal |
| PASC Pascack Valley Line | Rail | purple |
| PRIN Princeton Shuttle | Rail | red |
| RARV Raritan Valley Line | Rail | yellow |
| RVLN Riverline Light Rail | Tram / light rail | blue |
| BNTN Montclair-Boonton Line | Rail | pink |
| BNTNM Montclair-Boonton Line | Rail | pink |
| HBLR Hudson-Bergen Light Rail | Tram / light rail | teal |
| MNBN Main/Bergen County Line | Rail | yellow |
| MNBNP Port Jervis Line | Rail | yellow |
| MNE Morris & Essex Line | Rail | green |
| MNEG Gladstone Branch | Rail | gray |
| MRL Meadowlands Rail Line | Rail | gray |
List every stop
- 30TH ST. PHL.
- ATLANTIC CITY
- NANUET
- NETCONG
- NETHERWOOD
- NEW BRUNSWICK
- NEW PROVIDENCE
- NEW YORK PENN STATION
- NEWARK BROAD ST
- NEWARK PENN STATION
- NORTH BRANCH
- NORTH ELIZABETH
- AVENEL
- NEW BRIDGE LANDING
- ORADELL
- ORANGE
- OTISVILLE
- PARK RIDGE
- PASSAIC
- PATERSON
- PEAPACK
- PEARL RIVER
- PERTH AMBOY
- BASKING RIDGE
- PLAINFIELD
- PLAUDERVILLE
- POINT PLEASANT
- PORT JERVIS
- PRINCETON
- PRINCETON JCT.
- RADBURN
- RAHWAY
- RAMSEY
- RARITAN
- BAY HEAD
- RED BANK
- RIDGEWOOD
- RIVER EDGE
- RUTHERFORD
- SALISBURY MILLS-CORNWALL
- SHORT HILLS
- SLOATSBURG
- SOMERVILLE
- SOUTH AMBOY
- BAY STREET
- SOUTH ORANGE
- SPRING LAKE
- SPRING VALLEY
- STIRLING
- SUFFERN
- SUMMIT
- TETERBORO
- TOWACO
- TRENTON TRANSIT CENTER
- TUXEDO
- BLOOMFIELD AVENUE LIGHT RAIL STATION
- ORANGE STREET LIGHT RAIL STATION
- BELMAR
- UPPER MONTCLAIR
- WALDWICK
- WALNUT STREET
- WATCHUNG AVENUE
- WATSESSING AVENUE
- WESTFIELD
- WESTWOOD
- WHITE HOUSE
- WOODBRIDGE
- WOODCLIFF LAKE
- WOOD-RIDGE
- BERKELEY HEIGHTS
- LINCOLN HARBOR LIGHT RAIL STATION
- BERNARDSVILLE
- BLOOMFIELD
- ABSECON
- BOONTON
- BOUND BROOK
- BRADLEY BEACH
- BRICK CHURCH
- BRIDGEWATER
- BROADWAY
- CAMPBELL HALL
- BRANCH BROOK PARK LIGHT RAIL STATION
- PENN STATION LIGHT RAIL DEPARTURE
- CHATHAM
- CHERRY HILL
- CLIFTON
- ALLENDALE
- CONVENT
- ROSELLE PARK
- MONMOUTH PARK
- CRANFORD
- HAMILTON
- JERSEY AVE.
- DELAWANNA
- DENVILLE
- DOVER
- DUNELLEN
- EXCHANGE PLACE LIGHT RAIL STATION
- ESSEX STREET LIGHT RAIL STATION
- MARIN BOULEVARD LIGHT RAIL STATION
- JERSEY AVENUE LIGHT RAIL STATION
- LIBERTY STATE PARK-RIDE LIGHT RAIL STA
- GARFIELD AVENUE LIGHT RAIL STATION
- EAST ORANGE
- MLK DRIVE LIGHT RAIL STATION
- WEST SIDE AVENUE LIGHT RAIL STATION
- RICHARD STREET LIGHT RAIL STATION
- DANFORTH AVENUE LIGHT RAIL STATION
- 45TH STREET LIGHT RAIL STATION
- 34TH STREET LIGHT RAIL STATION
- ABERDEEN-MATAWAN
- HARBORSIDE LIGHT RAIL STATION
- HARSIMUS COVE LIGHT RAIL STATION
- NEWPORT LIGHT RAIL STATION
- NEWARK AIRPORT RAILROAD STATION
- EDISON STATION
- SILVER LAKE LIGHT RAIL STATION
- GROVE STREET LIGHT RAIL STATION
- MSU
- UNION
- SECAUCUS LOWER LEVEL
- SECAUCUS UPPER LEVEL
- 22ND STREET LIGHT RAIL STATION
- TRENTON TRANSIT CENTER LIGHT RAIL STATION
- HAMILTON AVENUE LIGHT RAIL STATION
- CASS STREET LIGHT RAIL STATION
- BORDENTOWN LIGHT RAIL STATION
- ROEBLING LIGHT RAIL STATION
- FLORENCE LIGHT RAIL STATION
- BURLINGTON TOWNE CTR LIGHT RAIL STATION
- BURLINGTON SOUTH LIGHT RAIL STATION
- BEVERLY/EDGEWATER PARK LIGHT RAIL STA
- DELANCO LIGHT RAIL STATION
- RIVERSIDE LIGHT RAIL STATION
- CINNAMINSON LIGHT RAIL STATION
- RIVERTON LIGHT RAIL STATION
- PALMYRA LIGHT RAIL STATION
- ROUTE 73/PENNSAUKEN LIGHT RAIL STATION
- 36TH STREET LIGHT RAIL STATION
- WALTER RAND TRANSPORTATION CTR
- COOPER STREET/RUTGERS LIGHT RAIL STATION
- AQUARIUM LIGHT RAIL STATION
- ENTERTAINMENT CENTER LIGHT RAIL STATION
- RAMSEY ROUTE 17 STATION
- 2ND STREET LIGHT RAIL STATION
- 9TH STREET LIGHT RAIL STATION
- BERGENLINE AVE
- TONNELLE AVENUE LIGHT RAIL STATION
- EGG HARBOR
- BROAD STREET LIGHT RAIL STATION
- RIVERFRONT STADIUM LIGHT RAIL STATION
- HARRIET TUBMAN SQUARE LIGHT RAIL STATION
- ATLANTIC STREET LIGHT RAIL STATION
- NJPAC/CENTRE STREET LIGHT RAIL STATION
- HOBOKEN TERMINAL LIGHT RAIL STATION
- MOUNT ARLINGTON
- WAYNE/ROUTE 23 TRANSIT CENTER [RR]
- ALLENHURST
- ELBERON
- COMMUNIPAW JUNCTION
- NYNJ STADIUM
- ELIZABETH
- TONNELLE - WESTSIDE DEKALB JCT
- EMERSON
- PENN STATION LIGHT RAIL ARRIVAL
- 8TH STREET LIGHT RAIL STATION
- ESSEX STREET
- PENNSAUKEN TRANSIT CENTER LIGHT RAIL STA
- PENNSAUKEN TRANSIT CENTER
- WESMONT
- FANWOOD
- FAR HILLS
- GARFIELD
- GARWOOD
- GILLETTE
- GLADSTONE
- ANDERSON STREET
- GLEN RIDGE
- GLEN ROCK BORO HALL
- GLEN ROCK MAIN LINE
- HACKETTSTOWN
- HAMMONTON
- HARRIMAN
- HAWTHORNE
- HAZLET
- ANNANDALE
- HIGH BRIDGE
- HIGHLAND AVENUE
- HILLSDALE
- HOBOKEN
- HOHOKUS
- LAKE HOPATCONG
- LEBANON
- LINCOLN PARK
- MILITARY PARK LIGHT RAIL STATION
- DAVENPORT AVENUE LIGHT RAIL STATION
- NORFOLK STREET LIGHT RAIL STATION
- PARK AVENUE NEWARK LIGHT RAIL STATION
- WARREN STREET LIGHT RAIL STATION
- WASHINGTON STREET LIGHT RAIL STATION
- LINDEN
- LINDENWOLD
- LITTLE FALLS
- LITTLE SILVER
- LONG BRANCH
- LYNDHURST
- LYONS
- MADISON
- MAHWAH
- MANASQUAN
- ASBURY PARK
- MAPLEWOOD
- METROPARK
- METUCHEN
- MIDDLETOWN NJ
- MIDDLETOWN NY
- MILLBURN
- MILLINGTON
- MONTCLAIR HEIGHTS
- ATCO
- MONTVALE
- MORRIS PLAINS
- MORRISTOWN
- MOUNT OLIVE
- MOUNT TABOR
- MOUNTAIN AVENUE
- MOUNTAIN LAKES
- MOUNTAIN STATION
- MOUNTAIN VIEW
- PORT IMPERIAL HBLR STATION
- MURRAY HILL
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 48.4 | first check |
| 2026-07-30 | 48.4 | no change |
| 2026-07-31 | 44.1 | down 4.3 |
| 2026-08-01 | 44.1 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; 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-07-25 this feed started at grade F. On 2026-08-01 the grade held, though the score fell from 48 to 44. As of 2026-08-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-07-31 Score fell 4 points, correctness fell 10 points.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Error404 instances
Block trips with overlapping stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error103 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show transit vehicles jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3469 instances
3469 of 3469 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 (opens the GTFS Schedule reference on an external site)
- Warning2820 instances
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning231 instances
231 of 231 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 (opens the GTFS Schedule reference on an external site)
- Warning3 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong path or point riders to the wrong boarding location.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · 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 · 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info229 instances
About 229 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- 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 (opens the validator rules on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. 2 validator errors to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 2 validator errors to resolve.
- Current Ready
- Service data covers the next 176 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 NJB, NJT; your National Transit Database ID is 20080. 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 NJB, NJT to NTD ID 20080, and keep the feed value stable. Do not change it solely to make the two values equal.
- shapes.txt covers your trips Ready
- All 3469 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
This feed is close to the conformance mark. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 176 days.
- Accessible Not yet
- States wheelchair access on 0% 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 176 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 507 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 36 / 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 23 / 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.
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.
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/new-jersey-transit-nj-transit-509/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.