Sp 5283 5283 Schirnding – Cheb
Alerts for train 5283
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Sp 5283.
✓ Today’s run finished
Today, last fix heading to Cheb at 10:22 No data
- Schirnding10:12
- Pomezí nad Ohří z10:15
- Cheb-Skalka10:18
- Cheb10:21
Next service: tomorrow 10:12 from Schirnding · Fri 6 Nov
Last 30 days
Arrival delay at Cheb, 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 10 Aug Max en route +11 min · last fix heading to — +11 min
- Wed 9 Sept Max en route +9 min · last fix heading to — +9 min
- Thu 1 Oct Max en route +8 min · last fix heading to — +8 min
- Wed 23 Sept Max en route +8 min · last fix heading to — +8 min
- Mon 5 Oct Max en route +7 min · last fix heading to — +7 min
Distribution · 90 days
59 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 36% · 21
- 3–10 min 63% · 37
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 33% M n=9
- 38% T n=8
- 13% W n=8
- 50% T n=8
- 13% F n=8
- 67% S n=9
- 33% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 59 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 |
|---|---|---|---|
| 10:12 | +4 min | +7 min | |
| 10:15 | ≈ +4 min | ≈ +7 min | |
| 10:18 | ≈ +4 min | ≈ +7 min | |
| 10:21 | +4 min | +7 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 11 July 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 |
|---|---|---|---|
| Thu 5 Nov | Cheb 10:22 | No data | — |
| Wed 4 Nov | Cheb 10:22 | No data | — |
| Tue 3 Nov | Cheb 10:22 | No data | — |
| Mon 2 Nov | Cheb 10:22 | No data | — |
| Sun 1 Nov | Cheb 10:22 | No data | — |
| Sat 31 Oct | Cheb 10:22 | No data | — |
| Fri 30 Oct | Cheb 10:22 | No data | — |
| Thu 29 Oct | Cheb 10:22 | No data | — |
| Wed 28 Oct | Cheb 10:22 | No data | — |
| Tue 27 Oct | Cheb 10:22 | No data | — |
| Mon 26 Oct | Cheb 10:22 | No data | — |
| Sun 25 Oct | Cheb 10:22 | No data | — |
| Sat 24 Oct | Cheb 10:22 | No data | — |
| Fri 23 Oct | Cheb 10:23 | No data | — |
| Thu 22 Oct | Cheb 10:23 | No data | — |
| Wed 21 Oct | Cheb 10:22 | No data | — |
| Tue 20 Oct | Cheb 10:22 | No data | — |
| Mon 19 Oct | Cheb 10:22 | No data | — |
| Sun 18 Oct | Cheb 10:22 | No data | — |
| Sat 17 Oct | Cheb 10:22 | No data | — |
| Fri 16 Oct | Cheb 10:22 | No data | — |
| Thu 15 Oct | Cheb 10:22 | No data | — |
| Wed 14 Oct | Cheb 10:22 | No data | — |
| Tue 13 Oct | Cheb 10:22 | No data | — |
| Mon 12 Oct | Cheb 10:22 | No data | — |
| Sun 11 Oct | Cheb 10:22 | No data | — |
| Sat 10 Oct | Cheb 10:22 | No data | — |
| Fri 9 Oct | Cheb 10:22 | No data | — |
| Thu 8 Oct | Cheb 10:22 | No data | — |
| Wed 7 Oct | Cheb 10:22 | No data | — |