REG 55345 Aleksandrów Kujawski – Ciechocinek

View line REG

Aleksandrów Kujawski 19:05 → Ciechocinek 19:13 Daily 0 h 08 min · 3 stops PolRegio

✓ Today’s run finished

Today it reached Ciechocinek at 19:20 +7 min

  1. Aleksandrów Kujawski19:05
  2. Odolion19:08
  3. Ciechocinek19:13

Next service: tomorrow 19:05 from Aleksandrów Kujawski · Tue 17 Nov

Next departure 19:05 tomorrow · Aleksandrów Kujawski
On-time · 30 days
48%
11/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
38%
18/47 runs under 3 min
RT coverage: 47 full · 0 partial · 32 no data
Typical delay
+4min
Median at arrival, 90 days
30 days: +3 min
P90
+13min
9 in 10 runs arrive with less than this
30 days: +9 min

Last 30 days

Arrival delay at Ciechocinek, 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 +60 min · last fix heading to Ciechocinek +60 min
  • Sun 6 Sept Max en route +20 min · last fix heading to Aleksandrów Kujawski +20 min
  • Sun 8 Nov Max en route +13 min · last fix heading to Ciechocinek +13 min
  • Wed 7 Oct Max en route +13 min · last fix heading to Ciechocinek +13 min
  • Tue 6 Oct Max en route +13 min · last fix heading to Ciechocinek +13 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 38% · 18
  • 3–10 min 40% · 19
  • 10–30 min 19% · 9
  • 30+ min 2% · 1

On-time by weekday

  • 0% M n=7
  • 17% T n=6
  • 43% W n=7
  • 83% T n=6
  • 71% F n=7
  • 43% S n=7
  • 14% S n=7

Stops and timetable

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

Last 90 days, 47 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
19:05+4 min +13 min
19:08 / 19:09≈ +4 min ≈ +13 min
19:13+4 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 NovCiechocinek 19:19+7 min+7 min
Sun 15 NovCiechocinek 19:19+6 min+6 min
Sat 14 NovCiechocinek 19:18+4 min+4 min
Fri 13 NovCiechocinek 19:15+1 min+1 min
Thu 12 NovCiechocinek 19:14+1 min+1 min
Wed 11 NovCiechocinek 19:17+3 min+3 min
Tue 10 NovCiechocinek 19:23+9 min+9 min
Mon 9 NovCiechocinek 19:18+4 min+4 min
Sun 8 NovCiechocinek 19:27+13 min+13 min
Sat 7 NovCiechocinek 19:17+3 min+3 min
Fri 6 NovCiechocinek 19:14+2 min+2 min
Thu 5 NovCiechocinek 19:140 min—
Wed 4 NovCiechocinek 19:140 min—
Tue 3 NovCiechocinek 19:150 min—
Mon 2 NovCiechocinek 20:14+60 min+60 min
Sun 1 NovCiechocinek 19:19+5 min+5 min
Sat 31 OctCiechocinek 19:150 min—
Fri 30 OctCiechocinek 19:140 min—
Thu 29 OctCiechocinek 19:140 min—
Wed 28 OctCiechocinek 19:140 min—
Tue 27 OctCiechocinek 19:18+4 min+4 min
Mon 26 OctCiechocinek 19:20+5 min+5 min
Sun 25 OctCiechocinek 19:14No data—
Sat 24 OctCiechocinek 19:15No data—
Fri 23 OctCiechocinek 19:15No data—
Thu 22 OctCiechocinek 19:14No data—
Wed 21 OctCiechocinek 19:14No data—
Tue 20 OctCiechocinek 19:14No data—
Mon 19 OctCiechocinek 19:14No data—
Sun 18 OctCiechocinek 19:16+2 min+2 min