Os 25541 25541 Třebívlice → Litoměřice hor.n.

View line Os 25541

Třebívlice 18:00 → Litoměřice hor.n. 18:42 Daily 0 h 42 min · 12 stops AŽD Praha, s.r.o.

It has not run yet today

Last recorded run: Friday 20 November No data

Next service: today 18:00 from Třebívlice · Sat 21 Nov

Next departure 18:00 today · Třebívlice
On-time · 30 days
—
Too little data (0/24 runs with data)
RT coverage: 0 full · 0 partial · 24 no data
On-time · 90 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 38 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 Litoměřice hor.n., in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 22 Sept Max en route +6 min · last fix heading to — +6 min
  • Wed 30 Sept Max en route +5 min · last fix heading to — +5 min
  • Tue 15 Sept Max en route +4 min · last fix heading to — +4 min
  • Tue 8 Sept Max en route +3 min · last fix heading to — +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 86% · 25
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 50% T n=6
  • 83% W n=6
  • 100% T n=6
  • 100% F n=6
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 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.

StopSched.Usually 9 days in 10
18:00on time on time
18:04≈ on time ≈ +1 min
18:06≈ on time ≈ +1 min
18:09≈ on time ≈ +1 min
18:11 / 18:12≈ on time ≈ +1 min
18:16≈ on time ≈ +2 min
18:20≈ on time ≈ +2 min
18:25 / 18:32≈ on time ≈ +2 min
18:34≈ on time ≈ +3 min
18:36 / 18:37≈ on time ≈ +3 min
18:39≈ on time ≈ +3 min
18:42on 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
Fri 20 NovLitoměřice hor.n. 18:43No data—
Thu 19 NovLitoměřice hor.n. 18:43No data—
Wed 18 NovLitoměřice hor.n. 18:43No data—
Tue 17 NovLitoměřice hor.n. 18:43No data—
Mon 16 NovLitoměřice hor.n. 18:43No data—
Sun 15 NovLitoměřice hor.n. 18:43No data—
Sat 14 NovLitoměřice hor.n. 18:43No data—
Fri 13 NovLitoměřice hor.n. 18:43No data—
Thu 12 NovLitoměřice hor.n. 18:43No data—
Wed 11 NovLitoměřice hor.n. 18:43No data—
Tue 10 NovLitoměřice hor.n. 18:43No data—
Mon 9 NovLitoměřice hor.n. 18:43No data—
Sun 8 NovLitoměřice hor.n. 18:43No data—
Sat 7 NovLitoměřice hor.n. 18:43No data—
Fri 6 NovLitoměřice hor.n. 18:43No data—
Thu 5 NovLitoměřice hor.n. 18:43No data—
Wed 4 NovLitoměřice hor.n. 18:43No data—
Tue 3 NovLitoměřice hor.n. 18:43No data—
Mon 2 NovLitoměřice hor.n. 18:43No data—
Fri 30 OctLitoměřice hor.n. 18:43No data—
Thu 29 OctLitoměřice hor.n. 18:43No data—
Tue 27 OctLitoměřice hor.n. 18:44No data—
Mon 26 OctLitoměřice hor.n. 18:43No data—
Fri 23 OctLitoměřice hor.n. 18:44No data—
Thu 22 OctLitoměřice hor.n. 18:43No data—
Wed 21 OctLitoměřice hor.n. 18:43No data—
Tue 20 OctLitoměřice hor.n. 18:44No data—
Mon 19 OctLitoměřice hor.n. 18:43No data—
Fri 16 OctLitoměřice hor.n. 18:43No data—
Thu 15 OctLitoměřice hor.n. 18:43No data—