K5 30549 Nowy Targ – Zakopane

View line K5

Nowy Targ 05:05 → Zakopane 05:31 Daily 0 h 26 min · 8 stops PolRegio

✓ Today’s run finished

Today it reached Zakopane at 05:31 0 min

  1. Nowy Targ05:05
  2. Szaflary05:09
  3. Szaflary Centrum05:11
  4. Biały Dunajec05:18
  5. Poronin05:23
  6. Poronin Misiagi05:25
  7. Zakopane05:31

Next service: tomorrow 05:05 from Nowy Targ · Fri 20 Nov

Next departure 05:05 tomorrow · Nowy Targ
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 23 full · 1 partial · 5 no data
On-time · 90 days
95%
38/40 runs under 3 min
RT coverage: 39 full · 1 partial · 41 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Tue 15 Sept Max en route +15 min · last fix heading to Biały Dunajec +15 min
  • Sun 1 Nov Max en route +6 min · last fix heading to Zakopane +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 38
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 86% T n=7
  • 100% W n=6
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 40 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
05:05on time on time
05:09≈ on time ≈ on time
05:11 / 05:12≈ on time ≈ on time
05:15≈ on time ≈ on time
05:18 / 05:19≈ on time ≈ on time
05:23≈ on time ≈ on time
05:25 / 05:26≈ on time ≈ on time
05:31on time on time

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
Thu 19 NovZakopane 05:330 min—
Wed 18 NovZakopane 05:320 min—
Tue 17 NovZakopane 05:320 min—
Mon 16 NovZakopane 05:320 min—
Sun 15 NovZakopane 05:320 min—
Sat 14 NovZakopane 05:320 min—
Fri 13 NovZakopane 05:320 min—
Thu 12 NovZakopane 05:320 min—
Wed 11 NovZakopane 05:320 min—
Tue 10 NovZakopane 05:330 min—
Mon 9 NovZakopane 05:320 min—
Sun 8 NovZakopane 05:320 min—
Sat 7 NovZakopane 05:330 min—
Fri 6 NovZakopane 05:320 min—
Thu 5 NovZakopane 05:320 min—
Wed 4 NovZakopane 05:320 min—
Tue 3 NovZakopane 05:320 min—
Mon 2 NovZakopane 05:320 min—
Sun 1 NovZakopane 05:38+6 min+6 min
Sat 31 OctZakopane 05:320 min—
Fri 30 OctZakopane 05:320 min—
Wed 28 OctSzaflary Centrum 05:12Partial coverage0 min—
Tue 27 OctZakopane 05:330 min—
Mon 26 OctZakopane 05:320 min—
Sun 25 OctZakopane 05:32No data—
Sat 24 OctZakopane 05:32No data—
Fri 23 OctZakopane 05:32No data—
Thu 22 OctZakopane 05:32No data—
Wed 21 OctZakopane 05:32No data—
Tue 20 OctZakopane 05:32No data—