A412 A412 Dublin Heuston – Limerick (Colbert)

View line A412

Dublin Heuston 17:25 → Limerick (Colbert) 19:42 Mon, Tue, Wed, Thu, Fri, Sat 2 h 17 min · 8 stops Iarnród Éireann

It has not run yet today

Last recorded run: Wednesday 4 November +11 min

Next service: today 17:25 from Dublin Heuston · Thu 5 Nov

Next departure 17:25 today · Dublin Heuston
On-time · 30 days
46%
11/24 runs under 3 min
RT coverage: 24 full · 0 partial · 0 no data
On-time · 90 days
42%
30/72 runs under 3 min
RT coverage: 72 full · 0 partial · 0 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +3 min
P90
+11min
9 in 10 runs arrive with less than this
30 days: +10 min

Last 30 days

Arrival delay at Limerick (Colbert), in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 14 Sept Max en route +39 min · last fix heading to — +31 min
  • Wed 12 Aug Max en route +27 min · last fix heading to — +25 min
  • Sat 24 Oct Max en route +22 min · last fix heading to — +22 min
  • Tue 1 Sept Max en route +22 min · last fix heading to — +22 min
  • Wed 4 Nov Max en route +11 min · last fix heading to — +11 min

Distribution · 90 days

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

  • Early 1% · 1
  • On time 40% · 29
  • 3–10 min 44% · 32
  • 10–30 min 13% · 9
  • 30+ min 1% · 1

On-time by weekday

  • 31% M n=13
  • 31% T n=13
  • 46% W n=13
  • 42% T n=12
  • 50% F n=12
  • 56% S n=9
  • — S n=0

Stops and timetable

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

Last 90 days, 72 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
17:25+2 min +6 min
17:55≈ +3 min ≈ +6 min
18:07≈ +3 min ≈ +7 min
18:20≈ +2 min ≈ +7 min
18:34≈ +3 min ≈ +8 min
18:45≈ +3 min ≈ +8 min
18:54≈ +3 min ≈ +8 min
19:42+3 min +11 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
Wed 4 Nov— 20:03+11 min+11 min
Tue 3 Nov— 19:59+9 min+9 min
Mon 2 Nov— 19:44−4 min+3 min
Fri 30 Oct— 19:54+2 min+10 min
Thu 29 Oct— 20:01+9 min+10 min
Wed 28 Oct— 19:59+7 min+10 min
Tue 27 Oct— 20:03+11 min+14 min
Mon 26 Oct— 19:23+1 min+4 min
Sat 24 Oct— 19:45+22 min+22 min
Fri 23 Oct— 19:48+3 min+3 min
Thu 22 Oct— 19:49+2 min+5 min
Wed 21 Oct— 19:57+5 min+9 min
Tue 20 Oct— 19:56+4 min+7 min
Mon 19 Oct— 19:53+1 min+13 min
Sat 17 Oct— 19:220 min+3 min
Fri 16 Oct— 19:50+1 min+6 min
Thu 15 Oct— 19:510 min+7 min
Wed 14 Oct— 19:52+1 min+6 min
Tue 13 Oct— 19:510 min+6 min
Mon 12 Oct— 19:47+3 min+4 min
Sat 10 Oct— 19:49+2 min+4 min
Fri 9 Oct— 19:56+5 min+9 min
Thu 8 Oct— 19:47+3 min+7 min
Wed 7 Oct— 19:59+7 min+12 min
Tue 6 Oct— 19:47+4 min+9 min
Mon 5 Oct— 19:48+3 min+6 min
Sat 3 Oct— 19:46+4 min+5 min
Fri 2 Oct— 19:510 min+5 min
Thu 1 Oct— 19:53+1 min+6 min
Wed 30 Sept— 19:50+1 min+5 min