Skip to content
All guides

Reading the delay history

For each day, the chart shows the latest reported delay of the runs with a given train number. It is not a confirmed arrival time at the final station.

Days without data are left out, not counted as zero. An empty history and a temporarily unavailable history are two different situations. A short sample says nothing about national punctuality or about all of an operator’s services.

Make a personal history reproducible

Choose the journey you want to understand and record the same event each time. An arrival at your destination and a departure from an intermediate station are different measurements. Record the service date, station, planned time and actual outcome together. Keep cancellations and unavailable observations visible rather than excluding them without explanation.

If you compare different days, check whether the timetable changed between them. A train number alone may not establish an identical route or stopping pattern. Explain why each observation belongs in the comparison, and avoid replacing a missing actual time with an earlier forecast. A small personal diary can help you plan, provided its limits are stated clearly.

Do not turn a partial sample into a promise

A run of punctual trips does not guarantee your next connection, and several poor trips do not establish the performance of every service from that operator. Think about the decision you need to make: choosing an earlier train may be prudent when missing an appointment would be costly, even when no national statistic is available.

MapaPociągów does not publish a verified historical punctuality ranking for every Polish service. If a page lacks an aggregate, do not infer that the value is zero or that the train has a perfect record. For an immediate journey, use current official operational information. For a claim, use the evidence of the specific trip rather than a broad impression of how the line usually performs.

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.