P210 P210 Newbridge – Dublin Heuston

View line P210

Newbridge 10:27 → Dublin Heuston 11:07 Mon, Tue, Wed, Thu, Fri 0 h 40 min · 8 stops Iarnród Éireann

Running now · updated 11:11

Heading to Dublin Heuston +1 min

Estimated arrival at Dublin Heuston 11:08 11:07

  1. Newbridge10:27
  2. Sallins and Naas10:34
  3. Hazelhatch and Celbridge10:43
  4. Kishoge10:51
  5. Clondalkin Fonthill10:54
  6. Park West and Cherry Orchard10:57
  7. Dublin Heuston11:07

Today it is running no worse than usual: typical arrival delay is +1 min; 71% of the last 21 runs arrived on time.

On-time · 30 days
71%
15/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
63%
40/63 runs under 3 min
RT coverage: 63 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Mon 2 Nov Max en route +12 min · last fix heading to — +12 min
  • Mon 21 Sept Max en route +10 min · last fix heading to — +10 min
  • Fri 28 Aug Max en route +9 min · last fix heading to — +9 min
  • Tue 15 Sept Max en route +8 min · last fix heading to — +8 min
  • Tue 3 Nov Max en route +7 min · last fix heading to — +7 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 63% · 40
  • 3–10 min 33% · 21
  • 10–30 min 3% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=12
  • 54% T n=13
  • 54% W n=13
  • 85% T n=13
  • 75% F n=12
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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 10Today
10:27on time +4 min
10:34 / 10:35≈ +1 min ≈ +4 min
10:43 / 10:44≈ +1 min ≈ +5 min
10:47 / 10:48≈ +1 min ≈ +5 min
10:51 / 10:52≈ +1 min ≈ +5 min
10:54 / 10:55≈ +1 min ≈ +5 min
10:57 / 10:58≈ +1 min ≈ +5 min
11:07+1 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
Thu 5 Nov— 11:09+1 min+1 min
Wed 4 Nov— 11:18+1 min+1 min
Tue 3 Nov— 11:24+7 min+7 min
Mon 2 Nov— 11:29+12 min+12 min
Fri 30 Oct— 11:170 min+4 min
Thu 29 Oct— 11:170 min+1 min
Wed 28 Oct— 11:20+3 min+3 min
Tue 27 Oct— 11:19+2 min+3 min
Fri 23 Oct— 11:17+1 min+1 min
Thu 22 Oct— 11:18+1 min+2 min
Wed 21 Oct— 11:20+3 min+3 min
Tue 20 Oct— 11:21+4 min+4 min
Mon 19 Oct— 11:17+1 min+1 min
Fri 16 Oct— 11:170 min—
Thu 15 Oct— 11:170 min+1 min
Wed 14 Oct— 11:18+2 min+2 min
Tue 13 Oct— 11:160 min—
Mon 12 Oct— 11:24+7 min+10 min
Fri 9 Oct— 11:18+1 min+1 min
Thu 8 Oct— 11:160 min—
Wed 7 Oct— 11:170 min—
Tue 6 Oct— 11:17+1 min+10 min
Mon 5 Oct— 11:19+3 min+3 min
Fri 2 Oct— 11:170 min+1 min
Thu 1 Oct— 11:160 min+1 min
Wed 30 Sept— 11:24+7 min+7 min
Tue 29 Sept— 11:22+6 min+6 min
Mon 28 Sept— 11:19+3 min+3 min
Fri 25 Sept— 11:170 min+3 min
Thu 24 Sept— 11:18+1 min+2 min