S18 40780 Gliwice – Bytom

View line S18

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

It has not run yet today

Last recorded run: Wednesday 11 November +9 min

Next service: today 21:40 from Gliwice · Thu 12 Nov

Next departure 21:40 today · Gliwice
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
88%
42/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
+5min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Thu 10 Sept Max en route +10 min · last fix heading to Zabrze Północne +10 min
  • Wed 11 Nov Max en route +9 min · last fix heading to Bytom +9 min
  • Sun 1 Nov Max en route +9 min · last fix heading to Bytom +9 min
  • Tue 22 Sept Max en route +6 min · last fix heading to Bytom +6 min
  • Mon 21 Sept Max en route +6 min · last fix heading to Bytom +6 min

Distribution · 90 days

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

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

On-time by weekday

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

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