S18 40770 Gliwice – Bytom

View line S18

Gliwice 15:36 → Bytom 15:54 Daily 0 h 18 min · 4 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Bytom at 15:54 0 min

  1. Gliwice15:36
  2. Zabrze Maciejów15:42
  3. Zabrze Północne15:45
  4. Bytom15:54

Next service: tomorrow 15:36 from Gliwice · Sun 8 Nov

Next departure 15:36 tomorrow · Gliwice
On-time · 30 days
75%
15/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
On-time · 90 days
73%
30/41 runs under 3 min
RT coverage: 41 full · 0 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +14 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 26 Oct Max en route +29 min · last fix heading to Gliwice +29 min
  • Tue 3 Nov Max en route +15 min · last fix heading to Bytom +15 min
  • Wed 4 Nov Max en route +14 min · last fix heading to Bytom +14 min
  • Sun 1 Nov Max en route +9 min · last fix heading to Bytom +9 min
  • Wed 30 Sept Max en route +8 min · last fix heading to Zabrze Północne +8 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 68% · 28
  • 3–10 min 20% · 8
  • 10–30 min 7% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 67% T n=6
  • 57% W n=7
  • 83% T n=6
  • 67% F n=6
  • 100% S n=4
  • 83% S n=6

Stops and timetable

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

Last 90 days, 41 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
15:36on time +8 min
15:42≈ on time ≈ +8 min
15:45 / 15:46≈ on time ≈ +8 min
15:54on time +8 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
Sat 7 NovBytom 15:540 min—
Fri 6 NovBytom 15:54No data—
Thu 5 NovBytom 15:54No data—
Wed 4 NovBytom 16:09+14 min+14 min
Tue 3 NovBytom 16:10+15 min+15 min
Mon 2 NovBytom 15:540 min—
Sun 1 NovBytom 16:04+9 min+9 min
Sat 31 OctBytom 15:550 min—
Fri 30 OctBytom 15:56+1 min+1 min
Thu 29 OctBytom 15:550 min—
Wed 28 OctBytom 15:58+3 min+3 min
Mon 26 OctGliwice 16:03+29 min+29 min
Sun 25 OctBytom 15:55No data—
Sat 24 OctBytom 15:54No data—
Fri 23 OctBytom 15:54No data—
Thu 22 OctBytom 15:54No data—
Wed 21 OctBytom 15:55No data—
Tue 20 OctBytom 15:54No data—
Mon 19 OctBytom 15:55No data—
Sun 18 OctBytom 15:53−1 min—
Sat 17 OctBytom 15:550 min—
Fri 16 OctBytom 15:540 min—
Thu 15 OctBytom 15:53−1 min—
Wed 14 OctBytom 15:540 min—
Tue 13 OctBytom 15:550 min—
Mon 12 OctBytom 15:540 min—
Sun 11 OctBytom 15:540 min—
Sat 10 OctBytom 15:550 min—
Fri 9 OctBytom 15:540 min—
Thu 8 OctBytom 15:540 min—