REG 90313 Gdynia Główna – Hel

View line REG

Gdynia Główna 15:36 → Hel 17:04 Daily 1 h 28 min · 17 stops PolRegio

Running now · updated 16:39

Between Chałupy and Kuźnica (Hel) 0 min

Estimated arrival at Hel 17:04 · 63 km/h

  1. Gdynia Główna15:36
  2. Reda15:56
  3. Mrzezino16:07
  4. Swarzewo16:20
  5. Chałupy16:36
  6. Kuźnica (Hel)16:41
  7. Hel17:04

Today it is running no worse than usual: typical arrival delay is 0 min; 83% of the last 23 runs arrived on time.

On-time · 30 days
83%
19/23 runs under 3 min
RT coverage: 22 full · 1 partial · 7 no data
On-time · 90 days
68%
28/41 runs under 3 min
RT coverage: 40 full · 1 partial · 21 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +6 min

Last 30 days

Arrival delay at Hel, 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 +29 min · last fix heading to Chałupy +29 min
  • Fri 2 Oct Max en route +28 min · last fix heading to Chałupy +28 min
  • Sun 1 Nov Max en route +10 min · last fix heading to Hel +10 min
  • Wed 28 Oct Max en route +10 min · last fix heading to Hel +10 min
  • Sun 27 Sept Max en route +8 min · last fix heading to Hel +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 68% · 28
  • 3–10 min 22% · 9
  • 10–30 min 10% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 60% M n=5
  • 60% T n=5
  • 83% W n=6
  • 83% T n=6
  • 57% F n=7
  • 67% S n=6
  • 67% S n=6

Stops and timetable

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

Last 90 days, 41 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
15:36on time +8 minPassed
15:41 / 15:43≈ on time ≈ +8 minPassed
15:49 / 15:52≈ on time ≈ +8 minPassed
15:56 / 15:57≈ on time ≈ +8 minPassed
16:02 / 16:03≈ on time ≈ +8 minPassed
16:07 / 16:08≈ on time ≈ +8 minPassed
16:10 / 16:11≈ on time ≈ +8 minPassed
16:15 / 16:16≈ on time ≈ +8 minPassed
16:20 / 16:21≈ on time ≈ +8 minPassed
16:27 / 16:28≈ on time ≈ +8 minPassed
16:30≈ on time ≈ +8 minPassed
16:36≈ on time ≈ +8 minPassed
16:41 / 16:42≈ on time ≈ +8 minNext
16:47≈ on time ≈ +8 min
16:50≈ on time ≈ +8 min
16:54≈ on time ≈ +8 min
17:04on time +8 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 1 August 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
Sun 8 NovChałupy 16:34Partial coverage0 min—
Sat 7 NovHel 17:040 min—
Fri 6 NovHel 17:040 min—
Thu 5 NovHel 17:040 min—
Wed 4 NovHel 17:040 min—
Tue 3 NovHel 17:050 min—
Mon 2 NovHel 17:040 min—
Sun 1 NovHel 17:15+10 min+10 min
Sat 31 OctHel 17:060 min—
Fri 30 OctHel 17:050 min—
Thu 29 OctHel 17:06+1 min+1 min
Wed 28 OctHel 17:05+10 min+10 min
Tue 27 OctHel 17:09+4 min+4 min
Mon 26 OctHel 17:12+6 min+6 min
Sun 25 OctHel 17:05No data—
Sat 24 OctHel 17:05No data—
Fri 23 OctHel 17:06No data—
Thu 22 OctHel 17:05No data—
Wed 21 OctHel 17:06No data—
Tue 20 OctHel 17:05No data—
Mon 19 OctHel 17:05No data—
Sun 18 OctHel 17:060 min—
Sat 17 OctHel 17:060 min—
Fri 16 OctHel 17:050 min—
Thu 15 OctHel 17:050 min—
Wed 14 OctHel 17:050 min—
Tue 13 OctHel 17:060 min—
Mon 12 OctHel 17:050 min—
Sun 11 OctHel 17:050 min—
Sat 10 OctHel 17:060 min—