Os 6102 6102 Úštěk – Postoloprty

View line Os 6102

Úštěk 05:20 → Postoloprty 07:15 Sat, Sun 1 h 55 min · 28 stops České dráhy, a.s.

✓ Today’s run finished

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

  1. Úštěk05:20
  2. Litoměřice hor.n.05:42
  3. Lovosice05:55
  4. Slatina pod Hazmburkem06:22
  5. Křesín06:36
  6. Louny06:56
  7. Postoloprty07:15

Next service: Saturday 05:20 from Úštěk · Sat 14 Nov

Next departure 05:20 Saturday · Úštěk
On-time · 30 days
—
Too little data (0/11 runs with data)
RT coverage: 0 full · 0 partial · 11 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 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

Worst days

  • Sun 30 Aug Max en route +34 min · last fix heading to — +21 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 0% · 0
  • 10–30 min 6% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
05:20on time +2 min
05:25 / 05:27≈ on time ≈ +2 min
05:29≈ on time ≈ +2 min
05:34≈ on time ≈ +2 min
05:38≈ on time ≈ +2 min
05:42 / 05:44≈ on time ≈ +1 min
05:46≈ on time ≈ +1 min
05:49≈ on time ≈ +1 min
05:52≈ on time ≈ +1 min
05:55 / 06:02≈ on time ≈ +1 min
06:06≈ on time ≈ +1 min
06:09 / 06:11≈ on time ≈ +1 min
06:14≈ on time ≈ +1 min
06:19≈ on time ≈ +1 min
06:22≈ on time ≈ +1 min
06:25 / 06:28≈ on time ≈ +1 min
06:30≈ on time ≈ +1 min
06:33≈ on time ≈ +1 min
06:36≈ on time ≈ +1 min
06:38≈ on time ≈ +1 min
06:42≈ on time ≈ +1 min
06:48≈ on time ≈ +1 min
06:52≈ on time ≈ +1 min
06:56 / 06:59≈ on time ≈ +1 min
07:01≈ on time ≈ +1 min
07:03≈ on time ≈ +1 min
07:09 / 07:11≈ on time ≈ +1 min
07: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
Sun 8 NovPostoloprty 07:14No data—
Sat 7 NovPostoloprty 07:14No data—
Sun 1 NovPostoloprty 07:16No data—
Sat 31 OctPostoloprty 07:16No data—
Wed 28 OctPostoloprty 07:16No data—
Sun 25 OctPostoloprty 07:16No data—
Sat 24 OctPostoloprty 07:16No data—
Sun 18 OctPostoloprty 07:17No data—
Sat 17 OctPostoloprty 07:16No data—
Sun 11 OctPostoloprty 07:16No data—
Sat 10 OctPostoloprty 07:16No data—
Sun 4 Oct— 07:29−1 min+3 min
Sat 3 Oct— 07:290 min+4 min
Mon 28 Sept— 07:28−1 min+3 min
Sun 27 Sept— 07:300 min+4 min
Sat 26 Sept— 07:300 min+4 min
Sun 20 Sept— 08:120 min+4 min
Sat 19 Sept— 07:31+1 min+3 min
Sun 13 Sept— 07:290 min—
Sat 12 Sept— 07:29−1 min+1 min
Sun 6 Sept— 07:30+1 min+3 min
Sat 5 Sept— 07:28−1 min+5 min
Sun 30 Aug— 07:50+21 min+34 min
Sat 29 Aug— 07:300 min+7 min
Sun 23 Aug— 07:290 min+2 min
Sat 22 Aug— 07:290 min+3 min
Sun 16 Aug— 07:28−1 min+2 min
Sat 15 Aug— 07:28−1 min+3 min