A delayed train is stressful enough on its own — add a connecting train waiting at the other end, and it turns into a math problem you're solving with incomplete information.
Start with the actual delay, not the scheduled arrival
Your ticket's scheduled arrival time is irrelevant once your train is running late — what matters is the current expected arrival based on live status, which updates as the journey progresses. Basing your connection math on the original timetable instead of live status is the most common way people miscalculate.
Build in a real buffer, not a hopeful one
Delays reported mid-journey can grow or shrink by the time the train actually arrives, especially over longer remaining distances. Treat the current expected arrival as your best estimate, and give yourself more buffer than the bare minimum before assuming you'll make a tight connection.
When to consider a backup plan
If your connection window is already tight on the original schedule, a delay of even 15–20 minutes can be the difference. It's worth checking live status again as you get closer, rather than deciding once early in the journey and not revisiting it.
Where CoSeat fits in
Check live train status on CoSeat throughout your journey — not just once — to see updated delay and arrival estimates as they change, so your connection decisions are based on where the train actually is, not where it was scheduled to be.