A483 A483 Galway (Ceannt) – Limerick (Colbert)

View line A483

Galway (Ceannt) 10:25 → Limerick (Colbert) 12:22 Mon, Tue, Wed, Thu, Fri, Sat 1 h 57 min · 9 stops Iarnród Éireann

✓ Today’s run finished

Today, last fix heading to — at 12:29 0 min

  1. Galway (Ceannt)10:25
  2. Oranmore10:32
  3. Craughwell11:00
  4. Ardrahan11:08
  5. Gort11:17
  6. Sixmilebridge11:58
  7. Limerick (Colbert)12:22

Next service: tomorrow 10:25 from Galway (Ceannt) · Thu 19 Nov

Next departure 10:25 tomorrow · Galway (Ceannt)
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 8 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 33 full · 0 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
10:25on time on time
10:32≈ on time ≈ on time
10:44 / 10:50≈ on time ≈ on time
11:00≈ on time ≈ on time
11:08≈ on time ≈ on time
11:17≈ on time ≈ on time
11:41≈ on time ≈ on time
11:58≈ on time ≈ on time
12:22on 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
Wed 18 Nov— 12:290 min—
Thu 12 Nov— 12:070 min—
Thu 5 Nov— 12:290 min—
Wed 4 Nov— 12:290 min—
Tue 3 Nov— 12:290 min—
Mon 2 Nov— 12:290 min—
Sat 31 Oct— 11:00No data—
Fri 30 Oct— 10:34No data—
Thu 29 Oct— 10:34No data—
Wed 28 Oct— 10:34No data—
Tue 27 Oct— 12:310 min—
Mon 26 Oct— 10:34No data—
Sat 24 Oct— 11:510 min—
Fri 23 Oct— 10:34No data—
Thu 22 Oct— 10:34No data—
Wed 21 Oct— 10:34No data—
Tue 20 Oct— 12:310 min—
Mon 19 Oct— 12:310 min—
Sat 17 Oct— 10:34No data—
Fri 16 Oct— 10:34No data—
Thu 15 Oct— 10:34No data—
Wed 14 Oct— 12:310 min—
Tue 13 Oct— 12:310 min—
Mon 12 Oct— 10:34No data—
Sat 10 Oct— 10:34No data—
Fri 9 Oct— 10:34No data—
Thu 8 Oct— 12:310 min—
Wed 7 Oct— 10:34No data—
Tue 6 Oct— 10:34No data—
Mon 5 Oct— 12:310 min—