REG 50700 Chojnice – Tczew

View line REG

Chojnice 03:43 → Tczew 05:16 Daily 1 h 33 min · 19 stops PolRegio

✓ Today’s run finished

Today it reached Tczew at 05:17 +1 min

  1. Chojnice03:43
  2. Rytel Wieś03:58
  3. Łąg04:16
  4. Kaliska04:29
  5. Pinczyn04:41
  6. Szpęgawsk04:58
  7. Tczew05:16

Next service: tomorrow 03:43 from Chojnice · Sun 8 Nov

Next departure 03:43 tomorrow · Chojnice
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 10 full · 0 partial · 20 no data
On-time · 90 days
75%
18/24 runs under 3 min
RT coverage: 24 full · 0 partial · 37 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +1 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Thu 8 Oct Max en route +5 min · last fix heading to Tczew +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Tczew +4 min
  • Mon 5 Oct Max en route +4 min · last fix heading to Tczew +4 min
  • Mon 12 Oct Max en route +3 min · last fix heading to Tczew +3 min
  • Wed 7 Oct Max en route +3 min · last fix heading to Tczew +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 18
  • 3–10 min 25% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 67% T n=3
  • 33% W n=3
  • 67% T n=3
  • 100% F n=4
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 24 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
03:43+1 min +3 min
03:49 / 03:50≈ +1 min ≈ +3 min
03:54 / 03:55≈ +1 min ≈ +3 min
03:58≈ +1 min ≈ +3 min
04:03 / 04:04≈ +1 min ≈ +3 min
04:10 / 04:11≈ +1 min ≈ +3 min
04:16 / 04:17≈ +1 min ≈ +3 min
04:20 / 04:21≈ +1 min ≈ +3 min
04:25≈ +1 min ≈ +3 min
04:29 / 04:30≈ +1 min ≈ +3 min
04:34≈ +1 min ≈ +3 min
04:37 / 04:38≈ +1 min ≈ +3 min
04:41≈ +1 min ≈ +3 min
04:45≈ +2 min ≈ +3 min
04:52 / 04:53≈ +2 min ≈ +3 min
04:58≈ +2 min ≈ +3 min
05:02 / 05:03≈ +2 min ≈ +3 min
05:08 / 05:09≈ +2 min ≈ +3 min
05:16+2 min +4 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 7 NovTczew 05:19+1 min+1 min
Fri 6 NovTczew 05:18+1 min+1 min
Thu 5 NovTczew 05:17No data—
Wed 4 NovTczew 05:17No data—
Tue 3 NovTczew 05:17No data—
Mon 2 NovTczew 05:18+1 min+1 min
Sun 1 NovTczew 05:18No data—
Sat 31 OctTczew 05:19+2 min+2 min
Fri 30 OctTczew 05:17No data—
Thu 29 OctTczew 05:17No data—
Wed 28 OctTczew 05:17No data—
Tue 27 OctTczew 05:18No data—
Mon 26 OctTczew 05:170 min—
Sun 25 OctTczew 05:17No data—
Sat 24 OctTczew 05:17No data—
Fri 23 OctTczew 05:17No data—
Thu 22 OctTczew 05:17No data—
Wed 21 OctTczew 05:17No data—
Tue 20 OctTczew 05:17No data—
Mon 19 OctTczew 05:170 min—
Sun 18 OctTczew 05:170 min—
Sat 17 OctTczew 05:17No data—
Fri 16 OctTczew 05:18No data—
Thu 15 OctTczew 05:17No data—
Wed 14 OctTczew 05:17No data—
Tue 13 OctTczew 05:170 min—
Mon 12 OctTczew 05:21+3 min+3 min
Sun 11 OctTczew 05:17No data—
Sat 10 OctTczew 05:17No data—
Fri 9 OctTczew 05:18+1 min+1 min