REG 50787 Tczew – Chojnice

View line REG

Tczew 16:37 → Chojnice 18:08 Daily 1 h 31 min · 19 stops PolRegio

✓ Today’s run finished

Today it reached Chojnice at 18:14 +6 min

  1. Tczew16:37
  2. Szpęgawsk16:52
  3. Pinczyn17:10
  4. Kaliska17:21
  5. Łąg17:33
  6. Rytel Wieś17:52
  7. Chojnice18:08

Next service: tomorrow 16:37 from Tczew · Mon 16 Nov

Next departure 16:37 tomorrow · Tczew
On-time · 30 days
11%
1/9 runs under 3 min
RT coverage: 9 full · 0 partial · 21 no data
On-time · 90 days
42%
8/19 runs under 3 min
RT coverage: 19 full · 0 partial · 57 no data
Typical delay
+4min
Median at arrival, 90 days
30 days: +6 min
P90
+8min
9 in 10 runs arrive with less than this
30 days: +9 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

  • Mon 2 Nov Max en route +19 min · last fix heading to Chojnice +19 min
  • Mon 31 Aug Max en route +10 min · last fix heading to Krojanty +10 min
  • Mon 9 Nov Max en route +7 min · last fix heading to Chojnice +7 min
  • Sun 15 Nov Max en route +6 min · last fix heading to Chojnice +6 min
  • Sat 14 Nov Max en route +6 min · last fix heading to Chojnice +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 42% · 8
  • 3–10 min 47% · 9
  • 10–30 min 11% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 17% M n=6
  • 100% T n=3
  • 100% W n=1
  • 100% T n=1
  • 0% F n=2
  • 33% S n=3
  • 33% S n=3

Stops and timetable

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

Last 90 days, 19 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
16:37on time +6 min
16:42≈ on time ≈ +6 min
16:48 / 16:49≈ +1 min ≈ +6 min
16:52 / 16:53≈ +1 min ≈ +6 min
16:58 / 16:59≈ +1 min ≈ +6 min
17:06 / 17:07≈ +1 min ≈ +6 min
17:10≈ +1 min ≈ +6 min
17:13 / 17:14≈ +2 min ≈ +6 min
17:16 / 17:17≈ +2 min ≈ +6 min
17:21≈ +2 min ≈ +7 min
17:25≈ +2 min ≈ +7 min
17:29 / 17:30≈ +2 min ≈ +7 min
17:33≈ +2 min ≈ +7 min
17:39 / 17:41≈ +3 min ≈ +7 min
17:46 / 17:47≈ +3 min ≈ +7 min
17:52≈ +3 min ≈ +7 min
17:55 / 17:56≈ +3 min ≈ +7 min
18:00≈ +4 min ≈ +7 min
18:08+4 min +8 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
Sun 15 NovChojnice 18:14+6 min+6 min
Sat 14 NovChojnice 18:14+6 min+6 min
Fri 13 NovChojnice 18:15+6 min+6 min
Thu 12 NovChojnice 18:09No data—
Wed 11 NovChojnice 18:09No data—
Tue 10 NovChojnice 18:09No data—
Mon 9 NovChojnice 18:14+7 min+7 min
Sun 8 NovChojnice 18:14+6 min+6 min
Sat 7 NovChojnice 18:09No data—
Fri 6 NovChojnice 18:10No data—
Thu 5 NovChojnice 18:09No data—
Wed 4 NovChojnice 18:09No data—
Tue 3 NovChojnice 18:09No data—
Mon 2 NovChojnice 18:28+19 min+19 min
Sun 1 NovChojnice 18:09No data—
Sat 31 OctChojnice 18:15+5 min+5 min
Fri 30 OctChojnice 18:09No data—
Thu 29 OctChojnice 18:09No data—
Wed 28 OctChojnice 18:09No data—
Tue 27 OctChojnice 18:09No data—
Mon 26 OctChojnice 18:14+4 min+4 min
Sun 25 OctChojnice 18:09No data—
Sat 24 OctChojnice 18:11No data—
Fri 23 OctChojnice 18:12No data—
Thu 22 OctChojnice 18:12No data—
Wed 21 OctChojnice 18:11No data—
Tue 20 OctChojnice 18:11No data—
Mon 19 OctChojnice 18:11No data—
Sun 18 OctChojnice 18:120 min—
Sat 17 OctChojnice 18:11No data—