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

View line Os 25500

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

It has not run yet today

Last recorded run: Monday 9 November No data

Next service: today 04:09 from Litoměřice hor.n. · Tue 10 Nov

Next departure 04:09 today · Litoměřice hor.n.
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
96%
52/54 runs under 3 min
RT coverage: 54 full · 0 partial · 35 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Most, in minutes. One bar per run.

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

Worst days

  • Wed 19 Aug Max en route +9 min · last fix heading to — +4 min
  • Wed 30 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 19% · 10
  • On time 78% · 42
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 71% W n=7
  • 100% T n=8
  • 100% F n=8
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 55 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:09on time on time
04:11≈ on time ≈ on time
04:14≈ on time ≈ on time
04:17≈ on time ≈ on time
04:20 / 04:22≈ on time ≈ on time
04:26≈ on time ≈ on time
04:28 / 04:29≈ on time ≈ on time
04:33≈ on time ≈ on time
04:35≈ on time ≈ on time
04:39≈ on time ≈ on time
04:40≈ on time ≈ on time
04:46≈ 1 min early ≈ +1 min
04:52≈ 1 min early ≈ +1 min
04:55 / 04:56≈ 1 min early ≈ +1 min
05:02≈ 1 min early ≈ +1 min
05:13≈ 1 min early ≈ +1 min
05:171 min early +1 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
Mon 9 NovMost 05:18No data—
Sun 8 NovMost 05:18No data—
Sat 7 NovMost 05:18No data—
Fri 6 NovMost 05:18No data—
Thu 5 NovMost 05:18No data—
Wed 4 NovMost 05:18No data—
Tue 3 NovMost 05:19No data—
Mon 2 NovMost 05:18No data—
Sun 1 NovMost 05:18No data—
Sat 31 OctMost 05:18No data—
Fri 30 OctMost 05:18No data—
Thu 29 OctMost 05:18No data—
Wed 28 OctMost 05:19No data—
Tue 27 OctMost 05:18No data—
Mon 26 OctMost 05:18No data—
Sun 25 OctMost 05:18No data—
Sat 24 OctMost 05:18No data—
Fri 23 OctMost 05:18No data—
Thu 22 OctMost 05:18No data—
Wed 21 OctMost 05:18No data—
Tue 20 OctMost 05:18No data—
Mon 19 OctMost 05:18No data—
Sun 18 OctMost 05:18No data—
Sat 17 OctMost 05:18No data—
Fri 16 OctMost 05:18No data—
Thu 15 OctMost 05:18No data—
Wed 14 OctMost 05:18No data—
Tue 13 OctMost 05:18No data—
Mon 12 OctMost 05:18No data—
Sun 11 OctMost 05:18No data—