S18 40713 Bytom – Gliwice

View line S18

Bytom 13:06 → Gliwice 13:24 Daily 0 h 18 min · 4 stops Koleje Śląskie

✓ Today’s run finished

Today, last fix heading to Gliwice at 13:24 No data

  1. Bytom13:06
  2. Zabrze Północne13:14
  3. Zabrze Maciejów13:17
  4. Gliwice13:24

Next service: tomorrow 13:06 from Bytom · Fri 13 Nov

Next departure 13:06 tomorrow · Bytom
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 19 full · 0 partial · 11 no data
On-time · 90 days
83%
33/40 runs under 3 min
RT coverage: 40 full · 0 partial · 35 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: +4 min

Last 30 days

Arrival delay at Gliwice, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 29 Sept Max en route +9 min · last fix heading to Zabrze Maciejów +7 min
  • Sun 1 Nov Max en route +7 min · last fix heading to Gliwice +7 min
  • Fri 2 Oct Max en route +6 min · last fix heading to Zabrze Maciejów +6 min
  • Wed 30 Sept Max en route +6 min · last fix heading to Zabrze Maciejów +6 min
  • Sun 8 Nov Max en route +5 min · last fix heading to Gliwice +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 33
  • 3–10 min 18% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 40 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
13:06on time +4 min
13:14≈ on time ≈ +4 min
13:17 / 13:18≈ on time ≈ +4 min
13:24on 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 12 NovGliwice 13:24No data—
Wed 11 NovGliwice 13:240 min—
Tue 10 NovGliwice 13:240 min—
Mon 9 NovGliwice 13:240 min—
Sun 8 NovGliwice 13:29+4 min+5 min
Sat 7 NovGliwice 13:24No data—
Fri 6 NovGliwice 13:29+4 min+4 min
Thu 5 NovGliwice 13:24−1 min—
Wed 4 NovGliwice 13:240 min—
Tue 3 NovGliwice 13:250 min—
Mon 2 NovGliwice 13:24No data—
Sun 1 NovGliwice 13:32+7 min+7 min
Sat 31 OctGliwice 13:250 min—
Fri 30 OctGliwice 13:250 min—
Thu 29 OctGliwice 13:250 min—
Wed 28 OctGliwice 13:250 min—
Tue 27 OctGliwice 13:25No data—
Mon 26 OctGliwice 13:260 min—
Sun 25 OctGliwice 13:25No data—
Sat 24 OctGliwice 13:27No data—
Fri 23 OctGliwice 13:27No data—
Thu 22 OctGliwice 13:27No data—
Wed 21 OctGliwice 13:27No data—
Tue 20 OctGliwice 13:28No data—
Mon 19 OctGliwice 13:27No data—
Sun 18 OctGliwice 13:280 min—
Sat 17 OctGliwice 13:280 min—
Fri 16 OctGliwice 13:270 min—
Thu 15 OctGliwice 13:28+1 min+1 min
Wed 14 OctGliwice 13:280 min—