S18 40739 Bytom – Gliwice

View line S18

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

It has not run yet today

Last recorded run: Friday 13 November 0 min

Next service: today 20:09 from Bytom · Sat 14 Nov

Next departure 20:09 today · Bytom
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
96%
43/45 runs under 3 min
RT coverage: 45 full · 0 partial · 27 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: 0 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

  • Wed 2 Sept Max en route +9 min · last fix heading to Zabrze Maciejów +9 min
  • Sun 1 Nov Max en route +7 min · last fix heading to Gliwice +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 43
  • 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
  • 83% W n=6
  • 100% T n=8
  • 100% F n=5
  • 100% S n=7
  • 88% S n=8

Stops and timetable

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

Last 90 days, 45 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:09on time +1 min
20:17≈ on time ≈ +1 min
20:20 / 20:21≈ on time ≈ +1 min
20:27on 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 13 NovGliwice 20:290 min—
Thu 12 NovGliwice 20:280 min—
Wed 11 NovGliwice 20:280 min—
Tue 10 NovGliwice 20:280 min—
Mon 9 NovGliwice 20:280 min—
Sun 8 NovGliwice 20:280 min—
Sat 7 NovGliwice 20:280 min—
Fri 6 NovGliwice 20:28No data—
Thu 5 NovGliwice 20:29No data—
Wed 4 NovGliwice 20:280 min—
Tue 3 NovGliwice 20:290 min—
Mon 2 NovGliwice 20:280 min—
Sun 1 NovGliwice 20:34+7 min+7 min
Sat 31 OctGliwice 20:290 min—
Fri 30 OctGliwice 20:280 min—
Thu 29 OctGliwice 20:27−1 min—
Wed 28 OctGliwice 20:27−1 min—
Tue 27 OctGliwice 20:280 min—
Mon 26 OctGliwice 20:290 min—
Sun 25 OctGliwice 20:28No data—
Sat 24 OctGliwice 20:34No data—
Fri 23 OctGliwice 20:34No data—
Thu 22 OctGliwice 20:33No data—
Wed 21 OctGliwice 20:33No data—
Tue 20 OctGliwice 20:33No data—
Mon 19 OctGliwice 20:33No data—
Sun 18 OctGliwice 20:330 min—
Sat 17 OctGliwice 20:330 min—
Fri 16 OctGliwice 20:340 min—
Thu 15 OctGliwice 20:33−1 min—