What Crew Members Say About Sestroretsk
IMO: 7801867
General Cargo Ship, Russia
Photos
Vessel Details
MMSI
273343110
Callsign
UBWJ
Width
16.0 m
Length
128.0 m
Reviews (1)
Harold
2025-04-17
Position: Second Engineer
Advantages:
Looking for information about this vessel. Looking for info about this ship? Was the crew alright?
Disadvantages:
No personal experience yet, just gathering info.
Latest News (2)
Bunker Tanker Collision on Volga–Caspian Sea Canal
On November 6, 2016, the cargo vessel 'Setroretsk' was involved in a maritime incident with the Russian bunker and oil recovery barge 'Kolonok 139', which has a gross tonnage of 118 gt and is identified by MMSI: 273347180. The collision occurred at the 17 km marker on the Volga–Caspian Sea Canal. Fortunately, both vessels sustained only minor damages. Following the incident, they were anchored to allow for a thorough investigation. The cargo ship 'Setroretsk' was able to continue its journey to Azov later that same day.
General Cargo Vessel Sestroretsk Runs Aground on the Volga River
On the morning of August 8, 2012, the general cargo vessel Sestroretsk encountered trouble and ran aground at the 2784.7 kilometer mark of the Volga River. The vessel was en route from Turkey to Astrakhan, Russia, carrying a load of general cargo. Efforts to refloat the vessel using its own means have thus far proven unsuccessful. For updates on the situation, refer to the Maritime Bulletin at http://www.odin.tc.
Frequently Asked Questions
💥 Was Sestroretsk involved in any collisions?
Based on available news reports, Sestroretsk has been mentioned in connection with collision-related incidents. There have been 1 news reports mentioning collisions. For detailed information about specific incidents, please refer to the latest news section above.
🛢️ Did Sestroretsk have any oil spills or pollution incidents?
Based on available news reports, Sestroretsk has been mentioned in connection with spill-related incidents. There have been 1 news reports mentioning spills. For detailed information about specific incidents, please refer to the latest news section above.