LIRR 2810 Atlantic Terminal – Jamaica

View line LIRR

Atlantic Terminal 01:56 → Jamaica 02:17 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 0 min

Next service: tomorrow 01:56 from Atlantic Terminal · Tue 10 Nov

Next departure 01:56 tomorrow · 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%
32/33 runs under 3 min
RT coverage: 17 full · 16 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+2min
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

  • Mon 24 Aug Max en route +4 min · last fix heading to 102 +4 min

Distribution · 90 days

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

  • Early 27% · 9
  • On time 70% · 23
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=6
  • 100% W n=7
  • 100% 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, 33 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
01:56+1 min +3 min
02:03≈ on time ≈ +2 min
02:08≈ on time ≈ +1 min
02:171 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 02:47Partial coverage0 min—
Thu 1 Oct102 02:48Partial coverage−2 min+1 min
Wed 30 Sept102 02:48Partial coverage−1 min—
Tue 29 Sept102 02:47Partial coverage−1 min—
Mon 28 Sept102 02:47Partial coverage0 min—
Fri 25 Sept102 02:57Partial coverage+2 min+4 min
Thu 24 Sept102 02:47Partial coverage−2 min+3 min
Wed 23 Sept102 02:47Partial coverage0 min—
Tue 22 Sept102 02:48Partial coverage−1 min—
Fri 18 Sept102 02:49Partial coverage+2 min+2 min
Thu 17 Sept102 02:47Partial coverage−1 min+2 min
Wed 16 Sept102 02:47Partial coverage−1 min—
Fri 11 Sept102 02:46Partial coverage−1 min+6 min
Thu 10 Sept102 02:49Partial coverage+2 min+3 min
Wed 9 Sept102 02:47Partial coverage−1 min+1 min
Tue 8 Sept102 02:53Partial coverage−1 min+2 min
Fri 4 Sept102 02:47−1 min—
Thu 3 Sept102 02:47−1 min+3 min
Wed 2 Sept102 02:470 min—
Tue 1 Sept102 02:48−1 min—
Mon 31 Aug102 02:47−1 min—
Fri 28 Aug102 02:47−1 min+1 min
Thu 27 Aug102 02:470 min+2 min
Wed 26 Aug102 02:47−1 min+2 min
Tue 25 Aug102 02:47−1 min+3 min
Mon 24 Aug102 02:54+4 min+4 min
Fri 21 Aug102 02:470 min—
Thu 20 Aug102 02:47−1 min—
Wed 19 Aug102 02:47−1 min—
Tue 18 Aug102 02:47−1 min—