LIRR 2958 Atlantic Terminal – Jamaica

View line LIRR

Atlantic Terminal 18:59 → Jamaica 19:20 Mon, Tue, Wed, Thu, Fri 0 h 21 min · 4 stops Long Island Rail Road

It has not run yet today

Last recorded run: Friday 2 October −1 min

Next service: today 18:59 from Atlantic Terminal · Mon 9 Nov

Next departure 18:59 today · Atlantic Terminal
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
97%
35/36 runs under 3 min
RT coverage: 18 full · 18 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Jamaica, 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 3 Sept Max en route +20 min · last fix heading to 102 +19 min

Distribution · 90 days

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

  • Early 33% · 12
  • On time 64% · 23
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=7
  • 100% W n=8
  • 88% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 36 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:59+1 min +1 min
19:06≈ on time ≈ +1 min
19:11≈ 1 min early ≈ on time
19:201 min early on time

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
Fri 2 Oct102 19:49Partial coverage−1 min—
Thu 1 Oct102 19:50Partial coverage0 min+1 min
Wed 30 Sept102 19:50Partial coverage−1 min—
Tue 29 Sept102 19:50Partial coverage−1 min—
Mon 28 Sept102 19:50Partial coverage0 min—
Fri 25 Sept102 19:54Partial coverage−1 min—
Thu 24 Sept102 19:52Partial coverage+1 min+2 min
Wed 23 Sept102 19:50Partial coverage−1 min+2 min
Tue 22 Sept102 19:50Partial coverage+1 min+1 min
Mon 21 Sept102 19:49Partial coverage0 min—
Fri 18 Sept102 19:50Partial coverage0 min+1 min
Thu 17 Sept102 19:50Partial coverage−1 min—
Wed 16 Sept102 19:50Partial coverage−2 min—
Tue 15 Sept102 19:50Partial coverage−2 min—
Fri 11 Sept102 19:51Partial coverage+2 min+3 min
Thu 10 Sept102 19:51Partial coverage+2 min+3 min
Wed 9 Sept102 19:51Partial coverage0 min+1 min
Tue 8 Sept102 19:50Partial coverage0 min+2 min
Fri 4 Sept102 19:50−2 min—
Thu 3 Sept102 20:08+19 min+20 min
Wed 2 Sept102 19:50−1 min—
Tue 1 Sept102 19:500 min+1 min
Mon 31 Aug102 19:50−5 min—
Fri 28 Aug102 19:50−2 min—
Thu 27 Aug102 19:50−2 min—
Wed 26 Aug102 19:50−1 min—
Tue 25 Aug102 19:50−1 min+1 min
Mon 24 Aug102 19:50−2 min—
Fri 21 Aug102 19:51−2 min—
Thu 20 Aug102 19:50−1 min—