AR 50410 Laskowice Pomorskie – Grudziądz

View line AR

Laskowice Pomorskie 12:06 → Grudziądz 12:31 Daily 0 h 25 min · 8 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 12:06 from Laskowice Pomorskie · Sat 7 Nov

Next departure 12:06 today · Laskowice Pomorskie
On-time · 30 days
77%
17/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
80%
28/35 runs under 3 min
RT coverage: 35 full · 0 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +10 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

  • Tue 20 Oct Max en route +31 min · last fix heading to Grupa +31 min
  • Sun 18 Oct Max en route +10 min · last fix heading to Grudziądz +10 min
  • Sat 17 Oct Max en route +10 min · last fix heading to Grudziądz +10 min
  • Wed 4 Nov Max en route +7 min · last fix heading to Grudziądz +7 min
  • Thu 15 Oct Max en route +5 min · last fix heading to Grudziądz +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 28
  • 3–10 min 11% · 4
  • 10–30 min 6% · 2
  • 30+ min 3% · 1

On-time by weekday

  • 75% M n=4
  • 86% T n=7
  • 86% W n=7
  • 80% T n=5
  • 80% F n=5
  • 67% S n=3
  • 75% S n=4

Stops and timetable

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

Last 90 days, 35 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
12:06on time +3 min
12:09≈ on time ≈ +3 min
12:13≈ on time ≈ +4 min
12:17 / 12:19≈ on time ≈ +5 min
12:22 / 12:23≈ on time ≈ +6 min
12:25≈ on time ≈ +6 min
12:28 / 12:29≈ on time ≈ +6 min
12:31on time +6 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
Fri 6 NovGrudziądz 12:320 min—
Thu 5 NovGrudziądz 12:320 min—
Wed 4 NovGrudziądz 12:39+7 min+7 min
Tue 3 NovGrudziądz 12:330 min—
Mon 2 NovGrudziądz 12:32No data—
Sun 1 NovGrudziądz 12:35+2 min+2 min
Sat 31 OctGrudziądz 12:320 min—
Fri 30 OctGrudziądz 12:320 min—
Thu 29 OctGrudziądz 12:320 min—
Wed 28 OctGrudziądz 12:320 min—
Tue 27 OctGrudziądz 12:320 min—
Mon 26 OctGrudziądz 12:320 min+1 min
Sun 25 OctGrudziądz 12:32No data—
Sat 24 OctGrudziądz 12:41No data—
Fri 23 OctGrudziądz 12:28No data—
Thu 22 OctGrudziądz 12:28No data—
Wed 21 OctGrudziądz 12:28No data—
Tue 20 OctGrupa 12:45+31 min+31 min
Mon 19 OctGrudziądz 12:28No data—
Sun 18 OctGrudziądz 12:51+10 min+10 min
Sat 17 OctGrudziądz 12:51+10 min+10 min
Fri 16 OctGrudziądz 12:280 min—
Thu 15 OctGrudziądz 12:33+5 min+5 min
Wed 14 OctGrudziądz 12:290 min—
Tue 13 OctGrudziądz 12:280 min—
Mon 12 OctGrudziądz 12:280 min—
Sun 11 OctGrudziądz 12:410 min—
Sat 10 OctGrudziądz 12:420 min—
Fri 9 OctGrudziądz 12:280 min—
Thu 8 OctGrudziądz 12:280 min—