Zakamsk appears on the OFAC SDN list and the Canadian autonomous sanctions list under RUSSIA-EO14024, Russia. Verify at OFAC.
Every vessel on:OFAC SDN listCanadian autonomous sanctions list
Zakamsk
Cargo ship · built 1966
In short
Zakamsk (Cargo ship) has no AIS position on record with Seadar. It appears on 2 sanctions lists (details below).
- Vessel type
- Cargo ship
- Flag
- —
- Year built
- 1966
- Gross tonnage
- 2,406
- Size (length × beam)
- 114 m × 13 m
- Registered owner
- —
Watch this ship
Get an email when Zakamsk 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 Zakamsk.
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
- Zakamsk
- IMO numberWhat is an IMO number?
- 8951413
- MMSIWhat is an MMSI?
- —
- Call signWhat is a call sign?
- —
- Flag
- —
- Vessel type
- Cargo ship
- Gross tonnageGross tonnage vs deadweight
- 2,406
- Deadweight (DWT)
- Source: Wikidata, record Q117077714. Added to Seadar on September 23, 2026. Licence: CC0 1.0.3,328 t
- Length overall
- 114 m
- Beam
- 13 m
- Year built
- 1966
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 Seadar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Listed on the Canadian autonomous sanctions list (Russia) | Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA) |
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 |
|---|---|---|---|---|
| Canadian autonomous sanctions list | Russia | Zakamsk | Jun 12, 2026 | In force |
| OFAC SDN list (US) | RUSSIA-EO14024 | ZAKAMSK | not published by the list | In force |
Source: Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Contains information licensed under the Open Government Licence – Canada. Licence: Open Government Licence – Canada.
Source: OFAC Specially Designated Nationals list. Licence: US Government public domain (17 U.S.C. §105).
Frequently asked questions
- Where is Zakamsk now?
- Seadar has no displayable AIS position for Zakamsk in this profile. A coverage gap does not establish whether the ship is transmitting or where it is now.
- What kind of ship is Zakamsk?
- Zakamsk is a cargo ship, built in 1966. The vessel is 114 m long with a beam of 13 m and has a gross tonnage of 2,406.
- What sanctions and inspection records does Seadar hold for Zakamsk?
- Zakamsk appears on the OFAC SDN list and the Canadian autonomous sanctions list under RUSSIA-EO14024, Russia. No matched inspection records are displayed for Zakamsk. 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/8951413Using 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.