EN 417 417 Chałupki – Bohumín

View line EN 417

Chałupki 00:05 → Bohumín 00:11 Daily 0 h 06 min · 2 stops PKP INTERCITY S.A.

✓ Today’s run finished

Today, last fix heading to Bohumín at 00:12 No data

  1. Chałupki00:05
  2. Bohumín00:11

Next service: tomorrow 00:05 from Chałupki · Sat 7 Nov

Next departure 00:05 tomorrow · Chałupki
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
39%
22/56 runs under 3 min
RT coverage: 56 full · 0 partial · 32 no data
Typical delay
+4min
Median at arrival, 90 days
P90
+17min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Bohumín, in minutes. One bar per run.

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

Worst days

  • Sun 6 Sept Max en route +49 min · last fix heading to — +49 min
  • Tue 1 Sept Max en route +41 min · last fix heading to — +41 min
  • Thu 10 Sept Max en route +22 min · last fix heading to — +22 min
  • Thu 17 Sept Max en route +21 min · last fix heading to — +21 min
  • Mon 31 Aug Max en route +19 min · last fix heading to — +19 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 39% · 22
  • 3–10 min 38% · 21
  • 10–30 min 20% · 11
  • 30+ min 4% · 2

On-time by weekday

  • 22% M n=9
  • 17% T n=6
  • 38% W n=8
  • 50% T n=8
  • 50% F n=8
  • 50% S n=8
  • 44% S n=9

Stops and timetable

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

Last 90 days, 56 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
00:05+4 min +20 min
00:11+4 min +17 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
Fri 6 NovBohumín 00:12No data—
Thu 5 NovBohumín 00:12No data—
Wed 4 NovBohumín 00:12No data—
Tue 3 NovBohumín 00:12No data—
Mon 2 NovBohumín 00:12No data—
Sun 1 NovBohumín 00:12No data—
Sat 31 OctBohumín 00:12No data—
Fri 30 OctBohumín 00:12No data—
Thu 29 OctBohumín 00:12No data—
Wed 28 OctBohumín 00:13No data—
Tue 27 OctBohumín 00:12No data—
Mon 26 OctBohumín 00:12No data—
Sun 25 OctBohumín 01:12No data—
Sat 24 OctBohumín 00:12No data—
Fri 23 OctBohumín 00:12No data—
Thu 22 OctBohumín 00:12No data—
Wed 21 OctBohumín 00:12No data—
Tue 20 OctBohumín 00:13No data—
Mon 19 OctBohumín 00:12No data—
Sun 18 OctBohumín 00:12No data—
Sat 17 OctBohumín 00:12No data—
Fri 16 OctBohumín 00:12No data—
Thu 15 OctBohumín 00:12No data—
Wed 14 OctBohumín 00:12No data—
Tue 13 OctBohumín 00:12No data—
Mon 12 OctBohumín 00:12No data—
Sun 11 OctBohumín 00:12No data—
Sat 10 OctBohumín 00:12No data—
Fri 9 OctBohumín 00:12No data—
Thu 8 OctBohumín 00:12No data—