S1 40909 Katowice – Gliwice

View line S1

Katowice 09:04 → Gliwice 09:32 Wed, Sat, Sun 0 h 28 min · 8 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Gliwice at 09:32 0 min

  1. Katowice09:04
  2. Katowice Załęże09:07
  3. Chorzów Batory09:11
  4. Ruda Chebzie09:17
  5. Ruda Śląska09:20
  6. Zabrze09:24
  7. Gliwice09:32

Next service: tomorrow 09:04 from Katowice · Sun 8 Nov

Next departure 09:04 tomorrow · Katowice
On-time · 30 days
71%
5/7 runs under 3 min
RT coverage: 7 full · 0 partial · 2 no data
On-time · 90 days
85%
11/13 runs under 3 min
RT coverage: 13 full · 0 partial · 7 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +9 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

  • Sun 1 Nov Max en route +13 min · last fix heading to Gliwice +13 min
  • Sat 31 Oct Max en route +6 min · last fix heading to Gliwice +6 min

Distribution · 90 days

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

  • Early 15% · 2
  • On time 69% · 9
  • 3–10 min 8% · 1
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 83% S n=6
  • 86% S n=7

Stops and timetable

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

Last 90 days, 13 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
09:04on time +2 min
09:07≈ +1 min ≈ +2 min
09:11 / 09:12≈ +1 min ≈ +2 min
09:14≈ +1 min ≈ +2 min
09:17 / 09:18≈ +1 min ≈ +3 min
09:20 / 09:21≈ +1 min ≈ +3 min
09:24 / 09:25≈ +1 min ≈ +4 min
09:32+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
Sat 7 NovGliwice 09:330 min—
Sun 1 NovGliwice 09:46+13 min+13 min
Sat 31 OctGliwice 09:39+6 min+6 min
Sun 25 OctGliwice 09:33No data—
Sat 24 OctGliwice 09:18No data—
Sun 18 OctGliwice 09:190 min—
Sat 17 OctGliwice 09:180 min—
Sun 11 OctGliwice 09:16−2 min—
Sat 10 OctGliwice 09:180 min—
Sun 4 OctGliwice 09:19+1 min+1 min
Sat 3 OctGliwice 09:16+2 min+2 min
Sun 27 SeptGliwice 09:16No data—
Sat 26 SeptGliwice 09:16No data—
Sun 20 SeptGliwice 09:16+1 min+1 min
Sat 19 SeptGliwice 09:16No data—
Sun 13 SeptGliwice 09:17+1 min+1 min
Sat 12 SeptGliwice 09:16+1 min+1 min
Sun 6 SeptGliwice 09:16−2 min—
Sat 5 SeptGliwice 09:16No data—
Sun 30 AugGliwice 09:16No data—