P506 P506 Cork (Kent) – Mallow

View line P506

Cork (Kent) 08:00 → Mallow 08:21 Mon, Tue, Wed, Thu, Fri, Sat 0 h 21 min · 2 stops Iarnród Éireann

It has not run yet today

Last recorded run: Tuesday 3 November 0 min

Next service: tomorrow 08:00 from Cork (Kent) · Sat 7 Nov

Next departure 08:00 tomorrow · Cork (Kent)
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
93%
63/68 runs under 3 min
RT coverage: 68 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Mallow, in minutes. One bar per run.

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

Worst days

  • Fri 23 Oct Max en route +14 min · last fix heading to — +14 min
  • Mon 24 Aug Max en route +8 min · last fix heading to — +8 min
  • Thu 1 Oct Max en route +7 min · last fix heading to — +7 min
  • Sat 24 Oct Max en route +4 min · last fix heading to — +4 min
  • Thu 13 Aug Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 63
  • 3–10 min 6% · 4
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 68 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
Cork (Kent)
08:00on time +2 min
Mallow
08:21on time +2 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
Tue 3 Nov— 08:220 min—
Sat 31 Oct— 08:33+2 min+2 min
Fri 30 Oct— 08:290 min—
Thu 29 Oct— 08:32+1 min+1 min
Wed 28 Oct— 08:310 min—
Tue 27 Oct— 08:32+1 min+1 min
Sat 24 Oct— 08:35+4 min+4 min
Fri 23 Oct— 08:44+14 min+14 min
Thu 22 Oct— 08:32+1 min+1 min
Wed 21 Oct— 08:300 min—
Tue 20 Oct— 08:300 min—
Mon 19 Oct— 08:300 min—
Sat 17 Oct— 08:33+2 min+2 min
Fri 16 Oct— 08:310 min—
Thu 15 Oct— 08:29+1 min+1 min
Wed 14 Oct— 08:28+1 min+1 min
Tue 13 Oct— 08:310 min—
Mon 12 Oct— 08:32+2 min+2 min
Sat 10 Oct— 08:32+1 min+1 min
Fri 9 Oct— 08:310 min—
Thu 8 Oct— 08:310 min—
Wed 7 Oct— 08:29+1 min+1 min
Tue 6 Oct— 08:300 min—
Mon 5 Oct— 08:29+1 min+1 min
Sat 3 Oct— 08:31+1 min+1 min
Fri 2 Oct— 08:33+2 min+2 min
Thu 1 Oct— 08:38+7 min+7 min
Wed 30 Sept— 08:310 min—
Tue 29 Sept— 08:31+1 min+1 min
Mon 28 Sept— 08:300 min—