P663 P663 Maynooth – Dublin Pearse

View line P663

Maynooth 15:30 → Dublin Pearse 16:23 Mon, Tue, Wed, Thu, Fri 0 h 53 min · 14 stops Iarnród Éireann

✓ Today’s run finished

Today, last fix heading to — at 16:24 +3 min

  1. Maynooth15:30
  2. Leixlip(Confey)15:39
  3. Coolmine15:49
  4. Ashtown15:57
  5. Broombridge16:02
  6. Connolly16:15
  7. Dublin Pearse16:23

Next service: tomorrow 15:30 from Maynooth · Thu 5 Nov

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

Last 30 days

Arrival delay at Dublin Pearse, 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 +20 min · last fix heading to — +20 min
  • Fri 30 Oct Max en route +11 min · last fix heading to — +10 min
  • Mon 28 Sept Max en route +11 min · last fix heading to — +10 min
  • Tue 22 Sept Max en route +10 min · last fix heading to — +9 min
  • Fri 18 Sept Max en route +11 min · last fix heading to — +9 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 30% · 19
  • 3–10 min 65% · 41
  • 10–30 min 5% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 33% M n=12
  • 23% T n=13
  • 46% W n=13
  • 25% T n=12
  • 23% F n=13
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 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:30+1 min +2 min
15:36 / 15:37≈ +1 min ≈ +3 min
15:39≈ +1 min ≈ +3 min
15:45 / 15:46≈ +2 min ≈ +4 min
15:49 / 15:50≈ +2 min ≈ +4 min
15:52≈ +2 min ≈ +4 min
15:55≈ +2 min ≈ +5 min
15:57 / 15:58≈ +3 min ≈ +5 min
16:00≈ +3 min ≈ +5 min
16:02 / 16:03≈ +3 min ≈ +5 min
16:09≈ +3 min ≈ +7 min
16:15 / 16:17≈ +4 min ≈ +8 min
16:20 / 16:21≈ +4 min ≈ +8 min
16:23+4 min +9 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
Wed 4 Nov— 16:24+3 min+3 min
Tue 3 Nov— 16:24+3 min+3 min
Mon 2 Nov— 16:24+4 min+4 min
Fri 30 Oct— 16:42+10 min+11 min
Thu 29 Oct— 16:38+5 min+8 min
Wed 28 Oct— 16:39+6 min+8 min
Tue 27 Oct— 16:41+8 min+10 min
Fri 23 Oct— 16:41+8 min+9 min
Thu 22 Oct— 16:39+7 min+8 min
Wed 21 Oct— 16:35+2 min+2 min
Tue 20 Oct— 16:37+4 min+5 min
Mon 19 Oct— 16:53+20 min+20 min
Fri 16 Oct— 16:320 min+3 min
Thu 15 Oct— 16:35+3 min+4 min
Wed 14 Oct— 16:330 min+3 min
Tue 13 Oct— 16:33+1 min+3 min
Mon 12 Oct— 16:34+1 min+3 min
Fri 9 Oct— 16:35+2 min+4 min
Thu 8 Oct— 16:37+5 min+7 min
Wed 7 Oct— 16:36+3 min+4 min
Tue 6 Oct— 16:330 min+4 min
Mon 5 Oct— 16:330 min+4 min
Fri 2 Oct— 16:41+8 min+10 min
Thu 1 Oct— 16:33+1 min+4 min
Wed 30 Sept— 16:320 min+1 min
Tue 29 Sept— 16:40+8 min+9 min
Mon 28 Sept— 16:43+10 min+11 min
Fri 25 Sept— 16:320 min+3 min
Thu 24 Sept— 16:320 min+4 min
Wed 23 Sept— 16:37+4 min+5 min