Os 26705 26705 Postoloprty – Louny

View line Os 26705

Postoloprty 11:41 → Louny 11:57 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 5 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Louny at 11:58 No data

  1. Postoloprty11:41
  2. Březno u Postoloprt11:45
  3. Louny město11:52
  4. Louny střed11:54
  5. Louny11:57

Next service: tomorrow 11:41 from Postoloprty · Fri 6 Nov

Next departure 11:41 tomorrow · Postoloprty
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
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Louny, 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 16 Sept Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 93% · 37
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 88% 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 (5 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
11:41on time on time
11:45≈ on time ≈ on time
11:52≈ 1 min early ≈ on time
11:54≈ 1 min early ≈ on time
11:571 min early on time

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 NovLouny 11:58No data—
Wed 4 NovLouny 11:58No data—
Tue 3 NovLouny 11:58No data—
Mon 2 NovLouny 11:58No data—
Fri 30 OctLouny 11:58No data—
Thu 29 OctLouny 11:58No data—
Tue 27 OctLouny 11:58No data—
Mon 26 OctLouny 11:58No data—
Fri 23 OctLouny 11:58No data—
Thu 22 OctLouny 11:58No data—
Wed 21 OctLouny 11:58No data—
Tue 20 OctLouny 11:58No data—
Mon 19 OctLouny 11:58No data—
Fri 16 OctLouny 11:58No data—
Thu 15 OctLouny 11:58No data—
Wed 14 OctLouny 11:58No data—
Tue 13 OctLouny 11:58No data—
Mon 12 OctLouny 11:58No data—
Fri 9 OctLouny 11:58No data—
Thu 8 OctLouny 11:58No data—
Wed 7 OctLouny 11:58No data—
Tue 6 OctLouny 11:58No data—
Mon 5 Oct— 12:110 min—
Fri 2 Oct— 12:11−1 min—
Thu 1 Oct— 12:11−1 min—
Wed 30 Sept— 12:09−2 min—
Tue 29 Sept— 12:110 min+1 min
Fri 25 Sept— 12:12−1 min—
Thu 24 Sept— 12:11−1 min—
Wed 23 Sept— 12:120 min—