Partizan appears on the OFAC SDN list under DPRK4. Verify at OFAC.
Every vessel on:OFAC SDN list
Partizan
Cargo ship · Russia · built 1996
In short
Partizan (Cargo ship, Russia flag) has no AIS position on record with Seadar. It appears on a sanctions list (details below).
- Vessel type
- Cargo ship
- Flag
- Russia
- Year built
- 1996
- Gross tonnage
- 3,891
- Size (length × beam)
- 102 m × 15 m
- Registered owner
- —
Watch this ship
Get an email when Partizan 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 Partizan.
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
No AIS position on record for this vessel. Identity and particulars are below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)
Try the live demo, no sign-upIdentity & particulars
- Name
- Partizan
- IMO numberWhat is an IMO number?
- 9113020
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- Source: Wikidata, record Q117066682$C389D40D-7D0B-429B-98F4-B454FB91F83A P8047. Added to Seadar on September 29, 2026. Licence: CC0 1.0.Russia
- Vessel type
- Cargo ship
- Gross tonnageGross tonnage vs deadweight
- 3,891
- Deadweight (DWT)
- Source: Wikidata, record Q117066682. Added to Seadar on September 23, 2026. Licence: CC0 1.0.5,820 t
- Length overall
- 102 m
- Beam
- 15 m
- Year built
- 1996
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.
| Date | Event | Source |
|---|---|---|
| Reported departure from PORT OF SOUTH LOUISIANA (LA)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from New OrleansAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at New OrleansAuthority-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.
Sanctions listings
Every listing of this ship on the sanctions lists Seadar tracks, current and past.
| List | Programme | Listed as | Listed | Status |
|---|---|---|---|---|
| OFAC SDN list (US) | DPRK4 | PARTIZAN | not published by the list | In force |
Source: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).
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
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| PORT OF SOUTH LOUISIANA (LA) | Departure | Aug 13, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | Aug 9, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Aug 4, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Departure | Mar 9, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Mar 6, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Feb 17, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Feb 9, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| New Orleans USMSY | Arrival | Feb 9, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Departure | Jan 28, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Arrival | Jan 23, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Departure | Jan 6, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Galveston USGLS | Arrival | Jan 6, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: September 8, 2003.
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 Partizan now?
- Seadar has no displayable AIS position for Partizan in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Partizan?
- Partizan is a cargo ship sailing under the flag of Russia, built in 1996 by Baltijos laivų statykla, AB. The vessel is 102 m long with a beam of 15 m and has a gross tonnage of 3,891.
- What sanctions and inspection records does Seadar hold for Partizan?
- Partizan appears on the OFAC SDN list under DPRK4. No matched inspection records are displayed for Partizan. 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/9113020Using 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.