A485 A485 Galway (Ceannt) – Limerick (Colbert)

View line A485

Galway (Ceannt) 13:45 → Limerick (Colbert) 15:42 Mon, Tue, Wed, Thu, Fri, Sat 1 h 57 min · 9 stops Iarnród Éireann

It has not run yet today

Last recorded run: Saturday 31 October 0 min

Next service: today 13:45 from Galway (Ceannt) · Mon 9 Nov

Next departure 13:45 today · Galway (Ceannt)
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 14 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 50 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 Limerick (Colbert), 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

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

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

On-time by weekday

  • — M n=0
  • 100% T n=4
  • 100% W n=2
  • 100% T n=4
  • 100% F n=4
  • 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, 20 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
13:45on time on time
13:56≈ on time ≈ on time
14:07 / 14:10≈ on time ≈ on time
14:19≈ on time ≈ on time
14:28≈ on time ≈ on time
14:37≈ on time ≈ on time
15:00 / 15:01≈ on time ≈ on time
15:18≈ on time ≈ on time
15:42on 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
Sat 31 Oct— 15:510 min—
Fri 30 Oct— 13:54No data—
Thu 29 Oct— 13:54No data—
Wed 28 Oct— 13:54No data—
Tue 27 Oct— 15:510 min—
Mon 26 Oct— 13:54No data—
Sat 24 Oct— 15:090 min—
Fri 23 Oct— 13:54No data—
Thu 22 Oct— 15:510 min—
Wed 21 Oct— 13:54No data—
Tue 20 Oct— 13:55No data—
Mon 19 Oct— 13:54No data—
Sat 17 Oct— 13:54No data—
Fri 16 Oct— 13:54No data—
Thu 15 Oct— 13:54No data—
Wed 14 Oct— 13:54No data—
Tue 13 Oct— 13:54No data—
Mon 12 Oct— 13:54No data—
Sat 10 Oct— 15:510 min—
Fri 9 Oct— 13:54No data—
Thu 8 Oct— 15:510 min—
Wed 7 Oct— 15:510 min—
Tue 6 Oct— 13:54No data—
Mon 5 Oct— 13:54No data—
Sat 3 Oct— 13:54No data—
Fri 2 Oct— 13:54No data—
Thu 1 Oct— 13:54No data—
Wed 30 Sept— 13:54No data—
Tue 29 Sept— 15:510 min—
Mon 28 Sept— 13:54No data—