P813 P813 Hazelhatch and Celbridge – Connolly

View line P813

Hazelhatch and Celbridge 15:53 → Connolly 16:32 Mon, Tue, Wed, Thu, Fri 0 h 39 min · 7 stops Iarnród Éireann

It does not run today

Last recorded run: Friday 6 November +2 min

Next service: tomorrow 15:53 from Hazelhatch and Celbridge · Mon 9 Nov

Next departure 15:53 tomorrow · Hazelhatch and Celbridge
On-time · 30 days
26%
5/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
22%
14/63 runs under 3 min
RT coverage: 63 full · 0 partial · 0 no data
Typical delay
+4min
Median at arrival, 90 days
30 days: +5 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +8 min

Last 30 days

Arrival delay at Connolly, 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 19 Oct Max en route +14 min · last fix heading to — +14 min
  • Tue 3 Nov Max en route +8 min · last fix heading to — +8 min
  • Fri 30 Oct Max en route +8 min · last fix heading to — +8 min
  • Mon 12 Oct Max en route +8 min · last fix heading to — +8 min
  • Mon 28 Sept Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 22% · 14
  • 3–10 min 76% · 48
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 9% M n=11
  • 38% T n=13
  • 31% W n=13
  • 15% T n=13
  • 15% F n=13
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 63 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
15:53on time +2 min
15:57 / 15:58≈ +1 min ≈ +2 min
16:01 / 16:02≈ +1 min ≈ +3 min
16:05 / 16:06≈ +2 min ≈ +3 min
16:09 / 16:10≈ +2 min ≈ +4 min
16:24 / 16:25≈ +3 min ≈ +6 min
16:32+4 min +7 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
Fri 6 Nov— 16:29+2 min+2 min
Thu 5 Nov— 16:29+3 min+3 min
Wed 4 Nov— 16:29+3 min+3 min
Tue 3 Nov— 16:34+8 min+8 min
Mon 2 Nov— 16:32+5 min+5 min
Fri 30 Oct— 16:49+8 min+8 min
Thu 29 Oct— 16:46+5 min+7 min
Wed 28 Oct— 16:46+4 min+4 min
Tue 27 Oct— 16:49+7 min+7 min
Fri 23 Oct— 16:48+6 min+6 min
Thu 22 Oct— 16:46+4 min+4 min
Wed 21 Oct— 16:43+1 min+2 min
Tue 20 Oct— 16:47+5 min+5 min
Mon 19 Oct— 16:56+14 min+14 min
Fri 16 Oct— 16:48+6 min+7 min
Thu 15 Oct— 16:44+2 min+3 min
Wed 14 Oct— 16:43+1 min+3 min
Tue 13 Oct— 16:43+1 min+4 min
Mon 12 Oct— 16:50+8 min+8 min
Fri 9 Oct— 16:45+4 min+6 min
Thu 8 Oct— 16:47+6 min+6 min
Wed 7 Oct— 16:44+2 min+4 min
Tue 6 Oct— 16:44+2 min+3 min
Mon 5 Oct— 16:43+2 min+2 min
Fri 2 Oct— 16:45+4 min+5 min
Thu 1 Oct— 16:44+2 min+4 min
Wed 30 Sept— 16:46+4 min+5 min
Tue 29 Sept— 16:49+7 min+7 min
Mon 28 Sept— 16:50+8 min+8 min
Fri 25 Sept— 16:49+7 min+7 min