R 1190 1190 Kolín – Rumburk

View line R 1190

Kolín 17:45 → Rumburk 20:37 Daily 2 h 52 min · 40 stops ARRIVA vlaky s.r.o.

Running now · updated 18:11

Between Veleliby and Všejany +1 min

Estimated arrival at Rumburk 20:38 20:37 · 49 km/h

  1. Kolín17:45
  2. Nymburk hl. n.18:06
  3. Veleliby18:11
  4. Všejany18:15
  5. Dobrovice18:25
  6. Bělá pod Bezdězem18:56
  7. Rumburk20:37

Today it is running no worse than usual: typical arrival delay is +2 min; 60% of the last 10 runs arrived on time.

On-time · 30 days
60%
6/10 runs under 3 min
RT coverage: 9 full · 1 partial · 0 no data
On-time · 90 days
60%
6/10 runs under 3 min
RT coverage: 9 full · 1 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Rumburk, 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 9 Nov Max en route +15 min · last fix heading to Rumburk +9 min
  • Fri 6 Nov Max en route +5 min · last fix heading to Rumburk +4 min
  • Sun 8 Nov Max en route +5 min · last fix heading to Rumburk +3 min
  • Sat 7 Nov Max en route +3 min · last fix heading to Rumburk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 60% · 6
  • 3–10 min 40% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 10 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 10Today
17:45+1 min +5 minPassed
17:47≈ +1 min ≈ +3 minPassed
17:50≈ +1 min ≈ +3 minPassed
17:52≈ +1 min ≈ +3 minPassed
17:54≈ +1 min ≈ +3 minPassed
17:57 / 17:59≈ +1 min ≈ +3 minPassed
18:01≈ +1 min ≈ +3 minPassed
18:06 / 18:08≈ +1 min ≈ +3 minPassed
18:11≈ +1 min ≈ +3 minPassed
18:15≈ +1 min ≈ +2 minNext
18:17≈ +1 min ≈ +2 min
18:21≈ +1 min ≈ +2 min
18:22≈ +1 min ≈ +2 min
18:25≈ +1 min ≈ +2 min
18:26≈ +1 min ≈ +2 min
18:32 / 18:37≈ +1 min ≈ +2 min
18:42≈ +1 min ≈ +2 min
18:46 / 18:47≈ +1 min ≈ +2 min
18:49≈ +1 min ≈ +2 min
18:53≈ +1 min ≈ +2 min
18:56 / 18:57≈ +1 min ≈ +2 min
19:01≈ +1 min ≈ +2 min
19:05≈ +1 min ≈ +2 min
19:10≈ +1 min ≈ +2 min
19:14 / 19:15≈ +1 min ≈ +2 min
19:18≈ +1 min ≈ +2 min
19:22≈ +1 min ≈ +2 min
19:24≈ +1 min ≈ +2 min
19:29 / 19:40≈ +2 min ≈ +2 min
19:42 / 19:43≈ +2 min ≈ +2 min
19:50≈ +2 min ≈ +3 min
19:57 / 19:59≈ +2 min ≈ +3 min
20:05 / 20:06≈ +2 min ≈ +3 min
20:13≈ +2 min ≈ +3 min
20:15 / 20:16≈ +2 min ≈ +3 min
20:22≈ +2 min ≈ +3 min
20:26≈ +2 min ≈ +3 min
20:29≈ +2 min ≈ +3 min
20:31≈ +2 min ≈ +3 min
20:37+2 min +3 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
Wed 11 NovVeleliby 18:09Partial coverage+1 min+1 min
Tue 10 NovRumburk 20:380 min+4 min
Mon 9 NovRumburk 20:38+9 min+15 min
Sun 8 NovRumburk 20:38+3 min+5 min
Sat 7 NovRumburk 20:38+3 min+3 min
Fri 6 NovRumburk 20:38+4 min+5 min
Thu 5 NovRumburk 20:38+2 min+5 min
Wed 4 NovRumburk 20:380 min+2 min
Tue 3 NovRumburk 20:38+1 min+5 min
Mon 2 NovRumburk 20:380 min+4 min