Os 6180 6180 Libochovice – Postoloprty

View line Os 6180

Libochovice 04:28 → Postoloprty 05:13 Daily 0 h 45 min · 13 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Postoloprty at 05:14 No data

  1. Libochovice04:28
  2. Dubany04:33
  3. Koštice nad Ohří04:38
  4. Slavětín nad Ohří04:48
  5. Louny04:57
  6. Louny město05:02
  7. Postoloprty05:13

Next service: tomorrow 04:28 from Libochovice · Sat 7 Nov

Next departure 04:28 tomorrow · Libochovice
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
100%
58/58 runs under 3 min
RT coverage: 58 full · 0 partial · 32 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 58
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=8
  • 100% W n=8
  • 100% T n=8
  • 100% F n=8
  • 100% S n=8
  • 100% S n=9

Stops and timetable

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

Last 90 days, 58 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:28on time +2 min
04:30≈ on time ≈ +2 min
04:33≈ on time ≈ +2 min
04:36≈ on time ≈ +2 min
04:38≈ on time ≈ +2 min
04:42≈ on time ≈ +2 min
04:48≈ on time ≈ +2 min
04:52≈ +1 min ≈ +2 min
04:57 / 04:58≈ +1 min ≈ +2 min
05:00≈ +1 min ≈ +2 min
05:02≈ +1 min ≈ +2 min
05:08 / 05:09≈ +1 min ≈ +2 min
05:13+1 min +2 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
Fri 6 NovPostoloprty 05:14No data—
Thu 5 NovPostoloprty 05:14No data—
Wed 4 NovPostoloprty 05:14No data—
Tue 3 NovPostoloprty 05:15No data—
Mon 2 NovPostoloprty 05:14No data—
Sun 1 NovPostoloprty 05:14No data—
Sat 31 OctPostoloprty 05:14No data—
Fri 30 OctPostoloprty 05:14No data—
Thu 29 OctPostoloprty 05:14No data—
Wed 28 OctPostoloprty 05:15No data—
Tue 27 OctPostoloprty 05:14No data—
Mon 26 OctPostoloprty 05:14No data—
Sun 25 OctPostoloprty 05:14No data—
Sat 24 OctPostoloprty 05:14No data—
Fri 23 OctPostoloprty 05:14No data—
Thu 22 OctPostoloprty 05:14No data—
Wed 21 OctPostoloprty 05:14No data—
Tue 20 OctPostoloprty 05:14No data—
Mon 19 OctPostoloprty 05:14No data—
Sun 18 OctPostoloprty 05:14No data—
Sat 17 OctPostoloprty 05:14No data—
Fri 16 OctPostoloprty 05:14No data—
Thu 15 OctPostoloprty 05:14No data—
Wed 14 OctPostoloprty 05:14No data—
Tue 13 OctPostoloprty 05:14No data—
Mon 12 OctPostoloprty 05:14No data—
Sun 11 OctPostoloprty 05:14No data—
Sat 10 OctPostoloprty 05:14No data—
Fri 9 OctPostoloprty 05:14No data—
Thu 8 OctPostoloprty 05:14No data—