Compare tract accessibility across the current network and regional operating scenarios. Select a tract for its results or open the optional trip comparison.
Operating scenario
Land-use and weighting basis
Current · 2024 residents / 2023 jobs 2050 trend 2050 rail-concentrated sensitivity Changes tract population and jobs, the harmonized two-factor land-use score, and resident weighting of tract accessibility.
Service day Tuesday · Aug. 25, 2026 Saturday · Aug. 22, 2026
Time period All periods 6:00–9:00 a.m. 9:00 a.m.–3:00 p.m. 3:00–7:00 p.m. 7:00 p.m.–midnight
Travel-time threshold 45 minutes 60 minutes 90 minutes
Custom frequency
Map outcome
Penn Station Access is shown as an official service-envelope reference. Tract accessibility outcomes are unavailable because no train-level or fully reconciled period timetable is public.
New Jersey local fixed-route context
The preserved New Jersey Transit Score is distinct from the harmonized regional land-use score and from service access. Local-access measures use network walking thresholds of 1,312 feet for bus and 2,625 feet for rail, light rail, rapid transit, and ferry on Tuesday, August 18, 2026 and Saturday, August 15, 2026. The longer-walk sensitivity uses 2,625 feet for bus and 3,937 feet for the other modes. These measures are available only for New Jersey.
Map layers
NJ TRANSIT-exclusive physical-track segments use current official GTFS route colors. A physical track used by routes with different official colors is neutral gray; its tooltip lists the services. This avoids assigning one route’s color to shared infrastructure or inventing offset tracks.
NJ TRANSIT physical tracks Amtrak physical tracks Shared multi-route passenger tracks · neutral Long Island Rail Road physical tracks Metro-North physical tracks Light rail, PATH, and PATCO tracks Other mapped passenger tracks Rail stations Gateway, Penn Station Access, and Meadowlands
Rail lines
Regional projects
Service sources and material omissions
The regional rail model uses four official GTFS feeds. New Jersey local-access context uses separate dates and a separate geographic scope.
How to read the scenarios
Current service uses published schedules. Calculated through-running and custom scenarios retain that network. Schedule-preserving through-running analytically continues matched current trips without adding origin departures; declared frequency sensitivities add only the service stated in their cards and are not agency service plans. Every declared 4-, 8-, or custom-frequency pair stream applies its full assigned trains-per-hour rate at every retained eligible station in each line’s modeled corridor-side runtime set. This is an analytical convention, not a published stopping plan. Where current and analytical trains cover the same physical station pair, uniform passenger arrivals and an assumed evenly spaced pooled headway produce a half-headway wait of 30 divided by the sum of trains per hour; this is not timetable-derived. Pooled generalized time combines that wait with the frequency-weighted itinerary cost before the initial-wait term, including modeled running time, transfer wait, and transfer penalty, then takes the minimum across current-only, each analytical stream, all analytical streams pooled, and current-plus-analytical pooled choices. A pooled current-plus-analytical first-arrival choice can mix one-seat and transfer trips; the mixed pool is not counted as a categorical transfer removal, and expected transfers per accepted trip is reported instead. Schedule-preserving all-one-seat continuations retain their transfer-removal result. Documented operator aliases are collapsed to one physical station, and same-physical origin-destination pairs are excluded as non-trips. Penn Station Access 2027 and 2030 are non-calculated official reference states: their service envelopes and station sites are shown, while tract and origin-destination accessibility remain unavailable. Within a calculated combination, an unlisted tract is a calculated zero; an unlisted combination remains unavailable.