Os 25532 25532 Litoměřice hor.n. – Třebívlice

View line Os 25532

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

✓ Today’s run finished

Today, last fix heading to Třebívlice at 09:57 No data

  1. Litoměřice hor.n.09:14
  2. Žalhostice09:19
  3. Lovosice09:25
  4. Čížkovice09:38
  5. Třebenice09:43
  6. Dlažkovice09:49
  7. Třebívlice09:56

Next service: tomorrow 09:14 from Litoměřice hor.n. · Fri 6 Nov

Next departure 09:14 tomorrow · Litoměřice hor.n.
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
83%
33/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
−1min
Median at arrival, 90 days
P90
+5min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Třebívlice, 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 30 Sept Max en route +12 min · last fix heading to — +11 min
  • Tue 22 Sept Max en route +9 min · last fix heading to — +8 min
  • Wed 12 Aug 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
  • Thu 13 Aug Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 30% · 12
  • On time 53% · 21
  • 3–10 min 15% · 6
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 75% T n=8
  • 75% W n=8
  • 88% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
09:14on time +3 min
09:16≈ on time ≈ +3 min
09:19≈ on time ≈ +2 min
09:22≈ on time ≈ +2 min
09:25 / 09:32≈ on time ≈ +2 min
09:36≈ 1 min early ≈ +3 min
09:38 / 09:39≈ 1 min early ≈ +3 min
09:43≈ 1 min early ≈ +3 min
09:45≈ 1 min early ≈ +4 min
09:49≈ 1 min early ≈ +4 min
09:50≈ 1 min early ≈ +4 min
09:561 min early +5 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 5 NovTřebívlice 09:57No data—
Wed 4 NovTřebívlice 09:57No data—
Tue 3 NovTřebívlice 09:57No data—
Mon 2 NovTřebívlice 09:57No data—
Fri 30 OctTřebívlice 09:57No data—
Thu 29 OctTřebívlice 09:57No data—
Tue 27 OctTřebívlice 09:57No data—
Mon 26 OctTřebívlice 09:57No data—
Fri 23 OctTřebívlice 09:58No data—
Thu 22 OctTřebívlice 09:58No data—
Wed 21 OctTřebívlice 09:57No data—
Tue 20 OctTřebívlice 09:57No data—
Mon 19 OctTřebívlice 09:57No data—
Fri 16 OctTřebívlice 09:57No data—
Thu 15 OctTřebívlice 09:57No data—
Wed 14 OctTřebívlice 09:57No data—
Tue 13 OctTřebívlice 09:57No data—
Mon 12 OctTřebívlice 09:57No data—
Fri 9 OctTřebívlice 09:57No data—
Thu 8 OctTřebívlice 09:57No data—
Wed 7 OctTřebívlice 09:57No data—
Tue 6 OctTřebívlice 09:57No data—
Mon 5 Oct— 10:13+3 min+6 min
Fri 2 Oct— 10:10−1 min—
Thu 1 Oct— 10:08−3 min—
Wed 30 Sept— 10:21+11 min+12 min
Tue 29 Sept— 10:08−3 min+4 min
Fri 25 Sept— 10:08−2 min—
Thu 24 Sept— 10:10−1 min—
Wed 23 Sept— 10:09−2 min+1 min