LEI 5493003BOMZ88J4FVF26 · Luxembourg, LU-LU, LU · one of 3,428,529 GLEIF LEI records on the directory
5493003BOMZ88J4FVF26Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
UDY2RA000432B83976Verbatim 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_CONSOLIDATING549300S1TTZLHSPL3J21 · ACTIVE · from 2023-04-035493000NKOPVVOGIQP47 · ACTIVE · from 2018-05-0354930011D3BC6QQJBB89 · ACTIVE · from 2023-04-205493002GYTWIB4B51790 · ACTIVE · from 2023-04-1954930031XD80O33EY638 · ACTIVE · from 2023-04-0354930033MYWRNV0OYM24 · ACTIVE · from 2023-03-165493004HCKFSCEMJUT70 · ACTIVE · from 2023-04-265493004NKOX8H46YZV82 · ACTIVE · from 2023-04-205493004NRSVMYWK8EG94 · ACTIVE · from 2023-03-175493005C8M80TWX7T128 · ACTIVE · from 2023-03-025493005R4X0DLH70IA40 · ACTIVE · from 2023-04-035493009N6O5GOPYCPY23 · ACTIVE · from 2023-04-20Verbatim 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.
Tracking starts with the next complete refresh of the source. Each record keeps its newest 50 changes for 13 months.
#://CNXTTHePeoPLe/ORG/GLEIF/5493003BOMZ88J4FVF26web+usd://org-gleif-5493003bomz88j4fvf26 — 1-of-1 edition · universal linkweb+usd://org-gleif-5493003bomz88j4fvf26 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/5493003BOMZ88J4FVF26 — 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.