A463 A463 Limerick (Colbert) – Ballybrophy

View line A463

Limerick (Colbert) 17:10 → Ballybrophy 18:55 Mon, Tue, Wed, Thu, Fri, Sat 1 h 45 min · 7 stops Iarnród Éireann

It has not run yet today

Last recorded run: Monday 2 November 0 min

Next service: tomorrow 17:10 from Limerick (Colbert) · Sat 7 Nov

Next departure 17:10 tomorrow · Limerick (Colbert)
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 16 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 53 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 Ballybrophy, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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:10on time on time
17:30≈ on time ≈ on time
17:38 / 17:39≈ on time ≈ on time
18:02 / 18:03≈ on time ≈ on time
18:18 / 18:19≈ on time ≈ on time
18:35 / 18:36≈ on time ≈ on time
18:55on 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
Mon 2 Nov— 19:040 min—
Sat 31 Oct— 17:19No data—
Fri 30 Oct— 17:19No data—
Thu 29 Oct— 19:040 min—
Wed 28 Oct— 17:19No data—
Tue 27 Oct— 17:19No data—
Fri 23 Oct— 17:19No data—
Thu 22 Oct— 17:19No data—
Wed 21 Oct— 17:19No data—
Tue 20 Oct— 17:19No data—
Mon 19 Oct— 17:19No data—
Fri 16 Oct— 17:19No data—
Thu 15 Oct— 19:040 min—
Wed 14 Oct— 17:19No data—
Tue 13 Oct— 17:19No data—
Mon 12 Oct— 17:19No data—
Sat 10 Oct— 17:19No data—
Fri 9 Oct— 17:19No data—
Thu 8 Oct— 17:19No data—
Wed 7 Oct— 17:19No data—
Tue 6 Oct— 17:19No data—
Mon 5 Oct— 19:040 min—
Sat 3 Oct— 16:24No data—
Fri 2 Oct— 17:19No data—
Thu 1 Oct— 17:19No data—
Wed 30 Sept— 17:19No data—
Tue 29 Sept— 17:19No data—
Mon 28 Sept— 17:19No data—
Sat 26 Sept— 17:39No data—
Fri 25 Sept— 17:19No data—