AL-INMAA ENGINEERING AND CONTRACTING

• 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: AL-INMAA GROUP FOR TOURISM WORKS, LLC.
• 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 foundLebanon is named on a jurisdiction designation list — European Commission, EU list of high-risk third countries (AMLD Art. 9), section I: “High-risk third countries which have provided a written high-level political commitment to address the identified deficiencies and have developed an action plan with FATF.” The designation is of the jurisdiction, not of this record.
• Court records— Not assessedNothing has been read for this company on this dimension.

• OFACActive

  SDGT

  Designation date not published by this authority · OFAC SDN

Legal name

AL-INMAA ENGINEERING AND CONTRACTING

Also known as

AL-INMAA ENGINEERING AND CONTRACTING · AL-INMAA GROUP FOR ENGINEERING AND CONTRACTING · INMAA 'AL' FOR ENGINEERING AND CONTRACTING SARL

Jurisdiction

LB

Website

www.alinmaa.com.lb ↗

First recorded here

28 Aug 2026

1. Parent company recorded: AL-INMAA GROUP FOR TOURISM WORKS, LLC

   11 Sept 2026 · OFAC SDN

2. Sanctioned individual connected by OFAC: Muhammad BADR-AL-DIN

   28 Aug 2026 · OFAC SDN

3. Sanctioned individual connected by OFAC: Abdul Latif SAAD

   28 Aug 2026 · OFAC SDN

4. Sanctioned individual connected by OFAC: Nabil Mahmoud ASSAF

   28 Aug 2026 · OFAC SDN

5. Sanctioned individual connected by OFAC: Issam Ahmad SAAD

   28 Aug 2026 · OFAC SDN

6. Sanctioned individual connected by OFAC: Jihad Muhammad QANSU

   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.

Matched on the name as each register spells it, not on a resolved person. Where the name is common the match means little, and the label says so rather than leaving you to guess.

Shown as text on purpose, and not a link. These addresses come from sanctions and warning lists, where the site is usually the operation being named — the authority published it as evidence, not as a destination.

3 companies, 2 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

  al-inmaa engineering and contracting

  Legal name

  Evidence

  18220

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  LB

  Jurisdiction

  Evidence

  18220

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  OFAC — SDGT

  Designation

  Evidence

  18220

  Read 28 Aug 2026

  Source

  OFAC SDN

  Primary source ↗

• Fact

  www.alinmaa.com.lb

  Website

  Evidence

  18220

  Read 13 Sept 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.

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