Os 4244 4244 St. Město u U.H. – Moravský Písek

View line Os 4244

St. Město u U.H. 04:10 → Moravský Písek 04:22 Mon, Tue, Wed, Thu, Fri 0 h 12 min · 5 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 04:10 from St. Město u U.H. · Fri 6 Nov

Next departure 04:10 today · St. Město u U.H.
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
100%
40/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
−2min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Moravský Písek, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 63% · 25
  • On time 38% · 15
  • 3–10 min 0% · 0
  • 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
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
04:10+1 min +3 min
04:14≈ on time ≈ +2 min
04:15≈ 1 min early ≈ +2 min
04:20≈ 2 min early ≈ +1 min
04:222 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 NovMoravský Písek 04:23No data—
Wed 4 NovMoravský Písek 04:23No data—
Tue 3 NovMoravský Písek 04:23No data—
Mon 2 NovMoravský Písek 04:23No data—
Fri 30 OctMoravský Písek 04:23No data—
Thu 29 OctMoravský Písek 04:23No data—
Tue 27 OctMoravský Písek 04:23No data—
Mon 26 OctMoravský Písek 04:23No data—
Fri 23 OctMoravský Písek 04:23No data—
Thu 22 OctMoravský Písek 04:23No data—
Wed 21 OctMoravský Písek 04:23No data—
Tue 20 OctMoravský Písek 04:23No data—
Mon 19 OctMoravský Písek 04:23No data—
Fri 16 OctMoravský Písek 04:23No data—
Thu 15 OctMoravský Písek 04:23No data—
Wed 14 OctMoravský Písek 04:23No data—
Tue 13 OctMoravský Písek 04:23No data—
Mon 12 OctMoravský Písek 04:23No data—
Fri 9 OctMoravský Písek 04:23No data—
Thu 8 OctMoravský Písek 04:23No data—
Wed 7 OctMoravský Písek 04:23No data—
Tue 6 OctMoravský Písek 04:23No data—
Mon 5 Oct— 04:35−1 min—
Fri 2 Oct— 04:33−3 min—
Thu 1 Oct— 04:34−3 min—
Wed 30 Sept— 04:370 min+4 min
Tue 29 Sept— 04:370 min+4 min
Fri 25 Sept— 04:36−1 min+2 min
Thu 24 Sept— 04:34−2 min—
Wed 23 Sept— 04:33−3 min+1 min