YAMAKI, K.K.

• SanctionsRecords foundSanctioned by 1 authority: 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: YAMAGUCHI-GUMI.
• 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. The jurisdiction lists this system reads are: EU list of high-risk third countries (AMLD Art. 9). Each names specific countries, so absence from them is not a clearance of Japan. Separately, 5 of the sanctions authorities this system reads have designated companies registered in Japan — a count of this corpus, not a rating of the jurisdiction.
• Court records— Not assessedNothing has been read for this company on this dimension.

• OFACActive

  TCO

  Designation date not published by this authority · OFAC SDN

Legal name

YAMAKI, K.K.

Also known as

YAMAKI, K.K. · KK YAMATERU

Jurisdiction

JP

Registration number

1400-01-004182

First recorded here

28 Aug 2026

1. Identifier recorded: REG_NUMBER 1400-01-004182

   13 Sept 2026 · OFAC SDN

2. Parent company recorded: YAMAGUCHI-GUMI

   10 Sept 2026 · OFAC SDN

3. Sanction listed: OFAC — TCO

   28 Aug 2026 · OFAC SDN

4. Alias recorded: KK YAMATERU

   28 Aug 2026 · OFAC SDN

5. Alias recorded: YAMAKI, K.K.

   28 Aug 2026 · OFAC SDN

6. First recorded: YAMAKI, K.K.

   28 Aug 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.

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

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

  reg_number:1400-01-004182

  Registered identifier

  Evidence

  24683

  Read 13 Sept 2026 · asserted by 2 records

  Source

  OFAC SDN

  Primary source ↗

• Fact

  yamaki kk

  Legal name

  Evidence

  24683

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  JP

  Jurisdiction

  Evidence

  24683

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  OFAC — TCO

  Designation

  Evidence

  24683

  Read 28 Aug 2026

  Source

  OFAC SDN

  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.

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

Registration number

1400-01-004182JPvia OFAC SDN