S18 40750 Gliwice – Bytom

View line S18

Gliwice 04:09 → Bytom 04:27 Mon, Tue, Wed, Thu, Fri 0 h 18 min · 4 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Bytom at 04:27 −1 min

  1. Gliwice04:09
  2. Zabrze Maciejów04:15
  3. Zabrze Północne04:18
  4. Bytom04:27

Next service: Monday 04:09 from Gliwice · Mon 9 Nov

Next departure 04:09 Monday · Gliwice
On-time · 30 days
88%
15/17 runs under 3 min
RT coverage: 17 full · 0 partial · 5 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 25 full · 0 partial · 25 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

  • Mon 2 Nov Max en route +10 min · last fix heading to Bytom +10 min
  • Fri 16 Oct Max en route +3 min · last fix heading to Bytom +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=6
  • 75% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
04:09on time +2 min
04:15≈ on time ≈ +2 min
04:18 / 04:19≈ on time ≈ +2 min
04:27on 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
Fri 6 NovBytom 04:27−1 min—
Thu 5 NovBytom 04:27−1 min—
Wed 4 NovBytom 04:280 min—
Tue 3 NovBytom 04:280 min—
Mon 2 NovBytom 04:37+10 min+10 min
Fri 30 OctBytom 04:280 min—
Thu 29 OctBytom 04:30+2 min+2 min
Wed 28 OctBytom 04:29+1 min+1 min
Tue 27 OctBytom 04:290 min—
Mon 26 OctBytom 04:28No data—
Fri 23 OctBytom 04:28No data—
Thu 22 OctBytom 04:28No data—
Wed 21 OctBytom 04:28No data—
Tue 20 OctBytom 04:28No data—
Mon 19 OctBytom 04:280 min—
Fri 16 OctBytom 04:32+3 min+3 min
Thu 15 OctBytom 04:280 min—
Wed 14 OctBytom 04:280 min—
Tue 13 OctBytom 04:280 min—
Mon 12 OctBytom 04:28+1 min+1 min
Fri 9 OctBytom 04:280 min—
Thu 8 OctBytom 04:290 min—
Wed 7 OctBytom 04:280 min—
Tue 6 OctBytom 04:280 min—
Mon 5 OctBytom 04:290 min—
Fri 2 OctBytom 04:26No data—
Thu 1 OctBytom 04:27No data—
Wed 30 SeptBytom 04:26No data—
Tue 29 SeptBytom 04:26No data—
Mon 28 SeptBytom 04:26No data—