← Back to list

The Epaminondas: Crew Feedback and Vessel Data

IMO: 9153862

Container Ship, Liberia

Photos

Epaminondas - Container Ship vessel registered in Liberia

Vessel Details

MMSI

636020350

Callsign

D5YU7

Width

42.0 m

Length

299.0 m

Reviews (1)

Nicholas

2023-09-30

Position: Deck Hand

Advantages:

Looking for information about this vessel. Has anyone worked on this vessel? Any red flags?

Disadvantages:

No personal experience yet, just gathering info.

Latest News (4)

Container ships damaged by Iranian gunboat despite permit to transit Strait of Hormuz

Apr 23, 2026 11:29

**Title: Container Ships Targeted by Iranian Gunboat Amid Permitted Transit in Strait of Hormuz** On April 22, 2026, at 6:55 AM Greek time, the container ship 'Epaminondas' became the victim of an unprovoked attack by an Iranian gunboat associated with the Islamic Revolutionary Guard Corps (IRGC). The incident occurred approximately 15 nautical miles northeast of Oman in the strategically vital Strait of Hormuz, resulting in considerable damage to the vessel's bridge. Despite having previously received authorization to navigate through the strait, the 'Epaminondas' faced aggression with no prior communication established via VHF radio before the gunboat opened fire. Thankfully, no fires or environmental harm ensued, and all crew members aboard reported safe. Authorities are now investigating the legitimacy of the authorization message, suspecting that it might not be genuine. After the attack, the vessel was seized and is currently being escorted to Iran. As of April 23, the 'Epaminondas' was anchored at coordinates 26° 57' N 056° 22' E. In a separate incident on the same day, a report from the UK Maritime Trade Operations (UKMTO) detailed that the container ship 'Euphoria' (IMO: 9235828) was also targeted. The 'Euphoria' was attacked at approximately 6:38 AM UTC, eight nautical miles west of Iran, as it began its outbound journey through the Strait of Hormuz, with Jeddah as its destined port. Fortunately, the crew aboard the 'Euphoria' remained unharmed, and no damage to the vessel was recorded. The ship was anchored at coordinates 25° 25' N 056° 37' E as of April 23. Furthermore, the 'MSC Francesca' (IMO: 9401116) was also pursued while attempting to exit the strait on April 22. This vessel was roughly six nautical miles off the Iranian coast when the IRGC ordered it to halt and drop anchor. Reports indicate damage to the hull and accommodation areas of the 'MSC Francesca,' which has now been seized and is heading to Iran. As of April 23, it was anchored at position 26° 29' N 056° 55' E. The UKMTO has alerted maritime traffic regarding a notable increase in suspicious activities within the Strait of Hormuz, urging all vessels to report any unusual encounters immediately. For additional coverage, a video of the incident is available [here](https://x.com/i/status/2047132446710247634).

Maersk Kalmar sailing again

Jul 05, 2013 14:41

The repairs of the collision damage of the "Maersk Kalmar",suffered in the accident with the "Conmar Avenue", was conpleted by Schiedam Yard in Rotterdam on July 3. The ship left the Wilton Port at 10 a.m. and docked at the Europe Port at 1.30 p.m. On July 4 around 6 p.m. it shifted to the APM Terminal before sailing towards the Suez Canal.

Repair at Damen Shiprepair in Schiedam due to start

May 16, 2013 10:28

The "Maersk Kalmar" left Bremerhaven on May 12 at 10.20 a.m. and berthed at the APM Terminal in Rotterdam on Apr 13 at 10.15 p.m. After the cargo was unloaded, it was expected at the Schiedam Yard of Damen Shiprepair Rotterdam on May 16 at 10 p.m. for repairs of the collision damage. The "Conmar Avenue" was undergoing repairs at Bredo Shipyard in Bremerhaven.

Six containers lost after collision went adrift on the Weser

May 08, 2013 09:26

After its collision with the "Conmar Avenue" around 4 p.m. on May 7 the "Maersk Kalmar" berthed at the Strom Quay in Bremerhaven at 5.20 p.m. Nonoe of its crew of 28 was hurt. The casualty command in Cuxhaven took over the on-scene-command at 6 p.m. An oil surveillance flight started, but no pollutants were reported. The "Conmar Avenue" which had run aground following the collision was pulled off by tugs at 6.30 p.m. and was docked at the Stromquay around 9.30 p.m. The ship had come from Kotka at the time of the accident. Its crew of 15 reained uninjured too. The ship, however, lost some containers from deck which were treated by on the whole five tugs which tried to get the boxes under control. The anti pollution vessel "Neuwerk" established a security zone. The emergence tug "Nordic" was dispatched for further assistance in the Weser estuary and was on site on May 8 at 1 a.m. The lost containers were to be recovered after daybreak on May 8. The Weser traffic was reopened for ships with a depth of up to 9,5 meters. During the night hours, six containers broke lose from the tugs in the strong current. Two were recovered by the "Neuwerk", but four went adrift in the wetlands and were surveyed by radar. The sonar ship "Zenit" of the Shipping Authority Bremerhaven was surveying the fairway of the Weser. Photos: http://www.havariekommando.de/presse/gallery.php.html?file=bildergalerie/2013_05_07/index.html&oid=7277&tsize=1 http://www.havariekommando.de/presse/gallery.php.html?file=bildergalerie/2013_05_07/DSC_0060.JPG&oid=7294&tsize=1#inhalt http://www.havariekommando.de/presse/gallery.php.html?file=bildergalerie/2013_05_07/DSC_0058.JPG&oid=7295&tsize=1#inhalt

Frequently Asked Questions

🔥 Were there any fires on Epaminondas?

Based on available news reports, Epaminondas has been mentioned in connection with fire-related incidents. There have been 1 news reports mentioning fire incidents. For detailed information about specific incidents, please refer to the latest news section above.

Fire Incident Reported

🤕 Were there any injuries or accidents on Epaminondas?

Based on available news reports, Epaminondas has been mentioned in connection with injury-related incidents. There have been 2 news reports mentioning injury incidents. For detailed information about specific incidents, please refer to the latest news section above.

Injury Incident Reported

🏴‍☠️ Was Epaminondas involved in any pirate attacks?

Based on available news reports, Epaminondas has been mentioned in connection with pirate-related incidents. There have been 1 news reports mentioning pirate attacks. For detailed information about specific incidents, please refer to the latest news section above.

Pirate Attack Reported

⚙️ Did Epaminondas have any engine problems?

Based on available news reports, Epaminondas has been mentioned in connection with engine-related incidents. There have been 2 news reports mentioning engine problems. For detailed information about specific incidents, please refer to the latest news section above.

Engine Problem Reported

💥 Was Epaminondas involved in any collisions?

Based on available news reports, Epaminondas has been mentioned in connection with collision-related incidents. There have been 3 news reports mentioning collisions. For detailed information about specific incidents, please refer to the latest news section above.

Collision Reported

🛢️ Did Epaminondas have any oil spills or pollution incidents?

Based on available news reports, Epaminondas 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.

Spill Incident Reported

🚓 Was Epaminondas detained or arrested?

Based on available news reports, Epaminondas has been mentioned in connection with detention-related incidents. There have been 1 news reports mentioning detentions. For detailed information about specific incidents, please refer to the latest news section above.

Detention Reported

Share Your Experience

Similar Vessels You Might Be Interested In

A2b-Ambition

A2b-Ambition

Container Ship

(1)
A2b-Comfort

A2b-Comfort

Container Ship

(1)
A2b-Energy

A2b-Energy

Container Ship

(1)
A2b-Future

A2b-Future

Container Ship

(1)