Free · France
Reading small-town bus and rail information for Bourgogne-Franche-Comté
Finding two town names on a coach timetable does not yet tell you whether you can simply arrive at the stop. A service may need an advance booking; an individual departure may carry a special condition; a stop may be for alighting only. Those distinctions matter before you build a day around a train connection.
Take one practical question: for a journey between Montbard and Semur-en-Auxois, should you assume that every listed coach is available without advance arrangements? No. The official information separates regular-line listings from reservation-based transport, and the regular-line document itself contains conditional-service notes. The useful task is to identify the particular departure and its conditions—not to label the whole town pair “book” or “do not book.”
This guide explains how to read that information. It does not give a booked itinerary, promise a connection or reproduce a departure table that could soon change.
Start with the municipalities, then follow the service evidence
Montbard's municipal transport page identifies its railway station and places rail and Mobigo coach information together. That is useful orientation: the station is a place to investigate an interchange, not proof that every train meets a coach. Montbard: transport and parking
Semur-en-Auxois's municipal page identifies lines 119, 120 and 121, and names Montbard and Les Laumes–Alésia as nearby railway stations. It describes coach connections for some journeys on lines 120 and 121. The word “some” matters: a municipal overview does not establish a connection for your selected date, direction and departure. Semur-en-Auxois: public transport
Use the municipal pages to establish the local network's shape. Then move to the regional service listing and the appropriate timetable. Do not treat a general statement about a town's rail access as a promise that its centre has a railway station or that a coach will wait for a delayed train.
The same town pair appears in different service categories
Mobigo's Côte-d'Or timetable index lists LR120, connecting Montbard, Semur-en-Auxois, Saulieu and Liernais, among its regular lines. It separately lists TAD151 Montbard–Semur-en-Auxois under a heading for services requiring advance reservation. The index's regular-line section refers to timetables from 1 September 2026. These categories are a reason to inspect the correct document, not interchangeable descriptions of a single departure. Mobigo: Côte-d'Or timetable index
A useful first note therefore has three fields: line number, direction and journey date. “Montbard to Semur” alone is not sufficiently specific. Nor is a screenshot showing only a departure time, cropped away from the line heading, dates and footnotes.
Do not infer that the label “regular line” removes every reservation condition. The linked LR120 document contains a demand-responsive-service legend. Whether a particular column is affected must be read from its markers and notes. If you cannot establish that connection clearly, ask the operator about the exact departure before relying on it.
Three different meanings of “request”
The LR120 PDF, effective from 1 September 2026, distinguishes school and holiday periods and includes service-condition legends. Its notes include advance reservation for demand-responsive service, an alighting-only stop requested from the driver when boarding, and reservation arrangements for wheelchair users. It also tells readers to recheck rail times before travelling. These are different conditions, not three ways of saying the same thing. Mobigo: LR120 timetable and legends
Read them separately:
| Condition you encounter | Question to resolve | |---|---| | Advance-reservation service | Must this specific departure be booked, through which channel and by what deadline? | | Alighting-only/request-to-driver stop | Is this a permitted place to get off, and when must you tell the driver? Do not assume you may board there. | | An accessibility-related reservation note | What arrangements does the operator require for your journey and boarding needs? |
Telling a driver that you want to get off is not a substitute for booking a demand-responsive journey in advance. Conversely, a request-to-driver symbol does not by itself establish an advance-booking requirement. Preserve the exact meaning of the legend beside the relevant stop or service.
For accessibility, do not assume that a general route listing settles your requirements. Check the operator's current arrangements for the particular journey. This article has not tested a vehicle, stop or boarding procedure.
A currently linked document can have an older start date
At the source check, the same official index linked a TAD151 PDF headed as valid from 1 September 2024. Its instructions require reservation by the previous working-day deadline stated in the document, with a specific Friday rule for Monday journeys; they also describe registration for a first reservation. The document gives the booking channel and detailed conditions. Mobigo: TAD151 instructions
Do not silently change that date to 2026 to make the documents look consistent. Equally, “valid from 2024” is not the same statement as “expired in 2024.” The evidence here is that the official index linked this document when checked—not an assurance that it can never be superseded.
For a real trip, reopen the operator's index rather than relying only on a previously downloaded PDF or its filename. Compare the document's effective date, any expiry or exception, and service alerts. If two official sources conflict, keep that conflict unresolved until the operator clarifies it. Do not choose whichever version produces the most convenient journey.
The booking deadline also needs a real calendar. “The day before” must not be casually interpreted as any calendar day when the instructions distinguish working days, public holidays or Monday travel. Check the stated deadline and current reservation-channel availability; this article does not calculate one for you.
Build the journey in the right order
Work through the outward journey and return separately:
- Fix the date. Establish the relevant school/holiday period and any public-holiday exception in the actual timetable.
- Choose the direction. A return page is not merely the outward page read backwards.
- Locate the exact stops. Similar town names do not prove that two services use the same stop or platform.
- Read the departure column with its markers. Keep the footnote attached to the service it qualifies.
- Resolve the necessary arrangements. This includes booking, first-use registration where required and any relevant accessibility arrangements.
- Check the rail leg separately. A rail time printed for orientation does not remove the need to verify the train for your date.
- Leave an unresolved journey unresolved. A plausible combination is not yet a confirmed connection.
Keep a short evidence note: document title, effective date, date checked, selected departure and the applicable condition. Record a booking confirmation separately from an intention to book. If you later change the date or direction, revisit the conditions rather than assuming they transfer unchanged.
What this example teaches beyond Montbard and Semur
The transferable skill is not memorising a line number. It is separating network orientation, timetable applicability and the arrangements required for one journey. Municipal information helps with the first; the operator's current documents and confirmation channels are needed for the others.
That separation is especially useful when a town has several ways of reaching a railway station. Two options may serve the same general destination while using different stops, days or reservation rules. A longer list of possibilities is not necessarily a usable travel plan.
For Montbard–Semur-en-Auxois, the official sources establish why “just turn up” is an unsafe general assumption. They do not establish that every service needs reservation either. Identify your actual departure, read its conditions and verify the train connection before treating the journey as settled.
Source note: Municipal and Mobigo pages and the linked LR120 and TAD151 documents were checked on 26 October 2026. The LR120 PDF states an effective date of 1 September 2026; the linked TAD151 PDF states 1 September 2024. No journey was booked, operator contacted, vehicle tested or connection guaranteed. Recheck the live index, conditions and travel information for your date.