S18 40705 Bytom – Gliwice

View line S18

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

✓ Today’s run finished

Today it reached Gliwice at 07:27 0 min

  1. Bytom07:09
  2. Zabrze Północne07:17
  3. Zabrze Maciejów07:20
  4. Gliwice07:27

Next service: tomorrow 07:09 from Bytom · Mon 9 Nov

Next departure 07:09 tomorrow · Bytom
On-time · 30 days
95%
21/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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 +7 min · last fix heading to Gliwice +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 37
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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
07:09on time on time
07:17≈ on time ≈ on time
07:20 / 07:21≈ on time ≈ on time
07:27on time on time

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
Sun 8 NovGliwice 07:280 min—
Sat 7 NovGliwice 07:28No data—
Fri 6 NovGliwice 07:290 min—
Thu 5 NovGliwice 07:280 min—
Wed 4 NovGliwice 07:280 min—
Tue 3 NovGliwice 07:280 min—
Mon 2 NovGliwice 07:280 min—
Sun 1 NovGliwice 07:35+7 min+7 min
Sat 31 OctGliwice 07:280 min—
Fri 30 OctGliwice 07:280 min—
Thu 29 OctGliwice 07:280 min—
Wed 28 OctGliwice 07:280 min—
Tue 27 OctGliwice 07:28No data—
Mon 26 OctGliwice 07:280 min—
Sun 25 OctGliwice 07:28No data—
Sat 24 OctGliwice 07:28No data—
Fri 23 OctGliwice 07:28No data—
Thu 22 OctGliwice 07:28No data—
Wed 21 OctGliwice 07:28No data—
Tue 20 OctGliwice 07:28No data—
Mon 19 OctGliwice 07:280 min—
Sun 18 OctGliwice 07:27−1 min—
Sat 17 OctGliwice 07:280 min—
Fri 16 OctGliwice 07:280 min—
Thu 15 OctGliwice 07:280 min—
Wed 14 OctGliwice 07:290 min—
Tue 13 OctGliwice 07:280 min—
Mon 12 OctGliwice 07:290 min—
Sun 11 OctGliwice 07:280 min—
Sat 10 OctGliwice 07:280 min—