TRAVERSE SINGAPORE
Bulk carrier · Bahamas · built 2005 · AIS Class A
In short
TRAVERSE SINGAPORE (Bulk carrier, Bahamas flag) was last seen on AIS on , under way at 11.2 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 PORTSAID; its reported draught is 14 m (voyage report via AISstream.io global terrestrial AIS, received Sep 29, 2026, 06:02 UTC).
- Vessel type
- Bulk carrier
- Flag
- Bahamas
- Year built
- 2005
- Gross tonnage
- 39,738
- Size (length × beam)
- 225 m
- Registered owner
- —
Watch this ship
TRAVERSE SINGAPORE 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
- 37.3568° N, 4.6889° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.2 kn
- Course
- 86°
- Heading
- 87°
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
- TRAVERSE SINGAPORE
- IMO numberWhat is an IMO number?
- 9342865
- MMSIWhat is an MMSI?
- 311002275
- Call signWhat is a call sign?
- 3EDM7
- Flag
- Bahamas
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 39,738
- Length overall
- 224.9 m
- Beam
- —
- 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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 2026Source: EU MRV (THETIS-MRV) emissions · reporting years 2024–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 |
|---|---|---|
| ISM manager: GOLDENKING SHIP MANAGEMENT(GUANGZHOU) CO., LTD (previously Navios Maritime Management Inc) | Voydar relationship-change derivation (derived by Voydar from EU MRV (THETIS-MRV) emissions) | |
| 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 PORT OF SOUTH LOUISIANA (LA)Authority-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 | 3,810 t | 1,213 t | 39 days | 328 kg |
| 2019 | 4,187 t | 1,343 t | 43 days | 318 kg |
| 2020 | 6,389 t | 2,044 t | 84 days | 287 kg |
| 2023 | 8,788 t | 2,812 t | 118 days | 315 kg |
| 2024 | 3,128 t | 999 t | 47 days | 307 kg |
| 2025 | 5,847 t | 1,865 t | 77 days | 302 kg |
Technical efficiency: EEXI (3.6 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 | Jan 13, 2023, 17:42 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Hong Kong HKHKG | Arrival | Dec 12, 2022, 21:10 UTC | SELA | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Sep 15, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF PLAQUEMINES, LA | Arrival | Sep 4, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Departure | Aug 11, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| OTHER SAN FRANCISCO BAY AREA PORTS, CA (NET) | Arrival | Jul 21, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Departure | Jan 22, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SAN JOAQUIN RIVER, CA (INCLUDING COMMERCE OF PORT OF STOCKTON, CA) | Arrival | Jan 17, 2015(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Longview USLOG | Departure | Oct 23, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Longview USLOG | Arrival | Oct 18, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Oct 15, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Oct 13, 2013(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: October 5, 2006.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is TRAVERSE SINGAPORE now?
- TRAVERSE SINGAPORE (Bulk carrier, Bahamas flag) was last seen on AIS on Sep 29, 2026, 07:44 UTC, under way at 11.2 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 PORTSAID (voyage report via AISstream.io global terrestrial AIS, received Sep 29, 2026, 06:02 UTC). This report does not confirm the ship’s current route.
- What kind of ship is TRAVERSE SINGAPORE?
- TRAVERSE SINGAPORE is a bulk carrier sailing under the flag of Bahamas, built in 2005 by Imabari Shipbuilding Marugame Headquarters. The vessel is 224.9 m long and has a gross tonnage of 39,738.
- What sanctions and inspection records does Voydar hold for TRAVERSE SINGAPORE?
- Voydar has no matched sanctions record displayed for TRAVERSE SINGAPORE 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 TRAVERSE SINGAPORE. 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/9342865Using 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.