LEI 213800247F9DRTHRPW30 · LONDON, GB-LND, GB · one of 3,428,529 GLEIF LEI records on the directory
213800247F9DRTHRPW30Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
H0PORA00058502392609Verbatim from the GLEIF LEI Golden Copy record for this LEI (fetched 2026-07-12). Fields the golden copy does not publish are omitted — never guessed. Legal form and registration authority names are GLEIF's own list entries for the record's codes.
NON_CONSOLIDATINGNON_CONSOLIDATING21380017I2EOLV1ZXM34 · ACTIVE · from 2017-10-262138001KQ15A5EQIAG39 · ACTIVE · from 2017-10-182138003EJKVMA1WHNH54 · ACTIVE · from 2017-10-182138006XO2H12TEQJK84 · ACTIVE · from 2017-10-2621380097AVS27C7Y4662 · ACTIVE · from 2017-10-18213800CIXPM341M82B40 · ACTIVE · from 2017-10-26213800DT7J5JXJGF7Y80 · ACTIVE · from 2017-10-26213800EL9B6PCGS2CG75 · ACTIVE · from 2019-01-01213800FL1XGQSWOIJU70 · ACTIVE · from 2017-10-26213800JJ3NBWW3LBKT42 · ACTIVE · from 2017-10-182138001X9GVMR2O3WT97 · ACTIVE · from 2017-08-232138003AG7EHAADBT762 · ACTIVE · from 2014-02-122138003QRRCSHEIZZ770 · ACTIVE · from 2014-11-272138006AMU5G2UWA9K07 · ACTIVE · from 2018-05-032138009D6O354XEID471 · ACTIVE · from 2006-03-302138009JV4R5LMBVDU30 · ACTIVE · from 2013-12-182138009ZV5LYUQM5A484 · ACTIVE · from 2014-02-19213800AAM3KN6QW8DC44 · ACTIVE · from 2012-10-01213800BMNS2VUTTYVX39 · ACTIVE · from 2017-06-06213800BOM3O1O9Z65C03 · ACTIVE · from 2017-06-06Verbatim from GLEIF's Level 2 relationship and reporting-exception files (CC0). Each link is an LEI pair GLEIF publishes; names come from this directory and never create a link. No ownership share or value is stated. Complete refresh: 2026-10-20.
INUAGB21XXX · GBCross-registry identity (LiNx) for this LEI and BIC
Verbatim rows from GLEIF's certified BIC-to-LEI mapping file (bic-registry dataset) — a certified correspondence between this LEI and SWIFT BIC codes, not an inference.
None loaded for this LEI yet. CNXT has no proven complete refresh of GLEIF's ISIN-to-LEI file yet, so this is not a negative.
Indicative correspondences from the CNXT registry-linkage layer (SEC EDGAR / BIC / FedNow families) — asserted only where the registries' own published identifiers agree; certified BIC↔LEI rows appear in their own panel above.
Tracking starts with the next complete refresh of the source. Each record keeps its newest 50 changes for 13 months.
#://CNXTTHePeoPLe/ORG/GLEIF/213800247F9DRTHRPW30web+usd://org-gleif-213800247f9drthrpw30 — 1-of-1 edition · universal linkweb+usd://org-gleif-213800247f9drthrpw30 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/213800247F9DRTHRPW30 — JSONThis record is addressable on the CNXT network. Its web+usd:// edition address doubles as the record's settlement rail — reserved, with no holder and no balance, until the 1-of-1 edition is minted. The JSON endpoint returns the same org-level fields rendered here; person-level registry contacts are never exposed on this public tier.
Stage is derived live from real rows — directory row (Addressable), source-published domain or cross-registry links (Enriched), tokenized_entities registration (Reserved) and holder (Minted), CNXTCLOUD binding (Connected), settled transfers on the rail (Transacting). Nothing here is simulated.
Organization records are represented in CNXT — not operated by the listed entities. Registry identity is verbatim from the source registry's public data; CNXT issues only the disclosed token attributes and never implies affiliation or endorsement.