LEI 636700A999IXIVP1YD50 · Oslo, NO-03, NO · one of 3,472,754 GLEIF LEI records on the directory
636700A999IXIVP1YD50Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
YI42RA000472927 958 457Verbatim 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.
549300U4VF2QE8U8AH88 · ACTIVE · from 2022-03-2354930047YMTWHCTWMZ52 · ACTIVE · from 2025-01-236367003DKGDMCGCYHJ21 · ACTIVE · from 2026-01-286367003ORJEAOLUTRR73 · ACTIVE · from 2022-03-316367003YK1XH39RRIM15 · ACTIVE · from 2025-01-2363670074OAXOCURO3Z64 · ACTIVE · from 2025-01-236367008DKAK6JU1DGF28 · ACTIVE · from 2023-08-23636700AUOEMAQ2OA4X57 · ACTIVE · from 2025-01-23636700GZ8MTWN1EYTD36 · ACTIVE · from 2025-01-23636700LL608T0R4I0B10 · ACTIVE · from 2025-05-09636700MG93UVBM4VZ036 · ACTIVE · from 2024-06-10636700U75UDSBES7T336 · ACTIVE · from 2026-05-14Verbatim 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/636700A999IXIVP1YD50web+usd://org-gleif-636700a999ixivp1yd50 — 1-of-1 edition · universal linkweb+usd://org-gleif-636700a999ixivp1yd50 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/636700A999IXIVP1YD50 — 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.