Skip to content
All guides

Train notifications: current limits

Notifications are not active in this pilot. MapaPociągów does not send train alerts.

The pilot does not create new push subscriptions or alerts. Saving a train as a favourite does not enable notifications.

Check the service date and the time of the latest data, and base travel decisions on the operator’s notices and station announcements. Do not expect notifications from this pilot.

Prepare to check the journey yourself

Train notifications are not active in this version of MapaPociągów. Saving a favourite does not create a push subscription or enable a warning about disruption. If the timing of a train matters, make a plan to check it yourself before leaving and again at the station. Keep the operator’s official notices and the station search easy to reach on your phone.

Do not assume an absence of alerts on the device means the train is running normally. It may simply mean no notification service is active. For an important appointment or an evening connection, identify an alternative departure in advance. A reminder you set yourself can help you remember to check, but it is not a railway operational alert.

Understand what an alert would need to establish

A useful travel alert must identify the train, date, affected leg and source. A generic message that a line has engineering works is context, not proof that your particular train is cancelled. If an operator provides its own alert service, read its coverage and conditions, and confirm which journey you have selected. Keep important contact and booking details available even if the phone loses data connectivity.

When reading a notice in MapaPociągów News, open the credited original source and compare the validity period with your travel date. The national notice list and secondary Warsaw-area feed do not provide personal push notifications. Station announcements and direct instructions from railway staff remain important. Do not wait for an alert from this site when you need to make an immediate boarding decision.

Read the time, date and provenance together

Before using a displayed value, identify the train, service date and station it describes. Then look for the time of the last observation and the source. A number without this context is easy to misread. Yesterday’s arrival is not evidence for today’s departure, and a timetable entry is not a recent observation. Keep these distinctions when comparing a screenshot with the information now visible in MapaPociągów.

A planned time describes the timetable. An observed time describes a recorded event. A forecast may change as new information arrives. Avoid combining those three into one statement that a train “will certainly arrive” at a particular minute. When records disagree, ask which event each refers to and whether one has become stale. Confirm travel decisions with the official Portal Pasażera, the operator and current station information, especially when deciding whether to leave a platform or abandon a connection.

Treat missing information as missing

An absent delay is not automatically a zero-minute delay. An absent train record is not automatically a cancellation. Coverage can vary by service, date and source, so make a note of what the page actually shows. If a record is unavailable, search the official timetable using the full station name and travel date. Check the operator’s notices for the affected route rather than drawing a conclusion from an empty list.

For a personal record, save the train number, date, relevant station and the observation time alongside any displayed delay. If you are investigating a particular incident, keep official notices and the final arrival information separately. A live forecast made earlier in the journey cannot establish the final outcome by itself. Equally, a notice about planned works does not prove that every train on the line was late. It supplies context that must be checked against the actual service.

Use information without overstating it

When discussing punctuality, be clear about the population you have observed. A few journeys taken by one passenger are useful personal experience, but they do not establish an operator’s national performance. Do not average only the trains that happened to have complete records and describe that result as the performance of every service. Cancelled journeys and missing observations should remain identifiable rather than quietly disappearing into the calculation.

For an immediate trip, choose a practical alternative before relying on a tight forecast. Recheck the source near departure, keep the ticket available and follow station announcements. MapaPociągów does not turn an estimate into a certificate or a compensation decision. If a data discrepancy matters to a complaint, describe the discrepancy and preserve its context. The official passenger information linked below helps you identify the appropriate source and the operator responsible for the journey.

Frequently asked questions

Does a missing value mean the train is on time?

No. Missing information should remain missing. Check the service date and the official operational sources rather than replacing an unavailable observation with zero.

Can a forecast prove the final outcome?

No. A prediction earlier in the trip and an actual arrival at the destination are different records. Keep their times and sources separate, especially when explaining a disruption or collecting evidence for a complaint.

Where to confirm information

Editorial review: 9 October 2026.