LIRR 6265 Babylon → Grand Central

View line LIRR

Babylon 18:38 → Grand Central 19:51 Thu, Sat, Sun 1 h 13 min · 16 stops Metro-North Railroad

Train 6265 Babylon–Grand Central: final delay under 3 min on 6 of its 9 runs with data in the last 90 days (67%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 08:12 (GMT-5).

It has not run yet today

Last recorded run: Sunday 27 September −3 min

Next service: today 18:38 from Babylon · Sun 22 Nov

Next departure 18:38 today · Babylon
On-time · 30 days
—
Too little data (0/0 runs with data)
RT coverage: 0 full · 0 partial · 0 no data
On-time · 90 days
67%
6/9 runs under 3 min
RT coverage: 7 full · 2 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+6min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Grand Central, in minutes. One bar per run.

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

Worst days

  • Sat 19 Sept Max en route +9 min · last fix heading to 349 +7 min
  • Mon 7 Sept Max en route +9 min · last fix heading to 349 +6 min
  • Sat 5 Sept Max en route +8 min · last fix heading to 349 +5 min

Distribution · 90 days

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

  • Early 22% · 2
  • On time 44% · 4
  • 3–10 min 33% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 50% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 9 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
18:38on time +3 min
18:44≈ +1 min ≈ +3 min
18:47≈ +1 min ≈ +3 min
18:49≈ +1 min ≈ +3 min
18:51≈ +1 min ≈ +3 min
18:53≈ +1 min ≈ +3 min
18:56≈ +1 min ≈ +3 min
18:59≈ +1 min ≈ +4 min
19:02≈ +1 min ≈ +4 min
19:05≈ +1 min ≈ +4 min
19:08≈ +1 min ≈ +4 min
19:11≈ +1 min ≈ +4 min
19:14≈ +1 min ≈ +4 min
19:16≈ +1 min ≈ +4 min
19:29 / 19:31≈ +1 min ≈ +5 min
19:51+2 min +6 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
Sun 27 Sept349 20:27Partial coverage−3 min+2 min
Sat 26 Sept349 20:27Partial coverage−1 min+4 min
Sun 20 Sept349 20:060 min+3 min
Sat 19 Sept349 20:06+7 min+9 min
Mon 7 Sept349 20:07+6 min+9 min
Sun 6 Sept349 20:070 min+3 min
Sat 5 Sept349 20:06+5 min+8 min
Sun 30 Aug349 20:06−1 min+3 min
Sat 29 Aug349 20:05+2 min+3 min