K5 30592 Zakopane – Rabka Zaryte

View line K5

Zakopane 22:23 → Rabka Zaryte 23:31 Daily 1 h 08 min · 17 stops PolRegio

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 22:23 from Zakopane · Mon 9 Nov

Next departure 22:23 today · Zakopane
On-time · 30 days
73%
16/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
53%
31/59 runs under 3 min
RT coverage: 59 full · 0 partial · 12 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Rabka Zaryte, in minutes. One bar per run.

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

Worst days

  • Wed 2 Sept Max en route +45 min · last fix heading to Szaflary Centrum +45 min
  • Tue 1 Sept Max en route +45 min · last fix heading to Szaflary Centrum +45 min
  • Mon 31 Aug Max en route +8 min · last fix heading to Chabówka +8 min
  • Wed 23 Sept Max en route +6 min · last fix heading to Chabówka +6 min
  • Tue 22 Sept Max en route +6 min · last fix heading to Chabówka +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 53% · 31
  • 3–10 min 44% · 26
  • 10–30 min 0% · 0
  • 30+ min 3% · 2

On-time by weekday

  • 50% M n=8
  • 63% T n=8
  • 67% W n=9
  • 63% T n=8
  • 63% F n=8
  • 33% S n=9
  • 33% S n=9

Stops and timetable

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

Last 90 days, 59 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
22:23+2 min +6 min
22:27 / 22:28≈ +2 min ≈ +6 min
22:30≈ +2 min ≈ +6 min
22:34≈ +2 min ≈ +6 min
22:36 / 22:37≈ +2 min ≈ +6 min
22:40≈ +2 min ≈ +6 min
22:42 / 22:49≈ +2 min ≈ +6 min
22:53 / 22:54≈ +2 min ≈ +6 min
22:59≈ +2 min ≈ +6 min
23:03≈ +2 min ≈ +6 min
23:09≈ +2 min ≈ +6 min
23:15 / 23:16≈ +2 min ≈ +6 min
23:18 / 23:19≈ +2 min ≈ +6 min
23:21≈ +2 min ≈ +6 min
23:24 / 23:25≈ +2 min ≈ +6 min
23:27≈ +2 min ≈ +6 min
23:31+2 min +6 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 1 August 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
Sun 8 NovRabka Zaryte 23:320 min—
Sat 7 NovRabka Zaryte 23:320 min—
Fri 6 NovRabka Zaryte 23:330 min—
Thu 5 NovRabka Zaryte 23:320 min—
Wed 4 NovRabka Zaryte 23:320 min—
Tue 3 NovRabka Zaryte 23:330 min—
Mon 2 NovRabka Zaryte 23:320 min—
Sun 1 NovRabka Zaryte 23:34+4 min+4 min
Sat 31 OctRabka Zaryte 23:36+3 min+3 min
Fri 30 OctRabka Zaryte 23:35+3 min+3 min
Thu 29 OctRabka Zaryte 23:320 min—
Wed 28 OctRabka Zaryte 23:320 min—
Tue 27 OctRabka Zaryte 23:320 min—
Mon 26 OctRabka Zaryte 23:36+3 min+3 min
Sun 25 OctRabka Zaryte 23:32No data—
Sat 24 OctRabka Zaryte 23:27No data—
Fri 23 OctRabka Zaryte 23:27No data—
Thu 22 OctRabka Zaryte 23:26No data—
Wed 21 OctRabka Zaryte 23:26No data—
Tue 20 OctRabka Zaryte 23:26No data—
Mon 19 OctRabka Zaryte 23:26No data—
Sun 18 OctRabka Zaryte 23:30+3 min+3 min
Sat 17 OctRabka Zaryte 23:29+3 min+3 min
Fri 16 OctRabka Zaryte 23:28+2 min+2 min
Thu 15 OctRabka Zaryte 23:270 min—
Wed 14 OctRabka Zaryte 23:29+2 min+2 min
Tue 13 OctRabka Zaryte 23:260 min—
Mon 12 OctRabka Zaryte 23:260 min—
Sun 11 OctRabka Zaryte 23:28+2 min+2 min
Sat 10 OctRabka Zaryte 23:260 min—