Far Eastern Jupiter
Bulk carrier · Hong Kong · built 2007 · AIS Class A
In short
Far Eastern Jupiter (Bulk carrier, Hong Kong flag) was last seen on AIS on , moored, in the port of Gdansk. Its crew-entered AIS destination is GDANSK; its reported draught is 8.2 m (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 05:46 UTC). It arrived there on Oct 2, 2026, 21:42 UTC. ISM manager: TOSCO KEYMAX INTERNATIONAL SHIP MANAGEMENT CO.,LTD (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- Bulk carrier
- Flag
- Hong Kong
- Year built
- 2007
- Gross tonnage
- 43,158
- Size (length × beam)
- 229 m × 32 m
Watch this ship
Get an email when Far Eastern Jupiter arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
Free forever. No card. A free account follows up to 5 ships and ports.
Last reported position
received- Position
- 54.3869° N, 18.6717° E
- Area
- Baltic Sea
- StatusWhat do AIS statuses mean?
- Moored
- Speed
- 0 kn
- Course
- 275°
- Heading
- 164°
Last 30 days: 1 port call (Gdansk).
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
- Far Eastern Jupiter
- IMO numberWhat is an IMO number?
- 9442768
- MMSIWhat is an MMSI?
- 477826400
- Call signWhat is a call sign?
- VRGZ6
- Flag
- Hong Kong
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 43,158
- Deadweight (DWT)
- Source: Wikidata, record Q86061735. Added to Voydar on September 23, 2026. Licence: CC0 1.0.82,655 t
- Length overall
- 229 m
- Beam
- 32.3 m
- Year built
- 2007
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 |
|---|---|---|
| Arrived at GdanskAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at GdanskAuthority-reported | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) | |
| Reported departure from ELIZABETH RIVER, VAAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at CHESAPEAKE BAY, MD AND VAAuthority-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 | 1,521 t | 486 t | 27 days | 345 kg |
| 2019 | 3,152 t | 1,010 t | 35 days | 302 kg |
| 2020 | 7,870 t | 2,516 t | 93 days | 333 kg |
| 2023 | 2,567 t | 822 t | 26 days | 342 kg |
| 2025 | 3,783 t | 1,198 t | 44 days | 309 kg |
Technical efficiency: EEXI (3.47 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 |
|---|---|---|---|
| Gdansk PLGDN | Oct 2, 2026, 21:42 UTC | in port | — |
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 |
|---|---|---|---|---|
| Gdansk PLGDN | Arrival | Oct 2, 2026, 20:45 UTC | Rudowe | Urząd Morski w Gdyni: ships in port, expected and departing (Gdynia, Gdańsk) |
| ELIZABETH RIVER, VA | Departure | Apr 15, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Mar 30, 2011(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Oct 9, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| CHESAPEAKE BAY, MD AND VA | Arrival | Sep 29, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Aug 15, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Arrival | Aug 15, 2010(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Departure | Oct 13, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Arrival | Oct 5, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Departure | Apr 11, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Newport News USNNS | Arrival | Apr 11, 2009(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ELIZABETH RIVER, VA | Departure | Sep 4, 2008(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: January 7, 2008.
Source: Urząd Morski w Gdyni (www.umgdy.gov.pl); processed by Seadar (times converted to UTC, IMO checksum-validated). The retrieval date is shown with the data. Licence: Polish PSI reuse (ustawa o otwartych danych), conditions: cite source, date, processing.
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 Far Eastern Jupiter now?
- Far Eastern Jupiter (Bulk carrier, Hong Kong flag) was last seen on AIS on Oct 5, 2026, 05:54 UTC, moored, in the port of Gdansk. The crew-entered destination was GDANSK (voyage report via AISstream.io global terrestrial AIS, received Oct 5, 2026, 05:46 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Far Eastern Jupiter?
- Far Eastern Jupiter is a bulk carrier sailing under the flag of Hong Kong, built in 2007 by Tsuneishi Shipbuilding. The vessel is 229 m long with a beam of 32.3 m and has a gross tonnage of 43,158.
- Who is recorded as the owner or manager of Far Eastern Jupiter?
- TOSCO KEYMAX INTERNATIONAL SHIP MANAGEMENT CO.,LTD is recorded as ISM manager for Far Eastern Jupiter (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 Far Eastern Jupiter?
- Voydar has no matched sanctions record displayed for Far Eastern Jupiter 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 Far Eastern Jupiter. 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/9442768Using 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.