SANTA CATARINA EXP
Container ship · Singapore · built 2018 · AIS Class A
In short
SANTA CATARINA EXP (Container ship, Singapore flag) was last seen on AIS on , under way at 12 kn, near Santos (South 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 SINGAPORE, with an ETA of Oct 16, 2026, 08:00 UTC; its reported draught is 14.5 m (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 07:33 UTC). ISM manager: Seaspan Ship Management Ltd. (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- Container ship
- Flag
- Singapore
- Year built
- 2018
- Gross tonnage
- 113,828
- Size (length × beam)
- 330 m × 48 m
- ISM manager
- Seaspan Ship Management Ltd.
Watch this ship
SANTA CATARINA EXP 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.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 24.0876° S, 46.3721° W
- Area
- South Atlantic Ocean
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 12 kn
- Course
- 202°
- Heading
- 202°
Voydar detected no port call in the last 30 days.
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- SANTA CATARINA EXP
- IMO numberWhat is an IMO number?
- 9793911
- MMSIWhat is an MMSI?
- 563282400
- Call signWhat is a call sign?
- 9V5019
- Flag
- Singapore
- AIS ship type
- Cargo (hazardous cat. D)
- Gross tonnageGross tonnage vs deadweight
- 113,828
- Deadweight (DWT)
- Source: Wikidata, record Q104378036. Added to Voydar on September 23, 2026. Licence: CC0 1.0.132,584 t
- Length overall
- 330 m
- Beam
- 48 m
- Year built
- 2018
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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 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 |
|---|---|---|
| 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) | |
| 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) | |
| 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) |
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 |
|---|---|---|---|---|
| 2025 | 7,711 t | 2,501 t | 34 days | 616 kg |
Technical efficiency: EEXI (8.46 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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Aug 1, 2026, 20:30 UTC | KWAICHUNG CONTR. BERTH NO.17 (TERMINAL 9) | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 13, 2026, 20:19 UTC | KC19 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 18, 2026, 10:00 UTC | KC5 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 5, 2026, 08:46 UTC | KC5 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 1, 2025, 13:57 UTC | KC2 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Mar 24, 2025, 04:16 UTC | KC5 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 29, 2024, 23:45 UTC | KC17 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Oct 4, 2024, 04:50 UTC | KC5 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jul 12, 2024, 15:08 UTC | KC2 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Apr 6, 2024, 18:40 UTC | KC19 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Jan 15, 2024, 23:39 UTC | KC | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Nov 3, 2023, 15:16 UTC | KC2 | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
Records published by the authority named on each row. Earliest record for this ship: December 20, 2019.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Frequently asked questions
- Where is SANTA CATARINA EXP now?
- SANTA CATARINA EXP (Container ship, Singapore flag) was last seen on AIS on Sep 26, 2026, 07:54 UTC, under way at 12 kn, near Santos (South 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 SINGAPORE (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 07:33 UTC). This report does not confirm the ship’s current route.
- What kind of ship is SANTA CATARINA EXP?
- SANTA CATARINA EXP is a container ship sailing under the flag of Singapore, built in 2018 by Jiangsu Yangzi Xinfu Shipbuilding. The vessel is 330 m long with a beam of 48 m and has a gross tonnage of 113,828.
- Who is recorded as the owner or manager of SANTA CATARINA EXP?
- Seaspan Ship Management Ltd. is recorded as ISM manager for SANTA CATARINA EXP (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for SANTA CATARINA EXP?
- Voydar has no matched sanctions record displayed for SANTA CATARINA EXP 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 SANTA CATARINA EXP. 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/9793911Using 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.