K7 30676 Piwniczna – Stróże

View line K7

Piwniczna 08:10 → Stróże 09:17 Mon, Tue, Wed, Thu, Fri 1 h 07 min · 16 stops PolRegio

✓ Today’s run finished

Today it reached Stróże at 09:19 +2 min

  1. Piwniczna08:10
  2. Rytro08:20
  3. Stary Sącz08:29
  4. Nowy Sącz08:39
  5. Nowy Sącz Jamnica08:45
  6. Ptaszkowa09:01
  7. Stróże09:17

Next service: tomorrow 08:10 from Piwniczna · Fri 6 Nov

Next departure 08:10 tomorrow · Piwniczna
On-time · 30 days
72%
13/18 runs under 3 min
RT coverage: 18 full · 0 partial · 4 no data
On-time · 90 days
75%
15/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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

  • Mon 19 Oct Max en route +14 min · last fix heading to Stróże +8 min
  • Wed 28 Oct Max en route +7 min · last fix heading to Stróże +7 min
  • Tue 27 Oct Max en route +6 min · last fix heading to Stróże +6 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Stróże +5 min
  • Fri 9 Oct Max en route +10 min · last fix heading to Stróże +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 15
  • 3–10 min 25% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 75% T n=4
  • 50% W n=4
  • 100% T n=4
  • 67% F n=3
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 20 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
08:10on time +2 min
08:13≈ on time ≈ +2 min
08:17≈ on time ≈ +2 min
08:20≈ on time ≈ +2 min
08:25≈ on time ≈ +2 min
08:29≈ on time ≈ +3 min
08:33≈ on time ≈ +3 min
08:36≈ on time ≈ +3 min
08:39 / 08:40≈ on time ≈ +4 min
08:42 / 08:43≈ on time ≈ +4 min
08:45 / 08:46≈ on time ≈ +4 min
08:49 / 08:50≈ on time ≈ +5 min
08:55≈ on time ≈ +5 min
09:01≈ on time ≈ +5 min
09:12 / 09:13≈ on time ≈ +6 min
09:17on time +6 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 5 NovStróże 09:19+2 min+2 min
Wed 4 NovStróże 09:23+5 min+5 min
Tue 3 NovStróże 09:180 min—
Mon 2 NovStróże 09:180 min—
Fri 30 OctStróże 09:180 min—
Thu 29 OctStróże 09:180 min—
Wed 28 OctStróże 09:25+7 min+7 min
Tue 27 OctStróże 09:24+6 min+6 min
Mon 26 OctStróże 09:180 min—
Fri 23 OctStróże 09:24No data—
Thu 22 OctStróże 09:24No data—
Wed 21 OctStróże 09:24No data—
Tue 20 OctStróże 09:24No data—
Mon 19 OctStróże 09:32+8 min+14 min
Fri 16 OctStróże 09:240 min—
Thu 15 OctStróże 09:240 min—
Wed 14 OctStróże 09:250 min—
Tue 13 OctStróże 09:240 min—
Mon 12 OctStróże 09:240 min—
Fri 9 OctStróże 09:28+3 min+10 min
Thu 8 OctStróże 09:240 min—
Wed 7 OctStróże 09:250 min—
Tue 6 OctStróże 09:240 min—
Mon 5 OctStróże 09:250 min—
Fri 2 OctStróże 09:22No data—
Thu 1 OctStróże 09:23No data—
Wed 30 SeptStróże 09:22No data—
Tue 29 SeptStróże 09:22No data—
Mon 28 SeptStróże 09:23No data—