A786 A786 Limerick (Colbert) – Galway (Ceannt)

View line A786

Limerick (Colbert) 14:20 → Galway (Ceannt) 16:16 Mon, Tue, Wed, Thu, Fri, Sat 1 h 56 min · 9 stops Iarnród Éireann

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 14:20 from Limerick (Colbert) · Mon 16 Nov

Next departure 14:20 today · Limerick (Colbert)
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 11 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Galway (Ceannt), in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 21
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • — T n=0
  • 100% W n=4
  • 100% T n=3
  • 100% F n=3
  • 100% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 21 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
14:20on time on time
14:41≈ on time ≈ on time
14:59 / 15:02≈ on time ≈ on time
15:24≈ on time ≈ on time
15:33≈ on time ≈ on time
15:42≈ on time ≈ on time
15:53 / 15:56≈ on time ≈ on time
16:07≈ on time ≈ on time
16:16on time on time

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— 16:240 min—
Thu 12 Nov— 16:240 min—
Mon 9 Nov— 16:240 min—
Sat 31 Oct— 14:29No data—
Fri 30 Oct— 14:29No data—
Thu 29 Oct— 14:29No data—
Wed 28 Oct— 14:29No data—
Tue 27 Oct— 14:29No data—
Mon 26 Oct— 15:12No data—
Sat 24 Oct— 15:12No data—
Fri 23 Oct— 14:29No data—
Thu 22 Oct— 14:29No data—
Wed 21 Oct— 16:250 min—
Tue 20 Oct— 14:29No data—
Mon 19 Oct— 14:29No data—
Sat 17 Oct— 15:12No data—
Fri 16 Oct— 14:29No data—
Thu 15 Oct— 14:29No data—
Wed 14 Oct— 14:29No data—
Tue 13 Oct— 14:29No data—
Mon 12 Oct— 14:29No data—
Sat 10 Oct— 16:250 min—
Fri 9 Oct— 14:29No data—
Thu 8 Oct— 16:250 min—
Wed 7 Oct— 16:250 min—
Tue 6 Oct— 14:29No data—
Mon 5 Oct— 16:220 min—
Sat 3 Oct— 16:250 min—
Fri 2 Oct— 14:29No data—
Thu 1 Oct— 14:29No data—