REG 95868 Malbork – Grudziądz

View line REG

Malbork 11:16 → Grudziądz 12:27 Daily 1 h 11 min · 14 stops PolRegio

✓ Today’s run finished

Today it reached Grudziądz at 12:27 0 min

  1. Malbork11:16
  2. Sztum11:28
  3. Ryjewo11:38
  4. Sadlinki11:56
  5. Gardeja12:06
  6. Grudziądz Owczarki12:18
  7. Grudziądz12:27

Next service: tomorrow 11:16 from Malbork · Wed 11 Nov

Next departure 11:16 tomorrow · Malbork
On-time · 30 days
91%
21/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
88%
29/33 runs under 3 min
RT coverage: 33 full · 0 partial · 38 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: +2 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

  • Fri 6 Nov Max en route +6 min · last fix heading to Grudziądz +6 min
  • Sun 1 Nov Max en route +6 min · last fix heading to Grudziądz +6 min
  • Tue 22 Sept Max en route +5 min · last fix heading to Grudziądz Tuszewo +5 min
  • Mon 21 Sept Max en route +4 min · last fix heading to Grudziądz +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 29
  • 3–10 min 12% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 33 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
11:16on time +2 min
11:22 / 11:23≈ on time ≈ +2 min
11:28≈ on time ≈ +2 min
11:31 / 11:32≈ on time ≈ +2 min
11:38≈ on time ≈ +3 min
11:42≈ on time ≈ +3 min
11:49 / 11:50≈ on time ≈ +3 min
11:56 / 11:57≈ on time ≈ +3 min
12:01 / 12:02≈ on time ≈ +3 min
12:06≈ on time ≈ +3 min
12:12≈ on time ≈ +3 min
12:18≈ on time ≈ +3 min
12:21≈ on time ≈ +3 min
12:27on 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 NovGrudziądz 12:280 min—
Mon 9 NovGrudziądz 12:290 min—
Sun 8 NovGrudziądz 12:290 min—
Sat 7 NovGrudziądz 12:280 min—
Fri 6 NovGrudziądz 12:34+6 min+6 min
Thu 5 NovGrudziądz 12:280 min—
Wed 4 NovGrudziądz 12:280 min—
Tue 3 NovGrudziądz 12:280 min—
Mon 2 NovGrudziądz 12:280 min—
Sun 1 NovGrudziądz 12:34+6 min+6 min
Sat 31 OctGrudziądz 12:280 min—
Fri 30 OctGrudziądz 12:280 min—
Thu 29 OctGrudziądz 12:280 min—
Wed 28 OctGrudziądz 12:30+2 min+2 min
Tue 27 OctGrudziądz 12:30+2 min+2 min
Mon 26 OctGrudziądz 12:280 min—
Sun 25 OctGrudziądz 12:28No data—
Sat 24 OctGrudziądz 12:24No data—
Fri 23 OctGrudziądz 12:24No data—
Thu 22 OctGrudziądz 12:24No data—
Wed 21 OctGrudziądz 12:24No data—
Tue 20 OctGrudziądz 12:24No data—
Mon 19 OctGrudziądz 12:24No data—
Sun 18 OctGrudziądz 12:240 min—
Sat 17 OctGrudziądz 12:240 min—
Fri 16 OctGrudziądz 12:240 min—
Thu 15 OctGrudziądz 12:240 min—
Wed 14 OctGrudziądz 12:250 min—
Tue 13 OctGrudziądz 12:240 min—
Mon 12 OctGrudziądz 12:240 min—