S78 44960 Chałupki – Racibórz
Alerts for train 44960
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S78.
✓ Today’s run finished
Today, last fix heading to Racibórz at 13:18 No data
- Chałupki12:54
- Rudyszwałd12:57
- Roszków Raciborski13:00
- Krzyżanowice13:03
- Tworków13:08
- Racibórz13:16
Next service: tomorrow 12:54 from Chałupki · Wed 11 Nov
Last 30 days
Arrival delay at Racibórz, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 9 Nov Max en route +27 min · last fix heading to Racibórz +27 min
- Sun 1 Nov Max en route +7 min · last fix heading to Racibórz +7 min
- Mon 31 Aug Max en route +3 min · last fix heading to Racibórz +3 min
Distribution · 90 days
29 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 90% · 26
- 3–10 min 7% · 2
- 10–30 min 3% · 1
- 30+ min 0% · 0
On-time by weekday
- 60% M n=5
- 100% T n=4
- 100% W n=5
- 100% T n=4
- 100% F n=2
- 100% S n=4
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 29 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 |
|---|---|---|---|
| 12:54 | on time | +2 min | |
| 12:57 | ≈ on time | ≈ +2 min | |
| 13:00 | ≈ on time | ≈ +2 min | |
| 13:03 / 13:05 | ≈ on time | ≈ +2 min | |
| 13:08 | ≈ on time | ≈ +2 min | |
| 13:16 | 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 |
|---|---|---|---|
| Tue 10 Nov | Racibórz 13:18 | No data | — |
| Mon 9 Nov | Racibórz 13:44 | +27 min | +27 min |
| Sun 8 Nov | Racibórz 13:14 | −1 min | — |
| Sat 7 Nov | Racibórz 13:17 | 0 min | — |
| Fri 6 Nov | Racibórz 13:18 | +1 min | +1 min |
| Thu 5 Nov | Racibórz 13:17 | 0 min | — |
| Wed 4 Nov | Racibórz 13:17 | 0 min | — |
| Tue 3 Nov | Racibórz 13:15 | −1 min | — |
| Mon 2 Nov | Racibórz 13:17 | No data | — |
| Sun 1 Nov | Racibórz 13:24 | +7 min | +7 min |
| Sat 31 Oct | Racibórz 13:18 | 0 min | — |
| Fri 30 Oct | Racibórz 13:17 | No data | — |
| Thu 29 Oct | Racibórz 13:17 | 0 min | — |
| Wed 28 Oct | Racibórz 13:17 | 0 min | — |
| Tue 27 Oct | Racibórz 13:17 | No data | — |
| Mon 26 Oct | Racibórz 13:18 | 0 min | — |
| Sun 25 Oct | Racibórz 13:17 | No data | — |
| Sat 24 Oct | Racibórz 13:18 | No data | — |
| Fri 23 Oct | Racibórz 13:18 | No data | — |
| Thu 22 Oct | Racibórz 13:18 | No data | — |
| Wed 21 Oct | Racibórz 13:18 | No data | — |
| Tue 20 Oct | Racibórz 13:19 | No data | — |
| Mon 19 Oct | Racibórz 13:18 | No data | — |
| Sun 18 Oct | Racibórz 13:18 | −1 min | — |
| Sat 17 Oct | Racibórz 13:19 | 0 min | — |
| Fri 16 Oct | Racibórz 13:18 | No data | — |
| Thu 15 Oct | Racibórz 13:18 | No data | — |
| Wed 14 Oct | Racibórz 13:19 | No data | — |
| Tue 13 Oct | Racibórz 13:18 | 0 min | — |
| Mon 12 Oct | Racibórz 13:18 | 0 min | — |