Sp 103366 103366

View line Sp 103366

CZ

Not running right now

Last recorded run: Thursday 10 September +5 min

The mini-map returns when the train runs
On-time · 30 days
—
Too little data (1/1 runs with data)
RT coverage: 1 full · 0 partial · 0 no data
On-time · 90 days
17%
1/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
Typical delay
+4min
Median at arrival, 90 days
P90
+6min
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

  • Tue 8 Sept Max en route +8 min · last fix heading to — +7 min
  • Thu 10 Sept Max en route +5 min · last fix heading to — +5 min
  • Wed 9 Sept Max en route +4 min · last fix heading to — +4 min
  • Mon 7 Sept Max en route +5 min · last fix heading to — +4 min
  • Mon 20 Jul Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 17% · 1
  • 3–10 min 83% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Recent runs

DateLast stopFinalMax
Thu 10 Sept— 13:03+5 min+5 min
Wed 9 Sept— 13:04+4 min+4 min
Tue 8 Sept— 13:09+7 min+8 min
Mon 7 Sept— 13:05+4 min+5 min
Mon 20 Jul— 13:01+3 min+3 min
Fri 17 Jul— 13:09+2 min+2 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.