REG 55380 Ciechocinek – Aleksandrów Kujawski

View line REG

Ciechocinek 15:41 → Aleksandrów Kujawski 15:49 Mon, Tue, Wed, Thu, Fri 0 h 08 min · 3 stops PolRegio

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 15:41 from Ciechocinek · Fri 20 Nov

Next departure 15:41 today · Ciechocinek
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 20 full · 0 partial · 2 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Aleksandrów Kujawski, 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 +6 min · last fix heading to Aleksandrów Kujawski +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=5
  • — S n=0
  • 0% S n=1

Stops and timetable

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

Last 90 days, 30 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
15:41on time on time
15:43 / 15:44≈ on time ≈ on time
15:49on time on time

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
Thu 19 NovAleksandrów Kujawski 15:490 min—
Wed 18 NovAleksandrów Kujawski 15:490 min—
Tue 17 NovAleksandrów Kujawski 15:490 min—
Mon 16 NovAleksandrów Kujawski 15:490 min—
Fri 13 NovAleksandrów Kujawski 15:490 min—
Thu 12 NovAleksandrów Kujawski 15:490 min—
Wed 11 NovAleksandrów Kujawski 15:490 min—
Tue 10 NovAleksandrów Kujawski 15:49−1 min—
Mon 9 NovAleksandrów Kujawski 15:490 min—
Fri 6 NovAleksandrów Kujawski 15:490 min—
Thu 5 NovAleksandrów Kujawski 15:490 min—
Wed 4 NovAleksandrów Kujawski 15:490 min—
Tue 3 NovAleksandrów Kujawski 15:490 min—
Mon 2 NovAleksandrów Kujawski 15:490 min—
Sun 1 NovAleksandrów Kujawski 15:56+6 min+6 min
Fri 30 OctAleksandrów Kujawski 15:500 min—
Thu 29 OctAleksandrów Kujawski 15:500 min—
Wed 28 OctAleksandrów Kujawski 15:500 min—
Tue 27 OctAleksandrów Kujawski 15:500 min—
Mon 26 OctAleksandrów Kujawski 15:510 min—
Fri 23 OctAleksandrów Kujawski 15:51No data—
Thu 22 OctAleksandrów Kujawski 15:50No data—
Wed 21 OctAleksandrów Kujawski 15:51No data—
Tue 20 OctAleksandrów Kujawski 15:50No data—
Mon 19 OctAleksandrów Kujawski 15:51No data—
Fri 16 OctAleksandrów Kujawski 15:500 min—
Thu 15 OctAleksandrów Kujawski 15:500 min—
Wed 14 OctAleksandrów Kujawski 15:500 min—
Tue 13 OctAleksandrów Kujawski 15:510 min—
Mon 12 OctAleksandrów Kujawski 15:500 min—