S18 40721 Bytom – Gliwice

View line S18

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:09 from Bytom · Fri 6 Nov

Next departure 17:09 today · Bytom
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 8 no data
On-time · 90 days
94%
30/32 runs under 3 min
RT coverage: 32 full · 0 partial · 34 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: +2 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

  • Sun 1 Nov Max en route +14 min · last fix heading to Gliwice +14 min
  • Sat 31 Oct Max en route +7 min · last fix heading to Gliwice +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 30
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=7
  • 100% F n=4
  • 67% S n=3
  • 80% S n=5

Stops and timetable

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

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