AR 50251 Tuchola – Chojnice

View line AR

Tuchola 04:55 → Chojnice 05:21 Mon, Tue, Wed, Thu, Fri, Sat 0 h 26 min · 6 stops Arriva

It has not run yet today

Last recorded run: Wednesday 18 November No data

Next service: today 04:55 from Tuchola · Thu 19 Nov

Next departure 04:55 today · Tuchola
On-time · 30 days
100%
6/6 runs under 3 min
RT coverage: 6 full · 0 partial · 19 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 53 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 14
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=2
  • 100% W n=1
  • 100% T n=1
  • 100% F n=2
  • 100% S n=1
  • — S n=0

Stops and timetable

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

Last 90 days, 14 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
04:55on time on time
05:00 / 05:01≈ on time ≈ on time
05:04 / 05:05≈ on time ≈ on time
05:08 / 05:09≈ on time ≈ on time
05:12≈ on time ≈ on time
05:21on time on time

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
Wed 18 NovChojnice 05:22No data—
Tue 17 NovChojnice 05:22No data—
Mon 16 NovChojnice 05:220 min—
Sat 14 NovChojnice 05:220 min—
Fri 13 NovChojnice 05:220 min—
Thu 12 NovChojnice 05:22No data—
Tue 10 NovChojnice 05:23No data—
Mon 9 NovChojnice 05:220 min—
Sat 7 NovChojnice 05:23No data—
Fri 6 NovChojnice 05:23No data—
Thu 5 NovChojnice 05:22No data—
Wed 4 NovChojnice 05:22No data—
Tue 3 NovChojnice 05:22No data—
Mon 2 NovChojnice 05:220 min—
Sun 1 NovChojnice 05:23No data—
Sat 31 OctChojnice 05:22No data—
Fri 30 OctChojnice 05:22No data—
Thu 29 OctChojnice 05:22No data—
Wed 28 OctChojnice 05:22No data—
Tue 27 OctChojnice 05:23No data—
Mon 26 OctChojnice 05:220 min—
Sat 24 OctChojnice 05:25No data—
Fri 23 OctChojnice 05:25No data—
Thu 22 OctChojnice 05:25No data—
Wed 21 OctChojnice 05:25No data—
Tue 20 OctChojnice 05:25No data—
Mon 19 OctChojnice 05:260 min—
Sat 17 OctChojnice 05:25No data—
Fri 16 OctChojnice 05:26No data—
Thu 15 OctChojnice 05:25No data—