REG 50783 Tczew – Chojnice

View line REG

Tczew 15:13 → Chojnice 16:48 Daily 1 h 35 min · 19 stops PolRegio

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 15:13 from Tczew · Wed 18 Nov

Next departure 15:13 today · Tczew
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 19 no data
On-time · 90 days
82%
18/22 runs under 3 min
RT coverage: 22 full · 0 partial · 48 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +1 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

Worst days

  • Wed 30 Sept Max en route +10 min · last fix heading to Krojanty +10 min
  • Tue 22 Sept Max en route +8 min · last fix heading to Krojanty +8 min
  • Mon 21 Sept Max en route +7 min · last fix heading to Chojnice +7 min
  • Sun 27 Sept Max en route +5 min · last fix heading to Chojnice +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 18
  • 3–10 min 14% · 3
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 75% T n=4
  • 50% W n=2
  • 100% T n=1
  • 100% F n=2
  • 100% S n=2
  • 75% S n=4

Stops and timetable

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

Last 90 days, 22 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
15:13on time +5 min
15:18≈ on time ≈ +5 min
15:25≈ on time ≈ +5 min
15:29 / 15:30≈ on time ≈ +5 min
15:36 / 15:37≈ on time ≈ +5 min
15:44≈ on time ≈ +5 min
15:48≈ on time ≈ +5 min
15:51 / 15:52≈ on time ≈ +5 min
15:55≈ on time ≈ +5 min
16:00≈ on time ≈ +5 min
16:04 / 16:05≈ on time ≈ +5 min
16:09≈ on time ≈ +5 min
16:12 / 16:13≈ on time ≈ +5 min
16:19 / 16:20≈ on time ≈ +6 min
16:26≈ on time ≈ +6 min
16:31≈ on time ≈ +6 min
16:35≈ on time ≈ +6 min
16:40≈ on time ≈ +7 min
16:48on time +7 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
Tue 17 NovChojnice 16:490 min—
Mon 16 NovChojnice 16:490 min—
Sun 15 NovChojnice 16:490 min—
Sat 14 NovChojnice 16:490 min—
Fri 13 NovChojnice 16:50+1 min+1 min
Thu 12 NovChojnice 16:49No data—
Wed 11 NovChojnice 16:49No data—
Tue 10 NovChojnice 16:49No data—
Mon 9 NovChojnice 16:490 min—
Sun 8 NovChojnice 16:490 min—
Sat 7 NovChojnice 16:49No data—
Fri 6 NovChojnice 16:49No data—
Thu 5 NovChojnice 16:49No data—
Wed 4 NovChojnice 16:49No data—
Tue 3 NovChojnice 16:50No data—
Mon 2 NovChojnice 16:49+1 min+1 min
Sun 1 NovChojnice 16:49No data—
Sat 31 OctChojnice 16:51+1 min+1 min
Fri 30 OctChojnice 16:49No data—
Thu 29 OctChojnice 16:49No data—
Wed 28 OctChojnice 16:49No data—
Tue 27 OctChojnice 16:49No data—
Mon 26 OctChojnice 16:500 min—
Sun 25 OctChojnice 16:49No data—
Sat 24 OctChojnice 16:51No data—
Fri 23 OctChojnice 16:52No data—
Thu 22 OctChojnice 16:51No data—
Wed 21 OctChojnice 16:52No data—
Tue 20 OctChojnice 16:51No data—
Mon 19 OctChojnice 16:51No data—