A520 A520 Dublin Heuston – Waterford (Plunkett)

View line A520

Dublin Heuston 16:05 → Waterford (Plunkett) 17:54 Fri 1 h 49 min · 4 stops Iarnród Éireann

It does not run today

Last recorded run: Friday 13 November +4 min

Next service: tomorrow 16:05 from Dublin Heuston · Fri 20 Nov

Next departure 16:05 tomorrow · Dublin Heuston
On-time · 30 days
0%
0/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
25%
3/12 runs under 3 min
RT coverage: 12 full · 0 partial · 0 no data
Typical delay
+6min
Median at arrival, 90 days
P90
+9min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Waterford (Plunkett), 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 30 Oct Max en route +21 min · last fix heading to — +20 min
  • Fri 16 Oct Max en route +10 min · last fix heading to — +9 min
  • Fri 11 Sept Max en route +10 min · last fix heading to — +8 min
  • Fri 6 Nov Max en route +8 min · last fix heading to — +7 min
  • Fri 4 Sept Max en route +8 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 25% · 3
  • 3–10 min 67% · 8
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 25% F n=12
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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.

StopSched.Usually 9 days in 10
16:05+2 min +3 min
16:46≈ +3 min ≈ +5 min
16:59 / 17:00≈ +3 min ≈ +5 min
17:54+6 min +9 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
Fri 13 Nov— 18:07+4 min+5 min
Fri 6 Nov— 18:09+7 min+8 min
Fri 30 Oct— 18:24+20 min+21 min
Fri 23 Oct— 18:09+6 min+8 min
Fri 16 Oct— 18:12+9 min+10 min
Fri 9 Oct— 18:07+3 min+6 min
Fri 2 Oct— 18:05+2 min+4 min
Fri 25 Sept— 18:030 min+5 min
Fri 18 Sept— 18:06+2 min+4 min
Fri 11 Sept— 18:12+8 min+10 min
Fri 4 Sept— 18:11+7 min+8 min
Fri 28 Aug— 18:09+5 min+6 min