Your train is late, FYI.

Send this

To:      ICE145@late.fyi
Subject: From: Amsterdam Centraal, To: Berlin Ostbahnhof, Trip: Germany

Trip: is optional — group several trains under one tag to stop them all at once.

Reply (in seconds)

From: latefyi <ICE145@late.fyi>
Subject: Tracking ICE 145 [Germany] — Amsterdam Centraal → Berlin Ostbahnhof — Monday, 2026-05-04

Tracking ICE 145, Amsterdam Centraal → Berlin Ostbahnhof.
Trip: Germany
Scheduled: dep Monday, 2026-05-04 10:00 Amsterdam Centraal, arr Monday, 2026-05-04 16:02 Berlin Ostbahnhof.
Departure platform: TBC    Arrival platform: TBC
Status: TBC
Updates by email starting T-30 at 09:30.

Stop tracking this train:
  mailto:stop@late.fyi?subject=STOP%20ICE145&body=STOP%20ICE145
Stop the whole trip (Germany):
  mailto:stop@late.fyi?subject=STOP%20TRIP%20Germany&body=STOP%20TRIP%20Germany

— late.fyi
list@late.fyi (your active trains) | feedback@late.fyi | we don't store your email past notifications or STOP

TBC fields fill in at T-30. One tap on a mailto link cancels.

Travelling later?

Add On: in the subject. We'll wake up on the day.

To:      ICE145@late.fyi
Subject: From: Amsterdam Centraal, To: Berlin Ostbahnhof, On: 2026-05-04

Up to 90 days ahead. ISO date or named month (5 May 2026).

What we don't do

No accounts. No analytics. No ads. No third parties.
Your address is kept only while a train is being tracked,
so we can reply. When the trip ends — arrival, STOP, or
cancellation — your address AND the trip record are deleted.
Operator metrics are aggregate only.

Open source. Auditable end-to-end.