Reading a bus timetable after midnight: dates and transfers
A fictional Friday-night journey shows how to keep the correct date, read timetable notes and check whether a connection leaves enough time.
Write the date beside the time
A bus leaves at 23:42 and reaches your connection at 00:06. That is a 24-minute ride, but the arrival is on the next calendar date. Before choosing the next bus, check which timetable applies to that night and how much time the transfer actually needs.
This guide uses invented places and departures. The method helps you read an operator’s timetable; none of the examples is a real service.
1. Check the heading and the small print
Start with the route, direction and day of travel, as SMART’s timetable guide recommends. Then check the timetable’s validity dates and any holiday or temporary-service notice for your travel date. A weekday heading alone does not establish that a trip runs on a particular holiday.
Find your boarding stop and destination. Identify whether each row or each column follows one trip, then stay on that trip as you read. Check whether a time means arrival or departure. For a stop omitted from the table, use the operator’s guidance rather than inventing an exact time.
Big Blue Bus specifically points readers to symbols and their exception notes. Read any mark attached to your departure: it may change whether the trip is useful for you.
2. Separate calendar date from service day
The calendar date changes at midnight. A service day is the period an operator uses to organise a schedule; it can continue into the following calendar date. The GTFS schedule specification explicitly says that its definition varies between agencies.
GTFS data can express a time after midnight as more than 24 hours: on a night without a clock change, 24:14 means 00:14 the next calendar day. This is a data convention, not a promise that your passenger timetable uses that notation.
Look for the operator’s explanation of after-midnight trips. Do not automatically switch to Saturday’s table at 00:00, or automatically keep using Friday’s. In a journey planner, enter the actual calendar date and local clock time requested by its interface.
3. Put dates on a fictional journey
Assume the following invented timetable is valid from 1 to 30 November 2026, with no holiday exception for 6 November. Its own note says that every departure below belongs to Friday service. Here “+1” means the next calendar day. There is no clock change or time-zone change during this example.
Fictional Friday service: Market → Central → Harbour
Line A: Market to Central
Market departure Central arrival
23:42 00:06 +1
00:12 +1 00:36 +1
Line B: Central to Harbour
Central departure Harbour arrival
00:14 +1 00:34 +1
00:40 +1 01:00 +1
+1 = next calendar day, within Friday serviceEach row is one trip. The times, route names and +1 convention are invented for this exercise.
Read the night, not just the weekday label
Choose the 23:42 departure on Friday 6 November. Arrival at Central is Saturday 7 November at 00:06. The ride takes 18 minutes to midnight plus 6 minutes after it: 24 minutes.
The 00:12 departure in the same Friday table is also on Saturday 7 November. It is not at the start of Friday 6 November. Writing both dates beside the times prevents that one-day mistake.
4. Subtract the walking time from the connection
The first Line B departs at 00:14, eight minutes after your 00:06 arrival. Suppose you need six minutes to reach its stop and choose a further five minutes of spare time. You need eleven minutes altogether; the eight-minute gap does not meet your plan.
The 00:40 departure gives 34 minutes between vehicles. After the six-minute walk, 28 minutes remain, including your chosen five-minute allowance. It meets this example’s plan and reaches Harbour at 01:00. The whole journey from 23:42 takes 78 minutes.
These walking and spare-time allowances are assumptions, not a universal minimum. For your trip, account for the actual stop or platform, crossings, stairs or lifts, and any boarding cutoff. A positive gap does not guarantee a connection or mean the next vehicle will wait.
Try one: a transfer across midnight
Use the stated dates and the same local clock, with no clock change. Work out the time until departure, then subtract the walk and the extra allowance. Open the answers below if you want an explanation.
Answers and explanations
- An 11-minute gap, with 1 minute beyond the walk and allowance: Yes. Three minutes to midnight plus eight after it makes 11. Subtract 7 and 3: one minute remains. This meets the stated plan but does not guarantee the connection.
- An 8-minute gap, so the plan is short by 2 minutes: That drops the three minutes before midnight. The full gap is 11 minutes, not 8.
- A 49-minute gap, with 39 minutes spare: Subtracting 08 from 57 ignores the date change. Count forward: 3 minutes to midnight, then 8 minutes after it.
Copy this short trip check
Travel date(s) and local times:
Operator / route / direction:
Timetable valid from–to; day type; exceptions:
After-midnight notation means:
Boarding stop + departure date/time:
Transfer arrival date/time:
Next stop + departure date/time:
Gap ___ min − walk ___ min − allowance ___ min = ___ min
Destination arrival date/time:
Later option / last service checked:
Alerts checked at:If a date, stop or exception is unresolved, check it before relying on the connection.
Before you leave
Check the operator’s current notices and the exact boarding location, especially for the last service of the night. If the night includes a clock change or the journey crosses time zones, confirm the dated journey with the operator’s planner; the simple clock arithmetic above assumes neither occurs.