K5 30505 Kraków Główny – Zakopane

View line K5

Kraków Główny 07:21 → Zakopane 11:02 Daily 3 h 41 min · 49 stops PolRegio

Running now · updated 10:03

Position estimated from the timetable

Between Skawa and Skawa Środkowa 0 min

Estimated arrival at Zakopane 11:02 · 50 km/h

  1. Kraków Główny07:21
  2. Kraków Opatkowice07:39
  3. Wola Radziszowska Lipki08:01
  4. Dąbrówka Jezioro Mucharskie08:54
  5. Skawa10:01
  6. Skawa Środkowa10:04
  7. Zakopane11:02

Today it is running no worse than usual: typical arrival delay is 0 min; 88% of the last 24 runs arrived on time.

On-time · 30 days
88%
21/24 runs under 3 min
RT coverage: 23 full · 1 partial · 6 no data
On-time · 90 days
79%
49/62 runs under 3 min
RT coverage: 61 full · 1 partial · 19 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: +2 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 +91 min · last fix heading to Osielec +91 min
  • Fri 18 Sept Max en route +51 min · last fix heading to Raba Wyżna +51 min
  • Fri 11 Sept Max en route +41 min · last fix heading to Sieniawa +41 min
  • Tue 29 Sept Max en route +30 min · last fix heading to Nowy Targ +30 min
  • Thu 17 Sept Max en route +39 min · last fix heading to Nowy Targ +30 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 79% · 49
  • 3–10 min 11% · 7
  • 10–30 min 2% · 1
  • 30+ min 8% · 5

On-time by weekday

  • 91% M n=11
  • 80% T n=10
  • 88% W n=8
  • 86% T n=7
  • 56% F n=9
  • 89% S n=9
  • 63% S n=8

Stops and timetable

Timetable of the latest run from the operator’s GTFS (49 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 10Today
07:21on time +5 minPassed
07:23≈ on time ≈ +5 minPassed
07:25≈ on time ≈ +5 minPassed
07:27≈ on time ≈ +5 minPassed
07:30≈ on time ≈ +5 minPassed
07:32≈ on time ≈ +5 minPassed
07:34≈ on time ≈ +5 minPassed
07:36 / 07:37≈ on time ≈ +5 minPassed
07:39 / 07:40≈ on time ≈ +5 minPassed
07:42≈ on time ≈ +5 minPassed
07:45≈ on time ≈ +5 minPassed
07:48 / 07:49≈ on time ≈ +5 minPassed
07:51 / 07:52≈ on time ≈ +5 minPassed
07:54≈ on time ≈ +5 minPassed
07:56≈ on time ≈ +6 minPassed
07:59≈ on time ≈ +6 minPassed
08:01 / 08:02≈ on time ≈ +6 minPassed
08:03 / 08:04≈ on time ≈ +5 minPassed
08:06 / 08:07≈ on time ≈ +5 minPassed
08:09 / 08:10≈ on time ≈ +5 minPassed
08:13 / 08:14≈ on time ≈ +5 minPassed
08:18 / 08:36≈ on time ≈ +5 minPassed
08:44 / 08:45≈ on time ≈ +5 minPassed
08:50 / 08:51≈ on time ≈ +5 minPassed
08:54≈ on time ≈ +5 minPassed
08:58 / 08:59≈ on time ≈ +5 minPassed
09:05 / 09:23≈ on time ≈ +5 minPassed
09:30 / 09:31≈ on time ≈ +5 minPassed
09:34≈ on time ≈ +5 minPassed
09:37≈ on time ≈ +5 minPassed
09:41 / 09:47≈ on time ≈ +5 minPassed
09:50 / 09:51≈ on time ≈ +5 minPassed
09:56≈ on time ≈ +5 minPassed
10:01≈ on time ≈ +5 minPassed
10:04≈ on time ≈ +5 minNext
10:08≈ on time ≈ +5 min
10:10 / 10:11≈ on time ≈ +5 min
10:14≈ on time ≈ +5 min
10:20 / 10:21≈ on time ≈ +5 min
10:25 / 10:26≈ on time ≈ +5 min
10:30≈ on time ≈ +5 min
10:35 / 10:36≈ on time ≈ +5 min
10:40 / 10:41≈ on time ≈ +5 min
10:43≈ on time ≈ +5 min
10:46 / 10:47≈ on time ≈ +5 min
10:50≈ on time ≈ +5 min
10:54 / 10:55≈ on time ≈ +5 min
10:57≈ on time ≈ +5 min
11:02on 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
Wed 18 NovSkawa 09:59Partial coverage0 min—
Tue 17 NovZakopane 11:030 min—
Mon 16 NovZakopane 11:040 min—
Sun 15 NovZakopane 11:040 min—
Sat 14 NovZakopane 11:030 min—
Fri 13 NovZakopane 11:030 min—
Thu 12 NovZakopane 11:030 min—
Wed 11 NovZakopane 11:030 min—
Tue 10 NovZakopane 11:030 min—
Mon 9 NovZakopane 11:030 min—
Sun 8 NovZakopane 11:14+10 min+10 min
Sat 7 NovZakopane 11:030 min—
Fri 6 NovZakopane 11:04+3 min+3 min
Thu 5 NovZakopane 11:030 min—
Wed 4 NovZakopane 11:030 min—
Tue 3 NovZakopane 11:030 min—
Mon 2 NovZakopane 11:030 min—
Sun 1 NovZakopane 11:08+5 min+5 min
Sat 31 OctZakopane 11:030 min—
Fri 30 OctZakopane 11:030 min—
Thu 29 OctZakopane 11:030 min—
Wed 28 OctZakopane 11:030 min—
Tue 27 OctZakopane 11:030 min—
Mon 26 OctZakopane 11:04+1 min+1 min
Sun 25 OctZakopane 11:03No data—
Sat 24 OctZakopane 10:56No data—
Fri 23 OctZakopane 10:56No data—
Thu 22 OctZakopane 10:56No data—
Wed 21 OctZakopane 10:56No data—
Tue 20 OctZakopane 10:56No data—