D312 D312 Clonsilla – M3 Parkway

View line D312

Clonsilla 13:19 → M3 Parkway 13:31 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 4 stops Iarnród Éireann

It has not run yet today

Last recorded run: Wednesday 4 November +1 min

Next service: today 13:19 from Clonsilla · Thu 5 Nov

Full trip card
Next departure 13:19 today · Clonsilla
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
98%
61/62 runs under 3 min
RT coverage: 62 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at M3 Parkway, in minutes. One bar per run.

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

Worst days

  • Thu 20 Aug Max en route +6 min · last fix heading to — +3 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 98% · 61
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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
Clonsilla
13:19+1 min +2 min
Hansfield
13:22≈ +1 min ≈ +2 min
Dunboyne
13:26 / 13:27≈ +1 min ≈ +1 min
M3 Parkway
13:31+1 min +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
Wed 4 Nov— 13:29+1 min+1 min
Tue 3 Nov— 13:29+1 min+1 min
Mon 2 Nov— 13:29+2 min+2 min
Fri 30 Oct— 13:390 min+1 min
Thu 29 Oct— 13:400 min+1 min
Wed 28 Oct— 13:410 min+2 min
Tue 27 Oct— 13:410 min+2 min
Fri 23 Oct— 13:38+1 min+1 min
Thu 22 Oct— 13:38+1 min+1 min
Wed 21 Oct— 13:39+1 min+1 min
Tue 20 Oct— 13:39+1 min+1 min
Mon 19 Oct— 13:390 min+1 min
Fri 16 Oct— 13:39+1 min+1 min
Thu 15 Oct— 13:39+1 min+1 min
Wed 14 Oct— 13:39+1 min+1 min
Tue 13 Oct— 13:39+1 min+1 min
Mon 12 Oct— 13:39+1 min+1 min
Fri 9 Oct— 13:400 min+1 min
Thu 8 Oct— 13:38+1 min+1 min
Wed 7 Oct— 13:38+2 min+2 min
Tue 6 Oct— 13:39+1 min+1 min
Mon 5 Oct— 13:39+1 min+1 min
Fri 2 Oct— 13:42+1 min+3 min
Thu 1 Oct— 13:410 min+3 min
Wed 30 Sept— 13:39+1 min+1 min
Tue 29 Sept— 13:400 min+2 min
Mon 28 Sept— 13:400 min+2 min
Fri 25 Sept— 13:38+1 min+1 min
Thu 24 Sept— 13:400 min+2 min
Wed 23 Sept— 13:39+1 min+1 min