S18 40737 Bytom – Gliwice

View line S18

Bytom 12:08 → Gliwice 12:26 Daily 0 h 18 min · 4 stops Koleje Śląskie

It has not run yet today

Last recorded run: Wednesday 18 November −1 min

Next service: today 12:08 from Bytom · Thu 19 Nov

Next departure 12:08 today · Bytom
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
88%
45/51 runs under 3 min
RT coverage: 51 full · 0 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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
  • Sat 7 Nov Max en route +5 min · last fix heading to Gliwice +5 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Gliwice +5 min
  • Wed 30 Sept Max en route +4 min · last fix heading to Gliwice +4 min
  • Mon 26 Oct Max en route +3 min · last fix heading to Gliwice +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 86% · 44
  • 3–10 min 12% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 86% W n=7
  • 100% T n=8
  • 89% F n=9
  • 75% S n=8
  • 86% S n=7

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