Hagland-Boss Ship Details and Seafarer Feedback
IMO: 9171058
Multi Purpose Carrier, Malta
Photos
Vessel Details
MMSI
249934000
Callsign
9HLE5
Width
12.0 m
Length
88.0 m
Reviews (1)
Joshua
2025-04-08
Position: Fitter
Advantages:
Looking for information about this vessel. Any thoughts on this vessel? Good food and quarters?
Disadvantages:
No personal experience yet, just gathering info.
Latest News (3)
Hagland Boss Grounded Near Glatved, Refloated and Resumed Voyage
On May 25, 2021, at approximately 3 p.m., the cargo vessel 'Hagland Boss' experienced a grounding incident as it was navigating near the port of Glatved, having departed from Oxelösund. Fortunately, the vessel was refloated with the assistance of tugboats and successfully docked in Grenaa by 11 p.m. Subsequent inspections revealed no damage to the ship, allowing port authorities to approve its departure. The 'Hagland Boss' then continued its journey to Malmö, arriving at the early hours of May 27 at 2 a.m.
Cargo Ship Rescues Asylum Seeker Lost at Sea
On May 1, 2020, the 'Hagland Boss', a cargo vessel traveling from Ystad to Haugesund, provided a lifesaving act of compassion by rescuing an asylum seeker found adrift on a sailing yacht in the Skagerrak Strait. The man had launched his journey from Sweden days earlier but had encountered treacherous weather that left his boat incapacitated. Exhausted and vulnerable, he was spotted and subsequently assisted by the NSSR lifeboat, 'Inge Steensland', along with local police who arrived on the scene to facilitate his recovery. The rescued individual was safely taken to Arendal for medical attention. The 'Hagland Boss' continued its journey and was anchored off Husoy Island by May 2. This incident highlights the critical importance of maritime safety and the humanitarian responses at sea. For more visuals and a detailed report, visit: https://www.vg.no/nyheter/i/EWebqA/mann-i-seilbaat-reddet-sa-han-var-asylsoeker
Hagland Boss Rescued After Grounding Incident in Oslo Fjord
In the early hours of November 6, 2016, the cargo vessel 'Hagland Boss' ran aground near Langøya in the outer reaches of the Oslo Fjord. Following the incident, which resulted in damage to the ship's rudder and propeller—albeit with no reported leaks—emergency measures were swiftly enacted. The ship had just departed Langøya after completing its cargo unloading when it experienced significant maneuverability issues at around 2 a.m. as it approached Holmestrand, ultimately becoming grounded. To facilitate a safe recovery, the tugboat 'Boa Sund' (IMO: 7500798) was summoned to the scene. The towing operation commenced promptly, with 'Hagland Boss' being navigated towards Frederikshavn. The operation was successful, and by the evening of November 7, the ship was secured at the Orskov Yard at approximately 5:30 p.m., where it is now set for necessary repairs.
Frequently Asked Questions
🤕 Were there any injuries or accidents on Hagland-Boss?
Based on available news reports, Hagland-Boss has been mentioned in connection with injury-related incidents. There have been 1 news reports mentioning injury incidents. For detailed information about specific incidents, please refer to the latest news section above.
⚙️ Did Hagland-Boss have any engine problems?
Based on available news reports, Hagland-Boss has been mentioned in connection with engine-related incidents. There have been 1 news reports mentioning engine problems. For detailed information about specific incidents, please refer to the latest news section above.
🧑‍🚒 Was Hagland-Boss involved in any migrant rescue operations?
Based on available news reports, Hagland-Boss has been mentioned in connection with migrant-related incidents. There have been 2 news reports mentioning migrant operations. For detailed information about specific incidents, please refer to the latest news section above.
🛢️ Did Hagland-Boss have any oil spills or pollution incidents?
Based on available news reports, Hagland-Boss 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.