Os 305006 305006

View line Os 305006

CZ

Not running right now

Last recorded run: Sunday 13 September +3 min

The mini-map returns when the train runs
On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 2 full · 0 partial · 0 no data
On-time · 90 days
29%
2/7 runs under 3 min
RT coverage: 7 full · 0 partial · 1 no data
Typical delay
+3min
Median at arrival, 90 days
P90
+8min
9 in 10 runs arrive with less than this

Last 30 days

Delay at the end of each run, 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 7 Sept Max en route +11 min · last fix heading to — +11 min
  • Wed 9 Sept Max en route +6 min · last fix heading to — +6 min
  • Tue 8 Sept Max en route +5 min · last fix heading to — +5 min
  • Sun 13 Sept Max en route +3 min · last fix heading to — +3 min
  • Sat 12 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 29% · 2
  • 3–10 min 57% · 4
  • 10–30 min 14% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=1
  • 0% T n=1
  • 0% W n=1
  • 100% T n=1
  • 100% F n=1
  • 0% S n=1
  • 0% S n=1

Recent runs

DateLast stopFinalMax
Sun 13 Sept— 08:33+3 min+3 min
Sat 12 Sept— 08:34+3 min+3 min
Fri 11 Sept— 08:270 min—
Thu 10 Sept— 08:310 min—
Wed 9 Sept— 08:37+6 min+6 min
Tue 8 Sept— 08:36+5 min+5 min
Mon 7 Sept— 08:41+11 min+11 min
Sun 6 Sept— 11:35No data—

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.