Os 4313 4313 St. Město u U.H. – Bylnice

View line Os 4313

St. Město u U.H. 16:12 → Bylnice 17:52 Daily 1 h 40 min · 21 stops ARRIVA vlaky s.r.o.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 16:12 from St. Město u U.H. · Sat 7 Nov

Next departure 16:12 today · St. Město u U.H.
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
14%
8/57 runs under 3 min
RT coverage: 57 full · 0 partial · 32 no data
Typical delay
+6min
Median at arrival, 90 days
P90
+11min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Bylnice, in minutes. One bar per run.

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

Worst days

  • Sat 15 Aug Max en route +44 min · last fix heading to — +44 min
  • Sun 23 Aug Max en route +20 min · last fix heading to — +20 min
  • Mon 17 Aug Max en route +15 min · last fix heading to — +15 min
  • Sat 19 Sept Max en route +14 min · last fix heading to — +14 min
  • Thu 13 Aug Max en route +13 min · last fix heading to — +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 14% · 8
  • 3–10 min 70% · 40
  • 10–30 min 14% · 8
  • 30+ min 2% · 1

On-time by weekday

  • 22% M n=9
  • 0% T n=8
  • 13% W n=8
  • 13% T n=8
  • 13% F n=8
  • 13% S n=8
  • 25% S n=8

Stops and timetable

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

Last 90 days, 57 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
16:12on time +3 min
16:18 / 16:29≈ on time ≈ +3 min
16:32≈ +1 min ≈ +4 min
16:35≈ +2 min ≈ +4 min
16:37≈ +2 min ≈ +5 min
16:41≈ +2 min ≈ +5 min
16:45≈ +2 min ≈ +5 min
16:48 / 16:54≈ +3 min ≈ +5 min
16:57 / 17:05≈ +3 min ≈ +6 min
17:08≈ +4 min ≈ +7 min
17:10 / 17:11≈ +4 min ≈ +7 min
17:13≈ +4 min ≈ +8 min
17:16 / 17:17≈ +4 min ≈ +8 min
17:19≈ +4 min ≈ +8 min
17:22≈ +5 min ≈ +9 min
17:29≈ +5 min ≈ +9 min
17:35 / 17:36≈ +5 min ≈ +10 min
17:39≈ +5 min ≈ +10 min
17:41 / 17:42≈ +5 min ≈ +10 min
17:47≈ +6 min ≈ +11 min
17:52+6 min +11 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 NovBylnice 17:53No data—
Thu 5 NovBylnice 17:53No data—
Wed 4 NovBylnice 17:53No data—
Tue 3 NovBylnice 17:53No data—
Mon 2 NovBylnice 17:53No data—
Sun 1 NovBylnice 17:53No data—
Sat 31 OctBylnice 17:53No data—
Fri 30 OctBylnice 17:53No data—
Thu 29 OctBylnice 17:53No data—
Wed 28 OctBylnice 17:53No data—
Tue 27 OctBylnice 17:54No data—
Mon 26 OctBylnice 17:53No data—
Sun 25 OctBylnice 17:53No data—
Sat 24 OctBylnice 17:53No data—
Fri 23 OctBylnice 17:54No data—
Thu 22 OctBylnice 17:53No data—
Wed 21 OctBylnice 17:53No data—
Tue 20 OctBylnice 17:54No data—
Mon 19 OctBylnice 17:53No data—
Sun 18 OctBylnice 17:53No data—
Sat 17 OctBylnice 17:53No data—
Fri 16 OctBylnice 17:53No data—
Thu 15 OctBylnice 17:53No data—
Wed 14 OctBylnice 17:53No data—
Tue 13 OctBylnice 17:53No data—
Mon 12 OctBylnice 17:54No data—
Sun 11 OctBylnice 17:53No data—
Sat 10 OctBylnice 17:53No data—
Fri 9 OctBylnice 17:53No data—
Thu 8 OctBylnice 17:53No data—