S18 40719 Bytom – Gliwice

View line S18

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

It has not run yet today

Last recorded run: Friday 20 November +2 min

Next service: today 16:10 from Bytom · Sat 21 Nov

Next departure 16:10 today · Bytom
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 5 no data
On-time · 90 days
96%
44/46 runs under 3 min
RT coverage: 46 full · 0 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 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 +7 min · last fix heading to Gliwice +7 min
  • Sun 13 Sept Max en route +6 min · last fix heading to Zabrze Maciejów +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 44
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 46 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
16:10on time on time
16:18≈ on time ≈ on time
16:21 / 16:22≈ on time ≈ +1 min
16:28on time +1 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
Fri 20 NovGliwice 16:29+2 min+2 min
Thu 19 NovGliwice 16:290 min—
Wed 18 NovGliwice 16:290 min—
Tue 17 NovGliwice 16:290 min—
Mon 16 NovGliwice 16:290 min—
Sat 14 NovGliwice 16:290 min—
Fri 13 NovGliwice 16:290 min—
Thu 12 NovGliwice 16:290 min—
Wed 11 NovGliwice 16:290 min—
Tue 10 NovGliwice 16:290 min—
Mon 9 NovGliwice 16:290 min—
Sun 8 NovGliwice 16:290 min—
Sat 7 NovGliwice 16:290 min—
Fri 6 NovGliwice 16:29No data—
Thu 5 NovGliwice 16:29No data—
Wed 4 NovGliwice 16:290 min—
Tue 3 NovGliwice 16:29+1 min+2 min
Mon 2 NovGliwice 16:290 min—
Sun 1 NovGliwice 16:36+7 min+7 min
Sat 31 OctGliwice 16:300 min—
Fri 30 OctGliwice 16:290 min—
Thu 29 OctGliwice 16:290 min—
Wed 28 OctGliwice 16:290 min—
Sun 25 OctGliwice 16:29No data—
Sat 24 OctGliwice 16:29No data—
Fri 23 OctGliwice 16:30No data—
Thu 22 OctGliwice 16:29No data—
Wed 21 OctGliwice 16:30No data—
Tue 20 OctGliwice 16:29No data—
Mon 19 OctGliwice 16:29No data—