Os 6136 6136 Úštěk – Postoloprty

View line Os 6136

Úštěk 16:22 → Postoloprty 18:15 Mon, Tue, Wed, Thu, Fri 1 h 53 min · 28 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 16:22 from Úštěk · Thu 5 Nov

Next departure 16:22 today · Úštěk
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
100%
40/40 runs under 3 min
RT coverage: 40 full · 0 partial · 21 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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

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

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

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 100% 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 (28 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
16:22on time on time
16:27 / 16:29≈ on time ≈ on time
16:31≈ on time ≈ on time
16:36≈ on time ≈ on time
16:38≈ on time ≈ on time
16:42 / 16:44≈ on time ≈ on time
16:46≈ on time ≈ on time
16:49≈ on time ≈ on time
16:52≈ on time ≈ on time
16:55 / 17:02≈ on time ≈ on time
17:06≈ on time ≈ on time
17:09 / 17:11≈ on time ≈ on time
17:14≈ on time ≈ on time
17:19≈ on time ≈ +1 min
17:22≈ on time ≈ +1 min
17:25 / 17:28≈ on time ≈ +1 min
17:30≈ on time ≈ +1 min
17:33≈ on time ≈ +1 min
17:36≈ on time ≈ +1 min
17:38≈ on time ≈ +1 min
17:42≈ on time ≈ +1 min
17:48≈ on time ≈ +1 min
17:52≈ on time ≈ +1 min
17:56 / 17:59≈ on time ≈ +1 min
18:01≈ on time ≈ +1 min
18:03≈ on time ≈ +1 min
18:09 / 18:11≈ on time ≈ +1 min
18:15on time +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
Wed 4 NovPostoloprty 18:15No data—
Tue 3 NovPostoloprty 18:14No data—
Mon 2 NovPostoloprty 18:14No data—
Fri 30 OctPostoloprty 18:16No data—
Thu 29 OctPostoloprty 18:16No data—
Tue 27 OctPostoloprty 18:17No data—
Mon 26 OctPostoloprty 18:16No data—
Fri 23 OctPostoloprty 18:17No data—
Thu 22 OctPostoloprty 18:16No data—
Wed 21 OctPostoloprty 18:16No data—
Tue 20 OctPostoloprty 18:17No data—
Mon 19 OctPostoloprty 18:16No data—
Fri 16 OctPostoloprty 18:16No data—
Thu 15 OctPostoloprty 18:16No data—
Wed 14 OctPostoloprty 18:17No data—
Tue 13 OctPostoloprty 18:16No data—
Mon 12 OctPostoloprty 18:17No data—
Fri 9 OctPostoloprty 18:16No data—
Thu 8 OctPostoloprty 18:16No data—
Wed 7 OctPostoloprty 18:16No data—
Tue 6 OctPostoloprty 18:16No data—
Mon 5 OctPostoloprty 18:16+1 min+3 min
Fri 2 Oct— 18:290 min+12 min
Thu 1 Oct— 18:300 min+4 min
Wed 30 Sept— 18:29−1 min+3 min
Tue 29 Sept— 18:30+1 min+4 min
Fri 25 Sept— 18:29−1 min+6 min
Thu 24 Sept— 18:290 min+4 min
Wed 23 Sept— 18:31+1 min+2 min
Tue 22 Sept— 18:300 min+8 min