FOX 276 Grand Central – Babylon

View line FOX

Grand Central 19:08 → Babylon 20:22 Mon, Tue, Wed, Thu, Fri 1 h 14 min · 16 stops SEPTA

It has not run yet today

Last recorded run: Monday 9 November +6 min

Next service: today 19:08 from Grand Central · Tue 10 Nov

Next departure 19:08 today · Grand Central
On-time · 30 days
38%
5/13 runs under 3 min
RT coverage: 12 full · 1 partial · 0 no data
On-time · 90 days
81%
39/48 runs under 3 min
RT coverage: 47 full · 1 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: +4 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Babylon, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 15 Oct Max en route +16 min · last fix heading to septa-rail:90005 +16 min
  • Thu 29 Oct Max en route +14 min · last fix heading to septa-rail:1 +10 min
  • Wed 28 Oct Max en route +16 min · last fix heading to septa-rail:1 +8 min
  • Thu 5 Nov Max en route +10 min · last fix heading to septa-rail:1 +7 min
  • Mon 9 Nov Max en route +29 min · last fix heading to septa-rail:1 +6 min

Distribution · 90 days

48 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 50% · 24
  • On time 31% · 15
  • 3–10 min 15% · 7
  • 10–30 min 4% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 89% T n=9
  • 80% W n=10
  • 73% T n=11
  • 90% F n=10
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (16 stops).

Last 90 days, 48 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.

StopSched.Usually 9 days in 10
19:08+1 min +3 min
19:20≈ +1 min ≈ +3 min
19:28 / 19:29≈ +1 min ≈ +3 min
19:44≈ on time ≈ +3 min
19:47≈ on time ≈ +3 min
19:50≈ on time ≈ +3 min
19:53≈ on time ≈ +4 min
19:56≈ on time ≈ +4 min
19:59≈ on time ≈ +4 min
20:03≈ on time ≈ +4 min
20:05≈ on time ≈ +4 min
20:07≈ 1 min early ≈ +4 min
20:10≈ 1 min early ≈ +4 min
20:13≈ 1 min early ≈ +4 min
20:16≈ 1 min early ≈ +5 min
20:221 min early +5 min

Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 10 July 2026.

Will I make my connection?

Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.

Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.

Recent runs

DateLast stopFinalMax
Mon 9 Novsepta-rail:1 13:26Partial coverage+6 min+29 min
Fri 6 Novsepta-rail:90300 17:16+3 min+12 min
Thu 5 Novsepta-rail:1 00:47+7 min+10 min
Wed 4 Novsepta-rail:90302 19:58+6 min+13 min
Tue 3 Novsepta-rail:90007 19:560 min+22 min
Mon 2 Novsepta-rail:90007 20:280 min+5 min
Fri 30 Octsepta-rail:90417 23:560 min+9 min
Thu 29 Octsepta-rail:1 18:41+10 min+14 min
Wed 28 Octsepta-rail:1 23:42+8 min+16 min
Tue 20 Octsepta-rail:90007 23:130 min+19 min
Mon 19 Octsepta-rail:90007 19:35+4 min+22 min
Thu 15 Octsepta-rail:90005 18:49+16 min+16 min
Wed 14 Octsepta-rail:90815 22:050 min+3 min
Fri 2 Oct27 21:12−1 min+4 min
Thu 1 Oct27 21:08+1 min+4 min
Wed 30 Sept27 21:080 min+5 min
Tue 29 Sept8 21:11+1 min+2 min
Mon 28 Sept27 21:080 min+4 min
Fri 25 Sept27 21:08−1 min+1 min
Thu 24 Sept27 21:06−3 min+3 min
Wed 23 Sept27 20:57−1 min+3 min
Tue 22 Sept8 21:06+4 min+4 min
Mon 21 Sept27 21:10+3 min+6 min
Fri 18 Sept27 21:16−3 min+3 min
Thu 17 Sept27 21:10−3 min+4 min
Wed 16 Sept8 21:120 min+1 min
Tue 15 Sept27 21:080 min+4 min
Fri 11 Sept8 21:13−1 min+7 min
Thu 10 Sept27 21:07−1 min+2 min
Wed 9 Sept27 21:06−3 min+3 min