S18 40717 Bytom – Gliwice

View line S18

Bytom 15:07 → Gliwice 15:25 Daily 0 h 18 min · 4 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Gliwice at 15:25 0 min

  1. Bytom15:07
  2. Zabrze Północne15:15
  3. Zabrze Maciejów15:18
  4. Gliwice15:25

Next service: tomorrow 15:07 from Bytom · Wed 11 Nov

Next departure 15:07 tomorrow · Bytom
On-time · 30 days
57%
12/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
66%
27/41 runs under 3 min
RT coverage: 41 full · 0 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +7 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 26 Oct Max en route +79 min · last fix heading to Gliwice +79 min
  • Tue 27 Oct Max en route +77 min · last fix heading to Gliwice +77 min
  • Mon 31 Aug Max en route +12 min · last fix heading to Zabrze Północne +12 min
  • Sun 4 Oct Max en route +7 min · last fix heading to Gliwice +7 min
  • Sun 1 Nov Max en route +7 min · last fix heading to Gliwice +7 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 63% · 26
  • 3–10 min 27% · 11
  • 10–30 min 2% · 1
  • 30+ min 5% · 2

On-time by weekday

  • 50% M n=6
  • 57% T n=7
  • 50% W n=4
  • 100% T n=5
  • 100% F n=6
  • 60% S n=5
  • 50% S n=8

Stops and timetable

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

Last 90 days, 41 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:07on time +5 min
15:15≈ on time ≈ +7 min
15:18 / 15:19≈ on time ≈ +7 min
15:25on time +7 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 10 NovGliwice 15:240 min—
Mon 9 NovGliwice 15:240 min—
Sun 8 NovGliwice 15:29+5 min+5 min
Sat 7 NovGliwice 15:29+5 min+5 min
Fri 6 NovGliwice 15:24No data—
Thu 5 NovGliwice 15:24No data—
Wed 4 NovGliwice 15:29+3 min+3 min
Tue 3 NovGliwice 15:30+3 min+3 min
Mon 2 NovGliwice 15:29+4 min+4 min
Sun 1 NovGliwice 15:33+7 min+7 min
Sat 31 OctGliwice 15:270 min—
Fri 30 OctGliwice 15:260 min—
Thu 29 OctGliwice 15:260 min—
Wed 28 OctGliwice 15:31+5 min+5 min
Tue 27 OctGliwice 16:43+77 min+77 min
Mon 26 OctGliwice 16:46+79 min+79 min
Sun 25 OctGliwice 15:26No data—
Sat 24 OctGliwice 15:26No data—
Fri 23 OctGliwice 15:27No data—
Thu 22 OctGliwice 15:26No data—
Wed 21 OctGliwice 15:27No data—
Tue 20 OctGliwice 15:26No data—
Mon 19 OctGliwice 15:27No data—
Sun 18 OctGliwice 15:260 min—
Sat 17 OctGliwice 15:270 min—
Fri 16 OctGliwice 15:260 min—
Thu 15 OctGliwice 15:25−1 min—
Wed 14 OctGliwice 15:260 min—
Tue 13 OctGliwice 15:260 min—
Mon 12 OctGliwice 15:260 min—