LEI 549300QDJHZ1HF5UC735 · WILMINGTON, US-DE, US · one of 3,490,409 GLEIF LEI records on the directory
549300QDJHZ1HF5UC735Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
8888RA0006650000217087Verbatim from the GLEIF LEI Golden Copy record for this LEI (fetched 2026-11-11). Fields the golden copy does not publish are omitted — never guessed. The registration authority name is GLEIF's own list entry for the record's code.
NON_CONSOLIDATINGNON_CONSOLIDATING549300QDJHZ1HF5UC735 · ACTIVE · from 2023-01-01549300QDJHZ1HF5UC735 · ACTIVE · from 2023-01-015493001MQV26KYOSDP36 · ACTIVE · from 2016-12-315493002EPLDHVX7IVS94 · ACTIVE · from 2013-04-2354930048Q6OB360YDF79 · ACTIVE · from 2016-12-315493006I0TSRF6VO1C08 · ACTIVE · from 2023-03-295493008QP6PWS1VNJM21 · ACTIVE · from 2013-05-29549300HHX5K5Y48ZKI93 · ACTIVE · from 2016-12-31549300JCHW1MWENDS812 · ACTIVE · from 2013-06-06549300KRQSBPNKM3ER41 · ACTIVE · from 2023-03-29549300KTVG0K0HAUNZ26 · ACTIVE · from 2013-04-23549300RSTGB92L5RU061 · ACTIVE · from 2013-04-22Verbatim 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-11-11.
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: GLEIF's ISIN-to-LEI file links no ISIN to this LEI (complete refresh 2026-11-11).
No changes seen since tracking began on 2026-10-20. Each record keeps its newest 50 changes for 13 months.
#://CNXTTHePeoPLe/ORG/GLEIF/549300QDJHZ1HF5UC735web+usd://org-gleif-549300qdjhz1hf5uc735 — 1-of-1 edition · universal linkweb+usd://org-gleif-549300qdjhz1hf5uc735 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/549300QDJHZ1HF5UC735 — 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.