S18 40723 Bytom – Gliwice

View line S18

Bytom 18:09 → Gliwice 18:27 Daily 0 h 18 min · 4 stops Koleje Śląskie

✓ Today’s run finished

Today it reached Gliwice at 18:27 0 min

  1. Bytom18:09
  2. Zabrze Północne18:17
  3. Zabrze Maciejów18:20
  4. Gliwice18:27

Next service: tomorrow 18:09 from Bytom · Sat 21 Nov

Next departure 18:09 tomorrow · Bytom
On-time · 30 days
92%
22/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
93%
43/46 runs under 3 min
RT coverage: 46 full · 0 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sun 1 Nov Max en route +9 min · last fix heading to Gliwice +9 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Gliwice +4 min
  • Sun 20 Sept Max en route +3 min · last fix heading to Gliwice +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 43
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 83% T n=6
  • 100% W n=7
  • 100% T n=8
  • 100% F n=6
  • 100% S n=5
  • 75% S n=8

Stops and timetable

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

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