Skip to content

Mafuta

Other · Namibia · built 1983 · AIS Class A

IMO8125064MMSI659389000Call signV5DXLast AIS position Oct 1, 2026, 17:56 UTC

In short

Mafuta (Other, Namibia flag) was last seen on AIS on , not moving, in the South Atlantic Ocean. Its crew-entered AIS destination is ATLANTIC 1; its reported draught is 7.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 17:41 UTC).

Vessel type
Other
Year built
1983
Gross tonnage
14,793
Size (length × beam)
170 m × 24 m
Registered owner
—

Watch this ship

Get an email when Mafuta arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.

We email you a link and a code. That creates a free account, no password or card, and follows Mafuta.

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 Mafuta
Photo: Gary · Licence: CC BY-SA 2.0 · via Wikimedia Commons

Last reported position

received
Position
28.6486° S, 15.9407° E
Area
South Atlantic Ocean
StatusWhat do AIS statuses mean?
Restricted manoeuvrability
Speed
0.2 kn
Course
165°
Heading
198°
28.6486° S, 15.9407° E
Open the full live map →

Seadar detected no port call in the last 30 days.

Port calls are detected by Seadar 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)

Try the live demo, no sign-up

Identity & particulars

Name
Mafuta
IMO numberWhat is an IMO number?
8125064
MMSIWhat is an MMSI?
659389000
Vessel type
Other
Gross tonnageGross tonnage vs deadweight
14,793
Length overall
169.5 m
Beam
24.2 m
Year built
1983

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.

Builder
Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026

Timeline

Dated events for this ship from every source Seadar 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 PortlandAuthority-reportedUSACE foreign traffic vessel entrances & clearances
Reported departure from Long BeachAuthority-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.

Port calls

Two kinds of evidence, kept apart: calls Seadar 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 USPDXDepartureMar 18, 2003(date only)—USACE foreign traffic vessel entrances & clearances
Portland USPDXArrivalNov 26, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureOct 19, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBDepartureOct 8, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Long Beach USLGBArrivalOct 1, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Astoria USASTDepartureJul 30, 2002(date only)—USACE foreign traffic vessel entrances & clearances
Astoria USASTArrivalJul 30, 2002(date only)—USACE foreign traffic vessel entrances & clearances
PISCATAQUA RIVER, ME AND NEW HAMPSHIREDepartureJun 28, 2002(date only)—USACE foreign traffic vessel entrances & clearances
PISCATAQUA RIVER, ME AND NEW HAMPSHIREArrivalMay 9, 2002(date only)—USACE foreign traffic vessel entrances & clearances

Records published by the authority named on each row. Earliest record for this ship: May 9, 2002.

About Mafuta

Mafuta is a diamond-mining ship owned and operated by De Beers in the western coast of South Africa. Built in 1983 as Dock Express 20 for Dock Express Shipping (later Dockwise), the semisubmersible, multirole, heavy-lift vessel was converted to the world's largest cable layer in 1993. In 2005, she was purchased by De Beers, and converted to a subsea diamond-mining ship by A&P Tyne over the course of 11 months. The ship's new name, Peace in Africa, may have implied that it was providing an alternative to blood diamonds. In 2013, still under ownership of De Beers Marine Namibia, the vessel was renamed to MV Mafuta.

Summary from Wikipedia, licensed CC BY-SA.

Frequently asked questions

Where is Mafuta now?
Mafuta (Other, Namibia flag) was last seen on AIS on Oct 1, 2026, 17:56 UTC, not moving, in the South Atlantic Ocean. The crew-entered destination was ATLANTIC 1 (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 17:41 UTC). This report does not confirm the ship’s current route.
What kind of ship is Mafuta?
Mafuta is a other sailing under the flag of Namibia, built in 1983 by Verolme Scheepswerf Heusden. The vessel is 169.5 m long with a beam of 24.2 m and has a gross tonnage of 14,793.
What sanctions and inspection records does Seadar hold for Mafuta?
Seadar has no matched sanctions record displayed for Mafuta from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for Mafuta. 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/8125064
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