K5 30549 Nowy Targ – Zakopane
Alerts for train 30549
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line K5.
✓ Today’s run finished
Today it reached Zakopane at 05:31 0 min
- Nowy Targ05:05
- Szaflary05:09
- Szaflary Centrum05:11
- Biały Dunajec05:18
- Poronin05:23
- Poronin Misiagi05:25
- Zakopane05:31
Next service: tomorrow 05:05 from Nowy Targ · Fri 20 Nov
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 05:05 | on 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:31 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 19 Nov | Zakopane 05:33 | 0 min | — |
| Wed 18 Nov | Zakopane 05:32 | 0 min | — |
| Tue 17 Nov | Zakopane 05:32 | 0 min | — |
| Mon 16 Nov | Zakopane 05:32 | 0 min | — |
| Sun 15 Nov | Zakopane 05:32 | 0 min | — |
| Sat 14 Nov | Zakopane 05:32 | 0 min | — |
| Fri 13 Nov | Zakopane 05:32 | 0 min | — |
| Thu 12 Nov | Zakopane 05:32 | 0 min | — |
| Wed 11 Nov | Zakopane 05:32 | 0 min | — |
| Tue 10 Nov | Zakopane 05:33 | 0 min | — |
| Mon 9 Nov | Zakopane 05:32 | 0 min | — |
| Sun 8 Nov | Zakopane 05:32 | 0 min | — |
| Sat 7 Nov | Zakopane 05:33 | 0 min | — |
| Fri 6 Nov | Zakopane 05:32 | 0 min | — |
| Thu 5 Nov | Zakopane 05:32 | 0 min | — |
| Wed 4 Nov | Zakopane 05:32 | 0 min | — |
| Tue 3 Nov | Zakopane 05:32 | 0 min | — |
| Mon 2 Nov | Zakopane 05:32 | 0 min | — |
| Sun 1 Nov | Zakopane 05:38 | +6 min | +6 min |
| Sat 31 Oct | Zakopane 05:32 | 0 min | — |
| Fri 30 Oct | Zakopane 05:32 | 0 min | — |
| Wed 28 Oct | Szaflary Centrum 05:12Partial coverage | 0 min | — |
| Tue 27 Oct | Zakopane 05:33 | 0 min | — |
| Mon 26 Oct | Zakopane 05:32 | 0 min | — |
| Sun 25 Oct | Zakopane 05:32 | No data | — |
| Sat 24 Oct | Zakopane 05:32 | No data | — |
| Fri 23 Oct | Zakopane 05:32 | No data | — |
| Thu 22 Oct | Zakopane 05:32 | No data | — |
| Wed 21 Oct | Zakopane 05:32 | No data | — |
| Tue 20 Oct | Zakopane 05:32 | No data | — |