TL 20913 20913 Seifhennersdorf → Liberec

View line TL 20913

Seifhennersdorf 09:30 → Liberec 10:28 Daily 0 h 58 min · 16 stops Die Länderbahn GmbH DLB

TL 20913 Seifhennersdorf–Liberec: final delay under 3 min on 37 of its 42 runs with data in the last 90 days (88%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 07:58 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November No data

Next service: today 09:30 from Seifhennersdorf · Sun 22 Nov

Next departure 09:30 today · Seifhennersdorf
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
88%
37/42 runs under 3 min
RT coverage: 42 full · 0 partial · 47 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Liberec, 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 27 Aug Max en route +22 min · last fix heading to — +21 min
  • Fri 11 Sept Max en route +11 min · last fix heading to — +7 min
  • Sat 19 Sept Max en route +6 min · last fix heading to — +5 min
  • Thu 24 Sept Max en route +3 min · last fix heading to — +3 min
  • Mon 31 Aug Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 21% · 9
  • On time 67% · 28
  • 3–10 min 10% · 4
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=6
  • 100% W n=6
  • 67% T n=6
  • 83% F n=6
  • 83% S n=6
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (16 stops).

Last 90 days, 42 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
09:30on time +2 min
09:36≈ on time ≈ +2 min
09:38≈ on time ≈ +2 min
09:42≈ on time ≈ +2 min
09:46≈ on time ≈ +2 min
09:50≈ on time ≈ +2 min
09:53≈ on time ≈ +3 min
09:59≈ on time ≈ +2 min
10:06≈ on time ≈ +2 min
10:08≈ on time ≈ +2 min
10:12≈ on time ≈ +2 min
10:16 / 10:17≈ on time ≈ +2 min
10:19≈ on time ≈ +2 min
10:21≈ on time ≈ +3 min
10:22≈ on time ≈ +3 min
10:28on time +3 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

DateLast stopFinalMax
Sat 21 NovLiberec 10:29No data—
Fri 20 NovLiberec 10:29No data—
Thu 19 NovLiberec 10:29No data—
Wed 18 NovLiberec 10:29No data—
Tue 17 NovLiberec 10:29No data—
Mon 16 NovLiberec 10:29No data—
Sun 15 NovLiberec 10:29No data—
Sat 14 NovLiberec 10:29No data—
Fri 13 NovLiberec 10:29No data—
Thu 12 NovLiberec 10:29No data—
Wed 11 NovLiberec 10:29No data—
Tue 10 NovLiberec 10:29No data—
Mon 9 NovLiberec 10:29No data—
Sun 8 NovLiberec 10:29No data—
Sat 7 NovLiberec 10:29No data—
Fri 6 NovLiberec 10:29No data—
Thu 5 NovLiberec 10:29No data—
Wed 4 NovLiberec 10:29No data—
Tue 3 NovLiberec 10:29No data—
Mon 2 NovLiberec 10:29No data—
Sun 1 NovLiberec 10:29No data—
Sat 31 OctLiberec 10:29No data—
Fri 30 OctLiberec 10:29No data—
Thu 29 OctLiberec 10:29No data—
Wed 28 OctLiberec 10:29No data—
Tue 27 OctLiberec 10:29No data—
Mon 26 OctLiberec 10:29No data—
Sun 25 OctLiberec 10:29No data—
Sat 24 OctLiberec 10:29No data—
Fri 23 OctLiberec 10:29No data—