Skip to content

Berge Asahidake

General cargo ship · United Kingdom · built 2016 · AIS Class A

IMO9713181MMSI235113778Call sign2IYI4Last AIS position Sep 24, 2026, 02:15 UTC

In short

Berge Asahidake (General cargo ship, United Kingdom flag) was last seen on AIS on , under way at 11.8 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 TN SFA (Sfax); its reported draught is 10.3 m (voyage report via AISstream.io global terrestrial AIS, received Sep 23, 2026, 22:28 UTC). ISM manager: Berge Bulk Maritime Pte. Ltd (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).

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

Watch this ship

Berge Asahidake 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
36.5145° N, 1.0466° W
Area
Mediterranean Sea
StatusWhat do AIS statuses mean?
Under way using engine
Speed
11.8 kn
Course
81°
Heading
82°
36.5145° N, 1.0466° W
Open the full live map →

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

Identity & particulars

Name
Berge Asahidake
IMO numberWhat is an IMO number?
9713181
MMSIWhat is an MMSI?
235113778
Call signWhat is a call sign?
2IYI4
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 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.

DateEventSource
Reported departure from PortlandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported arrival at VancouverAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from RichmondAuthority-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
2018719 t228 t24 days161 kg
20213,247 t1,026 t66 days206 kg
20221,931 t614 t41 days209 kg
20250 t0 t0 days—

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

PortRecordDate (UTC)BerthSource
Portland USPDXDepartureFeb 15, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Vancouver USVANArrivalFeb 14, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Richmond USRCHDepartureFeb 11, 2016(date only)—USACE foreign traffic vessel entrances & clearances
Richmond USRCHArrivalFeb 4, 2016(date only)—USACE foreign traffic vessel entrances & clearances

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

Frequently asked questions

Where is Berge Asahidake now?
Berge Asahidake (General cargo ship, United Kingdom flag) was last seen on AIS on Sep 24, 2026, 02:15 UTC, under way at 11.8 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 TN SFA (voyage report via AISstream.io global terrestrial AIS, received Sep 23, 2026, 22:28 UTC). This report does not confirm the ship’s current route.
What kind of ship is Berge Asahidake?
Berge Asahidake is a general cargo ship 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 Asahidake?
Berge Bulk Maritime Pte. Ltd is recorded as ISM manager for Berge Asahidake (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 Asahidake?
Voydar has no matched sanctions record displayed for Berge Asahidake 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 Asahidake. 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/9713181
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