K5 30554 Rabka Zaryte – Zakopane

View line K5

Rabka Zaryte 09:03 → Zakopane 10:14 Daily 1 h 11 min · 17 stops PolRegio

✓ Today’s run finished

Today it reached Zakopane at 10:14 0 min

  1. Rabka Zaryte09:03
  2. Chabówka Stadion09:15
  3. Raba Wyżna09:21
  4. Lasek09:42
  5. Szaflary Centrum09:55
  6. Biały Dunajec10:02
  7. Zakopane10:14

Next service: tomorrow 09:03 from Rabka Zaryte · Wed 11 Nov

Next departure 09:03 tomorrow · Rabka Zaryte
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 6 no data
On-time · 90 days
68%
30/44 runs under 3 min
RT coverage: 44 full · 0 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

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

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

Worst days

  • Sat 12 Sept Max en route +39 min · last fix heading to Lasek +39 min
  • Fri 11 Sept Max en route +32 min · last fix heading to Nowy Targ +32 min
  • Sat 7 Nov Max en route +11 min · last fix heading to Zakopane +11 min
  • Mon 9 Nov Max en route +10 min · last fix heading to Zakopane +10 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Zakopane +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 68% · 30
  • 3–10 min 23% · 10
  • 10–30 min 5% · 2
  • 30+ min 5% · 2

On-time by weekday

  • 75% M n=8
  • 83% T n=6
  • 80% W n=5
  • 75% T n=4
  • 57% F n=7
  • 43% S n=7
  • 71% S n=7

Stops and timetable

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

Last 90 days, 44 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
09:03on time +5 min
09:07≈ on time ≈ +5 min
09:10 / 09:13≈ on time ≈ +5 min
09:15≈ on time ≈ +5 min
09:18≈ on time ≈ +5 min
09:21 / 09:26≈ on time ≈ +5 min
09:32≈ on time ≈ +5 min
09:37 / 09:38≈ on time ≈ +5 min
09:42≈ on time ≈ +5 min
09:47 / 09:48≈ on time ≈ +5 min
09:52 / 09:53≈ on time ≈ +5 min
09:55≈ on time ≈ +5 min
09:58 / 09:59≈ on time ≈ +5 min
10:02≈ on time ≈ +5 min
10:06 / 10:07≈ on time ≈ +5 min
10:09≈ on time ≈ +5 min
10:14on time +5 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
Tue 10 NovZakopane 10:140 min—
Mon 9 NovZakopane 10:24+10 min+10 min
Sun 8 NovZakopane 10:140 min—
Sat 7 NovZakopane 10:24+11 min+11 min
Fri 6 NovZakopane 10:140 min—
Thu 5 NovZakopane 10:140 min—
Wed 4 NovZakopane 10:140 min—
Tue 3 NovZakopane 10:140 min—
Mon 2 NovZakopane 10:140 min—
Sun 1 NovZakopane 10:21+5 min+5 min
Sat 31 OctZakopane 10:150 min—
Fri 30 OctZakopane 10:150 min—
Tue 27 OctZakopane 10:150 min—
Mon 26 OctZakopane 10:150 min—
Sun 25 OctZakopane 10:15No data—
Sat 24 OctZakopane 10:03No data—
Fri 23 OctZakopane 10:03No data—
Thu 22 OctZakopane 10:03No data—
Wed 21 OctZakopane 10:03No data—
Tue 20 OctZakopane 10:03No data—
Mon 19 OctZakopane 10:030 min—
Sun 18 OctZakopane 10:030 min—
Sat 17 OctZakopane 10:030 min—
Fri 16 OctZakopane 10:030 min—
Thu 15 OctZakopane 10:030 min—
Wed 14 OctZakopane 10:040 min—
Tue 13 OctZakopane 10:030 min—
Mon 12 OctZakopane 10:030 min—
Sun 11 OctZakopane 10:030 min—
Sat 10 OctZakopane 10:030 min—