Os 26245 26245 Tanvald – Plavy

View line Os 26245

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

  1. Tanvald07:30
  2. Velké Hamry město07:33
  3. Velké Hamry07:35
  4. Plavy07:38

Next service: Monday 07:30 from Tanvald · Mon 23 Nov

Next departure 07:30 Monday · 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
75%
18/24 runs under 3 min
RT coverage: 24 full · 0 partial · 32 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+4min
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

  • Tue 1 Sept Max en route +7 min · last fix heading to — +6 min
  • Mon 5 Oct Max en route +6 min · last fix heading to — +4 min
  • Fri 11 Sept Max en route +5 min · last fix heading to — +4 min
  • Fri 2 Oct Max en route +5 min · last fix heading to — +3 min
  • Mon 21 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 18
  • 3–10 min 25% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=4
  • 80% T n=5
  • 100% W n=5
  • 80% T n=5
  • 60% F n=5
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 24 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
07:30+2 min +5 min
07:33≈ +2 min ≈ +5 min
07:35≈ +2 min ≈ +4 min
07:38+2 min +4 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
Fri 20 NovPlavy 07:39No data—
Thu 19 NovPlavy 07:39No data—
Wed 18 NovPlavy 07:39No data—
Mon 16 NovPlavy 07:39No data—
Fri 13 NovPlavy 07:40No data—
Thu 12 NovPlavy 07:39No data—
Wed 11 NovPlavy 07:39No data—
Tue 10 NovPlavy 07:39No data—
Mon 9 NovPlavy 07:39No data—
Fri 6 NovPlavy 07:39No data—
Thu 5 NovPlavy 07:39No data—
Wed 4 NovPlavy 07:39No data—
Tue 3 NovPlavy 07:39No data—
Mon 2 NovPlavy 07:39No data—
Fri 30 OctPlavy 07:39No data—
Thu 29 OctPlavy 07:39No data—
Tue 27 OctPlavy 07:39No data—
Mon 26 OctPlavy 07:39No data—
Fri 23 OctPlavy 07:39No data—
Thu 22 OctPlavy 07:39No data—
Wed 21 OctPlavy 07:39No data—
Tue 20 OctPlavy 07:39No data—
Mon 19 OctPlavy 07:39No data—
Fri 16 OctPlavy 07:39No data—
Thu 15 OctPlavy 07:39No data—
Wed 14 OctPlavy 07:39No data—
Tue 13 OctPlavy 07:39No data—
Mon 12 OctPlavy 07:39No data—
Fri 9 OctPlavy 07:39No data—
Thu 8 OctPlavy 07:39No data—