AR 50330 Tuchola – Serock

View line AR

Tuchola 17:46 → Serock 18:34 Daily 0 h 48 min · 10 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 17:46 from Tuchola · Sat 7 Nov

Next departure 17:46 today · Tuchola
On-time · 30 days
44%
4/9 runs under 3 min
RT coverage: 9 full · 0 partial · 20 no data
On-time · 90 days
63%
10/16 runs under 3 min
RT coverage: 16 full · 0 partial · 47 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +4 min
P90
+9min
9 in 10 runs arrive with less than this
30 days: +19 min

Last 30 days

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

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

Worst days

  • Mon 2 Nov Max en route +49 min · last fix heading to Serock +49 min
  • Sun 1 Nov Max en route +12 min · last fix heading to Serock +12 min
  • Thu 29 Oct Max en route +7 min · last fix heading to Serock +7 min
  • Mon 12 Oct Max en route +6 min · last fix heading to Bydgoszcz Główna +6 min
  • Sun 18 Oct Max en route +4 min · last fix heading to Bydgoszcz Główna +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 63% · 10
  • 3–10 min 25% · 4
  • 10–30 min 6% · 1
  • 30+ min 6% · 1

On-time by weekday

  • 60% M n=5
  • 100% T n=4
  • 100% W n=2
  • 50% T n=2
  • 0% F n=1
  • — S n=0
  • 0% S n=2

Stops and timetable

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

Last 90 days, 16 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
17:46+1 min +5 min
17:49≈ +1 min ≈ +6 min
17:57≈ +1 min ≈ +6 min
18:02≈ +1 min ≈ +7 min
18:07 / 18:14≈ +1 min ≈ +7 min
18:20≈ +1 min ≈ +8 min
18:23≈ +1 min ≈ +8 min
18:26 / 18:27≈ +1 min ≈ +9 min
18:30≈ +1 min ≈ +9 min
18:34+1 min +9 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 NovSerock 18:34No data—
Thu 5 NovSerock 18:34No data—
Wed 4 NovSerock 18:34No data—
Tue 3 NovSerock 18:34No data—
Mon 2 NovSerock 19:24+49 min+49 min
Sun 1 NovSerock 18:47+12 min+12 min
Sat 31 OctSerock 17:39No data—
Fri 30 OctSerock 18:35No data—
Thu 29 OctSerock 18:42+7 min+7 min
Wed 28 OctSerock 18:36+1 min+1 min
Tue 27 OctSerock 18:36+1 min+1 min
Mon 26 OctSerock 18:37+1 min+1 min
Sun 25 OctSerock 17:38No data—
Sat 24 OctBydgoszcz Główna 18:56No data—
Fri 23 OctBydgoszcz Główna 18:57No data—
Thu 22 OctBydgoszcz Główna 18:57No data—
Wed 21 OctBydgoszcz Główna 18:56No data—
Tue 20 OctBydgoszcz Główna 18:56No data—
Mon 19 OctBydgoszcz Główna 18:56No data—
Sun 18 OctBydgoszcz Główna 19:00+4 min+4 min
Sat 17 OctBydgoszcz Główna 18:56No data—
Fri 16 OctBydgoszcz Główna 18:56No data—
Thu 15 OctBydgoszcz Główna 18:56No data—
Wed 14 OctBydgoszcz Główna 18:56No data—
Tue 13 OctBydgoszcz Główna 18:58+2 min+2 min
Mon 12 OctBydgoszcz Główna 19:02+6 min+6 min
Sun 11 OctBydgoszcz Główna 18:56No data—
Sat 10 OctBydgoszcz Główna 18:57No data—
Fri 9 OctBydgoszcz Główna 18:56No data—
Thu 8 OctBydgoszcz Główna 18:57+1 min+1 min