GLOBAL ARSENAL
General cargo ship · Barbados · built 2008 · AIS Class A
In short
GLOBAL ARSENAL (General cargo ship, Barbados flag) was last seen on AIS on , at anchor, near Bari (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 IT BRI (Bari); its reported draught is 10.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 22:39 UTC). ISM manager: AB BULKERS GROUP LTD. (source: EU MRV (THETIS-MRV) emissions, reporting years 2024–2025).
- Vessel type
- General cargo ship
- Flag
- Barbados
- Year built
- 2008
- Gross tonnage
- 20,236
- Size (length × beam)
- 177 m × 28 m
- ISM manager
- AB BULKERS GROUP LTD.
Watch this ship
GLOBAL ARSENAL 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
- 41.1519° N, 16.8901° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 0 kn
- Course
- 0°
- Heading
- 259°
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
- GLOBAL ARSENAL
- IMO numberWhat is an IMO number?
- 9363302
- MMSIWhat is an MMSI?
- 314862000
- Call signWhat is a call sign?
- 8PAB2
- Flag
- Barbados
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 20,236
- Deadweight (DWT)
- Source: Wikidata, record Q105765961. Added to Voydar on September 23, 2026. Licence: CC0 1.0.32,313 t
- Length overall
- 177.1 m
- Beam
- 28.4 m
- Year built
- 2008
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 years 2024–2025 · reported · confidence 0.9 · retrieved Oct 5, 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 |
|---|---|---|
| Call sign changed from 8PAB2 to DATAHUB | AIS, seen by Voydar | |
| Reported departure from VancouverAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at VancouverAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from PortlandAuthority-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.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Mar 30, 2013衝突 · 貨物船運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports)宮崎県日向市細島港内 細島港余島防波堤灯台から真方位032°285m付近
貨物船GLOBAL SERENITY漁船新戎丸衝突Report published Jan 31, 2014
A船は、船長Aほか20人が乗り組み、水先人Aが水先し、細島港の航路を出航して約5.5ノット(kn)の速力(対地速力、以下同じ。)で東進した。 水先人Aは、船橋前部中央のレピータコンパスの左側に立ち、同コンパスの右側に立つ船長A、左舷後方の機関制御盤の後部で機関操作を行う三等航海士A及び中央後方の操舵スタンドで手動操舵に当たる甲板員Aに指示を出しながら、航行を続けた。 水先人Aは、余島防波堤東方沖を北西進するB船を認め、B船がA船の船首に接近することを予測し、汽笛スイッチを押したが、汽笛が吹鳴しなかったものの、港内では漁船が接近してから避航することがよくあるので、B船がA船を避けるものと思い、予定地点で右転すれば、更にB船に接近することとなるので、右転せず、東進を続けた。 水先人Aは、B船が接近し、船首の右舷側に隠れ、左舷側から出た後、航行を続けていたので、衝突は避けられたと思い、港外の下船
Source: 運輸安全委員会 船舶事故等調査報告書 (JTSB marine accident and incident reports). 出典:運輸安全委員会「船舶事故等調査報告書」(https://jtsb.mlit.go.jp/)。Seadar が項目を抽出・加工して作成 (Source: Japan Transport Safety Board marine accident reports; fields extracted and edited by Seadar). Licence: Public Data License 1.0 (公共データ利用規約 第1.0版, PDL1.0; compatible with CC BY 4.0).
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 |
|---|---|---|---|---|
| 2024 | 3,857 t | 1,236 t | 71 days | 228 kg |
| 2025 | 1,749 t | 555 t | 29 days | 212 kg |
Technical efficiency: EEXI (6.64 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 |
|---|---|---|---|---|
| Vancouver USVAN | Departure | Dec 18, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Vancouver USVAN | Arrival | Dec 3, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Jun 18, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Astoria USAST | Arrival | Jun 14, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Feb 7, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Astoria USAST | Arrival | Jan 29, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Jun 3, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Astoria USAST | Arrival | May 26, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Departure | Feb 19, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Portland USPDX | Arrival | Feb 2, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Departure | Jan 25, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Long Beach USLGB | Arrival | Jan 25, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: February 24, 2009.
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 4, 2026, 17:46 UTC | Two positions This MMSI was reported in two places 555 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 16:46 UTC | Two positions This MMSI was reported in two places 550 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 16:18 UTC | Two positions This MMSI was reported in two places 546 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
| Oct 4, 2026, 15:48 UTC | Two positions This MMSI was reported in two places 543 km apart at the same time: two transmitters may share the number, or the positions were disturbed. Method seadar.behaviour.mmsi_conflict v1 | Medium (70%) |
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 GLOBAL ARSENAL now?
- GLOBAL ARSENAL (General cargo ship, Barbados flag) was last seen on AIS on Oct 5, 2026, 22:38 UTC, at anchor, near Bari (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 IT BRI (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 22:39 UTC). This report does not confirm the ship’s current route.
- What kind of ship is GLOBAL ARSENAL?
- GLOBAL ARSENAL is a general cargo ship sailing under the flag of Barbados, built in 2008. The vessel is 177.1 m long with a beam of 28.4 m and has a gross tonnage of 20,236.
- Who is recorded as the owner or manager of GLOBAL ARSENAL?
- AB BULKERS GROUP LTD. is recorded as ISM manager for GLOBAL ARSENAL (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 GLOBAL ARSENAL?
- Voydar has no matched sanctions record displayed for GLOBAL ARSENAL 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 GLOBAL ARSENAL. 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/9363302Using 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.