How to Read a UK Bus Timetable: A Worked Example

How do you read a UK bus timetable?

Check the direction and travel day first. In a table with stops down the side, read across your boarding stop's row to choose a departure, then follow that same journey's column to your destination. Read its footnotes before relying on it. Confirm the current timetable, exact stops and service updates with the operator.

The LincsBus timetable guide illustrates that row-and-column method. Layouts differ, so establish what each row and column represents before using the examples below. This is an independent reading guide, not live travel information.

What should you check before looking for a departure?

Find the route, direction, date and day heading. Save those alongside the time rather than copying an isolated number.

For online planning, Traveline's instructions explain how to select a travel date and search for a timetable using the service number and locality. The locality matters: a route number alone is not your complete journey description.

Our practical order is:

• Identify the place you are starting from and the place you want to reach.
• Confirm which direction of the route connects them.
• Select the actual date, not merely the weekday you remember.
• Check the timetable's validity information and any applicable notices.
• Locate the boarding stop before choosing a time.

If someone sends a cropped screenshot, ask for the heading and notes too. A clearly printed departure can still belong to the wrong day or direction. Keep the source link with your saved copy so you can check it again.

Can you follow one journey through this example?

Everything in the following table is fictional: the stop names, times, journeys and note codes. It is an original teaching exercise, not a service you can catch. The example runs towards Example Station, Monday to Saturday, excluding bank holidays.

The example's key defines SD as school days only. Its dash means this journey does not serve that stop. These meanings belong to this exercise. Use the actual operator's key when reading a real timetable.

Suppose you want to travel from Example Library to Example Garden on a school-day Tuesday. Read across the Library row. Journey A leaves at 08:17. Stay in column A and move down to Garden: 08:29. The scheduled interval in the exercise is 12 minutes.

Do not move sideways to another column while following that journey. Pairing A's Library departure with C's Garden time would combine different buses.

Journey B leaves Library at 08:47, but its Garden cell contains a dash. The table's key explicitly says B does not serve Garden. Its later arrival at Station does not make it an option for the Garden trip.

Journey C provides the next Garden departure pairing shown: Library at 09:17 and Garden at 09:29. The exercise therefore offers two listed Library-to-Garden journeys on that school-day Tuesday, not three.

What changes when you change the day?

Now use the same fictional table for a Saturday that is neither a school day nor a bank holiday. The main heading permits Saturday operation, but A's school-days-only note removes A from the options.

For Library to Garden, B still does not serve the destination. C is the only suitable journey shown. Its times have not changed. What changed is which column you may use.

This is why a day heading and a column note must be read together. LincsBus's guide shows school-day, school-holiday and Saturday restrictions in its examples. It also explicitly warns that those sample timetables are not accurate travel information.

A school holiday and a bank holiday are different conditions. Do not decide which applies by guessing from the presence of children or the apparent quietness of a road. For a real journey, check the service's own calendar and current operator information.

How do you read the time without mixing morning and afternoon?

Our exercise uses the 24-hour clock. Here are basic clock conversions, not service information:

Keep the date with an after-midnight departure. “Friday night” can be an ambiguous way to describe 00:15. Confirm the operator's dated journey display rather than translating an informal description into a booking or travel assumption.

Some tables show an arrival and a departure at the same location. Treat the labels as different events. If your task is boarding, find the departure entry. If your task is calculating an onward connection, establish which arrival entry belongs to the journey you selected.

What if a stop is missing from the main table?

A short list of major stops is not necessarily every stop along the route. Do not estimate your boarding time by dividing the gap between two displayed entries.

Traveline's timetable help describes switching between major stops and all stops. It explicitly says its times between major timing points are estimates.

Reading Buses gives a local explanation of timing points in its passenger FAQ. It distinguishes designated stops where buses should not depart before their allocated time from ordinary stops with estimated times. That is the operator's explanation, not a promise about every UK stop.

Check the exact stop with the current operator and allow time to be there before departure. An estimate should not become a guarantee in your plan.

How do you distinguish a timetable from a live prediction?

A timetable describes planned operation. A live prediction uses current information to estimate arrival. They answer different questions.

For its own system, Reading Buses explains that a clock time generally means a scheduled, untracked departure, while minutes generally indicate live tracking. It also explains that traffic can affect predictions. Do not assume another app uses the same display convention.

Look for the service's own legend or help page. If the displayed information is unclear, check official service updates or contact the operator. Neither a disappearing entry nor a frozen countdown is enough for you to invent a reason for the disruption.

Keep your saved timetable, but recheck current notices before travelling. This page cannot tell you whether a particular bus is running today.

How do you calculate the time between buses?

Use complete dated journeys, not two attractive times taken from separate screens.

In an additional fictional connection exercise, your first bus arrives at 10:42 and the onward bus departs at 11:05. From 10:42 to 11:00 is 18 minutes. Add the remaining 5 minutes: the timetable gap is 23 minutes.

If you have independently established that the transfer walk takes 8 minutes in your circumstances, subtracting that leaves 15 minutes in the exercise. That remainder is not a guaranteed connection margin. The first bus could be late, the boarding location could change, or your actual transfer could take longer.

Write the calculation as separate fields:

• Scheduled arrival: 10:42.
• Scheduled onward departure: 11:05.
• Scheduled gap: 23 minutes.
• Assumed transfer time for this fictional exercise: 8 minutes.
• Remaining planned margin: 15 minutes.

Keeping the walking assumption visible is the useful habit. It stops a neat subtraction from disguising a missing piece of the journey.

For a real transfer, verify the stop locations, usable walking route, access requirements and alternatives with appropriate current information. Choose a plan that does not require running, unsafe road crossing or reliance on perfect service operation.

How should you save the journey you intend to use?

Make a small journey card. This is our organisational suggestion, not an operator document.

Record the travel date, route, direction, boarding stop, destination stop, selected departure, relevant footnotes and source link. If the itinerary changes, update the complete card. Do not leave the outward journey from one version beside the return journey from another.

Read it back in a sentence: “On this date, I board this service at this stop, in this direction, using this departure.” Then check each part against its source.

For an unfamiliar return journey, repeat the process from the beginning. Confirm the return stop rather than assuming it is opposite the arrival stop. Identify the planned return and what you would do if it cannot be used.

The routes and days out collection covers broader trip planning. Keep ticket and concession questions separate from timetable reading, using the fares and passes collection as a starting point and current official terms for the actual journey.

What should you do when the information disagrees?

Keep the conflicting versions and note where each came from. Compare dates, directions and stop names first. The disagreement may be about a different journey rather than a changed departure.

If the same journey still has conflicting information, ask the operator which current timetable or service notice applies. Explain the exact date, route and boarding stop. Do not average two times or choose whichever would make the day easier.

The aim is to finish with an identifiable journey and the right questions answered. A timetable is easier to use when every time stays attached to its day, stop, direction and notes.

Sources

Opened and read September 10, 2026. Examples above are original and fictional. No route, fare, accessibility entitlement or current service operation is promised.

• LincsBus: How to Read a Timetable. Rows, columns, direction and operating-day notes.
• Traveline: How to use our site. Date selection, timetable searches, all-stop views and estimated intermediate times.
• Reading Buses: Frequently Asked Questions. That operator's timing-point and live-display explanations.