REG 55328 Ciechocinek – Aleksandrów Kujawski

View line REG

Ciechocinek 18:45 → Aleksandrów Kujawski 18:53 Daily 0 h 08 min · 3 stops PolRegio

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 18:45 from Ciechocinek · Sun 15 Nov

Next departure 18:45 today · Ciechocinek
On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 22 full · 0 partial · 7 no data
On-time · 90 days
94%
33/35 runs under 3 min
RT coverage: 35 full · 0 partial · 42 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

  • Mon 2 Nov Max en route +66 min · last fix heading to Aleksandrów Kujawski +66 min
  • Sun 1 Nov Max en route +6 min · last fix heading to Aleksandrów Kujawski +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 33
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 35 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
18:45on time on time
18:47 / 18:48≈ on time ≈ on time
18:53on 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
Sat 14 NovAleksandrów Kujawski 18:540 min—
Fri 13 NovAleksandrów Kujawski 18:550 min—
Thu 12 NovAleksandrów Kujawski 18:540 min—
Wed 11 NovAleksandrów Kujawski 18:540 min—
Tue 10 NovAleksandrów Kujawski 18:540 min—
Mon 9 NovAleksandrów Kujawski 18:540 min—
Sun 8 NovAleksandrów Kujawski 18:540 min—
Sat 7 NovAleksandrów Kujawski 18:540 min—
Fri 6 NovAleksandrów Kujawski 18:550 min—
Thu 5 NovAleksandrów Kujawski 18:540 min—
Wed 4 NovAleksandrów Kujawski 18:540 min—
Tue 3 NovAleksandrów Kujawski 18:550 min—
Mon 2 NovAleksandrów Kujawski 19:59+66 min+66 min
Sun 1 NovAleksandrów Kujawski 18:59+6 min+6 min
Sat 31 OctAleksandrów Kujawski 18:550 min—
Fri 30 OctAleksandrów Kujawski 18:540 min—
Thu 29 OctAleksandrów Kujawski 18:540 min—
Wed 28 OctAleksandrów Kujawski 18:540 min—
Tue 27 OctAleksandrów Kujawski 18:540 min—
Mon 26 OctAleksandrów Kujawski 18:550 min—
Sun 25 OctAleksandrów Kujawski 18:54No data—
Sat 24 OctAleksandrów Kujawski 18:54No data—
Fri 23 OctAleksandrów Kujawski 18:55No data—
Thu 22 OctAleksandrów Kujawski 18:55No data—
Wed 21 OctAleksandrów Kujawski 18:54No data—
Tue 20 OctAleksandrów Kujawski 18:54No data—
Mon 19 OctAleksandrów Kujawski 18:54No data—
Sun 18 OctAleksandrów Kujawski 18:540 min—
Sat 17 OctAleksandrów Kujawski 18:540 min—
Fri 16 OctAleksandrów Kujawski 18:540 min—