S17 44524 Gliwice – Rybnik

View line S17

Gliwice 15:20 → Rybnik 16:11 Mon, Tue, Wed, Thu, Fri 0 h 51 min · 6 stops Koleje Śląskie

It has not run yet today

Last recorded run: Tuesday 17 November −2 min

Next service: today 15:20 from Gliwice · Wed 18 Nov

Next departure 15:20 today · Gliwice
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 15 full · 0 partial · 5 no data
On-time · 90 days
75%
27/36 runs under 3 min
RT coverage: 36 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Rybnik, in minutes. One bar per run.

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

Worst days

  • Fri 2 Oct Max en route +16 min · last fix heading to Leszczyny +16 min
  • Mon 14 Sept Max en route +13 min · last fix heading to Leszczyny +13 min
  • Tue 15 Sept Max en route +10 min · last fix heading to Leszczyny +10 min
  • Mon 9 Nov Max en route +5 min · last fix heading to Rybnik +5 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Rybnik +4 min

Distribution · 90 days

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

  • Early 19% · 7
  • On time 56% · 20
  • 3–10 min 17% · 6
  • 10–30 min 8% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 63% T n=8
  • 83% W n=6
  • 71% T n=7
  • 86% 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, 36 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
15:20on time +5 min
15:35≈ on time ≈ +4 min
15:45 / 15:46≈ on time ≈ +4 min
15:59 / 16:02≈ on time ≈ +4 min
16:07 / 16:08≈ on time ≈ +4 min
16:11on time +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
Tue 17 NovRybnik 16:09−2 min—
Mon 16 NovRybnik 16:130 min—
Fri 13 NovRybnik 16:09−1 min—
Thu 12 NovRybnik 16:120 min—
Tue 10 NovRybnik 16:17+4 min+4 min
Mon 9 NovRybnik 16:17+5 min+5 min
Fri 6 NovRybnik 16:09−1 min—
Thu 5 NovRybnik 16:120 min—
Wed 4 NovRybnik 16:120 min—
Tue 3 NovRybnik 16:10−1 min—
Mon 2 NovRybnik 16:120 min+1 min
Fri 30 OctRybnik 16:11−1 min—
Thu 29 OctRybnik 16:120 min—
Wed 28 OctRybnik 16:12No data—
Tue 27 OctRybnik 16:10−2 min—
Mon 26 OctRybnik 16:130 min—
Fri 23 OctRybnik 16:13No data—
Thu 22 OctRybnik 16:12No data—
Wed 21 OctRybnik 16:13No data—
Tue 20 OctRybnik 16:12No data—
Mon 19 OctRybnik 16:13No data—
Fri 16 OctRybnik 16:13+1 min+1 min
Thu 15 OctRybnik 16:12No data—
Wed 14 OctRybnik 16:120 min—
Tue 13 OctRybnik 16:130 min—
Mon 12 OctRybnik 16:120 min—
Fri 9 OctRybnik 16:11−1 min—
Thu 8 OctRybnik 16:10−2 min—
Wed 7 OctRybnik 16:10−2 min—
Tue 6 OctRybnik 16:10−2 min—