AR 50300 Tuchola – Serock

View line AR

Tuchola 03:20 → Serock 04:01 Daily 0 h 41 min · 10 stops Arriva

✓ Today’s run finished

Today, last fix heading to Serock at 04:02 No data

  1. Tuchola03:20
  2. Cekcyn03:31
  3. Wierzchucin Stary03:36
  4. Błądzim03:47
  5. Lipienica03:50
  6. Lubania-Lipiny03:57
  7. Serock04:01

Next service: tomorrow 03:20 from Tuchola · Fri 6 Nov

Next departure 03:20 tomorrow · Tuchola
On-time · 30 days
80%
8/10 runs under 3 min
RT coverage: 10 full · 0 partial · 20 no data
On-time · 90 days
78%
14/18 runs under 3 min
RT coverage: 18 full · 0 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+10min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Wed 23 Sept Max en route +19 min · last fix heading to Stronno +19 min
  • Tue 22 Sept Max en route +18 min · last fix heading to Stronno +18 min
  • Fri 9 Oct Max en route +6 min · last fix heading to Bydgoszcz Główna +6 min
  • Thu 8 Oct Max en route +3 min · last fix heading to Bydgoszcz Główna +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 14
  • 3–10 min 11% · 2
  • 10–30 min 11% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 67% T n=3
  • 50% W n=2
  • 0% T n=1
  • 50% F n=2
  • 100% S n=3
  • 100% S n=3

Stops and timetable

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

Last 90 days, 18 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
03:20on time +9 min
03:23≈ on time ≈ +9 min
03:31≈ on time ≈ +9 min
03:36≈ on time ≈ +9 min
03:40 / 03:41≈ on time ≈ +9 min
03:47≈ on time ≈ +10 min
03:50≈ on time ≈ +10 min
03:53 / 03:54≈ on time ≈ +10 min
03:57≈ on time ≈ +10 min
04:01on time +10 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
Thu 5 NovSerock 04:02No data—
Wed 4 NovSerock 04:02No data—
Tue 3 NovSerock 04:02No data—
Mon 2 NovSerock 04:02No data—
Sun 1 NovSerock 04:02No data—
Sat 31 OctSerock 04:020 min—
Fri 30 OctSerock 04:02No data—
Thu 29 OctSerock 04:02No data—
Wed 28 OctSerock 04:02No data—
Tue 27 OctSerock 04:03No data—
Mon 26 OctSerock 04:02No data—
Sun 25 OctSerock 04:02No data—
Sat 24 OctBydgoszcz Główna 04:42No data—
Fri 23 OctBydgoszcz Główna 04:42No data—
Thu 22 OctBydgoszcz Główna 04:42No data—
Wed 21 OctBydgoszcz Główna 04:42No data—
Tue 20 OctBydgoszcz Główna 04:42No data—
Mon 19 OctBydgoszcz Główna 04:420 min—
Sun 18 OctBydgoszcz Główna 04:420 min—
Sat 17 OctBydgoszcz Główna 04:420 min—
Fri 16 OctBydgoszcz Główna 04:43No data—
Thu 15 OctBydgoszcz Główna 04:42No data—
Wed 14 OctBydgoszcz Główna 04:42No data—
Tue 13 OctBydgoszcz Główna 04:420 min—
Mon 12 OctBydgoszcz Główna 04:45+2 min+2 min
Sun 11 OctBydgoszcz Główna 04:420 min—
Sat 10 OctBydgoszcz Główna 04:42No data—
Fri 9 OctBydgoszcz Główna 04:48+6 min+6 min
Thu 8 OctBydgoszcz Główna 04:46+3 min+3 min
Wed 7 OctBydgoszcz Główna 04:41−1 min—