S18 40786 Gliwice – Bytom

View line S18

Gliwice 12:38 → Bytom 12:56 Daily 0 h 18 min · 4 stops Koleje Śląskie

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 12:38 from Gliwice · Sun 15 Nov

Next departure 12:38 today · Gliwice
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 47 full · 0 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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 30 Sept Max en route +12 min · last fix heading to Zabrze Maciejów +12 min
  • Sun 1 Nov Max en route +9 min · last fix heading to Bytom +9 min

Distribution · 90 days

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

  • Early 21% · 10
  • On time 74% · 35
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 47 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
12:38on time on time
12:44≈ on time ≈ on time
12:47 / 12:48≈ on time ≈ on time
12:56on time on time

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
Sat 14 NovBytom 12:570 min—
Fri 13 NovBytom 12:54−2 min—
Thu 12 NovBytom 12:54−2 min—
Wed 11 NovBytom 12:570 min—
Tue 10 NovBytom 12:580 min—
Mon 9 NovBytom 12:580 min—
Sun 8 NovBytom 12:580 min—
Sat 7 NovBytom 12:570 min—
Fri 6 NovBytom 12:54−1 min—
Thu 5 NovBytom 12:570 min—
Wed 4 NovBytom 12:570 min—
Tue 3 NovBytom 12:580 min—
Mon 2 NovBytom 12:57No data—
Sun 1 NovBytom 13:06+9 min+9 min
Sat 31 OctBytom 12:570 min—
Fri 30 OctBytom 12:570 min—
Thu 29 OctBytom 12:570 min—
Wed 28 OctBytom 12:570 min—
Tue 27 OctBytom 12:57No data—
Mon 26 OctBytom 12:570 min—
Sun 25 OctBytom 12:57No data—
Sat 24 OctBytom 12:59No data—
Fri 23 OctBytom 12:59No data—
Thu 22 OctBytom 12:59No data—
Wed 21 OctBytom 12:59No data—
Tue 20 OctBytom 13:00No data—
Mon 19 OctBytom 12:59No data—
Sun 18 OctBytom 13:000 min—
Sat 17 OctBytom 12:590 min—
Fri 16 OctBytom 12:590 min—