S18 40774 Gliwice – Bytom
Alerts for train 40774
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S18.
✓ Today’s run finished
Today it reached Bytom at 17:57 0 min
- Gliwice17:39
- Zabrze Maciejów17:45
- Zabrze Północne17:48
- Bytom17:57
Next service: tomorrow 17:39 from Gliwice · Sun 15 Nov
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 +9 min · last fix heading to Bytom +9 min
- Mon 26 Oct Max en route +4 min · last fix heading to Bytom +4 min
- Tue 29 Sept Max en route +4 min · last fix heading to Bytom +4 min
- Fri 30 Oct Max en route +3 min · last fix heading to Bytom +3 min
- Mon 31 Aug Max en route +3 min · last fix heading to Bytom +3 min
Distribution · 90 days
46 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 13% · 6
- On time 76% · 35
- 3–10 min 11% · 5
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 71% M n=7
- 88% T n=8
- 100% W n=6
- 100% T n=6
- 83% F n=6
- 100% S n=6
- 86% S n=7
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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 17:39 | on time | on time | |
| 17:45 | ≈ on time | ≈ +1 min | |
| 17:48 / 17:49 | ≈ on time | ≈ +1 min | |
| 17:57 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 14 Nov | Bytom 17:58 | 0 min | — |
| Fri 13 Nov | Bytom 17:59 | 0 min | — |
| Thu 12 Nov | Bytom 17:58 | 0 min | — |
| Wed 11 Nov | Bytom 17:58 | 0 min | — |
| Tue 10 Nov | Bytom 17:58 | 0 min | — |
| Mon 9 Nov | Bytom 17:58 | 0 min | — |
| Sun 8 Nov | Bytom 17:58 | 0 min | — |
| Sat 7 Nov | Bytom 17:57 | −1 min | — |
| Fri 6 Nov | Bytom 17:58 | No data | — |
| Thu 5 Nov | Bytom 17:58 | No data | — |
| Wed 4 Nov | Bytom 17:58 | 0 min | — |
| Tue 3 Nov | Bytom 17:58 | −1 min | — |
| Mon 2 Nov | Bytom 17:58 | 0 min | — |
| Sun 1 Nov | Bytom 18:07 | +9 min | +9 min |
| Sat 31 Oct | Bytom 17:59 | 0 min | — |
| Fri 30 Oct | Bytom 18:01 | +3 min | +3 min |
| Thu 29 Oct | Bytom 17:58 | 0 min | — |
| Wed 28 Oct | Bytom 17:58 | 0 min | — |
| Tue 27 Oct | Bytom 17:58 | 0 min | — |
| Mon 26 Oct | Bytom 18:03 | +4 min | +4 min |
| Sun 25 Oct | Bytom 17:58 | No data | — |
| Sat 24 Oct | Bytom 17:59 | No data | — |
| Fri 23 Oct | Bytom 18:00 | No data | — |
| Thu 22 Oct | Bytom 18:00 | No data | — |
| Wed 21 Oct | Bytom 17:59 | No data | — |
| Tue 20 Oct | Bytom 17:59 | No data | — |
| Mon 19 Oct | Bytom 17:59 | No data | — |
| Sun 18 Oct | Bytom 18:00 | 0 min | — |
| Sat 17 Oct | Bytom 17:59 | 0 min | — |
| Fri 16 Oct | Bytom 17:59 | 0 min | — |