S18 40764 Gliwice – Bytom

View line S18

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

✓ Today’s run finished

Today it reached Bytom at 11:58 0 min

  1. Gliwice11:40
  2. Zabrze Maciejów11:46
  3. Zabrze Północne11:49
  4. Bytom11:58

Next service: tomorrow 11:40 from Gliwice · Fri 20 Nov

Next departure 11:40 tomorrow · Gliwice
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
86%
44/51 runs under 3 min
RT coverage: 51 full · 0 partial · 31 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +1 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 +9 min · last fix heading to Bytom +9 min
  • Fri 9 Oct Max en route +9 min · last fix heading to Bytom +7 min
  • Wed 30 Sept Max en route +5 min · last fix heading to Bytom +5 min
  • Sun 13 Sept Max en route +5 min · last fix heading to Bytom +5 min
  • Sat 12 Sept Max en route +5 min · last fix heading to Bytom +5 min

Distribution · 90 days

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

  • Early 8% · 4
  • On time 78% · 40
  • 3–10 min 14% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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