S18 40756 Gliwice – Bytom

View line S18

Gliwice 06:41 → Bytom 06:59 Daily 0 h 18 min · 4 stops Koleje Śląskie

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 06:41 from Gliwice · Fri 6 Nov

Next departure 06:41 today · Gliwice
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
93%
37/40 runs under 3 min
RT coverage: 40 full · 0 partial · 27 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: +2 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 +8 min · last fix heading to Bytom +8 min
  • Mon 12 Oct Max en route +6 min · last fix heading to Bytom +6 min
  • Thu 1 Oct Max en route +3 min · last fix heading to Bytom +3 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 88% · 35
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=6
  • 100% W n=5
  • 88% T n=8
  • 100% F n=6
  • 100% S n=4
  • 75% S n=4

Stops and timetable

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

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