REG 95835 Grudziądz – Malbork

View line REG

Grudziądz 14:58 → Malbork 16:13 Daily 1 h 15 min · 14 stops PolRegio

✓ Today’s run finished

Today it reached Malbork at 16:13 0 min

  1. Grudziądz14:58
  2. Grudziądz Owczarki15:05
  3. Gardeja15:17
  4. Kwidzyn15:32
  5. Ryjewo15:44
  6. Sztum15:54
  7. Malbork16:13

Next service: tomorrow 14:58 from Grudziądz · Mon 16 Nov

Next departure 14:58 tomorrow · Grudziądz
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
95%
37/39 runs under 3 min
RT coverage: 39 full · 0 partial · 38 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Malbork, 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 18 Sept Max en route +10 min · last fix heading to Gościszewo +10 min
  • Sun 1 Nov Max en route +8 min · last fix heading to Malbork +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 37
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 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
14:58on time on time
15:01 / 15:02≈ on time ≈ on time
15:05 / 15:06≈ on time ≈ on time
15:11≈ on time ≈ on time
15:17≈ on time ≈ on time
15:20 / 15:21≈ on time ≈ on time
15:26≈ on time ≈ on time
15:32 / 15:33≈ on time ≈ on time
15:39 / 15:40≈ on time ≈ on time
15:44≈ on time ≈ on time
15:50≈ on time ≈ on time
15:54 / 16:01≈ on time ≈ on time
16:05 / 16:06≈ on time ≈ on time
16:13on time 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 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 15 NovMalbork 16:140 min—
Sat 14 NovMalbork 16:140 min—
Fri 13 NovMalbork 16:140 min—
Thu 12 NovMalbork 16:140 min—
Wed 11 NovMalbork 16:140 min—
Tue 10 NovMalbork 16:140 min—
Mon 9 NovMalbork 16:140 min—
Sun 8 NovMalbork 16:140 min—
Sat 7 NovMalbork 16:140 min—
Fri 6 NovMalbork 16:140 min—
Thu 5 NovMalbork 16:140 min—
Wed 4 NovMalbork 16:140 min—
Tue 3 NovMalbork 16:140 min—
Mon 2 NovMalbork 16:140 min—
Sun 1 NovMalbork 16:22+8 min+8 min
Sat 31 OctMalbork 16:150 min—
Fri 30 OctMalbork 16:140 min—
Thu 29 OctMalbork 16:140 min—
Wed 28 OctMalbork 16:140 min—
Tue 27 OctMalbork 16:140 min—
Mon 26 OctMalbork 16:150 min—
Sun 25 OctMalbork 16:14No data—
Sat 24 OctMalbork 16:12No data—
Fri 23 OctMalbork 16:13No data—
Thu 22 OctMalbork 16:12No data—
Wed 21 OctMalbork 16:13No data—
Tue 20 OctMalbork 16:12No data—
Mon 19 OctMalbork 16:13No data—
Sun 18 OctMalbork 16:120 min—
Sat 17 OctMalbork 16:130 min—