TL;DR / Summary: European rail apps display times in 24-hour format, and a misread departure is the most expensive mistake a traveller can make. Learn the four conversion anchors and check the platform board rather than trusting the app alone.
The format is not the problem; the habit is
Reading 24-hour times is straightforward once you have practised. The problem is that travellers who are used to 12-hour clocks read the format quickly and confidently and get it wrong, because the error is not in the reading but in the assumption.
A departure listed as 18:04 is obviously evening to someone who reads 24-hour time daily. To someone who does not, it can be skimmed as 8:04 with an unfamiliar prefix, especially when tired or rushing.
Four anchors eliminate the confusion. Below 12 is morning. Twelve is noon. Thirteen is one in the afternoon. Anything above twelve subtracts twelve to give the afternoon time.
The four anchors in practice
Write them on the back of your ticket if you are new to the format. The act of writing helps more than reading a chart.
- 06:40 — twenty to seven in the morning
- 12:15 — quarter past noon
- 13:00 — one o’clock in the afternoon
- 21:45 — quarter to ten at night
Midnight and noon are the two edge cases worth noting. Some systems display midnight as 00:00 and others as 24:00, and rail systems differ by country.
If a ticket says 00:20, that is twenty minutes past midnight at the start of the day. It is not the evening of the previous day, and this distinction has caused many missed trains.
The overnight train trap
An overnight service departing at 23:50 and one departing at 00:10 are twenty minutes apart and on different days. Apps sometimes list the arrival date rather than the departure date, which makes the confusion worse.
Always check the date on the ticket alongside the time. A sleeper train is the single most common context for this error.
The app shows the time. The board shows the platform. You need both.
Platform boards and app discrepancies
Rail apps are usually accurate and occasionally wrong. Platform changes, short-notice cancellations, and engineering works often reach the station board before they reach the app.
Check the board at the station even when the app is confident. The board is the operational truth at that moment, and it is the one the train will follow.
If the app and the board disagree, ask staff. A two-minute conversation at a ticket desk is cheaper than a missed connection.
Connections and buffer time
24-hour times make connection arithmetic easier once the conversion is automatic. Subtract the arrival from the departure and you have the connection buffer in minutes.
For a change of under ten minutes, assume the connection is at risk. Rail systems that advertise short connections often rely on trains being punctual, and punctuality varies.
Write the connection time down. Doing mental arithmetic on a platform with a rucksack on your back is how a six-minute connection becomes a two-minute sprint.
Announcements and local conventions
Announcements in 24-hour countries are usually spoken as numbers rather than converted to 12-hour phrasing. “Departing at eighteen oh four” is normal and takes a few journeys to feel natural.
Learn the local phrasing for the hours around noon. Some languages use a different word for afternoon hours, and the announcement may not match the ticket’s digits.
Where announcements are in a language you do not speak, rely on the board and the platform number rather than the spoken time.
Timetable planning
When planning a journey, convert the whole itinerary into one consistent format before comparing options. Mixing formats across a comparison is how a route that looked faster turns out to depart at ten at night.
Note the arrival time too. A train that arrives at 01:20 requires a plan for the following hours, and that plan belongs in the itinerary rather than in improvisation at the station.
If you are crossing a time zone, convert to local time at each end and note the difference. Rail apps usually handle this, but the displayed time zone is not always labelled clearly.
A small travelling habit
Before leaving for the station, read the departure time aloud in full—”eighteen oh four, six oh four in the evening”—and check the date. The verbal conversion catches errors that silent reading does not.
For quick conversion while planning, a 24 hour time chart is easier than mental arithmetic for the evening hours, which are the ones people get wrong.
Rail travel is mostly waiting and then briefly urgent. Getting the time right before you leave is what keeps the urgent part short.
Night trains and sleeper berths
Sleeper services often show boarding times well before departure, and a boarding time of 22:30 for a 23:10 departure is not an error.
Check both. Arriving at the departure time for a sleeper can mean missing the boarding window, and the train does not wait.
Set two alarms: one for leaving the hotel and one for boarding. The second is the one people forget, and it is the one that matters.
Delays and connection risk
Delays are announced in 24-hour format, and a revised arrival time needs recalculating against your onward connection. Do the arithmetic once rather than estimating.
If the delay makes a connection impossible, speak to staff before the train arrives. Rebooking on board is often easier than at a ticket desk with a queue.
Keep the tickets accessible offline. A dead battery at a ticket gate is a problem that a screenshot prevents.
