LEI 549300ZP4WYAFKOF3J73 · LONDON, GB-LND, GB · one of 3,428,529 GLEIF LEI records on the directory
549300ZP4WYAFKOF3J73Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
VV0WRA000585IC000499Verbatim from the GLEIF LEI Golden Copy record for this LEI (fetched 2026-07-13). 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_CONSOLIDATING5493007VV85UTQ8CV292 · ACTIVE · from 2023-07-212138001EW7JGUAXB2F13 · ACTIVE · from 2023-08-142138006W1GTBPQQY1B10 · ACTIVE · from 2023-08-14213800IU98P939N6HM75 · ACTIVE · from 2023-08-14213800SULMKOM6H71M60 · ACTIVE · from 2023-08-015493001NAHZEDK0NWA65 · ACTIVE · from 2012-02-065493002FQSQR9X4HCZ37 · ACTIVE · from 2020-10-055493004WPW8R8A0BLK64 · ACTIVE · from 2012-02-065493008RVDHT2VPXMX96 · ACTIVE · from 2006-10-245493009KZMUZVMPDMT58 · ACTIVE · from 2020-07-15549300BWNB8P6HMM7S16 · ACTIVE · from 2012-02-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.
None loaded for this LEI yet. CNXT has no proven complete refresh of GLEIF's BIC-to-LEI file yet, so this is not a negative.
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.
#://CNXTTHePeoPLe/ORG/GLEIF/549300ZP4WYAFKOF3J73web+usd://org-gleif-549300zp4wyafkof3j73 — 1-of-1 edition · universal linkweb+usd://org-gleif-549300zp4wyafkof3j73 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/549300ZP4WYAFKOF3J73 — 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.