Os 26244 26244 Plavy – Tanvald

View line Os 26244

Plavy 06:42 → Tanvald 06:50 Mon, Tue, Wed, Thu, Fri 0 h 08 min · 4 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Tanvald at 06:49 No data

  1. Plavy06:42
  2. Velké Hamry06:43
  3. Velké Hamry město06:45
  4. Tanvald06:50

Next service: tomorrow 06:42 from Plavy · Fri 6 Nov

Next departure 06:42 tomorrow · Plavy
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 Tanvald, in minutes. One bar per run.

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

Worst days

  • Fri 28 Aug Max en route +3 min · last fix heading to — +3 min

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 98% · 39
  • 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
  • 100% W n=8
  • 100% T n=8
  • 88% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 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
06:42on time +1 min
06:43≈ on time ≈ +1 min
06:45≈ on time ≈ +1 min
06:501 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 NovTanvald 06:49No data—
Wed 4 NovTanvald 06:49No data—
Tue 3 NovTanvald 06:49No data—
Mon 2 NovTanvald 06:49No data—
Fri 30 OctTanvald 06:51No data—
Thu 29 OctTanvald 06:51No data—
Tue 27 OctTanvald 06:51No data—
Mon 26 OctTanvald 06:51No data—
Fri 23 OctTanvald 06:51No data—
Thu 22 OctTanvald 06:51No data—
Wed 21 OctTanvald 06:51No data—
Tue 20 OctTanvald 06:51No data—
Mon 19 OctTanvald 06:51No data—
Fri 16 OctTanvald 06:51No data—
Thu 15 OctTanvald 06:51No data—
Wed 14 OctTanvald 06:51No data—
Tue 13 OctTanvald 06:51No data—
Mon 12 OctTanvald 06:51No data—
Fri 9 OctTanvald 06:51No data—
Thu 8 OctTanvald 06:51No data—
Wed 7 OctTanvald 06:51No data—
Tue 6 OctTanvald 06:51No data—
Mon 5 Oct— 07:04−1 min—
Fri 2 Oct— 07:060 min+2 min
Thu 1 Oct— 07:050 min—
Wed 30 Sept— 07:040 min+2 min
Tue 29 Sept— 07:040 min—
Fri 25 Sept— 07:03−1 min—
Thu 24 Sept— 07:040 min—
Wed 23 Sept— 07:03−1 min—