R 1099 1099 Most – Blatno u Jesenice

View line R 1099

Most 19:10 → Blatno u Jesenice 20:48 Mon, Tue, Wed, Thu 1 h 38 min · 19 stops GW Train Regio a.s.

It does not run today

Last recorded run: Thursday 5 November No data

Next service: tomorrow 19:10 from Most · Mon 9 Nov

Next departure 19:10 tomorrow · Most
On-time · 30 days
—
Too little data (0/14 runs with data)
RT coverage: 0 full · 0 partial · 14 no data
On-time · 90 days
43%
13/30 runs under 3 min
RT coverage: 30 full · 0 partial · 18 no data
Typical delay
+3min
Median at arrival, 90 days
P90
+7min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Blatno u Jesenice, 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 24 Aug Max en route +28 min · last fix heading to — +22 min
  • Tue 18 Aug Max en route +17 min · last fix heading to — +14 min
  • Mon 31 Aug Max en route +10 min · last fix heading to — +9 min
  • Wed 9 Sept Max en route +7 min · last fix heading to — +7 min
  • Wed 23 Sept Max en route +7 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 43% · 13
  • 3–10 min 50% · 15
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 33% M n=6
  • 38% T n=8
  • 38% W n=8
  • 63% T n=8
  • — F n=0
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 30 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
19:10on time on time
19:16≈ on time ≈ +1 min
19:25 / 19:26≈ on time ≈ +1 min
19:30 / 19:31≈ +1 min ≈ +2 min
19:31≈ +1 min ≈ +2 min
19:34 / 19:36≈ +1 min ≈ +2 min
19:46≈ +1 min ≈ +3 min
19:48≈ +1 min ≈ +3 min
19:50≈ +1 min ≈ +3 min
19:51≈ +1 min ≈ +3 min
19:54≈ +1 min ≈ +3 min
19:56 / 20:00≈ +1 min ≈ +3 min
20:02≈ +2 min ≈ +4 min
20:18≈ +2 min ≈ +5 min
20:23 / 20:24≈ +2 min ≈ +5 min
20:32 / 20:33≈ +3 min ≈ +6 min
20:38≈ +3 min ≈ +6 min
20:43≈ +3 min ≈ +7 min
20:48+3 min +7 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
Thu 5 NovBlatno u Jesenice 20:49No data—
Wed 4 NovBlatno u Jesenice 20:49No data—
Tue 3 NovBlatno u Jesenice 20:49No data—
Mon 2 NovBlatno u Jesenice 20:49No data—
Thu 29 OctBlatno u Jesenice 20:50No data—
Mon 26 OctBlatno u Jesenice 20:50No data—
Thu 22 OctBlatno u Jesenice 20:50No data—
Wed 21 OctBlatno u Jesenice 20:50No data—
Tue 20 OctBlatno u Jesenice 20:50No data—
Mon 19 OctBlatno u Jesenice 20:50No data—
Thu 15 OctBlatno u Jesenice 20:50No data—
Wed 14 OctBlatno u Jesenice 20:50No data—
Tue 13 OctBlatno u Jesenice 20:50No data—
Mon 12 OctBlatno u Jesenice 20:50No data—
Thu 8 OctBlatno u Jesenice 20:50No data—
Wed 7 OctBlatno u Jesenice 20:50No data—
Tue 6 OctBlatno u Jesenice 20:50No data—
Mon 5 OctBlatno u Jesenice 20:50No data—
Thu 1 Oct— 21:06+3 min+3 min
Wed 30 Sept— 21:04+1 min+3 min
Tue 29 Sept— 21:07+4 min+5 min
Thu 24 Sept— 21:020 min+3 min
Wed 23 Sept— 21:09+6 min+7 min
Tue 22 Sept— 21:05+3 min+4 min
Mon 21 Sept— 21:07+3 min+4 min
Thu 17 Sept— 21:10+6 min+6 min
Wed 16 Sept— 21:030 min+3 min
Tue 15 Sept— 21:030 min+2 min
Mon 14 Sept— 21:030 min+2 min
Thu 10 Sept— 21:04+1 min+3 min