AR 50300 Tuchola → Serock

View line AR

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

AR 50300 Tuchola–Serock: final delay under 3 min on 8 of its 8 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 18:37 (GMT+1).

✓ Today’s run finished

Today it reached Serock at 04:01 0 min

  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 · Sun 22 Nov

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

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

  • Early 0% · 0
  • On time 84% · 21
  • 3–10 min 8% · 2
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 67% T n=3
  • 50% W n=2
  • 50% T n=2
  • 75% F n=4
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 25 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 +5 min
03:23≈ on time ≈ +5 min
03:31≈ on time ≈ +5 min
03:36≈ on time ≈ +5 min
03:40 / 03:41≈ on time ≈ +5 min
03:47≈ on time ≈ +5 min
03:50≈ on time ≈ +5 min
03:53 / 03:54≈ on time ≈ +5 min
03:57≈ on time ≈ +5 min
04:01on time +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
Sat 21 NovSerock 04:020 min—
Fri 20 NovSerock 04:020 min—
Thu 19 NovSerock 04:020 min—
Wed 18 NovSerock 04:02No data—
Tue 17 NovSerock 04:02No data—
Mon 16 NovSerock 04:020 min—
Sun 15 NovSerock 04:030 min—
Sat 14 NovSerock 04:030 min—
Fri 13 NovSerock 04:020 min—
Thu 12 NovSerock 04:02No data—
Wed 11 NovSerock 04:02No data—
Tue 10 NovSerock 04:03No data—
Mon 9 NovSerock 04:02No data—
Sun 8 NovSerock 04:02No data—
Sat 7 NovSerock 04:02No data—
Fri 6 NovSerock 04:02No data—
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—