The bus returned to Ukraine long ago, but while preparing for another trip you see a result suggesting that you never left, or cannot understand how the remaining days were calculated. Your phone holds a ticket and photos of the journey, but these do not explain exactly what record the system contains. Start by describing the specific discrepancy and reconstructing the actual crossing, not by repeatedly entering the dates you want to see.
The official Netherlands border authority lists missing entries or exits, data that do not match the actual journey and duplicate files among possible EES problems. This confirms that errors are possible, but does not establish one in your case. Below is a way to prepare a request after a bus journey, not a means of changing a government record yourself or obtaining permission for your next entry.

Record exactly what seems wrong
Write down the name of the official tool, the date you checked it and the result displayed. Distinguish a page error message from a response about permitted stay. If the website does not load, that does not mean your departure is missing. If the result differs from your expectations, first check that you entered your own details correctly and used the appropriate document.
Do not call every unexpected result an “entry ban”. A more useful request would say: “After leaving by bus on this date, I see this result and ask you to check whether this crossing has been recorded correctly.” If you have not seen the file itself, do not claim to know its contents. Save the message with its context and time clear, but do not post it publicly alongside your passport details.
Reconstruct the bus crossing itself, not the timetable
Find the ticket, order number, name of the actual carrier and service messages. Note the departure location, final stop and known external border crossing point. The time you left a city is not automatically the time you left the Schengen area: the international journey may have continued past midnight, included stops or followed a changed route. Do not substitute the ticket date for an unknown border-check date.
Divide your notes into three columns: fact, supporting material and what still needs clarification. For example, buying a ticket establishes that a particular service was booked, but does not by itself prove that you actually travelled through every point. An arrival message helps reconstruct events, but does not always establish the exact time of crossing. Do not rename a file as though it were an official border-check certificate.
If you cannot remember the crossing point or day, ask the carrier specifically whether it can confirm the route and the circumstances of your service known to it. Do not demand that the seller correct EES or issue a conclusion on the legality of your stay. Its response may provide additional material for the competent authority, but does not replace a decision about the record.
- Your own details and the document used for the journey have been checked without assumptions.
- The crossing date is distinguished from the bus departure date.
- The ticket, confirmation of the actual journey and later messages have not been combined into a single item of “proof”.
- Unknown information is marked as unknown, not filled in to suit a convenient account.
Find the right recipient for your request
Start with the official contacts of the competent authorities in EES countries. The Marechaussee explanation directs you to the authority in the country of your last entry or exit; if responsibility for particular data is unclear, state this in your request. Do not choose a recipient merely because of the website language or the country where you bought the bus ticket. The seller may be in a different country from the border check.
The Report an issue form on the official EES website is intended for technical website problems. It separates questions about remaining stay or the result of the relevant tool from technical reports. Describing a button that does not work and requesting a check of a personal record are therefore different requests. Do not upload your whole passport to a technical comment field simply because it is available.
Before sending copies, check the authority’s address, the purpose of the form and the attachment instructions. A link from a public chat, an advertisement offering to “fix EES in a day” or a personal profile displaying a government logo is not a substitute for an official channel. Your bus order number is also not a government-service request number.
Draft a request that makes the action needed clear
Briefly describe the discrepancy, route and actual circumstances. Ask for the data concerning a specific crossing to be checked and for information on the appropriate access or correction procedure. Include a list of materials explaining what each establishes. Do not send dozens of identical unlabelled screenshots: the recipient needs to understand which is the ticket, which is a carrier message and which is your own note.
Send the personal data required by the official procedure through a verified private channel. Remove unnecessary fellow-passenger details from everyday photos if they are not needed for your request. Do not try to prove your departure using other people’s passports or a list of all passengers. If the authority requests another document, clarify its exact name and how to submit it rather than giving access to your email or account.
Keep the request text, attachments and confirmation of sending, if provided. Do not invent a registration number when you have only received an automated email. Refer to your earlier request in the next message and clearly identify new facts. If you discover a date error yourself, correct it openly rather than creating parallel, incompatible accounts.
Do not replace waiting for a response with another purchase
Submitting a request does not mean the data have already changed or the question of your next journey is resolved. Clarify the available response procedure and do not treat someone else’s processing time as a promise for your country. If departure is approaching, tell the competent authority the actual date, but do not require the carrier to guarantee the review’s outcome.
Separately check the conditions of the bus ticket you plan to buy or have already bought. A record-related request does not automatically pause purchase-change or cancellation deadlines. Do not pay for several alternative routes assuming a different crossing point “will not see” the problem. You need to clarify the data and your own documentary basis, not find a way around uncertainty.
After receiving a response, read what was actually done: access provided, a result explained, materials accepted or a correction confirmed. These are different stages. If the response does not address the discrepancy you raised, formulate one follow-up question and include the case number, if there is one. Keep the final result separate from the initial screenshot so you do not present an outdated version as current during a new check.
Questions and answers
Does a bus ticket prove departure took place on that exact day?
Not always. It describes the booked journey, whereas the actual crossing may have happened later. Explain the difference and submit the available supporting material as required by the recipient, without inventing precision.
Can the seller’s support team correct EES itself?
Do not count on it. Support can help with purchase or service details. Questions about access to and correction of government records must be addressed to the competent authority in the appropriate way.
Where should I write if the checking page itself does not work?
Use the website’s appropriate official channel for a technical problem. Do not combine it with a request to change your personal travel history: that has a different purpose and requires different information.
Can I travel with a copy of my submitted request instead of resolving the issue?
The copy shows that you contacted the authority, but is not entry permission and does not confirm a correction. Clarify your situation through competent sources before your next bus journey.
Should I delete all the old files after receiving a response?
Do not rush: separate the history from current materials. It may be needed to clarify the discrepancy reviewed, but must not replace the final response.
Official sources and further preparation
Checked on 23 October 2026: Marechaussee guidance on incorrect records, official EES information on data and the purpose of the technical form. For a basic introduction, see the article on EES at a bus border crossing. If checks are still continuing on site, also read how to coordinate contact with the crew. The competent authority determines the individual outcome, not this article.
