Divetechnoservices

• SanctionsRecords foundSanctioned by 2 authorities: US CSL (EL), OFAC. Confirmed present in a source snapshot within the last 90 days.
• Debarment & exclusion— Checked, nothing found16 sources read, none holding a record for this company.
• Ownership & controlRecords foundControlled by a designated company: FEDERAL SECURITY SERVICE.
• People— Not assessedNothing has been read for this company on this dimension.
• Identity & registration— Not assessedNothing has been read for this company on this dimension.
• JurisdictionRecords foundRussia is named on a jurisdiction designation list — European Commission, EU list of high-risk third countries (AMLD Art. 9), section IV: “High-risk third countries which are not identified as being subject to calls for action or increased monitoring by the FATF, but whose membership in that international standard-setter is suspended”. The designation is of the jurisdiction, not of this record.
• Court records— Not assessedNothing has been read for this company on this dimension.

• US CSL (EL)Active

  Entity List (EL) - Bureau of Industry and Security

  Designated 26 Sept 2018 · US Consolidated Screening List

• OFACActive

  CYBER2

  Designation date not published by this authority · OFAC SDN

Legal name

Divetechnoservices

Also known as

OOO NPP DTS and OOO DTS · Divetechnoservices · OOO Divetechnoservice · OOO Daivtekhnoservis +5

Jurisdiction

RU

Address

Ulitsa Zheleznovodskaya, 18 / 2 Litera A, Saint Petersburg, 199155

First recorded here

19 Jul 2026

1. Parent company recorded: FEDERAL SECURITY SERVICE

   10 Sept 2026 · OFAC SDN

2. Subsidiary recorded: VELA-MARINE LTD.

   10 Sept 2026 · OFAC SDN

3. Subsidiary recorded: OPTIMA FREIGHT OY

   10 Sept 2026 · OFAC SDN

4. Subsidiary recorded: LACNO S.R.O.

   10 Sept 2026 · OFAC SDN

5. Sanction listed: OFAC — CYBER2

   10 Sept 2026 · OFAC SDN

6. Alias recorded: DAYVTEKHNOSERVIS

   10 Sept 2026 · OFAC SDN

No ownership test is on file for this company. The test reads who holds a company's shares from its shareholder register, and it is run each day for companies with a number in Estonia's, Latvia's or Poland's register. For a company anywhere else, no register read here states its shareholders, so the test cannot be run.

None recorded with a stated ownership stake or control method.

12 companies, 11 recorded links, up to two steps from this record. Open the full graph ›

No other company on file shares Ulitsa Zheleznovodskaya, 18 / 2 Litera A, Saint Petersburg.

Each reading is kept with the methodology version that produced it. A later reading is not a correction of an earlier one — it is a different question asked of more sources.

• Fact

  divetechnoservices

  Legal name

  Evidence

  24647

  Read 10 Sept 2026 · asserted by 2 records

  Source

  OFAC SDN and 1 other source

  Primary source ↗

• Fact

  RU

  Jurisdiction

  Evidence

  24647

  Read 10 Sept 2026 · asserted by 2 records

  Source

  OFAC SDN and 1 other source

  Primary source ↗

• Fact

  OFAC — CYBER2

  Designation

  Evidence

  24647

  Read 10 Sept 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  US CSL (EL) — Entity List (EL) - Bureau of Industry and Security

  Designation

  Evidence

  EL-fcf8931ff55bf361a4b264de2b7fd9db3be25f37e588a866fae62f55

  Read 28 Aug 2026 · asserted by 2 records

  Source

  US Consolidated Screening List

  Primary source ↗

Records from these sources are matched into one company only on a shared identifier, or by a human reviewer — never on name similarity alone. How this works. Not legal or compliance advice: check the originals before acting on anything here.

TRUE

A source states it. Rendered as a fact, with the source attached.

FALSE

A source explicitly denies it. Rare, and never inferred from silence.

UNKNOWN

Checked, nothing found. Rendered as an em dash, never as 0 or "no".

NOT_ASSESSED

Never checked — nothing was read here. Excluded from coverage, and not counted as clean.

15 records on this company — identifiers, aliases, officers, listings, figures — each carry the source that wrote them and are shown beside their own entries. The fields above are different: the entities table has no source column, so what is shown is every source whose stored payload contains the value verbatim. That is strong evidence, not proof of which write landed it, and where nothing contains the value the row says so instead of naming a plausible source.