AR 50263 Serock – Tuchola

View line AR

Serock 11:38 → Tuchola 12:26 Mon, Tue, Wed, Thu, Fri 0 h 48 min · 10 stops Arriva

It has not run yet today

Last recorded run: Friday 13 November +5 min

Next service: today 11:38 from Serock · Mon 16 Nov

Next departure 11:38 today · Serock
On-time · 30 days
75%
6/8 runs under 3 min
RT coverage: 8 full · 0 partial · 12 no data
On-time · 90 days
55%
11/20 runs under 3 min
RT coverage: 20 full · 0 partial · 29 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 min

Last 30 days

Arrival delay at Tuchola, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Wed 23 Sept Max en route +6 min · last fix heading to Tuchola Rudzki Most +6 min
  • Fri 13 Nov Max en route +5 min · last fix heading to Tuchola +5 min
  • Mon 12 Oct Max en route +5 min · last fix heading to Tuchola +5 min
  • Mon 28 Sept Max en route +5 min · last fix heading to Tuchola Rudzki Most +5 min
  • Fri 25 Sept Max en route +5 min · last fix heading to Tuchola Rudzki Most +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 55% · 11
  • 3–10 min 45% · 9
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 57% M n=7
  • 75% T n=4
  • 67% W n=3
  • 67% T n=3
  • 0% F n=2
  • — S n=0
  • 0% S n=1

Stops and timetable

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

Last 90 days, 20 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:38on time +5 min
11:40 / 11:41≈ on time ≈ +5 min
11:44≈ on time ≈ +5 min
11:47 / 11:48≈ on time ≈ +5 min
11:51≈ on time ≈ +5 min
11:58 / 12:04≈ on time ≈ +5 min
12:07 / 12:08≈ +1 min ≈ +5 min
12:12 / 12:13≈ +1 min ≈ +5 min
12:21 / 12:22≈ +1 min ≈ +5 min
12:26+1 min +5 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 13 NovTuchola 12:32+5 min+5 min
Thu 12 NovTuchola 12:27No data—
Tue 10 NovTuchola 12:27No data—
Mon 9 NovTuchola 12:29+1 min+5 min
Fri 6 NovTuchola 12:27No data—
Thu 5 NovTuchola 12:27No data—
Wed 4 NovTuchola 12:27No data—
Tue 3 NovTuchola 12:27No data—
Mon 2 NovTuchola 12:270 min—
Sun 1 NovTuchola 12:32+4 min+4 min
Fri 30 OctTuchola 12:27No data—
Thu 29 OctTuchola 12:270 min—
Wed 28 OctTuchola 12:270 min—
Tue 27 OctTuchola 12:270 min—
Mon 26 OctTuchola 12:280 min—
Fri 23 OctTuchola 12:47No data—
Thu 22 OctTuchola 12:47No data—
Wed 21 OctTuchola 12:47No data—
Tue 20 OctTuchola 12:48No data—
Mon 19 OctTuchola 12:47No data—
Fri 16 OctTuchola 12:47No data—
Thu 15 OctTuchola 12:47No data—
Wed 14 OctTuchola 12:48No data—
Tue 13 OctTuchola 12:48+1 min+1 min
Mon 12 OctTuchola 12:52+5 min+5 min
Fri 9 OctTuchola 12:47No data—
Thu 8 OctTuchola 12:470 min—
Wed 7 OctTuchola 12:470 min—
Tue 6 OctTuchola 12:470 min—
Mon 5 OctTuchola 12:470 min—