E135 E135 Howth → Greystones

View line E135

Howth 20:42 → Greystones 22:09 Sun 1 h 27 min · 29 stops Iarnród Éireann

Train E135 Howth–Greystones: final delay under 3 min on 3 of its 4 runs with data in the last 30 days (75%). Running now, on time. Expected at Greystones: 22:09. TrainsRadar data as of 22 Nov 2026, 20:46 (UTC).

Running now · updated 20:45

Heading to Greystones 0 min

Estimated arrival at Greystones 22:09 · 65 km/h

  1. Howth20:42
  2. Raheny20:54
  3. Connolly21:07
  4. Sandymount21:19
  5. Salthill and Monkstown21:30
  6. Dalkey21:40
  7. Greystones22:09
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
70%
7/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

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 15 Nov Max en route +10 min · last fix heading to — +8 min
  • Sun 27 Sept Max en route +3 min · last fix heading to — +3 min
  • Sun 30 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 70% · 7
  • 3–10 min 30% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • 70% S n=10

Stops and timetable

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

Last 90 days, 10 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
20:42on time +1 min
20:45≈ on time ≈ +1 min
20:47≈ on time ≈ +1 min
20:50≈ on time ≈ +1 min
20:52≈ on time ≈ +1 min
20:54 / 20:55≈ on time ≈ +1 min
20:56 / 20:57≈ on time ≈ +1 min
20:58 / 20:59≈ on time ≈ +1 min
21:02≈ on time ≈ +1 min
21:07 / 21:08≈ on time ≈ +1 min
21:10 / 21:11≈ on time ≈ +1 min
21:12 / 21:13≈ +1 min ≈ +1 min
21:14 / 21:15≈ +1 min ≈ +1 min
21:17 / 21:18≈ +1 min ≈ +1 min
21:19 / 21:20≈ +1 min ≈ +2 min
21:22≈ +1 min ≈ +2 min
21:24 / 21:25≈ +1 min ≈ +2 min
21:26 / 21:27≈ +1 min ≈ +2 min
21:28 / 21:29≈ +1 min ≈ +2 min
21:30 / 21:31≈ +1 min ≈ +2 min
21:33≈ +1 min ≈ +2 min
21:36≈ +1 min ≈ +2 min
21:38≈ +1 min ≈ +2 min
21:40 / 21:41≈ +1 min ≈ +2 min
21:45≈ +1 min ≈ +3 min
21:48≈ +1 min ≈ +3 min
21:51≈ +1 min ≈ +3 min
21:56 / 21:57≈ +1 min ≈ +3 min
22:09+1 min +4 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— 20:440 min—
Sun 15 Nov— 22:09+8 min+10 min
Sun 8 Nov— 22:02+1 min+3 min
Sun 1 Nov— 22:02+1 min+3 min
Sun 18 Oct— 22:180 min+3 min
Sun 11 Oct— 22:19+1 min+4 min
Sun 27 Sept— 22:15+3 min+3 min
Sun 20 Sept— 22:17+1 min+1 min
Sun 6 Sept— 22:15+2 min+2 min
Sun 30 Aug— 22:15+3 min+3 min