K7 30682 Piwniczna – Stróże

View line K7

Piwniczna 12:40 → Stróże 13:46 Mon, Tue, Wed, Thu, Fri 1 h 06 min · 16 stops PolRegio

✓ Today’s run finished

Today it reached Stróże at 13:46 0 min

  1. Piwniczna12:40
  2. Rytro12:49
  3. Stary Sącz12:58
  4. Nowy Sącz13:07
  5. Nowy Sącz Jamnica13:14
  6. Ptaszkowa13:30
  7. Stróże13:46

Next service: tomorrow 12:40 from Piwniczna · Fri 13 Nov

Next departure 12:40 tomorrow · Piwniczna
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 16 full · 0 partial · 5 no data
On-time · 90 days
84%
21/25 runs under 3 min
RT coverage: 25 full · 0 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Stróże, in minutes. One bar per run.

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

Worst days

  • Wed 4 Nov Max en route +5 min · last fix heading to Stróże +5 min
  • Wed 28 Oct Max en route +3 min · last fix heading to Stróże +3 min
  • Fri 2 Oct Max en route +3 min · last fix heading to Stróże +3 min
  • Thu 1 Oct Max en route +3 min · last fix heading to Stróże +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 84% · 21
  • 3–10 min 16% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 50% W n=4
  • 83% T n=6
  • 80% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
12:40on time +3 min
12:42≈ on time ≈ +3 min
12:46 / 12:47≈ on time ≈ +3 min
12:49≈ on time ≈ +3 min
12:54 / 12:55≈ on time ≈ +3 min
12:58≈ on time ≈ +3 min
13:02≈ on time ≈ +3 min
13:04 / 13:05≈ on time ≈ +3 min
13:07 / 13:09≈ on time ≈ +3 min
13:11 / 13:12≈ on time ≈ +3 min
13:14 / 13:15≈ on time ≈ +3 min
13:18 / 13:19≈ on time ≈ +3 min
13:24≈ on time ≈ +3 min
13:30≈ on time ≈ +3 min
13:41 / 13:42≈ on time ≈ +3 min
13:46on time +3 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
Thu 12 NovStróże 13:470 min—
Tue 10 NovStróże 13:470 min+22 min
Mon 9 NovStróże 13:480 min—
Fri 6 NovStróże 13:49+2 min+2 min
Thu 5 NovStróże 13:470 min—
Wed 4 NovStróże 13:52+5 min+5 min
Tue 3 NovStróże 13:480 min—
Mon 2 NovStróże 13:470 min—
Fri 30 OctStróże 13:48+1 min+1 min
Thu 29 OctStróże 13:470 min—
Wed 28 OctStróże 13:50+3 min+3 min
Tue 27 OctStróże 13:48+1 min+1 min
Mon 26 OctStróże 13:470 min—
Fri 23 OctStróże 13:48No data—
Thu 22 OctStróże 13:48No data—
Wed 21 OctStróże 13:48No data—
Tue 20 OctStróże 13:49No data—
Mon 19 OctStróże 13:48No data—
Fri 16 OctStróże 13:480 min—
Thu 15 OctStróże 13:480 min—
Wed 14 OctStróże 13:49+1 min+1 min
Tue 13 OctStróże 13:480 min—
Mon 12 OctStróże 13:480 min—
Fri 9 OctStróże 13:50+2 min+2 min
Thu 8 OctStróże 13:480 min—
Wed 7 OctStróże 13:480 min—
Tue 6 OctStróże 13:480 min—
Mon 5 OctStróże 13:460 min—
Fri 2 OctStróże 13:46+3 min+3 min
Thu 1 OctStróże 13:46+3 min+3 min