REG 50722 Chojnice – Tczew

View line REG

Chojnice 20:50 → Tczew 22:25 Daily 1 h 35 min · 19 stops PolRegio

✓ Today’s run finished

Today it reached Tczew at 22:25 0 min

  1. Chojnice20:50
  2. Rytel Wieś21:05
  3. Łąg21:24
  4. Kaliska21:38
  5. Pinczyn21:49
  6. Szpęgawsk22:07
  7. Tczew22:25

Next service: tomorrow 20:50 from Chojnice · Mon 16 Nov

Next departure 20:50 tomorrow · Chojnice
On-time · 30 days
86%
19/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
91%
48/53 runs under 3 min
RT coverage: 53 full · 0 partial · 25 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sun 1 Nov Max en route +7 min · last fix heading to Tczew +6 min
  • Fri 16 Oct Max en route +4 min · last fix heading to Tczew +4 min
  • Thu 10 Sept Max en route +4 min · last fix heading to Tczew +4 min
  • Tue 10 Nov Max en route +3 min · last fix heading to Tczew +3 min
  • Tue 27 Oct Max en route +3 min · last fix heading to Tczew +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 89% · 47
  • 3–10 min 9% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 78% T n=9
  • 100% W n=6
  • 88% T n=8
  • 86% F n=7
  • 100% S n=7
  • 86% S n=7

Stops and timetable

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

Last 90 days, 53 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
20:50on time +2 min
20:56 / 20:57≈ on time ≈ +2 min
21:01 / 21:02≈ on time ≈ +2 min
21:05≈ on time ≈ +2 min
21:11≈ on time ≈ +2 min
21:18≈ on time ≈ +2 min
21:24≈ on time ≈ +2 min
21:28 / 21:29≈ on time ≈ +2 min
21:33≈ on time ≈ +2 min
21:38≈ on time ≈ +2 min
21:42 / 21:43≈ on time ≈ +2 min
21:46≈ on time ≈ +2 min
21:49 / 21:50≈ on time ≈ +2 min
21:53 / 21:54≈ on time ≈ +2 min
22:01 / 22:02≈ on time ≈ +2 min
22:07≈ on time ≈ +2 min
22:12≈ on time ≈ +2 min
22:18≈ on time ≈ +2 min
22:25on time +2 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 NovTczew 22:240 min—
Sat 14 NovTczew 22:240 min—
Fri 13 NovTczew 22:24−1 min—
Thu 12 NovTczew 22:24−1 min—
Wed 11 NovTczew 22:240 min—
Tue 10 NovTczew 22:29+3 min+3 min
Mon 9 NovTczew 22:240 min—
Sun 8 NovTczew 22:240 min—
Sat 7 NovTczew 22:240 min—
Fri 6 NovTczew 22:240 min—
Thu 5 NovTczew 22:24No data—
Wed 4 NovTczew 22:240 min—
Tue 3 NovTczew 22:24−1 min—
Mon 2 NovTczew 22:24−1 min—
Sun 1 NovTczew 22:32+6 min+7 min
Sat 31 OctTczew 22:29+2 min+2 min
Fri 30 OctTczew 22:28+2 min+2 min
Thu 29 OctTczew 22:28+2 min+2 min
Wed 28 OctTczew 22:27+1 min+1 min
Tue 27 OctTczew 22:29+3 min+3 min
Mon 26 OctTczew 22:29+2 min+2 min
Sun 25 OctTczew 22:26No data—
Sat 24 OctTczew 22:37No data—
Fri 23 OctTczew 22:37No data—
Thu 22 OctTczew 22:36No data—
Wed 21 OctTczew 22:36No data—
Tue 20 OctTczew 22:36No data—
Mon 19 OctTczew 22:36No data—
Sun 18 OctTczew 22:35−1 min—
Sat 17 OctTczew 22:35−1 min—