S18 40776 Gliwice – Bytom

View line S18

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

✓ Today’s run finished

Today it reached Bytom at 18:58 0 min

  1. Gliwice18:40
  2. Zabrze Maciejów18:46
  3. Zabrze Północne18:49
  4. Bytom18:58

Next service: tomorrow 18:40 from Gliwice · Mon 16 Nov

Next departure 18:40 tomorrow · Gliwice
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
91%
40/44 runs under 3 min
RT coverage: 44 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: 0 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

  • Wed 11 Nov Max en route +10 min · last fix heading to Bytom +10 min
  • Sun 1 Nov Max en route +9 min · last fix heading to Bytom +9 min
  • Thu 17 Sept Max en route +4 min · last fix heading to Bytom +4 min
  • Fri 25 Sept Max en route +3 min · last fix heading to Bytom +3 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 86% · 38
  • 3–10 min 7% · 3
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=7
  • 83% W n=6
  • 86% T n=7
  • 80% F n=5
  • 100% S n=8
  • 83% S n=6

Stops and timetable

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

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