A410 A410 Dublin Heuston → Limerick (Colbert)

View line A410

Dublin Heuston 21:10 → Limerick (Colbert) 23:16 Daily 2 h 06 min · 7 stops Iarnród Éireann

Train A410 Dublin Heuston–Limerick (Colbert): final delay under 3 min on 3 of its 28 runs with data in the last 30 days (11%). Median final delay: +9 min. Running now, 4 min late. Expected at Limerick (Colbert): 23:20. TrainsRadar data as of 22 Nov 2026, 21:51 (UTC).

Running now · updated 21:51

Heading to Limerick (Colbert) +4 min

Estimated arrival at Limerick (Colbert) 23:20 23:16

  1. Dublin Heuston21:10
  2. Newbridge21:31
  3. Kildare21:38
  4. Portarlington21:50
  5. Portlaoise22:03
  6. Thurles22:30
  7. Limerick (Colbert)23:16

Today it is running no worse than usual: typical arrival delay is +9 min; 11% of the last 28 runs arrived on time.

On-time · 30 days
11%
3/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
22%
18/82 runs under 3 min
RT coverage: 82 full · 0 partial · 0 no data
Typical delay
+6min
Median at arrival, 90 days
30 days: +9 min
P90
+19min
9 in 10 runs arrive with less than this
30 days: +20 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 +71 min · last fix heading to — +70 min
  • Wed 26 Aug Max en route +51 min · last fix heading to — +45 min
  • Tue 1 Sept Max en route +44 min · last fix heading to — +44 min
  • Sun 8 Nov Max en route +25 min · last fix heading to — +24 min
  • Wed 18 Nov Max en route +23 min · last fix heading to — +23 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 22% · 18
  • 3–10 min 52% · 43
  • 10–30 min 22% · 18
  • 30+ min 4% · 3

On-time by weekday

  • 0% M n=11
  • 15% T n=13
  • 8% W n=13
  • 15% T n=13
  • 31% F n=13
  • 38% S n=8
  • 55% S n=11

Stops and timetable

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

Last 90 days, 82 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
21:10+1 min +9 min
21:31≈ +2 min ≈ +12 min
21:38≈ +3 min ≈ +12 min
21:50≈ +3 min ≈ +12 min
22:03≈ +4 min ≈ +11 min
22:30≈ +5 min ≈ +14 min
23:16+6 min +19 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— 21:49+6 min+6 min
Sat 21 Nov— 18:59+13 min+13 min
Fri 20 Nov— 19:08+19 min+20 min
Thu 19 Nov— 19:09+20 min+23 min
Wed 18 Nov— 19:12+23 min+23 min
Tue 17 Nov— 18:58+9 min+10 min
Mon 16 Nov— 19:09+20 min+20 min
Sun 15 Nov— 23:28+2 min+5 min
Sat 14 Nov— 19:04+17 min+17 min
Fri 13 Nov— 19:04+18 min+22 min
Thu 12 Nov— 19:04+16 min+16 min
Wed 11 Nov— 18:58+9 min+11 min
Tue 10 Nov— 18:59+11 min+12 min
Mon 9 Nov— 18:59+12 min+12 min
Sun 8 Nov— 23:49+24 min+25 min
Sat 7 Nov— 18:54+7 min+9 min
Fri 6 Nov— 18:57+9 min+9 min
Thu 5 Nov— 18:54+7 min+7 min
Wed 4 Nov— 19:02+13 min+14 min
Tue 3 Nov— 18:49+3 min+8 min
Mon 2 Nov— 18:52+3 min+9 min
Sun 1 Nov— 23:24+1 min+7 min
Fri 30 Oct— 18:54+6 min+9 min
Thu 29 Oct— 18:57+8 min+10 min
Wed 28 Oct— 18:52+3 min+7 min
Tue 27 Oct— 18:56+7 min+9 min
Sun 25 Oct— 23:02+2 min+5 min
Sat 24 Oct— 18:20+6 min+9 min
Fri 23 Oct— 18:51+2 min+5 min
Thu 22 Oct— 18:54+5 min+9 min