JSC MIC NPO Mashinostroyenia

• SanctionsRecords foundSanctioned by 1 authority: Canada. 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 & control— Not scoredNot scored. No ownership, control or officer records are on file for this company, which is an absence of evidence rather than an absence of risk.
• 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.

• CanadaActive

  Russia

  Designated 24 Jul 2014 · Canada Consolidated Autonomous Sanctions List

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.

No people recorded against this company. Officer and ownership data comes from national business registers, and the registers this system reads cover a different set of countries from the sanctions lists — so a sanctioned company frequently has none.

Legal name

JSC MIC NPO Mashinostroyenia

Also known as

JSC MIC NPO Mashinostroyenia

First recorded here

19 Jul 2026

1. Sanction listed: Canada — Russia

   19 Jul 2026 · Canada Consolidated Autonomous Sanctions List

2. Alias recorded: JSC MIC NPO Mashinostroyenia

   19 Jul 2026 · Canada Consolidated Autonomous Sanctions List

3. First recorded: JSC MIC NPO Mashinostroyenia

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

No people recorded against this company. Officer data comes from national business registers, and a company outside those jurisdictions will have none here even when its officers are publicly known elsewhere.

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

  mic npo mashinostroyenia

  Legal name

  Evidence

  russia-1, Part 2-23-jsc-mic-npo-mashinostroyenia

  Read 28 Aug 2026

  Source

  Canada Consolidated Autonomous Sanctions List

  Primary source ↗

• Fact

  Canada — Russia

  Designation

  Evidence

  russia-1, Part 2-23-jsc-mic-npo-mashinostroyenia

  Read 28 Aug 2026 · in force from 24 Jul 2014 · asserted by 2 records

  Source

  Canada Consolidated Autonomous Sanctions 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.

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