LEI J6QROFUT418O3XX4OT04 · Wilmington, US-DE, US · one of 3,472,754 GLEIF LEI records on the directory
J6QROFUT418O3XX4OT04Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
HZEHRA0006024895597Verbatim from the GLEIF LEI Golden Copy record for this LEI (fetched 2026-10-25). 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.
NO_KNOWN_PERSONNO_KNOWN_PERSON549300LZFSCKYTIJTU56 · ACTIVE · from 2015-05-112549006WFI025EZZGJ14 · ACTIVE · from 2017-10-02254900CFFMSL34P8LR29 · ACTIVE · from 2022-03-02254900DUUKGKIZ5EAE20 · ACTIVE · from 2024-05-10254900FM4YEIW3TLA840 · ACTIVE · from 2019-12-30254900QSX2VIYKGEF141 · ACTIVE · from 2019-08-19254900WL1CW0NBPY6I37 · ACTIVE · from 2024-05-1054930003DU29TTRKOG20 · ACTIVE · from 2016-07-21549300OCFNTKUUAO1D05 · ACTIVE · from 2018-09-26549300RY6QUI06N64I23 · ACTIVE · from 2024-05-116488D51UP213HDO88C76 · ACTIVE · from 2024-02-29Verbatim 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-26.
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.
No changes seen since tracking began on 2026-10-21. Each record keeps its newest 50 changes for 13 months.
#://CNXTTHePeoPLe/ORG/GLEIF/J6QROFUT418O3XX4OT04web+usd://org-gleif-j6qrofut418o3xx4ot04 — 1-of-1 edition · universal linkweb+usd://org-gleif-j6qrofut418o3xx4ot04 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/J6QROFUT418O3XX4OT04 — 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.