• 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

  • News
  • Schiffsmeldungen
  • Hafenmeldungen

Category

Accident/Casualty42895Misc. for Ports and Vessels38193Scrapped/Beached/Broken Up22715Sold/Decommissioned8590Charter Changed6738Pirate attack2065

NORDSTJERNEN

Casualty

On Aug 19, 2025, at 6:45 p.m.,the "Nordstjernen" ran aground on the Warnow embankment when moving astern from berth 8 in Warnemünde into the fairway. Due to a technical malfunction, the engine did not respond when trying to move forward, and as a result, the ship struck the embankment on the opposite river bank, at buoy 24. Since the "Nordstjernen" was subsequently regained the ability to move forwar, it approached the nearest berth 7 under its own power. The Ship Safety Department issued a sailing ban. Initial investigations revealed that a malfunction in the pneumatic control of the controllable-pitch propeller was the cause of thefailure. With the approval of the Maritime Transport Authority, the "Nordstjernen" was towed to berth 46 in Rostock's overseas port on Aug 20 at 1:30 a.m. by the tug 'Fairplay 55' (IMO: 9021124). The extent of the damage to the vessel has not yet been quantified; the investigation was ongoing.

Timsen
2025-08-20

OTARIA

Scrapped

Beached at Alang 19.08.25 https://www.facebook.com/intractibleren/videos/1514979453009314?idorvanity=6884293942

BerndU
2025-08-20

MT GURAABU

Sold/Decommissioned

Sold to Breakers

BerndU
2025-08-20

TENACITY VENTURE

Casualty

On Aug 14, 2025, the 'Tenacity Venture', enroute from Come by Chance, CN, to Constanta with a cargo of 90730 tons oil on board, suffered an engine failure while transiting the Bosphorus. Ship traffic passing through the strait was temporarily suspended in both directions. The tanker slowed down off Kandilli. The response was coordinated by the Istanbul Vessel Traffic Services Centre. Under the guidance of a strait pilot, the vessel was safely towed towards Büyükdere by the tugs 'Kurtarma 8' (IMO: 9598610), 'Kurtarma 5' (IMO: 9463164) and 'Kurtarma 11' (IMO: 9854399). The tanker was secured at the anchorage where it remained stationary in pos. 40° 56' N 028° 47' E as of Aug 20. No oil pollution was reported. Video: https://x.com/i/status/1956078099981906232

Timsen
2025-08-20

MARIE MAEUM7

Casualty

The 'Marie Maersk' was still destined towards Tanjung Pelapas, assisted by the tugs 'Med Rigel' (IMO: 1048530) 'Captain Cat' (IMO: 1048528), and 'SL Loire' (IMO: 9190494), and the fire fighting offshore vessel 'Troms Hera' (IMO: 9732967). The status of 'restricted manoeverability' and a speed of 0,8 knots in pos. 04° 08' N 010° 35' W, suggested it was adrift as of Aug 18 with an ETA given as of Sep 6. While the ship was operating the AE4 service under the Gemini Cooperation, smoke was detected emanating from containers stowed on deck early on Aug 13. According to Maersk, the crew had responded swiftly, activating the onboard firefighting systems. All personnel were reported safe. The 'Captain Cat' and 'Med Rigel' had arrived on scene late on Aug 13, joining efforts coordinated by Dutch salvage firm SMIT, which has deployed additional resources to assist.The plan was for external firefighters to board the 'MArie Mersk' on Aug 18 and assist. It is not yet known whether they will be flown in or brought aboard by ship. Meanwhile, the 'Marie Maersk' has been diverted to receive shore support as quickly as possible. The port of call was not yet known. There was not yet an estimate about the extent of the fire's impact on the cargo.

Timsen
2025-08-20

LOYAL

Misc. for ports and Vessels

The "Loyal" was detained on Aug 14, 2025, in Szczecin with 16 deficiencies, three of which being regarded as seriously and grounds for a detention: 1) Certificate & Doc - Civil liability for Bunker Oil Pollution Damage Cert Missing 2) Certificate & Doc - Civil liability for Oil Pollution Damage cert Missing 3) ISM - Ism certificate Not as required The vessel was released again on Aug 18 and left the port en route to the Jose Terminal in Venezuela with an ETA as of Sep 5. https://www.facebook.com/profile.php?id=100063576908591

Timsen
2025-08-20

G SPRING

Misc. for ports and Vessels

The 'G Spring' was detained again on Aug 12 in Jiaxing with five deficiencies, two of which being regarded as seriously and grounds for a detention: 1) Fire safety - Fire detection and alarm system Inoperative 2) Fire safety - Fire doors/openings in fire resisting division Not as required The vessel was released again on Aug 14 and proceeded to Singapore with an ETA as of Aug 23. The last detention was on April 18 in Jiangyin with five deficiencies for three days. https://www.facebook.com/profile.php?id=100063576908591

Timsen
2025-08-20

W-SAPPHIRE

Casualty

The U.S. Coast Guard has reopened the Fort McHenry Federal Channel in and out of the Port of Baltimore in cooperation with tugs, pilots, and other port partners to achieve this as quickly as possible. The response to the explosion aboard the 'W Sapphire', which had forced the temporary closure of the Fort McHenry Federal Channel, was continued. The U.S. Coast Guard determined the timing of vessel arrivals and departures. As of Aug 19, the Patapsco River had been closed to all vessel traffic between pos. 39°11.70’ N, 076°31.71’ W, near Swan Creek, and 39°12.6’ N, 076°29.74’ W, near Sparrows Point, extending up to the former location of the Francis Scott Key Bridge. Additionally, a 500-yard safety zone has been established around the vessel, which was anchored in pos. 39°01.4’ N, 076°22.10 ’W, north of the Chesapeake Bay Bridge. No injuries have been reported, and the fire has been extinguished. The cause of the explosion remained under investigation. The explosion detached a hatch which was blown into the water. Plans to locate and retrieve the hatch were under development, but its exact location and potential impact on the navigable channel remained unknown. The U.S. Army Corps of Engineers deployed thesonar-equipped survey vessel 'Buck' to the incident site at approximately 7:30 a.m. The 'Buck' started collecting data to identify any obstructions to the safe navigation of traffic entering or exiting the Port of Baltimore via the Fort McHenry Federal Channel. This data will help determine the operational plan needed to fully reopen the federal channel. Multiple agencies have joined the response effort, including Coast Guard Station Curtis Bay response boat crews, a Coast Guard Station Annapolis response boat crew, Sector Maryland – National Capital Region responders, Baltimore Fire Department crews, and Maryland Department of Natural Resources Police. The port officials s were working closely with the Coast Guard and port partners to monitor the situation. The safety zone previously established for all navigable waters of the Chesapeake Bay within a 2,000-yard radius of a detached hatch cover in pos. 39.20692° N, 76.51733° W has been discontinued. An intermittent safety zone will be activated for all navigable waters within a 500-yard radius of the hatch cover in pos. 39.20865° N, 76.52017° W during dive and salvage operations that were tentatively scheduled for on Aug 20 at 6:00 a.m. A 500-yard safety zone remained in effect around the 'W Sapphire' in pos. 39.02333° N, 76.36833° W. Mariners were advised to avoid this area.A draft restriction has been established for vessels transiting within a 500-yard radius of the detached hatch cover, now located in pos. 39.20865° N, 76.52017° W. Vessels were restricted to a maximum navigational draft of 46.6 feet due to the depth of 49.7 feet at Mean Lower Low Water (MLLW). Crews are awaiting verification to confirm safe conditions before proceeding with further Coast Guard investigations aboard the 'W Sapphire:. The Coast Guard and partner agencies continued to actively monitor the situation and coordinate recovery efforts to ensure the safety of maritime operations in the area. Reports with graphics: https://www.news.uscg.mil/Press-Releases/Article/4279781/coast-guard-updates-safety-zones-and-draft-restrictions-following-w-sapphire-in/ https://www.news.uscg.mil/Press-Releases/Article/4278939/update-coast-guard-partner-agencies-respond-to-vessel-explosion-in-baltimore-ha/

Timsen
2025-08-20

MSC PALERMO

Casualty

The legal woes for the MSC were continuing in India, with the Kerala High Court continuing to side with plaintiffs and attach MSC vessels such as the 'MSC Palermo' and 'MSC Makoto II' as collateral for the growing number of claims after the sinking of the 'MSC Elsa 3'. Twice, the court has ordered ships detained at the Vizhinjam Port pending a bond from MSC. On Aug 14, was the latest court hearing after six separate admiralty claims were filed. According to the court papers, the suits alleged that fishing nets, wire ropes, and other fishing material became entangled with debris from the 'MSC Elsa 3'. The court issued an interim order to detain the 'MSC Makoto II' at the port pending a bond. Four Indian fishermen simultaneously had filed claims with the High Court for damages incurred to their fishing vessels. According to the individual claims filed with the court, the four individuals said their vessels had been damaged by debris floating below the surface after the 'MSC Elsa 3' went down. They also said that debris had become entangled in their fishing nets, causing severe damage. They also included claims for lost metal chains, ropes, and other fishing gear. The filings were timed to the call of the 'MSC Palermo' at Vizhinjam. They demanded the arrest of the vessel, until their claims could be heard by the court. The High Court found for the plaintiffs and ordered the detention of the vessel at the port on Aug 12. The company’s representatives were able to post a bond against the claims. The vessel was released and resumed its voyage on Aug 13 en route to Sines with an ETA as of Sep 4. These, however, were the fourth and fifth times that the court had detained an MSC vessel due to claims. In June, the 'MSC Polo II' was briefly detained for a claim by the Cashew Board, and four days later, the 'MSC Manasa F' was also detained. Both times, the company was able to post bonds for the release of the ships. The 'MSC Akiteta II' was detained in relation to the $1 billion claim filed by the state. MSC has not posted a bond to release the ship, which was originally detained on July 8. The ship remained at the Vizhinjam port as of Aug 16 with little prospect of being released in the short term.

Timsen
2025-08-20

LOCHNEVIS

Casualty

Due to the ongoing issue of the 'Lochnevis', serving on the route Mallaig-Small Isles and still under repair in Greenock, the ferry 'Loch Bhrusda' and the charter vessel 'Miss Marley' operated a timetable for booked traffic on Aug 20. In addition, the charter vessel 'Larven' was operating a passenger only service in order to provide services to the Small Isle, some amendments were required to the Skye timetable to prevent berthing clashes in Mallaig. This impacted afternoon sailing by the 'Loch Fyne' as follows: Departure Armadale – 2:00 p.m. (previously 2:15 p.m); Arrival Mallaig – 2:45 p.m. (previously 3:00 p.m); Departure Mallaig – 3:00 p.m. (previously 3:15 p.m); Arrival Armadale – 3:45 p.m. (previously 4:00 p.m.); Departure Armadale – 4:00 p.m. (previously 4:15 p.m.); Arrival Mallaig – 4:45 p.m. (previously 5:00 p.m).

Timsen
2025-08-20

FALKEFJELL

Casualty

On Aug 19, 2025, at 5.30 p.m, the 'Falkefjell', enroute from Hammerfest to Alta, was in collision with a whale in Vargsundet, just north of Lille Lerresfjord, en route to Storekorsnes with ten passengers and three crew members on board. The ship suffered a total propulsion failure after the impact. There had been no sign of the whale on the surface before. The disabled highspeed ferry requested assistance. A service boat from a nearby fish farm was first sent to the casualty, The speedboat 'Hornøy', which was nearby at the time of the accident, took on board the passengers and transported them to Hammerfest. They were offered a hotel or a taxi to Alta. The NSSR lifeboat "Utvær" from the station in Alta was deployed by the MRCC to take the 'Falkefjell' in tow to the port of Hammerfest. No injuries have been reported, but the whale, from all indications, has died as a result of the collision. There was a lot of blood around it as it splashed around after the impact and then floated away. The damage to the 'Falkefjell' had yet to be assessed, but there was no water ingress. Reports with photos and video: https://www.nrk.no/tromsogfinnmark/hurtigbat-har-kjort-pa-hval-1.17534064 https://www.nettavisen.no/nyheter/emma-satt-pa-hurtigbaten-som-traff-hvalen-falt-a-se/s/5-95-2577586

Timsen
2025-08-20

MARIE MAEUM7

Casualty

The crew of the 'Marie Maersk', which was operating on the Gemini Cooperation’s Asia–Europe AE4 service. managed to contain the fire which was noticed on the morning of Aug 13, when smoke was detected coming from containers. The crew immediately began firefighting and managed to keep the situation under control. Over the weekend of Aug 16/17, the crew’s continuous firefighting stopped the blaze from spreading. The five external assets, besides the already mentioned vessels meanwhile also the 'Setareh' (IMO: 9768071 ), supported the operation. Firefighting efforts were expected to intensify once external firefighters have boarded the 'Marie Maersk' to take over part of the operation, giving some relief to the ship’s crew. The vessel was to be diverted to a port of refuge, which was still being considered, so that landside support can be secured quickly. The Maersk Crisis Response Team was in constant contact with the crew to provide guidance and assistance. For now, the impact on the cargo remained uncertain. Due to the conditions inside the affected cargo bays, it was not yet possible to confirm the extent of the damage. The contents of the affected containers will only be investigated once the fire has been fully extinguished. As of Aug 20, the ship was in pos. 04° 23' N 010° 31' W.

Timsen
2025-08-20

BOREAS LPG

Misc. for ports and Vessels

The "Boreas LPG" was detained on Aug 8, 2025, in Midia with 14 deficiencies, seven of which being regarded as seriously and grounds for a detention: 1) Certificate & Doc - Minimum safe manning doc Invalid 2) Certificate & Doc - Civil liability for Bunker Oil Pollution Damage Cert. Missing 3) Certificate & Doc - Liability for the removal of wrecks certificate Missing 4) Safety of navigation - Lights, shapes and sound-signals Missing 5) Safety of navigation - Nautical publications Expired 6) Emergency systems - Fire drills Lack of training 7) ISM - Ism certificate Not as required The vessel was released again on Aug 18 and left the port enroute to Izmail with an ETA as of Aug 19. https://www.facebook.com/profile.php?id=100063576908591

Timsen
2025-08-20

ISLE OF LEWIS

Casualty

The 'Isle of Lewis', serving on the route Oban-Castlebay, suffered an issue with the bow visor in the port of Oban on Aug 19. As a consequence, the scheduled 1.10 p.m. sailing from Oban iwas delayed. After the issue was resolved, the 'Isle Of Lewis' finally departed Oban at 2:00 p.m.

Timsen
2025-08-19

ATLANTIC TREASURE

Casualty

On the night of Aug 17, 2025, the 'Atlantic Treasure' started rapidly taking on water about 140 nautical miles off St. John's, on its way to the Grand Banks. A seawater pipe burst was thought to have caused the vessel to take on water faster than pumps could cope. The Skipper Noah Deveau and his crew tried everything to get the situation under control. The crew deployed two life-rafts as a precaution. Three people prepared all the safety gear while the rest of the eight-person crew worked to try to save the ship. The water was flooding the deck at the same time as the engine room, while the pumps were losing power, and the shgip was listing over hard. The crew moved to a life-raft while they still had functioning lights to guide them. Deveau had made contact with the Canadian Coast Guard out of Placentia, N.L., and other vessels, including the "Maid of Amsterdam" (MMSI: 316053143), another fishing vessel from Nova Scotia, which was 40 kilometres away. The fishermen had been wrapping up a 12-day trip to the Grand Banks for halibut and heading back to port in Cape Breton to beat the looming hurricane.The captain immediately turned around. It took three hours for the vessel to reach the life rafts. The weather was still unusually calm with a drizzle and only light wind.. With practiced maneuvers, the crew brought all castaways aboard early on Aug 18. Just hours later, Hurricane Erin was due to pass the coast with winds of up to 180 km/h. A Coastguard helicopter arrived on scene about 10 minutes after the rescue. The 'Atlantic Treasure' sank stern first, while the crews were still at the scene. Report with video: https://www.cbc.ca/news/canada/nova-scotia/fishing-rescue-coast-guad-1.7611603

Timsen
2025-08-20

MSC MAKOTO II

Casualty

The legal woes for the MSC were continuing in India, with the Kerala High Court continuing to side with plaintiffs and attach MSC vessels such as the 'MSC Palermo' and 'MSC Makoto II' as collateral for the growing number of claims after the sinking of the 'MSC Elsa 3'. Twice, the court has ordered the ships detained at the Vizhinjam Port pending a bond from MSC. On Aug 14, was the latest court hearing after six separate admiralty claims were filed. According to the court papers, the suits alleged that fishing nets, wire ropes, and other fishing material became entangled with debris from the 'MSC Elsa 3'. The court issued an interim order to detain the 'MSC Makoto II' at the port of Vizhinjam, pending a bond. Four Indian fishermen simultaneously had filed claims with the High Court for damages incurred to their fishing vessels. According to the individual claims filed with the court, the four individuals said their vessels had been damaged by debris floating below the surface after the 'MSC Elsa 3' went down. They also said that debris had become entangled in their fishing nets, causing severe damage. They also included claims for lost metal chains, ropes, and other fishing gear. The filings were timed to the call of the 'MSC Palermo' at Vizhinjam. They demanded the arrest of the vessel, until their claims could be heard by the court. The High Court found for the plaintiffs and ordered the detention of the vessel at the port on Aug 12. The company’s representatives were able to post a bond against the claims. The vessel was released and resumed its voyage on Aug 13. The 'MSC Makoto II' left Vizhinjam on Aug 16 en route to Haldia with an ETA as of Aug 20. These, however, were the fourth and fifth times that the court had detained an MSC vessel due to claims. In June, the 'MSC Polo II' was briefly detained for a claim by the Cashew Board, and four days later, the 'MSC Manasa F' was also detained. Both times, the company was able to post bonds for the release of the ships. The 'MSC Akiteta II' was detained in relation to the $1 billion claim filed by the state. MSC has not posted a bond to release the ship, which was originally detained on July 8. The ship remained at the Vizhinjam port as of Aug 16 with little prospect of being released in the short term.

Timsen
2025-08-20

GLEN SANNOX

Casualty

Due to a technical issue on the 'Glen Sannox', serving on the route Troon-Brodick, the passenger gangway was unavailable on Aug 20. As a result, foot passengers have been required to embark and disembark via the car deck at Troon until further notice.

Timsen
2025-08-20

OCEAN MAJESTY

Charter changed

After in June it was announced that the authorities were seeking a more cost-effective alternative for the “Ocean Majesty” as accommodation for asylum seekers, which would likely have meant the end for the 60-year-old ship, the Dutch authorities now have agreed with the owners on lower rates. This means that the “Ocean Majesty” will remain at a berth in Velse until at least July 1, 2026, with an option to extend until Dec 31 also been agreed upon. On Dec 4, 2025, the “Ocean Majesty” will celebrate the 60th birthday.

Timsen
2025-08-20

VOLGODON 79

Misc. for ports and Vessels

The "Volgodon 79" was detained on Aug 10, 2025, in Constanta with 27 deficiencies, 14 of which being regarded as seriously and grounds for a detention: 1) Fire safety - Ventilation' Missing 2) Safety of navigation - Compass correction log Missing 3) Safety of navigation - Charts Not updated 4) Safety of navigation - Nautical publications Expired 5) Safety of navigation - Navigation bridge visibility Not as required 6) Water/Weather - Covers (Hatchway,- portable-, tarpaulin etc) Corroded 7) Water/Weather - Doors Damaged 8)) Labour conditions - Heating, air conditioning and ventilation Inoperative 9) Structural conditions - Bulkheads, cracking Not as required 10) Structural conditions - Beams, frames, floors corrosion Corroded 11) Structural conditions - Stability/strength/loading information Missing 12) Radio communications - Radio log (diary) Not as required 13) Emergency systems - Fire drills Lack of training 14) ISM - Ism certificate Not as required The vessel was released again on Aug 15 and proceeded to the shipyard area in Tuzla, where it dropped anchor on Aug 17 and remained stationary as of Aug 20. https://www.facebook.com/profile.php?id=100063576908591

Timsen
2025-08-20

VULIN

Misc. for ports and Vessels

The "Vulin" was detained on Aug 4, 2025, in Seaham with 21 deficiencies, one of which being regarded as serious and ground for a detention: 1) ISM - Ism certificate Not as required The vessel was released again on Aug 12 and left the port again en route to Ghent, where it arrived on Aug 20. https://www.facebook.com/profile.php?id=100063576908591

Timsen
2025-08-20
  • «
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • »

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