REG 95862 Malbork – Grudziądz

View line REG

Malbork 06:03 → Grudziądz 07:14 Daily 1 h 11 min · 14 stops PolRegio

Running now · updated 06:46

Between Sadlinki and Dziwno 0 min

Estimated arrival at Grudziądz 07:14 · 65 km/h

  1. Malbork06:03
  2. Sztum06:15
  3. Ryjewo06:25
  4. Sadlinki06:44
  5. Dziwno06:49
  6. Gardeja06:54
  7. Grudziądz07:14

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

On-time · 30 days
83%
20/24 runs under 3 min
RT coverage: 23 full · 1 partial · 6 no data
On-time · 90 days
76%
28/37 runs under 3 min
RT coverage: 36 full · 1 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Grudziądz, 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 12 Sept Max en route +13 min · last fix heading to Grudziądz Owczarki +13 min
  • Sun 11 Oct Max en route +12 min · last fix heading to Grudziądz +12 min
  • Sun 1 Nov Max en route +5 min · last fix heading to Grudziądz +5 min
  • Sat 3 Oct Max en route +4 min · last fix heading to Grudziądz +4 min
  • Wed 28 Oct Max en route +4 min · last fix heading to Grudziądz +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 76% · 28
  • 3–10 min 19% · 7
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=5
  • 75% W n=4
  • 60% T n=5
  • 83% F n=6
  • 67% S n=6
  • 60% S n=5

Stops and timetable

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

Last 90 days, 37 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
06:03on time +3 minPassed
06:09 / 06:10≈ on time ≈ +4 minPassed
06:15≈ on time ≈ +4 minPassed
06:19≈ on time ≈ +4 minPassed
06:25 / 06:26≈ on time ≈ +4 minPassed
06:29 / 06:30≈ on time ≈ +4 minPassed
06:37 / 06:38≈ on time ≈ +4 minPassed
06:44 / 06:45≈ on time ≈ +4 minPassed
06:49 / 06:50≈ on time ≈ +4 minNext
06:54≈ on time ≈ +4 min
07:00≈ on time ≈ +4 min
07:06≈ on time ≈ +4 min
07:09≈ on time ≈ +4 min
07:14on time +4 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
Tue 10 NovSadlinki 06:44Partial coverage0 min—
Mon 9 NovGrudziądz 07:18+3 min+3 min
Sun 8 NovGrudziądz 07:140 min—
Sat 7 NovGrudziądz 07:140 min—
Fri 6 NovGrudziądz 07:140 min—
Thu 5 NovGrudziądz 07:17+2 min+2 min
Wed 4 NovGrudziądz 07:140 min—
Tue 3 NovGrudziądz 07:140 min—
Mon 2 NovGrudziądz 07:140 min—
Sun 1 NovGrudziądz 07:20+5 min+5 min
Sat 31 OctGrudziądz 07:150 min—
Fri 30 OctGrudziądz 07:150 min—
Thu 29 OctGrudziądz 07:18+3 min+3 min
Wed 28 OctGrudziądz 07:19+4 min+4 min
Tue 27 OctGrudziądz 07:150 min—
Mon 26 OctGrudziądz 07:150 min—
Sun 25 OctGrudziądz 07:15No data—
Sat 24 OctGrudziądz 07:18No data—
Fri 23 OctGrudziądz 07:18No data—
Thu 22 OctGrudziądz 07:18No data—
Wed 21 OctGrudziądz 07:18No data—
Tue 20 OctGrudziądz 07:18No data—
Mon 19 OctGrudziądz 07:180 min—
Sun 18 OctGrudziądz 07:180 min—
Sat 17 OctGrudziądz 07:180 min—
Fri 16 OctGrudziądz 07:180 min—
Thu 15 OctGrudziądz 07:180 min—
Wed 14 OctGrudziądz 07:180 min—
Tue 13 OctGrudziądz 07:180 min—
Mon 12 OctGrudziądz 07:190 min—