P214 P214 Newbridge → Dublin Heuston

View line P214

Newbridge 12:25 → Dublin Heuston 13:11 Mon, Tue, Wed, Thu, Fri 0 h 46 min · 8 stops Iarnród Éireann

Train P214 Newbridge–Dublin Heuston: final delay under 3 min on 18 of its 18 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 02:29 (UTC).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 12:25 from Newbridge · Mon 23 Nov

Next departure 12:25 tomorrow · Newbridge
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 0 no data
On-time · 90 days
97%
60/62 runs under 3 min
RT coverage: 62 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Dublin Heuston, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 6 Oct Max en route +10 min · last fix heading to — +6 min
  • Mon 21 Sept Max en route +11 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 60
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 91% M n=11
  • 92% T n=12
  • 100% W n=13
  • 100% T n=13
  • 100% F n=13
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 62 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
12:25+1 min +5 min
12:32 / 12:33≈ +1 min ≈ +4 min
12:41 / 12:43≈ +1 min ≈ +3 min
12:46 / 12:48≈ +1 min ≈ +3 min
12:51 / 12:53≈ on time ≈ +2 min
12:55 / 12:57≈ on time ≈ +2 min
12:59 / 13:02≈ on time ≈ +2 min
13:11on time +1 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 20 Nov— 13:190 min+1 min
Thu 19 Nov— 13:190 min+2 min
Wed 18 Nov— 13:190 min+5 min
Mon 16 Nov— 13:190 min—
Fri 13 Nov— 13:22+2 min+6 min
Thu 12 Nov— 13:190 min+1 min
Wed 11 Nov— 13:190 min+2 min
Tue 10 Nov— 13:200 min+1 min
Mon 9 Nov— 13:19+1 min+1 min
Fri 6 Nov— 13:19−1 min+2 min
Thu 5 Nov— 13:23+2 min+3 min
Wed 4 Nov— 13:190 min+3 min
Tue 3 Nov— 13:190 min+4 min
Mon 2 Nov— 13:190 min—
Fri 30 Oct— 13:23+2 min+3 min
Thu 29 Oct— 13:200 min+6 min
Wed 28 Oct— 13:22+1 min+5 min
Tue 27 Oct— 13:210 min+1 min
Fri 23 Oct— 13:210 min+2 min
Thu 22 Oct— 13:210 min+3 min
Wed 21 Oct— 13:200 min+2 min
Tue 20 Oct— 13:200 min+1 min
Mon 19 Oct— 13:200 min+1 min
Fri 16 Oct— 13:210 min+2 min
Thu 15 Oct— 13:19+1 min+1 min
Wed 14 Oct— 13:210 min—
Tue 13 Oct— 13:210 min+1 min
Mon 12 Oct— 13:200 min+1 min
Fri 9 Oct— 13:210 min—
Thu 8 Oct— 13:210 min+2 min