MSC BHAVYA V
Container ship · Liberia · built 2005 · AIS Class A
In short
MSC BHAVYA V (Container ship, Liberia flag) was last seen on AIS on , under way at 16.7 kn, in the Mediterranean Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is PTSIE (Sines), with an ETA of Oct 6, 2026, 22:00 UTC; its reported draught is 13.4 m (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 15:25 UTC). ISM manager: MSC Shipmanagement Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Gioia Tauro (departed Oct 3, 2026, 11:07 UTC) to PTSIE (Sines)
- Vessel type
- Container ship
- Flag
- Liberia
- Year built
- 2005
- Gross tonnage
- 54,771
- Size (length × beam)
- 294 m × 32 m
- ISM manager
- MSC Shipmanagement Ltd
Watch this ship
Get an email when MSC BHAVYA V reaches Sines, and when it leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows MSC BHAVYA V.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.
Last reported position
received- Position
- 38.3783° N, 12.338° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 16.7 kn
- Course
- 264°
- Heading
- 262°
Last 30 days: 2 port calls (Gioia Tauro and Drapetzona).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)
Try the live demo, no sign-upIdentity & particulars
- Name
- MSC BHAVYA V
- IMO numberWhat is an IMO number?
- 9297876
- MMSIWhat is an MMSI?
- 636016423
- Call signWhat is a call sign?
- D5GC9
- Flag
- Liberia
- AIS ship type
- Cargo (hazardous cat. D)
- Gross tonnageGross tonnage vs deadweight
- 54,771
- Deadweight (DWT)
- Source: Wikidata, record Q84264448. Added to Voydar on September 23, 2026. Licence: CC0 1.0.66,799 t
- Length overall
- 294.1 m
- Beam
- 32.3 m
- Year built
- 2005
A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026MSC Shipmanagement(not linked to a company record)Source: Wikidata · reported · confidence 0.6 · retrieved Jun 10, 2026
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–2025 · reported · confidence 0.9 · retrieved Sep 28, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Timeline
Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Left Gioia TauroAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Gioia TauroAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left DrapetzonaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at DrapetzonaAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at Long BeachAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from Long BeachAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at OaklandAuthority-reported | USACE foreign traffic vessel entrances & clearances |
Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 82,357 t | 26,390 t | 263 days | 763 kg |
| 2019 | 84,920 t | 27,212 t | 270 days | 730 kg |
| 2020 | 58,757 t | 18,607 t | 234 days | 666 kg |
| 2021 | 22,692 t | 7,184 t | 101 days | 634 kg |
| 2022 | 13,399 t | 4,239 t | 67 days | 574 kg |
| 2023 | 24,199 t | 7,695 t | 151 days | 503 kg |
| 2024 | 38,345 t | 12,298 t | 219 days | 537 kg |
| 2025 | 31,397 t | 10,059 t | 161 days | 575 kg |
Technical efficiency: EEXI (9.43 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
Port calls
Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Gioia Tauro ITGIT | Oct 2, 2026, 12:42 UTC | Oct 3, 2026, 11:07 UTC | 22 h 25 min |
| Drapetzona GRDPA | Sep 15, 2026, 04:06 UTC | Oct 2, 2026, 12:42 UTC | 17 d 8 h |
Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Long Beach USLGB | Arrival | Aug 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Aug 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Aug 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Aug 6, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Departure | Aug 3, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Seattle USSEA | Arrival | Aug 2, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Arrival | Jul 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Oakland USOAK | Departure | Jul 29, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Jul 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Jul 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Arrival | May 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Los Angeles USLAX | Departure | May 30, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 17, 2006.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Behaviour at sea Voydar-derived
Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.
| When | What we observed | Confidence |
|---|---|---|
| Oct 3, 2026, 03:33 UTC | Draught change Reported draught went from 12.2 m to 13.5 m while in port at Gioia Tauro. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 28, 2026, 05:43 UTC | Draught change Reported draught went from 9.1 m to 10.1 m while in port at Drapetzona. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.
Frequently asked questions
- Where is MSC BHAVYA V now?
- MSC BHAVYA V (Container ship, Liberia flag) was last seen on AIS on Oct 3, 2026, 20:43 UTC, under way at 16.7 kn, in the Mediterranean Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was PTSIE (voyage report via AISstream.io global terrestrial AIS, received Oct 3, 2026, 15:25 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MSC BHAVYA V?
- MSC BHAVYA V is a container ship sailing under the flag of Liberia, built in 2005 by HD Hyundai Samho. The vessel is 294.1 m long with a beam of 32.3 m and has a gross tonnage of 54,771.
- Who is recorded as the owner or manager of MSC BHAVYA V?
- MSC Shipmanagement Ltd is recorded as ISM manager for MSC BHAVYA V (source: EU MRV (THETIS-MRV) emissions; reporting years 2024–2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for MSC BHAVYA V?
- Voydar has no matched sanctions record displayed for MSC BHAVYA V from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for MSC BHAVYA V. Missing records do not establish whether the ship has been detained.
Use this data
This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.
GET /api/v1/vessels/9297876Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.