LEI 815600139A1BDADE0A62 · TORINO, IT-TO, IT · one of 3,433,629 GLEIF LEI records on the directory
815600139A1BDADE0A62Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
P418RA00040704428430013Verbatim 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.
815600FE947DA0D03B37 · ACTIVE · from 2022-06-07815600DEE22D520C8779 · ACTIVE · from 2018-01-158156000642102FB0C728 · ACTIVE · from 2022-06-1581560015E1A862390A04 · ACTIVE · from 2003-06-198156003FA6CAA3BFD436 · ACTIVE · from 2023-03-238156006E2B2447E23767 · ACTIVE · from 2024-12-12815600747E952853E746 · ACTIVE · from 1983-10-2981560076C42F219B4277 · ACTIVE · from 2023-11-308156007819BCF1C20426 · ACTIVE · from 2019-12-188156008B64AA7DF48F97 · ACTIVE · from 2003-02-188156009BB96AE7BF7D75 · ACTIVE · from 1991-01-14815600C1F95515D8E991 · ACTIVE · from 2014-01-30Verbatim 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-22.
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/815600139A1BDADE0A62web+usd://org-gleif-815600139a1bdade0a62 — 1-of-1 edition · universal linkweb+usd://org-gleif-815600139a1bdade0a62 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/815600139A1BDADE0A62 — 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.