PAMIR appears on the OFAC SDN list, the New Zealand Russia Sanctions Register, the UK Sanctions List, the EU list of designated vessels and the Canadian autonomous sanctions list under UKRAINE-EO13662] [RUSSIA-EO14024, Russia Sanctions Act 2022 (New Zealand), Russia, Russia (Reg. 833/2014 Annex XLII). Verify at OFAC.
Every vessel on:OFAC SDN listNew Zealand Russia Sanctions RegisterUK Sanctions ListEU list of designated vesselsCanadian autonomous sanctions list
PAMIR
Tanker · Russia · built 2004 · AIS Class A
In short
PAMIR (Tanker, Russia flag) was last seen on AIS on , under way at 1.7 kn, in the Barents Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. It appears on 5 sanctions lists (details below).
Watch this ship
Get an email when PAMIR 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 PAMIR.
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
- 70.3502° N, 32.4615° E
- Area
- Barents Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 1.7 kn
- Course
- 251°
- Heading
- 184°
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)
Try the live demo, no sign-upIdentity & particulars
- Name
- PAMIR
- IMO numberWhat is an IMO number?
- 9276028
- MMSIWhat is an MMSI?
- 273276060
- Call signWhat is a call sign?
- 9HUC7
- Flag
- Russia
- Vessel type
- Tanker
- Gross tonnageGross tonnage vs deadweight
- 29,327
- Length overall
- —
- Beam
- —
- Year built
- 2004
RussiaA 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.
- Owner or operator (sanctions listing)
- Orchid Shipmanagement LLC-FZ(not linked to a company record)Source: UK Sanctions List (FCDO) · reported · confidence 0.7 · retrieved Oct 4, 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.
| Date | Event | Source |
|---|---|---|
| Listed on the New Zealand Russia Sanctions Register (MFAT) (Russia Sanctions Act 2022 (New Zealand)) | New Zealand Russia Sanctions Register (ships) | |
| Listed on the Canadian autonomous sanctions list (Russia) | Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA) | |
| Listed on the EU designated vessels (Official Journal) (Russia (Reg. 833/2014 Annex XLII)) | EU designated vessels (Reg. 833/2014 Annex XLII; Reg. 2017/1509 Annex XIV) | |
| Former name: PEGASUS | UK Sanctions List (FCDO) | |
| Listed on the UK Sanctions List (Russia) | UK Sanctions List (FCDO) | |
| Port State Control inspection at FPO, Armed Forces Pacific | USCG PSIX / CGMIX inspections | |
| Inspection at FPO, Armed Forces Pacific | USCG PSIX / CGMIX inspections | |
| Reported departure from Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Reported arrival at Hong KongAuthority-reported | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) | |
| Port State Control inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Inspection at San Pedro, California | USCG PSIX / CGMIX inspections | |
| Port State Control inspection at San Francisco, California | USCG PSIX / CGMIX inspections | |
| Reported departure from RichmondAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Port State Control inspection at San Francisco, California | USCG PSIX / CGMIX inspections | |
| Reported arrival at RichmondAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Port State Control inspection at North Charleston, South Carolina | USCG PSIX / CGMIX inspections | |
| Inspection at New Orleans, Louisiana | USCG PSIX / CGMIX inspections | |
| Inspection at Port Arthur, Texas | USCG PSIX / CGMIX inspections | |
| Inspection at San Juan, Puerto Rico | USCG 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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| PEGASUS | Former name | Sep 12, 2025 | UK Sanctions List (FCDO) |
A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.
Source: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.
Safety & inspections
| Date | Type | Port | Findings |
|---|---|---|---|
| Mar 14, 2020 | Vessel InspectionPSC | FPO, Armed Forces Pacific | clean |
| Mar 10, 2020 | Vessel Operational Control | FPO, Armed Forces Pacific | clean |
| Jun 18, 2018 | Vessel InspectionPSC | San Pedro, California | clean |
| Feb 18, 2017 | Vessel Operational Control | San Pedro, California | clean |
| Dec 8, 2016 | Vessel InspectionPSC | San Francisco, California | clean |
| Sep 26, 2016 | Vessel InspectionPSC | San Francisco, California | clean |
| Jan 28, 2014 | Vessel InspectionPSC | North Charleston, South Carolina | clean |
| Oct 3, 2012 | Boarding | New Orleans, Louisiana | clean |
| Sep 28, 2012 | Vessel Inspection | Port Arthur, Texas | clean |
| Sep 20, 2012 | Boarding | San Juan, Puerto Rico | clean |
| Sep 3, 2012 | Incident Investigation | WASHINGTON, District of Columbia | clean |
| Apr 14, 2012 | Vessel InspectionPSC | Houston, Texas | clean |
| Jul 14, 2011 | Boarding | North Charleston, South Carolina | clean |
| Dec 24, 2010 | Vessel InspectionPSC | Houston, Texas | clean |
| Aug 13, 2010 | Boarding | Miami Beach, Florida | clean |
| Jun 30, 2010 | Vessel InspectionPSC | Woods Hole, Massachusetts | clean |
| Mar 10, 2010 | Boarding | STATEN ISLAND, New York | clean |
| Mar 10, 2010 | Boarding | STATEN ISLAND, New York | clean |
| Dec 8, 2009 | Vessel Transfer Monitor | San Francisco, California | clean |
| Nov 28, 2009 | Vessel InspectionPSC | San Pedro, California | clean |
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.
Sanctions listings
Every listing of this ship on the sanctions lists Voydar tracks, current and past.
| List | Programme | Listed as | Listed | Status |
|---|---|---|---|---|
| New Zealand Russia Sanctions Register (MFAT) | Russia Sanctions Act 2022 (New Zealand) | Pegasus | Feb 20, 2026 | In force |
| Canadian autonomous sanctions list | Russia | Pegasus | Feb 19, 2026 | In force |
| EU designated vessels (Official Journal) | Russia (Reg. 833/2014 Annex XLII) | Pegasus | Oct 24, 2025 | In force |
| UK Sanctions List | Russia | PEGASUS | Sep 12, 2025 | In force |
| OFAC SDN list (US) | UKRAINE-EO13662] [RUSSIA-EO14024 | PEGASUS | not published by the list | In force |
Source: New Zealand Russia Sanctions Register (ships). © Crown copyright, New Zealand Ministry of Foreign Affairs and Trade, CC BY 4.0. Licence: CC-BY-4.0 (Crown copyright).
Source: Canada Consolidated Autonomous Sanctions List (SEMA/JVCFOA). Contains information licensed under the Open Government Licence – Canada. Licence: Open Government Licence – Canada.
Source: Council Regulation (EU) No 833/2014, Annex XLII, and Council Regulation (EU) 2017/1509, Annex XIV (Official Journal of the European Union); list compiled by the Danish Maritime Authority. Licence: EU legislation (Official Journal): reuse "for commercial or non-commercial purposes" (Decision 2011/833/EU); facts.
Source: UK Sanctions List (FCDO). Contains public sector information licensed under the Open Government Licence v3.0. Licence: OGL v3.
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 Voydar 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 |
|---|---|---|---|---|
| Hong Kong HKHKG | Arrival | Dec 3, 2019, 11:22 UTC | WL | Hong Kong vessel arrivals & departures (incl. VTMS daily reports) |
| Richmond USRCH | Departure | Oct 8, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Richmond USRCH | Arrival | Sep 24, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baton Rouge USBTR | Departure | Feb 14, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baton Rouge USBTR | Arrival | Feb 7, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Departure | Jan 31, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Arrival | Jan 31, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Departure | Jan 30, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Savannah USSAV | Arrival | Jan 30, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Departure | Jan 28, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Arrival | Jan 28, 2014(date only) | — | USACE foreign traffic vessel entrances & clearances |
| PORT OF SOUTH LOUISIANA (LA) | Departure | Oct 5, 2012(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: August 11, 2004.
Source: Marine Department, HKSAR Government — DATA.GOV.HK. Licence: DATA.GOV.HK Terms and Conditions.
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 PAMIR now?
- PAMIR (Tanker, Russia flag) was last seen on AIS on Jul 6, 2026, 10:33 UTC, under way at 1.7 kn, in the Barents Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report.
- What kind of ship is PAMIR?
- PAMIR is a tanker sailing under the flag of Russia, built in 2004 by HD Hyundai Mipo. The vessel has a gross tonnage of 29,327.
- What sanctions and inspection records does Voydar hold for PAMIR?
- PAMIR appears on the OFAC SDN list, the New Zealand Russia Sanctions Register, the UK Sanctions List, the EU list of designated vessels and the Canadian autonomous sanctions list under UKRAINE-EO13662] [RUSSIA-EO14024, Russia Sanctions Act 2022 (New Zealand), Russia, Russia (Reg. 833/2014 Annex XLII). PAMIR has 43 recorded Port State Control inspections. Detention and deficiency detail is not recorded for these inspections.
Neighbouring IMO numbers
IMO numbers are issued in sequence. These are the nearest numbers below and above this ship's that have a full Voydar profile.
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/9276028Using 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.