MSC Nitya B
Container ship · Portugal · built 2017 · AIS Class A
In short
MSC Nitya B (Container ship, Portugal flag) was last seen on AIS on , under way at 18.4 kn, in the North Atlantic Ocean. 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 PACTB (Cristobal), with an ETA of Oct 8, 2026, 15:00 UTC; its reported draught is 14.6 m (voyage report via AISstream.io global terrestrial AIS, received Sep 28, 2026, 08:06 UTC). ISM manager: MSC Shipmanagement Ltd (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
Current voyage: from Sines (departed Sep 28, 2026, 03:34 UTC) to PACTB (Cristobal)
- Vessel type
- Container ship
- Flag
- Portugal
- Year built
- 2017
- Gross tonnage
- 113,112
- Size (length × beam)
- 330 m × 48 m
- ISM manager
- MSC Shipmanagement Ltd
Watch this ship
MSC Nitya B has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.
We email you a link and a code. That creates a free account, no password or card, and follows MSC Nitya B.
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
- 37.4767° N, 10.7306° W
- Area
- North Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 18.4 kn
- Course
- 266°
- Heading
- 266°
Last 30 days: 1 port call (Sines).
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 Nitya B
- IMO numberWhat is an IMO number?
- 9778117
- MMSIWhat is an MMSI?
- 255806029
- Call signWhat is a call sign?
- CQIP4
- Flag
- Portugal
- Vessel type
- Detailed type from WikidataContainer ship
- AIS ship type
- Cargo (hazardous cat. A)
- Gross tonnageGross tonnage vs deadweight
- 113,112
- Deadweight (DWT)
- Source: Wikidata, record Q84264313. Added to Voydar on September 23, 2026. Licence: CC0 1.0.134,007 t
- Length overall
- 330 m
- Beam
- 48.3 m
- Year built
- 2017
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 8, 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 SinesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at SinesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Port State Control inspection at Seattle, Washington | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Port State Control inspection at PHILADELPHIA, Pennsylvania | USCG PSIX / CGMIX inspections | |
| Inspection at PHILADELPHIA, Pennsylvania | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at PHILADELPHIA, Pennsylvania | USCG PSIX / CGMIX inspections |
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.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Jun 17, 2025 | Vessel InspectionPSC | Seattle, Washington | clean |
| Mar 20, 2023 | Vessel InspectionPSC | Seattle, Washington | clean |
| Jun 21, 2021 | Vessel InspectionPSC | San Pedro, California | clean |
| Apr 8, 2019 | Vessel InspectionPSC | PHILADELPHIA, Pennsylvania | clean |
| Apr 25, 2018 | Vessel Inspection | PHILADELPHIA, Pennsylvania | clean |
| Feb 26, 2018 | Vessel InspectionPSC | PHILADELPHIA, Pennsylvania | clean |
Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.
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 | 43,210 t | 13,831 t | 140 days | 881 kg |
| 2019 | 23,376 t | 7,480 t | 74 days | 835 kg |
| 2020 | 46,652 t | 14,976 t | 148 days | 872 kg |
| 2021 | 47,199 t | 15,149 t | 122 days | 954 kg |
| 2022 | 32,312 t | 10,362 t | 99 days | 933 kg |
| 2023 | 39,536 t | 12,690 t | 154 days | 825 kg |
| 2024 | 23,879 t | 7,655 t | 67 days | 907 kg |
| 2025 | 23,755 t | 7,601 t | 67 days | 938 kg |
Technical efficiency: EEXI (8.22 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 |
|---|---|---|---|
| Sines PTSIE | Sep 27, 2026, 02:32 UTC | Sep 28, 2026, 03:34 UTC | 25 h 1 min |
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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Jan 10, 2026, 12:47 UTC | KC5 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jan 15, 2025, 09:08 UTC | KC19 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 24, 2019, 15:44 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: December 24, 2019.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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 |
|---|---|---|
| Sep 27, 2026, 05:54 UTC | Draught change Reported draught went from 13.1 m to 14.6 m while in port at Sines. 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 Nitya B now?
- MSC Nitya B (Container ship, Portugal flag) was last seen on AIS on Sep 28, 2026, 09:04 UTC, under way at 18.4 kn, in the North Atlantic Ocean. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was PACTB (voyage report via AISstream.io global terrestrial AIS, received Sep 28, 2026, 08:06 UTC). This report does not confirm the ship’s current route.
- What kind of ship is MSC Nitya B?
- MSC Nitya B is a container ship sailing under the flag of Portugal, built in 2017 by HHIC Phil. The vessel is 330 m long with a beam of 48.3 m and has a gross tonnage of 113,112.
- Who is recorded as the owner or manager of MSC Nitya B?
- MSC Shipmanagement Ltd is recorded as ISM manager for MSC Nitya B (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 Nitya B?
- Voydar has no matched sanctions record displayed for MSC Nitya B 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. MSC Nitya B has 6 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
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/9778117Using 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.