Skip to content

Berge Shari

Bulk carrier · United Kingdom · built 2016 · AIS Class A

IMO9713208MMSI235116731Call sign2JKR3No AIS position on record

In short

Berge Shari (Bulk carrier, United Kingdom flag) has no AIS position on record with Voydar. ISM manager: Berge Bulk Maritime Pte. Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

Vessel type
Bulk carrier
Year built
2016
Gross tonnage
21,530
Size (length × beam)
180 m

Watch this ship

Berge Shari 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 Berge Shari.

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.

Photo of Berge Shari
Photo: Farid mernissi · Licence: CC BY-SA 4.0 · via Wikimedia Commons

Last reported position

No AIS position on record for this vessel. Identity and particulars are below.

Pro shows Berge Shari's track before the last 30 days. Voydar has recorded its port calls since June 15, 2026.

Try the live demo, no sign-up

Identity & particulars

Name
Berge Shari
IMO numberWhat is an IMO number?
9713208
MMSIWhat is an MMSI?
235116731
Call signWhat is a call sign?
2JKR3
Vessel type
Bulk carrier
AIS ship type
Cargo
Gross tonnageGross tonnage vs deadweight
21,530
Length overall
179.9 m
Beam
—
Year built
2016

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 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.

DateEventSource
Left Pasir PanjangAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at Pasir PanjangAIS-detectedVoydar port-call detector (AIS geofence)
Reported departure from Long BeachAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at Long BeachAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from LongviewAuthority-reportedUSACE 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.

YearCO₂ emittedFuel burnedTime at seaCO₂ / n mile
20182,380 t764 t49 days203 kg
20191,109 t354 t22 days221 kg
20221,255 t400 t25 days185 kg
20232,750 t881 t56 days195 kg
20252,072 t660 t47 days184 kg

Technical efficiency: EEXI (5.15 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

PortArrivedDepartedTime in port
Pasir Panjang SGPAPJun 15, 2026, 20:43 UTCJun 15, 2026, 21:28 UTC45 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

PortRecordDate (UTC)BerthSource
Long Beach USLGBDepartureOct 18, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalOct 12, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGDepartureOct 7, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Longview USLOGArrivalOct 2, 2016(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: October 2, 2016.

Frequently asked questions

Where is Berge Shari now?
Voydar has no displayable AIS position for Berge Shari in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
What kind of ship is Berge Shari?
Berge Shari is a bulk carrier sailing under the flag of United Kingdom, built in 2016 by Hakodate Dock. The vessel is 179.9 m long and has a gross tonnage of 21,530.
Who is recorded as the owner or manager of Berge Shari?
Berge Bulk Maritime Pte. Ltd is recorded as ISM manager for Berge Shari (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 Berge Shari?
Voydar has no matched sanctions record displayed for Berge Shari 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 Berge Shari. 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/9713208
View JSONAPI documentationFree without a key for occasional use; use an API key for more.

Using 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.

See plans