Os 25501 25501 Most – Litoměřice hor.n.

View line Os 25501

Most 04:17 → Litoměřice hor.n. 05:42 Daily 1 h 25 min · 17 stops AŽD Praha, s.r.o.

It has not run yet today

Last recorded run: Wednesday 11 November No data

Next service: today 04:17 from Most · Thu 12 Nov

Next departure 04:17 today · Most
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
60%
31/52 runs under 3 min
RT coverage: 52 full · 0 partial · 37 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+4min
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

  • Thu 20 Aug Max en route +7 min · last fix heading to — +7 min
  • Tue 22 Sept Max en route +6 min · last fix heading to — +6 min
  • Fri 28 Aug Max en route +5 min · last fix heading to — +5 min
  • Sat 3 Oct Max en route +4 min · last fix heading to — +4 min
  • Sat 26 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 60% · 31
  • 3–10 min 40% · 21
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 86% T n=7
  • 43% W n=7
  • 43% T n=7
  • 43% F n=7
  • 50% S n=8
  • 63% S n=8

Stops and timetable

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

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