S18 40762 Gliwice – Bytom

View line S18

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 09:40 from Gliwice · Mon 16 Nov

Next departure 09:40 today · Gliwice
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
93%
43/46 runs under 3 min
RT coverage: 46 full · 0 partial · 32 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sun 1 Nov Max en route +9 min · last fix heading to Bytom +9 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Bytom +5 min
  • Wed 11 Nov Max en route +3 min · last fix heading to Bytom +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 91% · 42
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 86% W n=7
  • 100% T n=4
  • 86% F n=7
  • 100% S n=7
  • 89% S n=9

Stops and timetable

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

Last 90 days, 46 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
09:40on time on time
09:46≈ on time ≈ +1 min
09:49 / 09:50≈ on time ≈ +1 min
09:58on time +2 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
Sun 15 NovBytom 09:590 min—
Sat 14 NovBytom 09:590 min—
Fri 13 NovBytom 10:04+5 min+5 min
Thu 12 NovBytom 09:59No data—
Wed 11 NovBytom 10:02+3 min+3 min
Tue 10 NovBytom 09:590 min—
Mon 9 NovBytom 09:58−1 min—
Sun 8 NovBytom 09:590 min+1 min
Sat 7 NovBytom 09:59No data—
Fri 6 NovBytom 09:590 min—
Thu 5 NovBytom 09:590 min—
Wed 4 NovBytom 09:590 min—
Tue 3 NovBytom 09:590 min—
Mon 2 NovBytom 09:590 min—
Sun 1 NovBytom 10:08+9 min+9 min
Sat 31 OctBytom 09:590 min—
Fri 30 OctBytom 09:590 min—
Thu 29 OctBytom 09:58−1 min—
Wed 28 OctBytom 09:590 min—
Tue 27 OctBytom 09:59No data—
Mon 26 OctBytom 09:590 min—
Sun 25 OctBytom 09:59No data—
Sat 24 OctBytom 09:59No data—
Fri 23 OctBytom 09:59No data—
Thu 22 OctBytom 09:59No data—
Wed 21 OctBytom 09:59No data—
Tue 20 OctBytom 09:59No data—
Mon 19 OctBytom 09:590 min—
Sun 18 OctBytom 09:590 min—
Sat 17 OctBytom 09:590 min—