• Learn more about our technology and shipping tools andstart your free trial now
  • Produkte
  • Schiffe
  • Häfen
  • News
  • Über
    • Über
  • Community
  • Log in
    • English
    • German
  • Log in
    EN / DE

News

  • Produkt updates
  • News
  • Schiffsmeldungen
  • Hafenmeldungen

Category

Accident/Casualty42320Misc. for Ports and Vessels37996Scrapped/Beached/Broken Up22613Sold/Decommissioned8541Charter Changed6734Pirate attack2043

ANDREA

Scrapped

arrived Scrapyard Treffers at Haarlem, Netherlands 09.07.25 https://www.shipspotting.com/photos/3859909?navList=gallery&category=70&page=1&viewType=normal&sortBy=newest

BerndU
2025-07-12

MSC BALTIC III

Casualty

As of July 10, about 85% of the heavy fuel aboard the 'MSC Baltic III' has been safely transferred to other vessels. The ship, which ran aground near Wild Cove, Newfoundland on Feb 15, was carrying approximately 1.700 tons of fuel and marine gas oil. Crews continued to focus on removing the fuel from the engine room and smaller tanks. So far, 208 of the 472 containers have been offloaded. Minor oil traces remained on nearby shorelines. A one-nautical-mile safety zone remained in place around the vessel.

Timsen
2025-07-11

SOLVEIGA

Casualty

On July 1, 2025, at 6.30 a.m. the Russian tug 'Bikin' (IMO: 9402134) rammed into the port side of the 'Solveiga' at full speed in the port of Nakhodka before abruptly reversing course and fleeing the scene. Footage showed he tug accelerating directly towards the moored vessel without any attempt to slow down. The impact caused serious damage to the port side of the 'Solveiga'. Despite the allision, the tug’s captain made no effort to check for casualties or assess the damage. Instead, he turned the vessel around and departed the area immediately. Russian authorities have launched an official investigation into the incident. The Nakhodka Transport Prosecutor’s Office was conducting a probe into the accident under Article 263 of the Criminal Code of the Russian Federation (violation of traffic safety rules and operation of water transport). No oil spill has been detected. It turned out that during maneuvering, the tug captain had lost consciousness, which led to the loss of control over the vessel. He did not have a partner, which is why he had to constantly be at his workplace during a month-long work cycle, which took place without a single day off. Reports with phjoto and video: https://english.pravda.ru/news/hotspots/163168-tugboat-bikin-crashes-solveiga-nakhodka/ https://vladivostok1.ru/text/incidents/2025/07/10/75702410/

Timsen
2025-07-11

TUNU PRATAMA JAYA

Casualty

The death toll from the sinking of the 'Tunz Partama Jaya' in the Bali Strait has risen to 15 as of July 10, while the search continued for 20 people still missing by the East Java Search and Rescue Office. Two bodies were found on the morning and another on the evening of July 9. The SAR operations were launched from both Bali Island and East Java, as the incident occurred near the maritime boundary between the two regions. Harsh weather had posed significant challenges to the rescue efforts as visibility had decreased from 10 kilometres to only three kilometers on several occasions, waves reached heights of 2.5 metres, and strong winds were present in the area. The investigation by Indonesia's National Transportation Safety Committee (KNKT) was focusing on several key areas, including whether proper procedures were followed for the ship's departure, the seaworthiness of the vessel, the completeness of its documentation, and how the emergency response was carried out when the accident occurred. The Indonesian Meteorology, Climatology and Geophysics Agency (BMKG) had also issued a warning about the threat of extreme weather conditions following the accident. The East Java police's disaster victim identification (DVI) team announced on July 10 that a Malaysian national was among the victims of the sinking. He was identified as Fauzey Bin Awang, 58, which was confirmed through the DVI team's medical examination, as well as the victim's wallet and identity card. He was identified along with two other recovered bodies, who were identified as Noval Hardiansyah, 15, a resident of Banyuwangi, East Java; and Sofyan Wibowo, 18, a resident of Susukan Sub-district, Banjarnegara, Central Java. The fourth body, that of a woman found on Plengkung Beach in the Alas Purwo National Park area, Tegaldlimo Sub-district, Banyuwangi District, East Java, on Huly 10, has not yet been identified.

Timsen
2025-07-11

HUGO

Scrapped

Beached at Chittagong 26.06.25 https://www.facebook.com/photo/?fbid=122153576594471366&set=pcb.10165036275423943

BerndU
2025-07-11

MESHKA

Casualty

The captain of the 'Meshka', which ran aground off Landskrone near Ven on May 31, en route to the Russian port of Vysotsk, has been sentenced for negligence in maritime traffic to a daily fine of 47,500 Swedish Crowns. He was found guilty of carelessly and with a lack of attention operating the ship, which led to it running aground with 938 tons of oil in its tanks. The ship was inspected at the Öresund Drydocks Ship Repair Yard ffrom June 7-10 and finally reached the port of destination on June 14. It sailed again on July 18 en route to Dakar, where it arrived on July 10.

Timsen
2025-07-11

ETERNITY C

piracy

The Houthi terrorists were believed to be holding six of the 'Eternity C’s complement of 22 crew and three guards. On July 10 the rescuers have pulled three more crew members and a security guard alive from the Red Sea waters, where the bulk carrier was sunk. They said the Houthi militants were holding some of the crew who were still missing. “These are blameless victims who were simply doing their job. Seafarers should be able to work safely at sea. Instead, they are being unfairly forced into the firing line,” the UK-based Seafarers’ Charity association said. Four crew members were believed to have been killed in the attacks. The 'Eternity C' was first hit on July 7 with sea drones and rocket-propelled grenades fired from speed boats. Following a second attack on the morning of July 8, the crew members were forced to jump into the water. Rescuers have been searching for survivors since the morning of July 9. A total of 10 survivors have been rescued so far, among them eight Filipino crew members, one Indian national and one Greek security guard. The four people rescued on the morning of July 10 had spent nearly 48 hours in the water. The search for survivors was to be continued until all persons have been accounted for. 11 people were still missing. All ships passing the area have been asked to assist in the search. The vessel’s operator, Cosmoship Management, said the ship had delivered a cargo for the UN World Food Program to Berbera and was sailing in ballast condition to Jeddah for refueling at the time of the attack.

Timsen
2025-07-11

STRIDE

Scrapped

arrived M.A.R.S. scrapyard in Mobile,USA 16.05.24 https://www.shipspotting.com/photos/3858737?navList=gallery&category=70&page=1&viewType=normal&sortBy=newest

BerndU
2025-07-12

JACKIE LEE ANDERSON

Casualty

The Olmsted Locks and Dam on the Ohio River has reopened to navigation following the collision of the 'Jackie Lee Anderson' and the workboat '775' of the U.S. Army Corps of Engineers, Louisville District. The accident had occurred on July 1 at around 8:50 a.m. central time during routine fleeting operations. No injuries were reported, and all personnel were accounted for. Local emergency responders arrived on scene but were able to stand down upon confirming all personnel safety. As of July 10, the Corps confirmed the 'Jackie Lee Anderson' was currently listing on the Illinois riverbank, while the '775' remained capsized and submerged outside of the navigation channel. Locking operations resumed shortly after the incident, once it was confirmed that neither vessel was obstructing the navigation channel. Initial inspections showed only cosmetic/superficial damage to tainter gate 1. The gate remained functional and not impacting project operability.

Timsen
2025-07-11

LUMINOSITY

Misc. for ports and Vessels

The 'Luminosity' has been rotting away at a dock in Montenegro for years. The superyacht was finished in 2020 by the shipyard Benetti. It cost around $270 million. Due to the lengthy build time, The initial owner, the Kuwaiti billionaire Kutayba Yusuf Ahmed Alghanim, refused to accept the yacht when it was finally finished. Instead, the Russian oligarch Andrey Guryev purchased it, who appears on several sanction lists, causing the yacht to be seized in Montenegro. he management company dropped the 'Luminosity' from their portfolio, which meant the original crew had to be let go. A skeleton crew was retained, but it was later reduced to a 5-6 maintenance crew that was still believed to be onboard. In 2024, Luminosity was listed for sale at half its reported value, but the sale eventually fell for a variety of reasons, including the piling debt against the vessel and its legal status as a sanctioned asset. The debt piled on the 'Luminosity', while footage of the megayacht at anchor showed considerable growth all around the hull, teak decks that have been completely destroyed,, with missing panels on the deckheads, scratches and chippings in the paint, and rust, and fixing it will amount to millions in expenses and at least a few months in the drydock. The 'Luminosity' is $81 million short of maintenance work. Video: https://www.youtube.com/watch?v=G_9vln9gnEk

Timsen
2025-07-11

GRAND MASTER

Sold/Decommissioned

Sold to Breakers 07.07.25

BerndU
2025-07-11

EL.VENIZELOS

Misc. for ports and Vessels

The Entreprise nationale de transport maritime de voyageurs (ENTMV)on July 9 announced the resumption of service for the chartered ferry "El Venizelos," which has been stuck in the port of Alicante since July 4 and esumed its crossings starting on July 10 at 8 p.m.,, after completing all stages of the technical inspection scheduled for the port of Alicante. The company assured that "all conditions have been met to offer a journey under the best possible conditions, in terms of safety, comfort, and quality of service. The ship arrived in Algiers on July 11.

Timsen
2025-07-11

SEA ANGEL

Casualty

The Indian Coast Guard assisted the 'Sea Angel', which was stranded in rough seas southeast of Indira Point in the Andaman and Nicobar Islands after having suffered sail damage and propeller failure with two crew members, one American and one Turkish national, on board. On July 10, 2025, at 11:57 a.m. the MRCC in Port Blair received a distress signal from the sailing vessel. The yacht had suffered severe mechanical issues, its sail had been torn apart by fierce winds and its propeller had become entangled in ropes, rendering it immobile in dangerously rough waters, 52 nautical miles from India's southernmost tip. The MRCC activated the International Safety Net (ISN), alerting nearby merchant vessels while launching its emergency rescue protocol. The ICG deployed the patrol ship 'Rajveer' at 2 p.m. to reach the stricken vessel. By 5:30 p.m., it arrived at the scene. Despite battling harsh sea conditions, the crew managed to establish contact with the catamaran crew, which was found to be safe and in stable condition. At 6:50 p.m., the patrol vessel successfully took the 'Sea Angel' in tow. They arrived in Campbell Bay on July 11 at 8 a.m. Report with photos: https://news.abplive.com/news/india/indian-coast-guard-rescues-stranded-us-yacht-in-daring-operation-off-andaman-coast-1786948

Timsen
2025-07-11

WAN HAI 503

Casualty

On July 10 at 6 a.m. the 'Wan Hai 503' remained under tow by the 'Offshore Warrior', maintaining a controlled heading of 319° at a speed of 0.3 knots. The vessel’s position was 07° 49.79'N, 074° 43.51'E, beyond the Indian EEZ. The prevailing weather consists of winds from 305° at 20–22 knots, with moderate to rough sea conditions and high swells affecting operations. Light grey smoke was still observed emanating between Bay 33 to Bay 38, corresponding to cargo hold no. 4, where residual smouldering continued. No active flames have been reported, and the situation remained stable. Thermal imaging continued to be employed for monitoring heat levels across affected compartments. Dewatering of the engine room has progressed significantly. As of the evening of July 9, five onboard pumps had reduced the water level to approximately 0.3 metres improving accessibility for ongoing inspections and stability recovery efforts. The vessel’s name and port of registry were now visible, indicating improved external visibility. The salvage operations continued to be supported by a coordinated fleet of response assets. the 'SCI Panna' remained stationed on site and continued to conduct fire watch duties. The 'Water Lily' was actively engaged in personnel and material transfers between support vessels and the container vessel. Despite swell-related boarding challenges, critical movements were maintained to sustain onboard salvage efforts. The 'Advantis Virgo' was on standby for immediate fire-fighting or boundary cooling if required. The 'Saksham', having departed Kochi, was expected to reach the casualty site to augment salvage efforts and may participate in inspections or pump deployment, subject to weather permitting. Onboard the wreck, salvage teams were operating pumps in round-the-clock shifts. Inspection of hold no. 4 has commenced, and options were being explored for possible pump installation to expedite hold water removal. The team was also evaluating whether a second release of CO₂ in hold no. 5 was warranted based on ongoing thermal observations. The overall onboard situation was stable and improving, with active measures in place to mitigate fire risks and address flooding. While no new fire escalation has been reported, smoke persisted, and thermal surveys confirmed elevated readings, especially in the starboard section of cargo holds 4 and 5. Temperature readings of 130–140°C were previously recorded but have shown a declining trend over the last 48 hours. Structural access remained limited, and tunnel access areas were unsafe for entry due to heat and possibility of hazardous gases. The salvors were exercising extreme caution and would conduct further enclosed space entries only after formal risk assessments have been completed. The engine room was now accessible, and work continued to trace the suspected leak path, likely originating from cargo hold no. 3. However, further pump installation and complete compartment soundings remained contingent on weather improvement and reduced internal heat. The Port of Refuge issue remained unresolved. Discussions have been ongoing with the Harbour Master, and document submissions have been made by WAN HAI Lines and T&T Salvage. Simultaneously, contingency options were being pursued in coordination with the Maritime and Port Authority (MPA). The Directorate has reiterated that the vessel could not remain in its current location in the absence of a confirmed Port of Refuge clearance; relocation southward must be undertaken. The vessel is currently at the India–Sri Lanka–Maldives tri-junction area, and should be shifted 200 nautical miles south off Sri Lanka for this purpose. The 'Water Lily' will be released, once the 'Saksham' or another private tug (e.g., 'Nand Sarthi') have arrived to take over operational responsibilities. The Directorate has emphasized the need for finalisation of PoR permissions within the next 2–3 days, failing which the vessel must be moved if such a move is necessitated. The Indian Coast Guard continued aerial and maritime surveillance of the site and has confirmed that no new debris or pollution has been observed drifting toward the Indian coastline.

Timsen
2025-07-11

INDA

Scrapped

Beached at Alang 07/.2025

BerndU
2025-07-12

BIKIN

Casualty

On July 1, 2025, at 6.30 a.m. the 'Bikin' rammed into the port side of the fishing vessel 'Solveiga' (IMO: 8520173) at full speed in the port of Nakhodka at berth No. 60, before abruptly reversing course and fleeing the scene. Footage showed he tug accelerating directly towards the moored vessel without any attempt to slow down. The impact caused serious damage to the port side of the 'Solveiga'. Despite the allision, the tug’s captain made no effort to check for casualties or assess the damage. Instead, he turned the vessel around and departed the area immediately. Russian authorities have launched an official investigation into the incident. The Nakhodka Transport Prosecutor’s Office was conducting a probe into the accident under Article 263 of the Criminal Code of the Russian Federation (violation of traffic safety rules and operation of water transport). No oil spill has been detected. It turned out that during maneuvering, the tug captain had lost consciousness, which led to the loss of control over the vessel. He did not have a partner, which is why he had to constantly be at his workplace during a month-long work cycle, which took place without a single day off. Reports with phjoto and video: https://english.pravda.ru/news/hotspots/163168-tugboat-bikin-crashes-solveiga-nakhodka/ https://vladivostok1.ru/text/incidents/2025/07/10/75702410/

Timsen
2025-07-11

SENAZ

Sold/Decommissioned

Sold to Breakers 07.07.25

BerndU
2025-07-11

TECHNO

Scrapped

Beached at Alang 10.07.25 https://www.facebook.com/photo/?fbid=10161722808970036&set=gm.10165029115548943&idorvanity=6884293942

BerndU
2025-07-11

TORVANG

Casualty

The 'Torvang', which capsized at Hendvågen in Averøy on May 23, has still not been removed as of July 11. The wreck has occupied the Henda Pukk quay since the sinking, and it was is still unclear when it will be removed. The Velta CEO Odd Halvor Gustad said that they hopde the ship can be removed next week. Until July, they had had expenses of 550,000 Norwegian Crowns in connection with transport, since they could not use the quay, and have to use alternative loading bays. Report with photo: https://www.nrk.no/mr/velta-skip-ligg-framleis-til-kai-i-averoy-1.17487806

Timsen
2025-07-11

SEA LADY II

Casualty

The 'Sea Lady II' was gutted by a major fire at the Quay de l’Epi in the old porot of Saint-Tropez on July 10, 2025. After the ship went ablaze at aroudn 8.15 p.m., two people believed to be crew members, aged 24 and 35, were rescued. Both had to be treated for smokle inhalation on site. First smoke was noticed from the cockpit on the upper deck, then the wheelhouse burst into flames. The owners of neighbouring yachts immediately sent their crews to bring these to safety. Just in time. Enormous flames were emanating from the ship. 30 firefighters responded within minutes, deploying four engines, two pump vans and quickly establishing a safety cordon to keep the gathered crowd at a safe distance They were supported by the gendarmerie and SNSM sea rescuers. Initially, the massive flames were fought from the dock with foam. As the fire intensified and plastics ignited, the Saint-Tropez’s fire brigade was joined by a fireboat, working to combat the flames from the water. Meanwhile, the firefighters boarded from the stern, attacking the blaze internally. Despite their efforts, the fire advanced to the yacht’s lower deck, prompting hours of extensive dousing and containment operations into the night.By 9:00 p.m., the flames had been largely contained on the upper structure, but flare-ups continued to threaten the lower levels. The firefighters believed they had extinguished the flames for the first time at around 10 p.m., but the fire started again. fueled by the 27,000 liters of fuel in the tanks, which had just been filled. It was still not extinguished after midnight and had spread to the three upper decks. A large security perimeter blocked the Mistral and Jean-Jaurès quays. The terraces were evacuated around midnight due to smoke. The fire figtherrs remained on deck until July 11 at 2 a.m. An oil boom was laid out around the vessel, as it was feared that it could sink. The ship was heavily listing to port side meanwhile. An investigation into the fire was launched, which was thought to have been caused by an electrical fault. Reports with photos and video: https://www.bbc.com/news/videos/c4g85005q93o https://www.thesun.co.uk/news/35795650/superyacht-bursts-flames-resort/ https://nauticmag.com/2025/07/10/fire-erupts-aboard-41-metre-superyacht-sea-lady-ii-in-saint-tropez-port/ https://www.liberation.fr/economie/transports/le-superyacht-de-luxe-sea-lady-ii-amarre-a-saint-tropez-prend-feu-20250711_B525FWPILJDXHEWTGISQFAABZI/ https://www.francebleu.fr/infos/faits-divers-justice/l-incendie-du-yacht-a-saint-tropez-eteint-apres-une-longue-lutte-des-pompiers-4526817 https://www.varmatin.com/faits-divers/un-superyacht-de-41-metres-en-feu-dans-le-port-de-saint-tropez-993842

Timsen
2025-07-11
  • «
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • »

Location + Contact

vesseltracker.com GmbH
Rödingsmarkt 20,
20459 Hamburg, Germany

+49-(0)40-970786-10
info@vesseltracker.com

Über

DatenschutzerklärungGeneral Terms and ConditionsTerms of useImprintContact

Explore

ProdukteSchiffeHäfenNewsÜberCommunity

Social

 

© vesseltracker 

Log in

Haben Sie Ihr Passwort vergessen? Reset

Noch kein account? Registrieren

Phishing - Warnung:

In sozialen Medien sind Links aufgetaucht, die einen kostenlosen Trial-Zugang zu vesseltracker versprechen. Die verlinkte Webseite wird für phishing benutzt und versucht, Zugangsdaten von vesseltracker Usern zu stehlen.

Bitte beachten Sie die folgenden Hinweise:

  • Loggen Sie sich nur auf den Original-Seiten (www.vesseltracker.com und cockpit.vesseltracker.com) ein
  • Stellen Sie sicher, dass sie ein grünes Schloss in der Adresszeile des Browsers sehen und dass es sich um eine sichere Verbindung handelt
  • Sollten Sie bereits ihre Zugangsdaten auf der falschen Seite eingegeben haben, ändern Sie bitte ihr Passwort. Um das zu tun, loggen Sie sich auf www.vesseltracker.com ein und klcken dann auf Ihren Usernamen => My Vesseltracker. Dort finden Sie die Möglichkeit, das Passwort zu ändern
  • Falls Sie weitere Fragen haben oder Hilfe beim Ändern des Passworts benötigen, schreiben Sie bitte an support@vesseltracker.com