REG 50708 Chojnice – Tczew

View line REG

Chojnice 06:04 → Tczew 07:40 Mon, Tue, Wed, Thu, Fri 1 h 36 min · 19 stops PolRegio

✓ Today’s run finished

Today it reached Tczew at 07:52 +12 min

  1. Chojnice06:04
  2. Rytel Wieś06:23
  3. Łąg06:41
  4. Kaliska06:54
  5. Pinczyn07:05
  6. Szpęgawsk07:23
  7. Tczew07:40

Next service: tomorrow 06:04 from Chojnice · Tue 17 Nov

Next departure 06:04 tomorrow · Chojnice
On-time · 30 days
0%
0/16 runs under 3 min
RT coverage: 16 full · 0 partial · 4 no data
On-time · 90 days
0%
0/46 runs under 3 min
RT coverage: 46 full · 0 partial · 4 no data
Typical delay
+7min
Median at arrival, 90 days
30 days: +7 min
P90
+13min
9 in 10 runs arrive with less than this
30 days: +15 min

Last 30 days

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

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

Worst days

  • Fri 6 Nov Max en route +18 min · last fix heading to Tczew +18 min
  • Thu 5 Nov Max en route +16 min · last fix heading to Tczew +16 min
  • Wed 4 Nov Max en route +13 min · last fix heading to Tczew +13 min
  • Thu 29 Oct Max en route +13 min · last fix heading to Tczew +13 min
  • Wed 28 Oct Max en route +13 min · last fix heading to Tczew +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 0% · 0
  • 3–10 min 85% · 39
  • 10–30 min 15% · 7
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=11
  • 0% T n=9
  • 0% W n=8
  • 0% T n=9
  • 0% F n=9
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 46 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
06:04+7 min +13 min
06:10≈ +7 min ≈ +13 min
06:15 / 06:20≈ +7 min ≈ +13 min
06:23 / 06:24≈ +7 min ≈ +13 min
06:28 / 06:29≈ +7 min ≈ +13 min
06:35≈ +7 min ≈ +13 min
06:41≈ +7 min ≈ +13 min
06:45≈ +7 min ≈ +13 min
06:49 / 06:50≈ +7 min ≈ +13 min
06:54≈ +7 min ≈ +13 min
06:58≈ +7 min ≈ +13 min
07:01 / 07:02≈ +7 min ≈ +13 min
07:05 / 07:06≈ +7 min ≈ +13 min
07:09 / 07:10≈ +7 min ≈ +13 min
07:17 / 07:18≈ +7 min ≈ +13 min
07:23≈ +7 min ≈ +13 min
07:27 / 07:28≈ +7 min ≈ +13 min
07:33 / 07:34≈ +7 min ≈ +13 min
07:40+7 min +13 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
Mon 16 NovTczew 07:53+12 min+12 min
Fri 13 NovTczew 07:47+6 min+6 min
Thu 12 NovTczew 07:44+5 min+5 min
Tue 10 NovTczew 07:48+7 min+7 min
Mon 9 NovTczew 07:47+6 min+6 min
Fri 6 NovTczew 07:59+18 min+18 min
Thu 5 NovTczew 07:57+16 min+16 min
Wed 4 NovTczew 07:54+13 min+13 min
Tue 3 NovTczew 07:48+7 min+7 min
Mon 2 NovTczew 07:47+6 min+6 min
Fri 30 OctTczew 07:50+9 min+9 min
Thu 29 OctTczew 07:54+13 min+13 min
Wed 28 OctTczew 07:54+13 min+13 min
Tue 27 OctTczew 07:48+7 min+7 min
Mon 26 OctTczew 07:45+4 min+4 min
Fri 23 OctTczew 07:43No data—
Thu 22 OctTczew 07:43No data—
Wed 21 OctTczew 07:43No data—
Tue 20 OctTczew 07:43No data—
Mon 19 OctTczew 07:50+7 min+7 min
Fri 16 OctTczew 07:51+8 min+8 min
Thu 15 OctTczew 07:50+7 min+7 min
Wed 14 OctTczew 07:48+5 min+5 min
Tue 13 OctTczew 07:48+5 min+5 min
Mon 12 OctTczew 07:49+5 min+5 min
Fri 9 OctTczew 07:52+8 min+8 min
Thu 8 OctTczew 07:50+7 min+7 min
Wed 7 OctTczew 07:51+7 min+7 min
Tue 6 OctTczew 07:51+7 min+7 min
Mon 5 OctTczew 07:52+8 min+8 min