E141 E141 Howth → Greystones

View line E141

Howth 22:41 → Greystones 00:08 Sat, Sun 1 h 27 min · 29 stops Iarnród Éireann

Train E141 Howth–Greystones: final delay under 3 min on 5 of its 7 runs with data in the last 30 days (71%). Median final delay: 0 min. Running now, 8 min late. Expected at Greystones: 00:16. TrainsRadar data as of 22 Nov 2026, 23:00 (UTC).

Running now · updated 23:00

Heading to Greystones +8 min

Estimated arrival at Greystones 00:16 00:08

  1. Howth22:41
  2. Raheny22:53
  3. Connolly23:06
  4. Sandymount23:18
  5. Salthill and Monkstown23:29
  6. Dalkey23:39
  7. Greystones00:08

Today it is running worse than usual: typical arrival delay is 0 min; 71% of the last 7 runs arrived on time.

On-time · 30 days
71%
5/7 runs under 3 min
RT coverage: 7 full · 0 partial · 0 no data
On-time · 90 days
77%
10/13 runs under 3 min
RT coverage: 13 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +7 min

Last 30 days

Arrival delay at Greystones, 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 22 Nov Max en route +8 min · last fix heading to — +8 min
  • Sun 8 Nov Max en route +9 min · last fix heading to — +6 min
  • Sun 6 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 77% · 10
  • 3–10 min 23% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 100% S n=1
  • 73% S n=11

Stops and timetable

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

Last 90 days, 13 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 10Today
22:41on time on time
22:44≈ on time ≈ on time
22:46≈ on time ≈ on time
22:49≈ on time ≈ +1 min
22:51≈ on time ≈ +1 min
22:53 / 22:54≈ on time ≈ +1 min
22:55 / 22:56≈ on time ≈ +1 min
22:57 / 22:58≈ on time ≈ +1 min
23:01≈ on time ≈ +1 min
23:06 / 23:07≈ +1 min ≈ +2 min
23:09 / 23:10≈ +1 min ≈ +2 min
23:11 / 23:12≈ +1 min ≈ +2 min
23:13 / 23:14≈ +1 min ≈ +2 min
23:16 / 23:17≈ +1 min ≈ +2 min
23:18 / 23:19≈ +1 min ≈ +2 min
23:21≈ +1 min ≈ +3 min
23:23 / 23:24≈ +1 min ≈ +3 min
23:25 / 23:26≈ +1 min ≈ +3 min
23:27 / 23:28≈ +1 min ≈ +3 min
23:29 / 23:30≈ +1 min ≈ +3 min
23:32≈ +1 min ≈ +3 min
23:35≈ +1 min ≈ +3 min
23:37≈ +1 min ≈ +4 min
23:39 / 23:40≈ +1 min ≈ +4 min
23:44≈ +1 min ≈ +4 min
23:47≈ +2 min ≈ +4 min
23:50≈ +2 min ≈ +4 min
23:55 / 23:56≈ +2 min ≈ +5 min
00:08+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 11 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 22 Nov— 22:59+8 min+8 min
Sun 15 Nov— 00:02+2 min+6 min
Sun 8 Nov— 00:04+6 min+9 min
Sun 1 Nov— 23:590 min+1 min
Mon 26 Oct— 11:000 min—
Sun 25 Oct— 11:000 min—
Sat 24 Oct— 09:210 min—
Sun 18 Oct— 00:15+2 min+2 min
Sun 11 Oct— 00:180 min+3 min
Sun 27 Sept— 00:15+2 min+3 min
Sun 20 Sept— 00:15+1 min+6 min
Sun 6 Sept— 00:13+4 min+4 min
Sun 30 Aug— 00:19+2 min+4 min