RUSICH MILITARY GROUP

• SanctionsRecords foundSanctioned by 1 authority: UK OFSI. 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 found2 designated individuals recorded in connection with this company: Alexey Yurevich MILCHAKOV, Yan Igorevich PETROVSKIY.
• 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.
• Jurisdiction— Not scoredNot scored. No country is recorded for this record.
• Court records— Not assessedNothing has been read for this company on this dimension.

• UK OFSIActive

  Russia

  Designated 6 Dec 2023 · UK Sanctions List (FCDO)

No corporate ownership records on file for this company. Ownership is recorded only where a register or a designating authority publishes it, and coverage is thin for companies outside the jurisdictions with open beneficial-ownership registers.

Legal name

RUSICH MILITARY GROUP

Also known as

RUSICH MILITARY GROUP · TASK FORCE RUSICH

First recorded here

18 Jul 2026

1. Sanctioned individual connected by OFAC: Yan Igorevich PETROVSKIY

   7 Aug 2026 · OFAC SDN

2. Sanctioned individual connected by OFAC: Alexey Yurevich MILCHAKOV

   7 Aug 2026 · OFAC SDN

3. Sanction listed: UK OFSI — Russia

   18 Jul 2026 · UK OFSI Consolidated List

4. Alias recorded: TASK FORCE RUSICH

   18 Jul 2026 · UK OFSI Consolidated List

5. Alias recorded: RUSICH MILITARY GROUP

   18 Jul 2026 · UK OFSI Consolidated List

6. First recorded: RUSICH MILITARY GROUP

   18 Jul 2026

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.

No corporate ownership records on file. This is an absence of evidence, not evidence of a simple structure — see the risk breakdown, where the ownership component is left unscored for exactly this reason.

None recorded with a stated ownership stake or control method.

Nothing to draw: this company has no recorded links to another company on file.

No address has been read for this company, so this was never checked — which is not the same as finding nothing.

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

  rusich military group

  Legal name

  Evidence

  16263

  Read 13 Sept 2026 · asserted by 2 records

  Source

  UK Sanctions List (FCDO) and 1 other source

  Primary source ↗

• Fact

  associate:Yan Igorevich PETROVSKIY

  Officer

  Evidence

  No per-record identifier published by this source

  Read 7 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  associate:Alexey Yurevich MILCHAKOV

  Officer

  Evidence

  No per-record identifier published by this source

  Read 7 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  UK OFSI — Russia

  Designation

  Evidence

  16263

  Read 13 Sept 2026 · asserted by 3 records

  Source

  UK Sanctions List (FCDO) and 1 other source

  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.

5 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.