WIL 811 Long Beach – Grand Central
Alerts for train 811
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line WIL.
It does not run today
Last recorded run: Thursday 29 October +4 min
Next service: Monday 05:48 from Long Beach · Mon 9 Nov
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
- Fri 4 Sept Max en route +10 min · last fix heading to 349 +9 min
- Thu 29 Oct Max en route +10 min · last fix heading to septa-rail:90205 +4 min
- Thu 27 Aug Max en route +4 min · last fix heading to 349 +3 min
Distribution · 90 days
38 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 24% · 9
- On time 68% · 26
- 3–10 min 8% · 3
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=6
- 100% T n=7
- 100% W n=8
- 78% T n=9
- 88% F n=8
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (10 stops).
Last 90 days, 38 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 |
|---|---|---|---|
| 05:48 | +2 min | +2 min | |
| 05:55 | ≈ +1 min | ≈ +2 min | |
| 05:59 | ≈ +1 min | ≈ +2 min | |
| 06:01 | ≈ +1 min | ≈ +2 min | |
| 06:03 | ≈ +1 min | ≈ +2 min | |
| 06:06 | ≈ +1 min | ≈ +2 min | |
| 06:09 | ≈ +1 min | ≈ +2 min | |
| 06:23 / 06:24 | ≈ on time | ≈ +1 min | |
| 06:29 | ≈ on time | ≈ +2 min | |
| 06:43 | on time | +2 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 |
|---|---|---|---|
| Thu 29 Oct | septa-rail:90205 16:42Partial coverage | +4 min | +10 min |
| Fri 2 Oct | 349 07:22 | −1 min | +2 min |
| Thu 1 Oct | 349 07:23 | 0 min | +3 min |
| Wed 30 Sept | 349 07:22 | +1 min | +2 min |
| Tue 29 Sept | 349 07:22 | −1 min | +2 min |
| Mon 28 Sept | 349 07:21 | +2 min | +3 min |
| Fri 25 Sept | 349 07:22 | −1 min | +2 min |
| Thu 24 Sept | 349 07:22 | −1 min | +2 min |
| Wed 23 Sept | 349 07:23 | 0 min | +3 min |
| Tue 22 Sept | 349 07:23 | −1 min | +2 min |
| Mon 21 Sept | 349 07:22 | −1 min | +2 min |
| Fri 18 Sept | 349 07:22 | +2 min | +5 min |
| Thu 17 Sept | 349 07:21 | −1 min | +3 min |
| Wed 16 Sept | 349 07:21 | 0 min | +4 min |
| Fri 11 Sept | 349 07:22 | 0 min | +3 min |
| Thu 10 Sept | 349 07:22 | +1 min | +4 min |
| Wed 9 Sept | 349 07:22 | 0 min | +3 min |
| Tue 8 Sept | 349 07:22 | 0 min | +4 min |
| Fri 4 Sept | 349 07:21 | +9 min | +10 min |
| Thu 3 Sept | 349 07:21 | 0 min | +3 min |
| Wed 2 Sept | 349 07:21 | +1 min | +5 min |
| Tue 1 Sept | 349 07:23 | −1 min | +2 min |
| Mon 31 Aug | 349 07:23 | −1 min | +2 min |
| Fri 28 Aug | 349 07:22 | 0 min | +3 min |
| Thu 27 Aug | 349 07:22 | +3 min | +4 min |
| Wed 26 Aug | 349 07:22 | −1 min | +2 min |
| Tue 25 Aug | 349 07:22 | +1 min | +5 min |
| Mon 24 Aug | 349 07:21 | −1 min | +2 min |
| Fri 21 Aug | 349 07:21 | 0 min | +3 min |
| Thu 20 Aug | 349 07:23 | 0 min | +3 min |