S18 40715 Bytom → Gliwice

View line S18

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

It has not run yet today

Last recorded run: Friday 20 November +4 min

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

Next departure 14:10 today · Bytom
On-time · 30 days
83%
20/24 runs under 3 min
RT coverage: 24 full · 0 partial · 5 no data
On-time · 90 days
71%
35/49 runs under 3 min
RT coverage: 49 full · 0 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+12min
9 in 10 runs arrive with less than this
30 days: +3 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 16 Sept Max en route +15 min · last fix heading to Zabrze Północne +15 min
  • Thu 8 Oct Max en route +13 min · last fix heading to Gliwice +13 min
  • Wed 7 Oct Max en route +13 min · last fix heading to Gliwice +13 min
  • Tue 6 Oct Max en route +13 min · last fix heading to Gliwice +13 min
  • Mon 5 Oct Max en route +13 min · last fix heading to Gliwice +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 71% · 35
  • 3–10 min 14% · 7
  • 10–30 min 14% · 7
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 43% T n=7
  • 63% W n=8
  • 71% T n=7
  • 67% F n=6
  • 100% S n=6
  • 88% S n=8

Stops and timetable

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

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