AR 50334 Chojnice → Tuchola

View line AR

Chojnice 22:30 → Tuchola 22:56 Daily 0 h 26 min · 6 stops Arriva

AR 50334 Chojnice–Tuchola: final delay under 3 min on 10 of its 15 runs with data in the last 30 days (67%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 06:15 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 22:30 from Chojnice · Sun 22 Nov

Next departure 22:30 today · Chojnice
On-time · 30 days
67%
10/15 runs under 3 min
RT coverage: 15 full · 0 partial · 14 no data
On-time · 90 days
80%
20/25 runs under 3 min
RT coverage: 25 full · 0 partial · 54 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +10 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

  • Mon 9 Nov Max en route +14 min · last fix heading to Tuchola +14 min
  • Fri 20 Nov Max en route +12 min · last fix heading to Tuchola +12 min
  • Thu 19 Nov Max en route +6 min · last fix heading to Tuchola +6 min
  • Sun 15 Nov Max en route +6 min · last fix heading to Tuchola +6 min
  • Mon 2 Nov Max en route +5 min · last fix heading to Tuchola +5 min

Distribution · 90 days

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

  • Early 4% · 1
  • On time 76% · 19
  • 3–10 min 12% · 3
  • 10–30 min 8% · 2
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
22:30on time +4 min
22:35 / 22:36≈ on time ≈ +5 min
22:40 / 22:41≈ on time ≈ +5 min
22:44≈ on time ≈ +5 min
22:48≈ on time ≈ +6 min
22:56on time +6 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 NovTuchola 22:570 min—
Fri 20 NovTuchola 23:09+12 min+12 min
Thu 19 NovTuchola 23:03+6 min+6 min
Wed 18 NovTuchola 22:57No data—
Tue 17 NovTuchola 22:58No data—
Mon 16 NovTuchola 22:570 min—
Sun 15 NovTuchola 23:03+6 min+6 min
Sat 14 NovTuchola 22:570 min—
Fri 13 NovTuchola 22:580 min—
Thu 12 NovTuchola 22:57No data—
Wed 11 NovTuchola 22:58No data—
Tue 10 NovTuchola 22:57No data—
Mon 9 NovTuchola 23:09+14 min+14 min
Sun 8 NovTuchola 22:570 min—
Sat 7 NovTuchola 22:570 min+2 min
Fri 6 NovTuchola 22:57No data—
Thu 5 NovTuchola 22:57No data—
Wed 4 NovTuchola 22:57No data—
Tue 3 NovTuchola 22:58No data—
Mon 2 NovTuchola 23:02+5 min+5 min
Sun 1 NovTuchola 22:57No data—
Sat 31 OctTuchola 22:58No data—
Fri 30 OctTuchola 22:57No data—
Thu 29 OctTuchola 22:570 min—
Wed 28 OctTuchola 22:570 min—
Tue 27 OctTuchola 22:570 min—
Mon 26 OctTuchola 22:580 min—
Sun 25 OctTuchola 22:57No data—
Sat 24 OctTuchola 22:44No data—
Fri 23 OctTuchola 22:44No data—