S18 40788 Gliwice – Bytom

View line S18

Gliwice 20:37 → Bytom 20:55 Daily 0 h 18 min · 4 stops Koleje Śląskie

It has not run yet today

Last recorded run: Tuesday 17 November −1 min

Next service: today 20:37 from Gliwice · Wed 18 Nov

Next departure 20:37 today · Gliwice
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
88%
45/51 runs under 3 min
RT coverage: 51 full · 0 partial · 27 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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 +13 min · last fix heading to Zabrze Maciejów +13 min
  • Sun 1 Nov Max en route +9 min · last fix heading to Bytom +9 min
  • Fri 16 Oct Max en route +3 min · last fix heading to Bytom +3 min
  • Wed 14 Oct Max en route +3 min · last fix heading to Bytom +3 min
  • Wed 2 Sept Max en route +3 min · last fix heading to Bytom +3 min

Distribution · 90 days

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

  • Early 12% · 6
  • On time 76% · 39
  • 3–10 min 10% · 5
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 89% T n=9
  • 78% W n=9
  • 83% T n=6
  • 83% F n=6
  • 100% S n=6
  • 86% S n=7

Stops and timetable

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

Last 90 days, 51 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
20:37on time +3 min
20:43≈ on time ≈ +3 min
20:46 / 20:47≈ on time ≈ +3 min
20:55on time +3 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 17 NovBytom 20:54−1 min—
Mon 16 NovBytom 20:540 min—
Sun 15 NovBytom 20:540 min—
Sat 14 NovBytom 20:58+2 min+2 min
Fri 13 NovBytom 20:59+2 min+2 min
Thu 12 NovBytom 20:58+2 min+2 min
Wed 11 NovBytom 20:540 min—
Tue 10 NovBytom 20:540 min—
Mon 9 NovBytom 20:540 min—
Sun 8 NovBytom 20:540 min—
Sat 7 NovBytom 20:540 min—
Fri 6 NovBytom 20:54No data—
Thu 5 NovBytom 20:57No data—
Wed 4 NovBytom 20:540 min—
Tue 3 NovBytom 20:570 min—
Mon 2 NovBytom 20:540 min—
Sun 1 NovBytom 21:04+9 min+9 min
Sat 31 OctBytom 20:58+1 min+1 min
Fri 30 OctBytom 20:57+1 min+1 min
Thu 29 OctBytom 20:560 min—
Wed 28 OctBytom 20:560 min—
Tue 27 OctBytom 20:560 min—
Mon 26 OctBytom 20:570 min—
Sun 25 OctBytom 20:56No data—
Sat 24 OctBytom 21:04No data—
Fri 23 OctBytom 21:04No data—
Thu 22 OctBytom 21:03No data—
Wed 21 OctBytom 21:03No data—
Tue 20 OctBytom 21:03No data—
Mon 19 OctBytom 21:03No data—