S17 44580 Rybnik – Gliwice

View line S17

Rybnik 19:55 → Gliwice 20:42 Mon, Tue, Wed, Thu, Fri 0 h 47 min · 6 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Gliwice at 20:42 0 min

  1. Rybnik19:55
  2. Rybnik Paruszowiec19:58
  3. Leszczyny20:04
  4. Knurów20:16
  5. Przyszowice20:25
  6. Gliwice20:42

Next service: tomorrow 19:55 from Rybnik · Fri 13 Nov

Next departure 19:55 tomorrow · Rybnik
On-time · 30 days
73%
11/15 runs under 3 min
RT coverage: 15 full · 0 partial · 6 no data
On-time · 90 days
70%
23/33 runs under 3 min
RT coverage: 33 full · 0 partial · 11 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

Arrival delay at Gliwice, 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 9 Nov Max en route +9 min · last fix heading to Gliwice +9 min
  • Tue 10 Nov Max en route +8 min · last fix heading to Gliwice +8 min
  • Fri 9 Oct Max en route +8 min · last fix heading to Gliwice +8 min
  • Fri 25 Sept Max en route +5 min · last fix heading to Gliwice +5 min
  • Thu 17 Sept Max en route +5 min · last fix heading to Gliwice +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 70% · 23
  • 3–10 min 30% · 10
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 75% T n=8
  • 80% W n=5
  • 57% T n=7
  • 57% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
19:55on time +5 min
19:58≈ on time ≈ +5 min
20:04≈ on time ≈ +5 min
20:16 / 20:17≈ +1 min ≈ +5 min
20:25 / 20:26≈ +1 min ≈ +5 min
20:42+1 min +5 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 NovGliwice 20:430 min—
Tue 10 NovGliwice 20:49+8 min+8 min
Mon 9 NovGliwice 20:52+9 min+9 min
Fri 6 NovGliwice 20:430 min—
Thu 5 NovGliwice 20:440 min—
Wed 4 NovGliwice 20:430 min—
Tue 3 NovGliwice 20:440 min—
Mon 2 NovGliwice 20:44+1 min+1 min
Fri 30 OctGliwice 20:46+3 min+3 min
Thu 29 OctGliwice 20:46+3 min+3 min
Wed 28 OctGliwice 20:43No data—
Tue 27 OctGliwice 20:430 min—
Mon 26 OctGliwice 20:45+1 min+1 min
Fri 23 OctGliwice 20:44No data—
Thu 22 OctGliwice 20:43No data—
Wed 21 OctGliwice 20:43No data—
Tue 20 OctGliwice 20:43No data—
Mon 19 OctGliwice 20:43No data—
Fri 16 OctGliwice 20:440 min—
Thu 15 OctGliwice 20:45+1 min+1 min
Wed 14 OctGliwice 20:45+2 min+2 min
Tue 13 OctGliwice 20:430 min—
Mon 12 OctGliwice 20:44+1 min+1 min
Fri 9 OctGliwice 20:51+8 min+8 min
Thu 8 OctGliwice 20:430 min—
Wed 7 OctGliwice 20:430 min—
Tue 6 OctGliwice 20:430 min—
Mon 5 OctGliwice 20:430 min—
Fri 2 OctGliwice 20:42+2 min+2 min
Thu 1 OctGliwice 20:41No data—