Os 26707 26707 Postoloprty – Louny

View line Os 26707

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 21:38 from Postoloprty · Thu 5 Nov

Next departure 21:38 today · Postoloprty
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%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 22 no data
Typical delay
0min
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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=7
  • 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 (5 stops).

Last 90 days, 39 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
21:38on time on time
21:42≈ on time ≈ on time
21:49≈ on time ≈ on time
21:51≈ on time ≈ on time
21:54on time 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
Wed 4 NovLouny 21:54No data—
Tue 3 NovLouny 21:54No data—
Mon 2 NovLouny 21:54No data—
Fri 30 OctLouny 21:55No data—
Thu 29 OctLouny 21:55No data—
Tue 27 OctLouny 21:56No data—
Mon 26 OctLouny 21:55No data—
Fri 23 OctLouny 21:55No data—
Thu 22 OctLouny 21:55No data—
Wed 21 OctLouny 21:55No data—
Tue 20 OctLouny 21:55No data—
Mon 19 OctLouny 21:56No data—
Fri 16 OctLouny 21:55No data—
Thu 15 OctLouny 21:55No data—
Wed 14 OctLouny 21:55No data—
Tue 13 OctLouny 21:55No data—
Mon 12 OctLouny 21:56No data—
Fri 9 OctLouny 21:55No data—
Thu 8 OctLouny 21:56No data—
Wed 7 OctLouny 21:55No data—
Tue 6 OctLouny 21:55No data—
Mon 5 OctLouny 21:55No data—
Fri 2 Oct— 22:080 min—
Thu 1 Oct— 22:080 min—
Wed 30 Sept— 22:07−1 min—
Tue 29 Sept— 22:07−1 min—
Fri 25 Sept— 22:090 min—
Thu 24 Sept— 22:090 min—
Wed 23 Sept— 22:090 min+1 min
Tue 22 Sept— 22:080 min+1 min