Os 25530 25530 Litoměřice hor.n. → Lovosice

View line Os 25530

Litoměřice hor.n. 07:14 → Lovosice 07:25 Daily 0 h 11 min · 5 stops AŽD Praha, s.r.o.

Os 25530 Litoměřice hor.n.–Lovosice: final delay under 3 min on 24 of its 29 runs with data in the last 90 days (83%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 07:32 (GMT+1).

✓ Today’s run finished

Today, last fix heading to Lovosice at 07:24 No data

  1. Litoměřice hor.n.07:14
  2. Litoměřice Cihelna07:16
  3. Žalhostice07:19
  4. Lovosice závod07:22
  5. Lovosice07:25

Next service: tomorrow 07:14 from Litoměřice hor.n. · Mon 23 Nov

Next departure 07:14 tomorrow · Litoměřice hor.n.
On-time · 30 days
—
Too little data (0/25 runs with data)
RT coverage: 0 full · 0 partial · 25 no data
On-time · 90 days
83%
24/29 runs under 3 min
RT coverage: 29 full · 0 partial · 39 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 Lovosice, 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 2 Sept Max en route +10 min · last fix heading to — +7 min
  • Tue 15 Sept Max en route +7 min · last fix heading to — +5 min
  • Tue 22 Sept Max en route +6 min · last fix heading to — +4 min
  • Mon 14 Sept Max en route +3 min · last fix heading to — +3 min
  • Fri 4 Sept Max en route +5 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 21% · 6
  • On time 62% · 18
  • 3–10 min 17% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
07:14+1 min +3 min
07:16≈ +1 min ≈ +3 min
07:19≈ on time ≈ +3 min
07:22≈ on time ≈ +3 min
07:25on 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
Sun 22 NovLovosice 07:24No data—
Sat 21 NovLovosice 07:25No data—
Fri 20 NovTřebívlice 07:57No data—
Thu 19 NovTřebívlice 07:57No data—
Wed 18 NovTřebívlice 07:57No data—
Tue 17 NovLovosice 07:24No data—
Mon 16 NovTřebívlice 07:57No data—
Sun 15 NovLovosice 07:24No data—
Sat 14 NovLovosice 07:24No data—
Fri 13 NovTřebívlice 07:57No data—
Thu 12 NovTřebívlice 07:57No data—
Wed 11 NovTřebívlice 07:57No data—
Tue 10 NovTřebívlice 07:57No data—
Mon 9 NovTřebívlice 07:57No data—
Sun 8 NovLovosice 07:24No data—
Sat 7 NovLovosice 07:24No data—
Fri 6 NovTřebívlice 07:57No data—
Thu 5 NovTřebívlice 07:57No data—
Wed 4 NovTřebívlice 07:57No data—
Tue 3 NovTřebívlice 07:57No data—
Mon 2 NovTřebívlice 07:57No data—
Fri 30 OctTřebívlice 07:57No data—
Thu 29 OctTřebívlice 07:57No data—
Tue 27 OctTřebívlice 07:57No data—
Mon 26 OctTřebívlice 07:57No data—
Fri 23 OctTřebívlice 07:57No data—
Thu 22 OctTřebívlice 07:57No data—
Wed 21 OctTřebívlice 07:57No data—
Tue 20 OctTřebívlice 07:57No data—
Mon 19 OctTřebívlice 07:57No data—