RJ 101036 101036

View line RJ 101036

Mon, Sat, Sun RegioJet a.s.

It does not run today

Last recorded run: Sunday 4 October +12 min

The mini-map returns when the train runs
On-time · 30 days
20%
1/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
On-time · 90 days
20%
1/5 runs under 3 min
RT coverage: 5 full · 0 partial · 0 no data
Typical delay
+13min
Median at arrival, 90 days
30 days: +13 min
P90
+63min
9 in 10 runs arrive with less than this
30 days: +63 min

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

  • Sat 3 Oct Max en route +68 min · last fix heading to — +67 min
  • Sun 27 Sept Max en route +60 min · last fix heading to — +57 min
  • Mon 28 Sept Max en route +15 min · last fix heading to — +13 min
  • Sun 4 Oct Max en route +13 min · last fix heading to — +12 min

Distribution · 90 days

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

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

On-time by weekday

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

Recent runs

DateLast stopFinalMax
Sun 4 Oct— 22:17+12 min+13 min
Sat 3 Oct— 23:12+67 min+68 min
Mon 28 Sept— 22:19+13 min+15 min
Sun 27 Sept— 23:02+57 min+60 min
Sat 26 Sept— 22:05−1 min+1 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.