Local transport timetables after midnight
Verify after-midnight transit departures against the agency’s service day, timetable and calendar exceptions when reviewing a regional journey planner.

A bus advertised at 00:20 on Saturday may still be the final journey of Friday’s transit service day. Travellers care about which calendar morning to show up. Transit feeds also need to preserve the agency’s service-day convention.
Choose a boundary trip
On a journey planner you manage, find a route that spans midnight. Match its route, trip and stop identifiers to the published timetable. Inspect the operating calendar and holiday exceptions before interpreting the departure. Compare what the journey planner shows just before and just after midnight in the agency’s local time. GTFS schedule reference.
Check a remote visitor’s experience
A visitor planning from abroad might use a device set to another time zone. Test that device setting separately from the IP country. XtremeProxy helps supply a regional network viewpoint where the planner localizes its content. A useful bug report identifies the trip, both time zones, service date and displayed time. The fix may involve formatting a time, not changing the transit agency’s schedule.
A useful regression set includes a normal Friday, a public-holiday Friday and the first scheduled departure on Saturday. Keep the agency’s service identifiers in the test results. Screenshots that show only “Saturday” can look identical while referring to two different operating calendars.
Reading a departure at 25:10
A Friday service table lists a departure at 25:10. On an ordinary weekend without a clock transition, that is Saturday at 01:10 in the agency's time zone. GTFS defines the service-day baseline using noon minus twelve hours, an important distinction around daylight-saving transitions. An application that assigns it to Saturday's service plan may accidentally apply the weekend schedule twice. Inspect the service identifier and its date exceptions, then compare the journey displayed for a passenger searching after midnight. Check a holiday exception separately because the correct weekly pattern can still be superseded on one date.
Cross the local day boundary twice
Select a journey that boards shortly before midnight and arrives after midnight and one that boards after midnight under the previous service day. Trace the same stop sequence in the source schedule and passenger display. Check where the agency time zone is configured, especially if the remote tester's computer uses another zone.
A live departure board can show a predicted time while a static timetable still shows its scheduled time. Label which one the traveler viewed. If a scheduled 25:10 trip appears at 01:18 on a live board, investigate an eight-minute delay before treating the discrepancy as an error in the service-day conversion.
Test a trip that crosses an agency boundary
An itinerary combines two services from different operators. Use each agency's timetable and documented time-zone context before constructing the transfer. Preserve the source trip identifiers and passenger-facing departure and arrival instants. A connection that disappears after an importer uses the tester's laptop time zone is a conversion error, even if the individual schedules still look plausible.
Check whether the night service actually runs on the chosen service date before interpreting its clock time. An agency can publish a regular Friday trip and also remove it for a particular holiday Friday. Use the trip's service identifier to look up the dated exception in the approved schedule. Keep an otherwise equivalent ordinary Friday as a control. A planner that suppresses the holiday trip may be correctly honoring the exception even though the regular timetable still contains the after-midnight departure.
Build one overnight fixture in which the same stop appears before and after midnight. Store its service date, trip identifier and stop sequence along with the displayed clock time. A join on stop name and time of day alone can merge this journey with the next day's service. Check the operator's service calendar exceptions for that date as a separate step. If a public holiday removes one trip, its absence should survive the comparison instead of being filled by a similarly timed departure from another service day.
Related fieldwork
Report the agency service day, passenger-facing local date and stop sequence together when sending a timetable defect to the feed owner. Rail services across midnight follows an overnight rail service across midnight. A traveler also needs facilities that will be operating when they arrive. Keeping a destination guide useful during seasonal closures shows how to align a guide with the visit date. Review XtremeProxy plans and allowances.
Frequently asked questions
Should a departure later than 24:00 be discarded as invalid?
A GTFS schedule can express trips after midnight with hours beyond 24 under the relevant service day. Preserve that meaning during import and convert to a passenger-facing civil date only when displaying or comparing the journey.


