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

View line Os 25516

Litoměřice hor.n. 18:14 → Most 19:27 Daily 1 h 13 min · 17 stops AŽD Praha, s.r.o.

Running now · updated 19:21

Position estimated from the timetable

Between Bělušice and Obrnice No data

Estimated arrival at Most 19:27 · 57 km/h

  1. Litoměřice hor.n.18:14
  2. Lovosice závod18:22
  3. Sulejovice18:36
  4. Třebenice město18:45
  5. Bělušice19:12
  6. Obrnice19:23
  7. Most19:27
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
92%
47/51 runs under 3 min
RT coverage: 51 full · 0 partial · 39 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

  • Sat 5 Sept Max en route +7 min · last fix heading to — +5 min
  • Sat 29 Aug Max en route +5 min · last fix heading to — +5 min
  • Fri 21 Aug Max en route +10 min · last fix heading to — +4 min
  • Sat 22 Aug Max en route +6 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 35% · 18
  • On time 57% · 29
  • 3–10 min 8% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 86% F n=7
  • 63% 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, 51 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 10Today
18:14+2 min +5 minPassed
18:16≈ +2 min ≈ +5 minPassed
18:19≈ +2 min ≈ +5 minPassed
18:22≈ +2 min ≈ +4 minPassed
18:25 / 18:32≈ +2 min ≈ +4 minPassed
18:36≈ +2 min ≈ +4 minPassed
18:38 / 18:39≈ +1 min ≈ +3 minPassed
18:43≈ +1 min ≈ +3 minPassed
18:45≈ +1 min ≈ +3 minPassed
18:49≈ +1 min ≈ +2 minPassed
18:50≈ +1 min ≈ +2 minPassed
18:56 / 18:57≈ +1 min ≈ +2 minPassed
19:03≈ on time ≈ +2 minPassed
19:06≈ on time ≈ +2 minPassed
19:12≈ on time ≈ +1 minPassed
19:23≈ 1 min early ≈ +1 minNext
19:271 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
Thu 12 NovObrnice 19:19Partial coverageNo data—
Wed 11 NovMost 19:28No data—
Tue 10 NovMost 19:28No data—
Mon 9 NovMost 19:28No data—
Sun 8 NovMost 19:28No data—
Sat 7 NovMost 19:28No data—
Fri 6 NovMost 19:28No data—
Thu 5 NovMost 19:28No data—
Wed 4 NovMost 19:28No data—
Tue 3 NovMost 19:28No data—
Mon 2 NovMost 19:28No data—
Sun 1 NovMost 19:28No data—
Sat 31 OctMost 19:28No data—
Fri 30 OctMost 19:28No data—
Thu 29 OctMost 19:28No data—
Wed 28 OctMost 19:28No data—
Tue 27 OctMost 19:29No data—
Mon 26 OctMost 19:28No data—
Sun 25 OctMost 19:28No data—
Sat 24 OctMost 19:28No data—
Fri 23 OctMost 19:28No data—
Thu 22 OctMost 19:28No data—
Wed 21 OctMost 19:28No data—
Tue 20 OctMost 19:28No data—
Mon 19 OctMost 19:28No data—
Sun 18 OctMost 19:28No data—
Sat 17 OctMost 19:28No data—
Fri 16 OctMost 19:28No data—
Thu 15 OctMost 19:28No data—
Wed 14 OctMost 19:28No data—