Os 13852 13852 Litovel předměstí – Červenka

View line Os 13852

Litovel předměstí 14:35 → Červenka 14:44 Tue, Sat, Sun 0 h 09 min · 5 stops České dráhy, a.s.

It does not run today

Last recorded run: Tuesday 17 November No data

Next service: Saturday 14:35 from Litovel předměstí · Sat 21 Nov

Next departure 14:35 Saturday · Litovel předměstí
On-time · 30 days
—
Too little data (0/10 runs with data)
RT coverage: 0 full · 0 partial · 10 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 14 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 Červenka, in minutes. One bar per run.

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

Worst days

  • Sat 3 Oct Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 86% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 15 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
14:35on time on time
14:36≈ on time ≈ on time
14:39≈ on time ≈ on time
14:41≈ on time ≈ +1 min
14:44on 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
Tue 17 NovČervenka 14:44No data—
Sun 15 NovČervenka 14:44No data—
Sat 14 NovČervenka 14:44No data—
Sun 8 NovČervenka 14:44No data—
Sat 7 NovČervenka 14:44No data—
Sun 1 NovČervenka 14:45No data—
Sat 31 OctČervenka 14:45No data—
Wed 28 OctČervenka 14:45No data—
Sun 25 OctČervenka 14:45No data—
Sat 24 OctČervenka 14:45No data—
Sun 18 OctČervenka 14:46No data—
Sat 17 OctČervenka 14:45No data—
Sun 11 OctČervenka 14:45No data—
Sat 10 OctČervenka 14:45No data—
Sun 4 Oct— 14:590 min—
Sat 3 Oct— 15:04+6 min+6 min
Mon 28 Sept— 14:59+1 min+2 min
Sun 27 Sept— 14:580 min—
Sat 26 Sept— 15:00+1 min+1 min
Sun 20 Sept— 14:580 min—
Sat 19 Sept— 14:590 min—
Sun 13 Sept— 14:580 min—
Sat 12 Sept— 14:590 min—
Sun 6 Sept— 14:580 min—
Sat 5 Sept— 14:590 min—
Sun 30 Aug— 14:580 min—
Sat 29 Aug— 14:590 min—
Sun 23 Aug— 14:590 min—
Sat 22 Aug— 14:57−1 min—