Skip to content

F/V MARAWA2

Fishing vessel · Kiribati · AIS Class A

IMO7806491MMSI529729001Call signT3NG2Last AIS position Jul 31, 2026, 22:38 UTC

In short

F/V MARAWA2 (Fishing vessel, Kiribati flag) was last seen on AIS on , not moving, near Busan (Sea of Japan). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its last detected port call was at Busan: arrived Jun 16, 2026, left Jul 2, 2026.

Vessel type
Fishing vessel
Year built
—
Gross tonnage
—
Size (length × beam)
—
Registered owner
—

Watch this ship

F/V MARAWA2 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 F/V MARAWA2.

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.

Last reported position

received
Position
35.0979° N, 129.0656° E
Area
Sea of Japan
StatusWhat do AIS statuses mean?
Under way sailing
Speed
0 kn
Course
0°
Heading
—
35.0979° N, 129.0656° E
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.

Pro shows F/V MARAWA2's track before the last 30 days. Voydar has recorded its port calls since June 10, 2026.

Try the live demo, no sign-up

Identity & particulars

Name
F/V MARAWA2
IMO numberWhat is an IMO number?
7806491
MMSIWhat is an MMSI?
529729001
Call signWhat is a call sign?
T3NG2
Vessel type
Fishing vessel
AIS ship type
Fishing
Length overall
—
Beam
—
Year built
—

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.

No owner, operator or manager is recorded for this vessel yet.

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 BusanAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BusanAIS-detectedVoydar port-call detector (AIS geofence)
Left BusanAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BusanAIS-detectedVoydar port-call detector (AIS geofence)
Left BusanAIS-detectedVoydar port-call detector (AIS geofence)
Arrived at BusanAIS-detectedVoydar port-call detector (AIS geofence)
Inspection at Honolulu, HawaiiUSCG PSIX / CGMIX inspections
Inspection at , HawaiiUSCG PSIX / CGMIX inspections
Inspection at FPO, Armed Forces PacificUSCG PSIX / CGMIX inspections
Inspection at FPO, Armed Forces PacificUSCG PSIX / CGMIX inspections
Inspection at FPO, Armed Forces PacificUSCG PSIX / CGMIX inspections
Inspection at FPO, Armed Forces PacificUSCG PSIX / CGMIX inspections
Inspection at ALAMEDA, CaliforniaUSCG PSIX / CGMIX inspections
Inspection at FPO, Armed Forces PacificUSCG PSIX / CGMIX inspections
Inspection at FPO, Armed Forces PacificUSCG PSIX / CGMIX inspections

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.

Safety & inspections

9
Inspections
not recorded
Detentions
0
Deficiencies
DateTypePortFindings
Jan 27, 2010BoardingHonolulu, Hawaiiclean
Aug 23, 2005Boarding, Hawaiiclean
Nov 16, 2004Vessel InspectionFPO, Armed Forces Pacificclean
Feb 7, 2001Vessel InspectionFPO, Armed Forces Pacificclean
Feb 2, 2001Vessel InspectionFPO, Armed Forces Pacificclean
Jan 17, 1996Vessel InspectionFPO, Armed Forces Pacificclean
Apr 6, 1995EnforcementALAMEDA, Californiaclean
Aug 4, 1992Vessel InspectionFPO, Armed Forces Pacificclean
Aug 7, 1990Vessel InspectionFPO, Armed Forces Pacificclean

Source: U.S. Coast Guard Port State Information Exchange (PSIX) — public domain. Covers inspections recorded in U.S. waters. Free on Voydar; the incumbents charge for this.

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
Busan KRPUSJun 16, 2026, 03:32 UTCJul 2, 2026, 12:07 UTC16 d 8 h
Busan KRPUSJun 15, 2026, 10:06 UTCJun 16, 2026, 03:30 UTC17 h 24 min
Busan KRPUSJun 10, 2026, 20:29 UTCJun 15, 2026, 10:05 UTC4 d 13 h

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.

Frequently asked questions

Where is F/V MARAWA2 now?
F/V MARAWA2 (Fishing vessel, Kiribati flag) was last seen on AIS on Jul 31, 2026, 22:38 UTC, not moving, near Busan (Sea of Japan). Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
What kind of ship is F/V MARAWA2?
F/V MARAWA2 is a fishing vessel sailing under the flag of Kiribati.
What sanctions and inspection records does Voydar hold for F/V MARAWA2?
Voydar has no matched sanctions record displayed for F/V MARAWA2 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. F/V MARAWA2 has 9 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.

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/7806491
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