Japan MOF
Active- Programme
- asset-freeze
- Designated
- 1 Mar 2024
- Legal basis
- MOFA public notice No. 255
- Source
- Japan MOF Sanctions List
- Last confirmed
- 26 Oct 2026
CompanyReg. 1045002200616Last read from source 26 Oct 2026
asset-freeze
Designated 1 Mar 2024 · Japan MOF Sanctions List
RUSSIA-EO14024
Designation date not published by this authority · OFAC SDN
Situation in Ukraine
Designated 2 Mar 2023 · Switzerland SECO 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.
Sanction listed: Switzerland SECO — Situation in Ukraine
8 Aug 2026 · Switzerland SECO Sanctions List
Alias recorded: АО ДМЗ ИМ. Н.П. ФЕДОРОВА
8 Aug 2026 · Switzerland SECO Sanctions List
Alias recorded: Joint-stock company “Dubnensky machine-building plant” named after N.P. Fedorov
8 Aug 2026 · Switzerland SECO Sanctions List
Sanction listed: Japan MOF — asset-freeze
22 Jul 2026 · Japan MOF Sanctions List
Alias recorded: Aktsionernoye obshchestvo Dubnenskiy mashinostroitel’nyy zavod imeni N.P. Fodorova
22 Jul 2026 · Japan MOF Sanctions List
Alias recorded: Dubna Engineering Plant
22 Jul 2026 · Japan MOF Sanctions List
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.
Sanction listed: Switzerland SECO — Situation in Ukraine
8 Aug 2026 · Switzerland SECO Sanctions List
Alias recorded: АО ДМЗ ИМ. Н.П. ФЕДОРОВА
8 Aug 2026 · Switzerland SECO Sanctions List
Alias recorded: Joint-stock company “Dubnensky machine-building plant” named after N.P. Fedorov
8 Aug 2026 · Switzerland SECO Sanctions List
Sanction listed: Japan MOF — asset-freeze
22 Jul 2026 · Japan MOF Sanctions List
Alias recorded: Aktsionernoye obshchestvo Dubnenskiy mashinostroitel’nyy zavod imeni N.P. Fodorova
22 Jul 2026 · Japan MOF Sanctions List
Alias recorded: Dubna Engineering Plant
22 Jul 2026 · Japan MOF Sanctions List
Alias recorded: Dubninsky machine-building plant
22 Jul 2026 · Japan MOF Sanctions List
Alias recorded: Dubna Machine-Building Plant
22 Jul 2026 · Japan MOF Sanctions List
Alias recorded: Dubnensky Machine-Building Plant JSC
22 Jul 2026 · Japan MOF Sanctions List
Alias recorded: Joint Stock Company Dubnensky Machine Building Plant named after N.P. Fedorov
22 Jul 2026 · Japan MOF Sanctions List
Sanction listed: OFAC — RUSSIA-EO14024
17 Jul 2026 · OFAC SDN
Identifier recorded: REG_NUMBER 1045002200616
17 Jul 2026 · OFAC SDN
Identifier recorded: TAX_ID 5010030050
17 Jul 2026 · OFAC SDN
Alias recorded: AKTSIONERNOYE OBSHCHESTVO DUBNENSKIY MASHINOSTROITELNYY ZAVOD IMENI NP FODOROVA
17 Jul 2026 · OFAC SDN
Alias recorded: DUBNA ENGINEERING PLANT
17 Jul 2026 · OFAC SDN
Alias recorded: DUBNA MACHINE BUILDING PLANT
17 Jul 2026 · OFAC SDN
Alias recorded: JOINT STOCK COMPANY DUBNENSKY MACHINE BUILDING PLANT NAMED AFTER NP FEDOROV
17 Jul 2026 · OFAC SDN
First recorded: JOINT STOCK COMPANY DUBNENSKY MACHINE BUILDING PLANT NAMED AFTER NP FEDOROV
17 Jul 2026
Dates are when each fact was first recorded here, which for older entries is when the source was first read rather than when the authority acted. Changes across all companies ›
No published story on this site mentions this company. Mentions are linked only where a published article names a company already resolved here, and the published set is small — so an empty section says nothing about how much has been written elsewhere.
Sanctions exposure: 76 · Ownership risk: not scored · Jurisdiction: 70 · Adverse media: not scored
Sanctions exposure: 76 · Ownership risk: not scored · Jurisdiction: 70 · Adverse media: not scored
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
reg_number:1045002200616
Registered identifier
Evidence
44975
Read 28 Aug 2026 · asserted by 2 records
Fact
tax_id:5010030050
Registered identifier
Evidence
44975
Read 28 Aug 2026 · asserted by 2 records
Fact
dubnensky machine building plant named after np fedorov
Legal name
Evidence
028-000255
Read 10 Sept 2026 · asserted by 2 records
Fact
dubnensky machine-building plant
Legal name
Evidence
60702
Read 17 Aug 2026
Fact
dubnensky machine building plant named after n p fedorov
Legal name
Evidence
028-000255
Read 17 Aug 2026
Superseded 10 Sept 2026 — the source has since published a different value. Kept rather than overwritten, so the change itself stays readable.
Fact
RU
Jurisdiction
Evidence
44975
Read 28 Aug 2026 · asserted by 2 records
Fact
OFAC — RUSSIA-EO14024
Designation
Evidence
44975
Read 28 Aug 2026 · asserted by 2 records
Fact
Switzerland SECO — Situation in Ukraine
Designation
Evidence
60702
Read 17 Aug 2026 · asserted by 2 records
Fact
Japan MOF — asset-freeze
Designation
Evidence
028-000255
Read 17 Aug 2026 · asserted by 2 records
Both readings are shown because both were published. Neither is corrected here.
No company register for this jurisdiction has been connected to this system, and none has been examined.
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.
17 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.