Legal entity
Every one of those 1 sits in a single category, regulation. Banque Misr UAE branch is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. We currently track 1 Legal story that mention Banque Misr, all published on September 7, 2026.
Last mentioned: 6d ago
Entity pulse
Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.
Every one of those 1 sits in a single category, regulation. Banque Misr UAE branch is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. We currently track 1 Legal story that mention Banque Misr, all published on September 7, 2026. Each carries 2 original sources on average.
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 3 Legal stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Other entities that clear the same relevance threshold in stories also covering Banque Misr. Shared-story counts are live from our verified record — not editorial picks.
U.S. Treasury identifies Banque Misr UAE branch
Treasury said the Emirati branch of Egyptian state-owned Banque Misr accessed U.S. correspondent accounts and routed up to $1.8 billion for companies potentially part of Iranian shadow-banking networks; it said it would move to cut the branch off.
The U.S. Treasury's Aug. 28 designation of Banque Misr's UAE branch over $1.8B in possible Iranian shadow-banking flows puts a sharp legal focus on U.S. correspondent banks' sanctions-compliance duties. The case highlights how third-party correspondent relationships can expose American institutions to enforcement risk even absent direct knowledge. Legal teams must review due-diligence, SAR, and OFAC screening obligations.
Banque Misr is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source link? Report a data issue.
