A Viking river ship stopped being a floating hotel on Tuesday, July 28 2026, when low Danube water left Viking Ullur hard aground near Vidin, Bulgaria. All 186 passengers had to leave the vessel after food and drinking water ran short.
Bulgarian border police completed the evacuation about 25 kilometers upstream from Vidin after a supply attempt by another ship could not get close enough. The ship remained stranded with 52 crew still aboard while authorities assessed how long the hull might sit until river levels or refloating work allowed movement.
- What happened: Viking Ullur grounded on the Danube near Vidin due to low water.
- When: Early July 28 2026, with passenger evacuation completed the same day.
- Who left the ship: All 186 passengers from EU countries, per Border Police via BTA.
- Crew status: 52 crew remained as the ship stayed stranded pending refloat options.
- Traveler decision: Confirm your Danube sailing status and low-water contingency terms now.
What Border Police and BTA reported
The Bulgarian News Agency (BTA) reported that Border Police finished evacuating every passenger from the Swiss-flagged Viking Ullur after the ship ran aground at river kilometre 817, opposite Gomotartsi and about 25 km upstream from Vidin.
The vessel grounded early Tuesday because of low water levels. It carried 186 passengers from EU countries and 52 crew members, according to the same official account.
Passengers ran out of food and drinking water after the ship, which had been scheduled to take on supplies in Vidin, could not reach the port. The ship’s agent dispatched the French-flagged Vivaldi to collect them, but that ship could not get close enough, so Border Police intervened.
After clearance from the River Supervision Directorate in Lom and a further assessment, passengers left on a patrol boat from the Vidin Border Police Vessels Base. Luggage was still being transferred Tuesday afternoon.
Crew fate was unclear in the initial notice, because Viking Ullur could stay stranded for an extended period depending on navigation conditions and refloating options. Initial misplacement of the ship near Salcia in Romania was corrected once the Vidin location was confirmed.
Location accuracy matters for families waiting on shore news. A Romania-side rumor and a Bulgaria-side official fix change which border, hotel market, and transfer road you should watch while bags and guests move.
For anyone still inbound to a Vidin call later this week, treat the local draft risk as live until the line or river authority says otherwise. A single successful passenger rescue does not prove the reach is open for the next longship.
Why this is more than a single bad pier call
River cruise products assume a continuous water itinerary with hotel nights on the ship. When draft depth fails at a bend or shallow reach, the product breaks even if the brand still owns the booking.
This grounding sits inside the wider July 2026 low-water pattern already tracked for Rhine and Danube operations. Deep Arrival’s earlier report on Rhine and Danube low-water reroutes in July 2026 covered contingency moves such as embarkation shifts and bus bridges, but it did not absorb a later named-ship evacuation with supply failure.
Ullur’s day adds a different traveler fact set: passengers left the ship after supplies ran out, luggage transfer lagged, and crew remained on a hull that might sit until conditions improve. That is a residual claims and itinerary story for anyone still sailing the lower Danube this summer.
For guests booked on Viking or competing Danube products in the next weeks, the practical question is not whether Europe still sells river cruises. It is whether your exact departure still runs as continuous ship nights, and what the line promises if a shallow reach repeats.
Evergreen planning tools still help for packing and route context, including Deep Arrival’s Viking river cruise packing list and the broader guide to most scenic river cruises in Europe, but they do not replace a current sailing advisory from your line.
What affected passengers should do next
If you were on Ullur on July 28, keep every Border Police, agent, and Viking communication, plus photos of cabin tags and bag tags. Those records support rebooking, hotel nights, refunds, and insurance claims after an evacuation day.
Ask Viking in writing for the replacement itinerary, meal coverage, hotel class if used, and whether any nights were lost without a comparable product. Do not rely on a dockside verbal summary alone.
If you hold a future Danube sailing, open the line’s current sailings or disruption page and your travel advisor thread before you leave home. Low water can force a ship swap, a bus segment, a hotel night, or a cancel window with little notice.
Travel insurance only helps if your policy covers trip interruption and supplier itinerary changes. Read the exclusion language for weather and water levels before you assume a full cash refund path.
Medical and mobility needs matter more on an evacuation day than on a normal dock call. If stairs, heat, or long transfers are hard, request accessible transfers in writing as soon as a contingency starts.
Independent river-cruise coverage has also framed the day as part of a broader low-water squeeze. Cruise Passenger reported that Viking Ullur ran aground in Bulgaria with passengers and crew later rescued safely, tying the incident to the same low-water stress European river lines have been managing all summer.
That second account does not replace the Border Police timeline. It does corroborate the traveler-facing outcome: the ship could not continue as a normal floating hotel night, and guests had to leave under official rescue conditions.
If you are shopping a late-summer Danube itinerary now, price the cancellation terms and the contingency menu before you pay the final balance. A cheap cabin fare is not a bargain if the product becomes three hotel nights and long coach days without clear compensation language.
Also ask whether shore excursions sold as prepaid packages still refund when the ship never reaches the intended pier. Many guests lose money twice: once on the sailing change, and again on nonrefundable third-party tours that assumed a dock call that never happened.
For groups and multi-generational cabins, appoint one person to own communications with Viking and the advisor. Fragmented group chats create conflicting rebooking requests that are harder to unwind after an evacuation.
| If you… | What to do |
|---|---|
| Were a passenger on Viking Ullur on July 28 | Save all notices, request written rebooking and cost coverage, and open insurance claims promptly. |
| Hold a Danube sailing in the next two weeks | Confirm sailing status daily and ask for the line’s current low-water contingency menu. |
| Need continuous ship nights only | Ask whether your departure still guarantees ship nights or can become hotels and coaches. |
| Travel with mobility limits | Request accessible transfer plans before any evacuation or ship-swap scenario starts. |
| Booked through an advisor | Loop the advisor into every Viking message so ticket, hotel, and insurance files stay aligned. |
- Refloat timing: How long Ullur stays at kilometre 817 depends on water and salvage options.
- Crew status: Initial notices left 52 crew aboard with an unclear stay length.
- Lower Danube sailings: Other Vidin-area calls may face the same draft risk while levels stay low.
- Line notices: Watch Viking current-sailings updates for broader Danube contingency language.
- Insurance clocks: Interruption claims often have short documentation deadlines after evacuation days.
A clean residual rule for the rest of summer 2026 is simple: treat every Danube booking as draft-dependent until your line confirms continuous navigation for your exact dates, and keep evacuation-day paperwork if you already lived through one.
What happened to Viking Ullur on July 28 2026?
According to Bulgarian Border Police via BTA, Viking Ullur ran aground on the Danube near Vidin due to low water, and all 186 passengers were evacuated after food and drinking water ran short.
Were passengers injured?
The official BTA account focuses on grounding, supply shortage, and complete passenger evacuation. It does not describe passenger injuries in the notice reviewed for this report.
Did the crew leave the ship too?
Initial Border Police information said 52 crew remained while the ship could stay stranded depending on navigation conditions and refloating options.
Is this the same story as general Rhine and Danube low water reroutes?
Related, but not identical. The wider low-water reroute stream covers contingency patterns across lines; Ullur adds a named-ship grounding and passenger evacuation on July 28 near Vidin.
What should future Danube cruisers do now?
Confirm your exact sailing status with the line, ask how continuous ship nights are protected under low water, and keep insurance and advisor contacts ready before travel day.
