K5 30507 Kraków Główny → Zakopane
Alerts for train 30507
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.
K5 30507 Janosik Kraków Główny–Zakopane: final delay under 3 min on 19 of its 27 runs with data in the last 30 days (70%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 00:47 (GMT+1).
An alert on this phone or computer when the 30507 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Saturday 21 November 0 min
Next service: today 09:25 from Kraków Główny · Sun 22 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 +36 min · last fix heading to Lasek +36 min
- Sat 5 Sept Max en route +36 min · last fix heading to Lasek +36 min
- Mon 14 Sept Max en route +34 min · last fix heading to Lasek +34 min
- Sat 12 Sept Max en route +20 min · last fix heading to Szaflary Centrum +20 min
- Mon 7 Sept Max en route +19 min · last fix heading to Szaflary Centrum +19 min
Distribution · 90 days
75 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 52% · 39
- 3–10 min 40% · 30
- 10–30 min 4% · 3
- 30+ min 4% · 3
On-time by weekday
- 45% M n=11
- 55% T n=11
- 73% W n=11
- 50% T n=10
- 64% F n=11
- 36% S n=11
- 40% S n=10
Stops and timetable
Timetable of the latest run from the operator’s GTFS (50 stops).
Last 90 days, 75 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 |
|---|---|---|---|
| 09:25 | +2 min | +8 min | |
| 09:27 | ≈ +2 min | ≈ +8 min | |
| 09:29 | ≈ +2 min | ≈ +8 min | |
| 09:31 / 09:32 | ≈ +2 min | ≈ +8 min | |
| 09:34 / 09:35 | ≈ +2 min | ≈ +8 min | |
| 09:36 / 09:37 | ≈ +2 min | ≈ +8 min | |
| 09:38 / 09:39 | ≈ +2 min | ≈ +8 min | |
| 09:41 | ≈ +2 min | ≈ +8 min | |
| 09:44 / 09:45 | ≈ +2 min | ≈ +8 min | |
| 09:47 | ≈ +2 min | ≈ +8 min | |
| 09:50 | ≈ +2 min | ≈ +8 min | |
| 09:52 / 09:53 | ≈ +2 min | ≈ +8 min | |
| 09:56 | ≈ +2 min | ≈ +8 min | |
| 09:58 / 09:59 | ≈ +2 min | ≈ +8 min | |
| 10:00 / 10:01 | ≈ +2 min | ≈ +8 min | |
| 10:03 / 10:09 | ≈ +2 min | ≈ +8 min | |
| 10:11 | ≈ +2 min | ≈ +8 min | |
| 10:13 | ≈ +2 min | ≈ +8 min | |
| 10:16 | ≈ +2 min | ≈ +8 min | |
| 10:18 / 10:24 | ≈ +2 min | ≈ +8 min | |
| 10:28 | ≈ +2 min | ≈ +8 min | |
| 10:32 / 10:33 | ≈ +2 min | ≈ +8 min | |
| 10:41 / 10:42 | ≈ +2 min | ≈ +8 min | |
| 10:47 / 10:48 | ≈ +2 min | ≈ +8 min | |
| 10:51 | ≈ +2 min | ≈ +8 min | |
| 10:55 / 10:56 | ≈ +2 min | ≈ +8 min | |
| 11:01 / 11:17 | ≈ +2 min | ≈ +8 min | |
| 11:24 / 11:25 | ≈ +2 min | ≈ +8 min | |
| 11:28 | ≈ +2 min | ≈ +8 min | |
| 11:31 / 11:32 | ≈ +2 min | ≈ +8 min | |
| 11:35 / 11:36 | ≈ +2 min | ≈ +8 min | |
| 11:39 / 11:40 | ≈ +2 min | ≈ +8 min | |
| 11:45 | ≈ +2 min | ≈ +8 min | |
| 11:49 / 11:50 | ≈ +2 min | ≈ +8 min | |
| 11:53 | ≈ +2 min | ≈ +8 min | |
| 11:58 / 12:09 | ≈ +2 min | ≈ +8 min | |
| 12:11 | ≈ +2 min | ≈ +8 min | |
| 12:14 | ≈ +2 min | ≈ +8 min | |
| 12:17 / 12:18 | ≈ +2 min | ≈ +8 min | |
| 12:24 | ≈ +2 min | ≈ +8 min | |
| 12:29 | ≈ +2 min | ≈ +8 min | |
| 12:33 / 12:34 | ≈ +2 min | ≈ +8 min | |
| 12:39 / 12:40 | ≈ +2 min | ≈ +8 min | |
| 12:44 / 12:51 | ≈ +2 min | ≈ +8 min | |
| 12:53 | ≈ +2 min | ≈ +8 min | |
| 12:56 / 12:57 | ≈ +2 min | ≈ +8 min | |
| 13:00 | ≈ +2 min | ≈ +8 min | |
| 13:04 / 13:10 | ≈ +2 min | ≈ +8 min | |
| 13:12 / 13:13 | ≈ +2 min | ≈ +8 min | |
| 13:18 | +2 min | +8 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 21 Nov | Zakopane 13:19 | 0 min | — |
| Fri 20 Nov | Zakopane 13:19 | 0 min | — |
| Thu 19 Nov | Zakopane 13:19 | 0 min | — |
| Wed 18 Nov | Zakopane 13:19 | 0 min | — |
| Tue 17 Nov | Zakopane 13:19 | 0 min | — |
| Mon 16 Nov | Zakopane 13:29 | +9 min | +9 min |
| Sun 15 Nov | Zakopane 13:19 | 0 min | — |
| Sat 14 Nov | Zakopane 13:19 | 0 min | — |
| Fri 13 Nov | Zakopane 13:19 | 0 min | — |
| Thu 12 Nov | Zakopane 13:19 | 0 min | — |
| Wed 11 Nov | Zakopane 13:19 | 0 min | — |
| Tue 10 Nov | Zakopane 13:19 | 0 min | — |
| Mon 9 Nov | Zakopane 13:19 | 0 min | — |
| Sun 8 Nov | Zakopane 13:19 | 0 min | — |
| Sat 7 Nov | Zakopane 13:24 | +7 min | +7 min |
| Fri 6 Nov | Zakopane 13:19 | 0 min | — |
| Thu 5 Nov | Zakopane 13:22 | +3 min | +3 min |
| Wed 4 Nov | Zakopane 13:19 | 0 min | — |
| Tue 3 Nov | Zakopane 13:19 | 0 min | — |
| Mon 2 Nov | Zakopane 13:19 | 0 min | — |
| Sun 1 Nov | Zakopane 13:31 | +12 min | +12 min |
| Sat 31 Oct | Zakopane 13:27 | +8 min | +8 min |
| Fri 30 Oct | Zakopane 13:27 | +8 min | +8 min |
| Thu 29 Oct | Zakopane 13:26 | +7 min | +7 min |
| Wed 28 Oct | Zakopane 13:19 | 0 min | — |
| Tue 27 Oct | Zakopane 13:23 | +4 min | +4 min |
| Mon 26 Oct | Zakopane 13:19 | 0 min | — |
| Sun 25 Oct | Zakopane 13:19 | No data | — |
| Sat 24 Oct | Zakopane 13:10 | No data | — |
| Fri 23 Oct | Zakopane 13:10 | No data | — |