Os 26241 26241 Tanvald – Plavy

View line Os 26241

Tanvald 05:30 → Plavy 05:38 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 Plavy at 05:39 No data

  1. Tanvald05:30
  2. Velké Hamry město05:33
  3. Velké Hamry05:35
  4. Plavy05:38

Next service: tomorrow 05:30 from Tanvald · Tue 10 Nov

Next departure 05:30 tomorrow · Tanvald
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
97%
37/38 runs under 3 min
RT coverage: 38 full · 0 partial · 24 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 Plavy, in minutes. One bar per run.

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

Worst days

  • Mon 17 Aug Max en route +9 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 95% · 36
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Last 90 days, 38 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:30+1 min +3 min
05:33≈ on time ≈ +2 min
05:35≈ on time ≈ +1 min
05:38on 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
Mon 9 NovPlavy 05:39No data—
Fri 6 NovPlavy 05:39No data—
Thu 5 NovPlavy 05:39No data—
Wed 4 NovPlavy 05:39No data—
Tue 3 NovPlavy 05:40No data—
Mon 2 NovPlavy 05:39No data—
Fri 30 OctPlavy 05:39No data—
Thu 29 OctPlavy 05:39No data—
Tue 27 OctPlavy 05:39No data—
Mon 26 OctPlavy 05:39No data—
Fri 23 OctPlavy 05:39No data—
Thu 22 OctPlavy 05:39No data—
Wed 21 OctPlavy 05:39No data—
Tue 20 OctPlavy 05:39No data—
Mon 19 OctPlavy 05:39No data—
Fri 16 OctPlavy 05:39No data—
Thu 15 OctPlavy 05:39No data—
Wed 14 OctPlavy 05:39No data—
Tue 13 OctPlavy 05:39No data—
Mon 12 OctPlavy 05:39No data—
Fri 9 OctPlavy 05:39No data—
Thu 8 OctPlavy 05:39No data—
Wed 7 OctPlavy 05:39No data—
Tue 6 OctPlavy 05:40No data—
Mon 5 Oct— 05:52−1 min+1 min
Fri 2 Oct— 05:51−1 min—
Thu 1 Oct— 05:51−1 min+1 min
Wed 30 Sept— 05:520 min—
Tue 29 Sept— 05:51−2 min—
Fri 25 Sept— 05:52−1 min—