REG 55320 Ciechocinek – Aleksandrów Kujawski

View line REG

Ciechocinek 06:32 → Aleksandrów Kujawski 06:40 Daily 0 h 08 min · 3 stops PolRegio

✓ Today’s run finished

Today it reached Aleksandrów Kujawski at 06:40 0 min

  1. Ciechocinek06:32
  2. Odolion06:34
  3. Aleksandrów Kujawski06:40

Next service: tomorrow 06:32 from Ciechocinek · Thu 12 Nov

Next departure 06:32 tomorrow · Ciechocinek
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 6 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 36 full · 0 partial · 38 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

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 100% F n=4
  • 100% S n=5
  • 83% S n=6

Stops and timetable

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

Last 90 days, 36 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
06:32on time on time
06:34 / 06:35≈ on time ≈ on time
06:40on 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
Wed 11 NovAleksandrów Kujawski 06:390 min—
Tue 10 NovAleksandrów Kujawski 06:390 min—
Mon 9 NovAleksandrów Kujawski 06:390 min—
Sun 8 NovAleksandrów Kujawski 06:390 min—
Sat 7 NovAleksandrów Kujawski 06:390 min—
Fri 6 NovAleksandrów Kujawski 06:390 min—
Thu 5 NovAleksandrów Kujawski 06:390 min—
Wed 4 NovAleksandrów Kujawski 06:390 min—
Tue 3 NovAleksandrów Kujawski 06:390 min—
Mon 2 NovAleksandrów Kujawski 06:390 min—
Sun 1 NovAleksandrów Kujawski 06:47+6 min+6 min
Sat 31 OctAleksandrów Kujawski 06:420 min—
Fri 30 OctAleksandrów Kujawski 06:410 min—
Thu 29 OctAleksandrów Kujawski 06:40−1 min—
Wed 28 OctAleksandrów Kujawski 06:410 min—
Tue 27 OctAleksandrów Kujawski 06:410 min—
Mon 26 OctAleksandrów Kujawski 06:410 min—
Sun 25 OctAleksandrów Kujawski 06:41No data—
Sat 24 OctAleksandrów Kujawski 06:41No data—
Fri 23 OctAleksandrów Kujawski 06:41No data—
Thu 22 OctAleksandrów Kujawski 06:41No data—
Wed 21 OctAleksandrów Kujawski 06:41No data—
Tue 20 OctAleksandrów Kujawski 06:41No data—
Mon 19 OctAleksandrów Kujawski 06:410 min—
Sun 18 OctAleksandrów Kujawski 06:420 min—
Sat 17 OctAleksandrów Kujawski 06:410 min—
Fri 16 OctAleksandrów Kujawski 06:410 min—
Thu 15 OctAleksandrów Kujawski 06:410 min—
Wed 14 OctAleksandrów Kujawski 06:410 min—
Tue 13 OctAleksandrów Kujawski 06:410 min—