S18 40731 Bytom → Gliwice

View line S18

Bytom 23:26 → Gliwice 23:44 Mon, Tue, Wed, Thu, Fri 0 h 18 min · 4 stops Koleje Śląskie

S18 40731 Bytom–Gliwice: final delay under 3 min on 14 of its 17 runs with data in the last 30 days (82%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 03:46 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 23:26 from Bytom · Mon 23 Nov

Next departure 23:26 tomorrow · Bytom
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 17 full · 0 partial · 2 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 33 full · 0 partial · 25 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: +5 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

  • Tue 17 Nov Max en route +7 min · last fix heading to Gliwice +7 min
  • Mon 16 Nov Max en route +7 min · last fix heading to Gliwice +7 min
  • Mon 2 Nov Max en route +3 min · last fix heading to Gliwice +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 30
  • 3–10 min 9% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 83% T n=6
  • 100% W n=6
  • 100% T n=9
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
23:26on time +1 min
23:34≈ on time ≈ +1 min
23:37 / 23:38≈ on time ≈ +1 min
23:44on 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 23:440 min—
Thu 19 NovGliwice 23:440 min—
Wed 18 NovGliwice 23:440 min—
Tue 17 NovGliwice 23:53+7 min+7 min
Mon 16 NovGliwice 23:52+7 min+7 min
Fri 13 NovGliwice 23:440 min—
Thu 12 NovGliwice 23:440 min—
Tue 10 NovGliwice 23:450 min—
Mon 9 NovGliwice 23:44+1 min+1 min
Fri 6 NovGliwice 23:44No data—
Thu 5 NovGliwice 23:44No data—
Wed 4 NovGliwice 23:440 min—
Tue 3 NovGliwice 23:440 min—
Mon 2 NovGliwice 23:48+3 min+3 min
Fri 30 OctGliwice 23:450 min—
Thu 29 OctGliwice 23:44−1 min—
Wed 28 OctGliwice 23:44−1 min—
Tue 27 OctGliwice 23:450 min—
Mon 26 OctGliwice 23:460 min—
Fri 23 OctGliwice 23:41No data—
Thu 22 OctGliwice 23:40No data—
Wed 21 OctGliwice 23:40No data—
Tue 20 OctGliwice 23:40No data—
Mon 19 OctGliwice 23:40No data—
Fri 16 OctGliwice 23:400 min—
Thu 15 OctGliwice 23:410 min—
Wed 14 OctGliwice 23:410 min—
Tue 13 OctGliwice 23:400 min—
Mon 12 OctGliwice 23:400 min—
Fri 9 OctGliwice 23:400 min—