S18 40778 Gliwice – Bytom

View line S18

Gliwice 19:41 → Bytom 19:59 Daily 0 h 18 min · 4 stops Koleje Śląskie

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 19:41 from Gliwice · Sun 15 Nov

Next departure 19:41 today · Gliwice
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 10 no data
On-time · 90 days
95%
40/42 runs under 3 min
RT coverage: 42 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: +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 +8 min · last fix heading to Bytom +8 min
  • Wed 11 Nov Max en route +5 min · last fix heading to Bytom +5 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 90% · 38
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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