Os 7974 7974 Písek město – Protivín

View line Os 7974

Písek město 23:13 → Protivín 23:34 Mon, Tue, Wed, Thu, Fri, Sat 0 h 21 min · 6 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 23:13 from Písek město · Sat 7 Nov

Next departure 23:13 today · Písek město
On-time · 30 days
—
Too little data (0/24 runs with data)
RT coverage: 0 full · 0 partial · 24 no data
On-time · 90 days
75%
36/48 runs under 3 min
RT coverage: 48 full · 0 partial · 28 no data
Typical delay
0min
Median at arrival, 90 days
P90
+9min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Protivín, in minutes. One bar per run.

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

Worst days

  • Thu 13 Aug Max en route +27 min · last fix heading to — +25 min
  • Mon 7 Sept Max en route +24 min · last fix heading to — +23 min
  • Fri 4 Sept Max en route +21 min · last fix heading to — +20 min
  • Mon 17 Aug Max en route +20 min · last fix heading to — +19 min
  • Thu 1 Oct Max en route +9 min · last fix heading to — +9 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 69% · 33
  • 3–10 min 17% · 8
  • 10–30 min 8% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 88% T n=8
  • 63% W n=8
  • 63% T n=8
  • 63% F n=8
  • 100% S n=8
  • 100% S n=1

Stops and timetable

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

Last 90 days, 48 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
23:13on time +9 min
23:16≈ on time ≈ +9 min
23:18 / 23:19≈ on time ≈ +9 min
23:23 / 23:24≈ on time ≈ +9 min
23:27≈ on time ≈ +9 min
23:34on time +9 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 6 NovProtivín 23:34No data—
Thu 5 NovProtivín 23:34No data—
Wed 4 NovProtivín 23:34No data—
Tue 3 NovProtivín 23:34No data—
Mon 2 NovProtivín 23:34No data—
Sat 31 OctProtivín 23:35No data—
Fri 30 OctProtivín 23:35No data—
Thu 29 OctProtivín 23:35No data—
Tue 27 OctProtivín 23:36No data—
Mon 26 OctProtivín 23:35No data—
Sat 24 OctProtivín 23:35No data—
Fri 23 OctProtivín 23:35No data—
Thu 22 OctProtivín 23:35No data—
Wed 21 OctProtivín 23:35No data—
Tue 20 OctProtivín 23:35No data—
Mon 19 OctProtivín 23:36No data—
Sat 17 OctProtivín 23:35No data—
Fri 16 OctProtivín 23:35No data—
Thu 15 OctProtivín 23:35No data—
Wed 14 OctProtivín 23:35No data—
Tue 13 OctProtivín 23:35No data—
Mon 12 OctProtivín 23:35No data—
Sat 10 OctProtivín 23:35No data—
Fri 9 OctProtivín 23:35No data—
Thu 8 OctProtivín 23:35No data—
Wed 7 OctProtivín 23:35No data—
Tue 6 OctProtivín 23:35No data—
Mon 5 OctProtivín 23:35No data—
Sat 3 Oct— 23:480 min—
Fri 2 Oct— 23:49+1 min+1 min