R 1098 1098 Blatno u Jesenice – Most

View line R 1098

Blatno u Jesenice 05:10 → Most 07:01 Mon, Tue, Wed, Thu, Fri 1 h 51 min · 19 stops GW Train Regio a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 05:10 from Blatno u Jesenice · Mon 9 Nov

Next departure 05:10 tomorrow · Blatno u Jesenice
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 39 full · 0 partial · 23 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Most, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 19 Aug Max en route +14 min · last fix heading to — +13 min
  • Wed 26 Aug Max en route +7 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 90% · 35
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=8
  • 75% W n=8
  • 100% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
05:10on time on time
05:16≈ on time ≈ on time
05:20 / 05:21≈ on time ≈ on time
05:26≈ on time ≈ on time
05:35 / 05:36≈ on time ≈ on time
05:41≈ on time ≈ on time
05:57≈ on time ≈ on time
05:59 / 06:09≈ on time ≈ on time
06:12≈ 1 min early ≈ on time
06:16 / 06:17≈ 1 min early ≈ on time
06:19≈ 1 min early ≈ on time
06:20≈ 1 min early ≈ on time
06:23 / 06:24≈ 1 min early ≈ on time
06:35 / 06:36≈ 1 min early ≈ on time
06:38≈ 1 min early ≈ on time
06:38 / 06:39≈ 1 min early ≈ on time
06:43 / 06:44≈ 1 min early ≈ on time
06:54 / 06:55≈ 1 min early ≈ on time
07:011 min early on time

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
Fri 6 NovMost 07:02No data—
Thu 5 NovMost 07:02No data—
Wed 4 NovMost 07:02No data—
Tue 3 NovMost 07:02No data—
Mon 2 NovMost 07:02No data—
Fri 30 OctMost 07:02No data—
Thu 29 OctMost 07:02No data—
Tue 27 OctMost 07:02No data—
Mon 26 OctMost 07:02No data—
Fri 23 OctMost 07:02No data—
Thu 22 OctMost 07:02No data—
Wed 21 OctMost 07:02No data—
Tue 20 OctMost 07:02No data—
Mon 19 OctMost 07:02No data—
Fri 16 OctMost 07:02No data—
Thu 15 OctMost 07:02No data—
Wed 14 OctMost 07:02No data—
Tue 13 OctMost 07:02No data—
Mon 12 OctMost 07:02No data—
Fri 9 OctMost 07:02No data—
Thu 8 OctMost 07:02No data—
Wed 7 OctMost 07:02No data—
Tue 6 OctMost 07:02No data—
Mon 5 Oct— 07:160 min—
Fri 2 Oct— 07:160 min+5 min
Thu 1 Oct— 07:15−1 min+2 min
Wed 30 Sept— 07:14−1 min+2 min
Tue 29 Sept— 07:150 min+2 min
Fri 25 Sept— 07:150 min+3 min
Thu 24 Sept— 07:13−2 min+2 min