S18 40727 Bytom – Gliwice

View line S18

Bytom 21:10 → Gliwice 21:28 Daily 0 h 18 min · 4 stops PKP

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 21:10 from Bytom · Thu 5 Nov

Next departure 21:10 today · Bytom
On-time · 30 days
95%
20/21 runs under 3 min
RT coverage: 21 full · 0 partial · 8 no data
On-time · 90 days
91%
30/33 runs under 3 min
RT coverage: 33 full · 0 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Thu 10 Sept Max en route +15 min · last fix heading to Zabrze Północne +15 min
  • Sun 1 Nov Max en route +8 min · last fix heading to Gliwice +8 min
  • Wed 9 Sept Max en route +9 min · last fix heading to Zabrze Maciejów +6 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 88% · 29
  • 3–10 min 6% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=5
  • 75% W n=4
  • 83% T n=6
  • 100% F n=4
  • 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, 33 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
21:10on time +2 min
21:18≈ on time ≈ +2 min
21:21 / 21:22≈ on time ≈ +2 min
21:28on time +2 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 4 NovGliwice 21:290 min—
Tue 3 NovGliwice 21:290 min—
Mon 2 NovGliwice 21:29+1 min+1 min
Sun 1 NovGliwice 21:34+8 min+8 min
Sat 31 OctGliwice 21:31+1 min+1 min
Fri 30 OctGliwice 21:290 min—
Thu 29 OctGliwice 21:27−2 min—
Wed 28 OctGliwice 21:28−1 min—
Tue 27 OctGliwice 21:290 min—
Mon 26 OctGliwice 21:300 min—
Sun 25 OctGliwice 21:30No data—
Sat 24 OctGliwice 21:32No data—
Fri 23 OctGliwice 21:32No data—
Thu 22 OctGliwice 21:31No data—
Wed 21 OctGliwice 21:31No data—
Tue 20 OctGliwice 21:31No data—
Mon 19 OctGliwice 21:31No data—
Sun 18 OctGliwice 21:310 min—
Sat 17 OctGliwice 21:310 min—
Fri 16 OctGliwice 21:310 min—
Thu 15 OctGliwice 21:33+1 min+1 min
Wed 14 OctGliwice 21:310 min—
Tue 13 OctGliwice 21:310 min—
Mon 12 OctGliwice 21:310 min—
Sun 11 OctGliwice 21:310 min—
Sat 10 OctGliwice 21:310 min—
Fri 9 OctGliwice 21:310 min—
Thu 8 OctGliwice 21:320 min—
Wed 7 OctGliwice 21:31No data—
Tue 6 OctGliwice 21:310 min—