LIRR 7768 Penn Station → Babylon
Alerts for train 7768
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line LIRR.
Train 7768 Penn Station–Babylon: final delay under 3 min on 4 of its 4 runs with data in the last 30 days (100%). TrainsRadar data as of 22 Nov 2026, 02:05 (GMT-5).
An alert on this phone or computer when the 7768 is 5 min or more late, every day it runs. No account, no email.
It does not run today
Last recorded run: Tuesday 17 November +2 min
Next service: tomorrow 08:49 from Penn Station · Mon 23 Nov
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
- Sun 30 Aug Max en route +9 min · last fix heading to 216 +7 min
- Sun 20 Sept Max en route +7 min · last fix heading to 216 +5 min
Distribution · 90 days
12 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 25% · 3
- On time 58% · 7
- 3–10 min 17% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=3
- 100% T n=1
- — W n=0
- — T n=0
- 100% F n=1
- 100% S n=4
- 33% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (16 stops).
Last 90 days, 12 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 08:49 | on time | +2 min | |
| 09:01 | ≈ on time | ≈ +1 min | |
| 09:08 / 09:10 | ≈ on time | ≈ +2 min | |
| 09:25 | ≈ on time | ≈ +4 min | |
| 09:28 | ≈ on time | ≈ +4 min | |
| 09:31 | ≈ +1 min | ≈ +4 min | |
| 09:34 | ≈ on time | ≈ +4 min | |
| 09:37 | ≈ on time | ≈ +4 min | |
| 09:40 | ≈ on time | ≈ +4 min | |
| 09:43 | ≈ on time | ≈ +4 min | |
| 09:45 | ≈ on time | ≈ +5 min | |
| 09:47 | ≈ on time | ≈ +5 min | |
| 09:50 | ≈ on time | ≈ +5 min | |
| 09:53 | ≈ on time | ≈ +5 min | |
| 09:56 | ≈ on time | ≈ +5 min | |
| 10:02 | on time | +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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 17 Nov | Amityville 10:42Partial coverage | +2 min | +8 min |
| Mon 16 Nov | Ronkonkoma 19:18 | −3 min | +4 min |
| Sat 7 Nov | Babylon 18:26 | 0 min | +3 min |
| Fri 6 Nov | Babylon 19:16 | −2 min | +2 min |
| Mon 19 Oct | West Hempstead 18:14 | −1 min | +2 min |
| Sun 20 Sept | 216 23:21 | +5 min | +7 min |
| Sat 19 Sept | 216 23:18 | +1 min | +2 min |
| Mon 7 Sept | 216 23:19 | +3 min | +4 min |
| Sun 6 Sept | 216 23:17 | 0 min | +2 min |
| Sat 5 Sept | 216 23:15 | 0 min | +2 min |
| Sun 30 Aug | 216 23:26 | +7 min | +9 min |
| Sat 29 Aug | 216 23:17 | +1 min | +3 min |