TL 20937 20937 Seifhennersdorf – Varnsdorf
Alerts for train 20937
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line TL 20937.
It has not run yet today
Last recorded run: Wednesday 11 November No data
Next service: today 23:30 from Seifhennersdorf · Thu 12 Nov
Last 30 days
Arrival delay at Varnsdorf, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sat 22 Aug Max en route +19 min · last fix heading to — +14 min
- Wed 23 Sept Max en route +13 min · last fix heading to — +13 min
- Mon 14 Sept Max en route +12 min · last fix heading to — +12 min
- Sat 29 Aug Max en route +14 min · last fix heading to — +12 min
- Fri 28 Aug Max en route +15 min · last fix heading to — +11 min
Distribution · 90 days
49 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 22% · 11
- On time 59% · 29
- 3–10 min 8% · 4
- 10–30 min 10% · 5
- 30+ min 0% · 0
On-time by weekday
- 71% M n=7
- 100% T n=6
- 67% W n=6
- 100% T n=7
- 71% F n=7
- 75% S n=8
- 88% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (4 stops).
Last 90 days, 49 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 |
|---|---|---|---|
| 23:30 | on time | +10 min | |
| 23:36 | ≈ on time | ≈ +9 min | |
| 23:38 | ≈ on time | ≈ +9 min | |
| 23:42 | on time | +9 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 |
|---|---|---|---|
| Wed 11 Nov | Varnsdorf 23:43 | No data | — |
| Tue 10 Nov | Varnsdorf 23:43 | No data | — |
| Mon 9 Nov | Varnsdorf 23:43 | No data | — |
| Sun 8 Nov | Varnsdorf 23:44 | No data | — |
| Sat 7 Nov | Liberec 00:29 | No data | — |
| Fri 6 Nov | Liberec 00:29 | No data | — |
| Thu 5 Nov | Varnsdorf 23:43 | No data | — |
| Wed 4 Nov | Varnsdorf 23:43 | No data | — |
| Tue 3 Nov | Varnsdorf 23:43 | No data | — |
| Mon 2 Nov | Varnsdorf 23:43 | No data | — |
| Sun 1 Nov | Varnsdorf 23:43 | No data | — |
| Sat 31 Oct | Liberec 00:29 | No data | — |
| Fri 30 Oct | Liberec 00:29 | No data | — |
| Thu 29 Oct | Varnsdorf 23:43 | No data | — |
| Wed 28 Oct | Varnsdorf 23:43 | No data | — |
| Tue 27 Oct | Liberec 00:30 | No data | — |
| Mon 26 Oct | Varnsdorf 23:43 | No data | — |
| Sun 25 Oct | Varnsdorf 23:43 | No data | — |
| Sat 24 Oct | Liberec 00:29 | No data | — |
| Fri 23 Oct | Liberec 00:29 | No data | — |
| Thu 22 Oct | Varnsdorf 23:43 | No data | — |
| Wed 21 Oct | Varnsdorf 23:43 | No data | — |
| Tue 20 Oct | Varnsdorf 23:43 | No data | — |
| Mon 19 Oct | Varnsdorf 23:44 | No data | — |
| Sun 18 Oct | Varnsdorf 23:43 | No data | — |
| Sat 17 Oct | Liberec 00:29 | No data | — |
| Fri 16 Oct | Liberec 00:29 | No data | — |
| Thu 15 Oct | Varnsdorf 23:43 | No data | — |
| Wed 14 Oct | Varnsdorf 23:43 | No data | — |
| Tue 13 Oct | Varnsdorf 23:43 | No data | — |