S18 40784 Gliwice – Bytom

View line S18

Gliwice 10:40 → Bytom 10:58 Daily 0 h 18 min · 4 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Bytom at 10:58 0 min

  1. Gliwice10:40
  2. Zabrze Maciejów10:46
  3. Zabrze Północne10:49
  4. Bytom10:58

Next service: tomorrow 10:40 from Gliwice · Sat 14 Nov

Next departure 10:40 tomorrow · Gliwice
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Bytom, 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 +8 min · last fix heading to Bytom +8 min

Distribution · 90 days

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

  • Early 13% · 6
  • On time 85% · 41
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=6
  • 100% T n=7
  • 100% F n=7
  • 100% S n=5
  • 83% S n=6

Stops and timetable

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

Last 90 days, 48 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
10:40on time on time
10:46≈ on time ≈ on time
10:49 / 10:50≈ on time ≈ on time
10:58on time on time

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
Fri 13 NovBytom 10:590 min—
Thu 12 NovBytom 10:590 min—
Wed 11 NovBytom 10:590 min—
Tue 10 NovBytom 10:590 min—
Mon 9 NovBytom 10:590 min—
Sun 8 NovBytom 10:590 min—
Sat 7 NovBytom 10:590 min—
Fri 6 NovBytom 10:590 min—
Thu 5 NovBytom 10:590 min—
Wed 4 NovBytom 10:590 min—
Tue 3 NovBytom 10:590 min—
Mon 2 NovBytom 10:590 min—
Sun 1 NovBytom 11:07+8 min+8 min
Sat 31 OctBytom 10:590 min—
Fri 30 OctBytom 10:590 min—
Thu 29 OctBytom 10:58−1 min—
Wed 28 OctBytom 10:590 min—
Tue 27 OctBytom 10:59No data—
Mon 26 OctBytom 10:590 min—
Sun 25 OctBytom 10:59No data—
Sat 24 OctBytom 10:59No data—
Fri 23 OctBytom 10:59No data—
Thu 22 OctBytom 10:59No data—
Wed 21 OctBytom 10:59No data—
Tue 20 OctBytom 10:59No data—
Mon 19 OctBytom 11:000 min—
Sun 18 OctBytom 10:590 min—
Sat 17 OctBytom 10:590 min—
Fri 16 OctBytom 10:590 min—
Thu 15 OctBytom 10:590 min—