REG 55350 Ciechocinek – Aleksandrów Kujawski

View line REG

Ciechocinek 21:31 → Aleksandrów Kujawski 21:39 Daily 0 h 08 min · 3 stops PolRegio

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 21:31 from Ciechocinek · Fri 13 Nov

Next departure 21:31 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
93%
38/41 runs under 3 min
RT coverage: 41 full · 0 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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
  • Sat 12 Sept Max en route +5 min · last fix heading to Odolion +5 min
  • Thu 15 Oct Max en route +3 min · last fix heading to Aleksandrów Kujawski +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 38
  • 3–10 min 7% · 3
  • 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
  • 83% T n=6
  • 100% F n=5
  • 83% S n=6
  • 83% S n=6

Stops and timetable

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

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