Checking bus times when you have no mobile signal
What still works offline, what does not, and what to note down before you lose reception.
Rural stops, valley roads and some village centres have poor reception, and that is exactly where services are least frequent and getting it wrong costs most. It is worth knowing in advance which parts of a bus journey depend on a signal and which do not.
What needs a connection and what does not
Scheduled times do not change while you travel. They come from a published timetable, so a time you looked up an hour ago is still correct now. If you have noted it down, you do not need a signal to use it.
Live expected times do need a connection. They are calculated from where buses are at this moment. With no signal there is no update, so you fall back to the timetable — which is still perfectly usable, just without the extra accuracy.
Disruption notices need a connection too, and these are the ones most likely to change after you set off.
The practical conclusion: a timetable checked before you leave covers most of what you need. Live data is an improvement on it, not a replacement for it.
What to note down before you go
If you are heading somewhere with poor reception, capture this while you still have a signal:
- The departure time you are aiming for, and the one after it. The second one is what turns a missed bus into a wait rather than a problem.
- The stop name and its code. Stops in villages are often unmarked or share a name with one across the road. The code on the pole is how you confirm you are at the right one. There is more on this in what the codes on a bus stop mean.
- The route number and its destination. The destination is what you check on the front of the bus, and on rural routes several services may pass the same stop going to quite different places.
- The last departure of the day, in both directions if you are coming back.
A screenshot of the departures does all of this in one step and stays readable with no signal.
Check the timetable on the pole as well
Printed timetables at rural stops are worth reading even if you have already checked online, for one specific reason: they sometimes carry information that does not appear in the digital timetable, such as a note that a journey runs on request or serves a village only on certain days.
Where the pole and the screen disagree, treat it as a question rather than assuming either is right, and allow more margin than usual. If the printed timetable is dated more recently than your last check, it is the better source. If you find a clear conflict, please tell us on the report a problem page.
Journeys that need booking
Some rural services do not run to a fixed pattern at all and must be booked in advance. Where a service works that way, it will not behave like a normal timetabled route, and turning up at the stop without booking will not get you a bus. If a route seems implausibly sparse or the timetable carries unusual notes, check with the operator before relying on it — the operator list will help you identify who runs it.
Plan for the return before you set off
The single most common rural problem is a comfortable outbound journey and no way back. Services can be much thinner in one direction, and the last return can be surprisingly early in the afternoon.
Check the return leg with the same care as the outbound one, and note the last departure. There is more on that in how to check the last bus home.
When you get reception again
If you get a signal on the way, it is worth a quick look at service updates to catch anything that has changed since you set off, and at the live times for your next departure. Neither is essential if you have the timetable noted, but both remove uncertainty.