LEI 259400RDL4HDQUMS0O69 · WARSZAWA, PL-14, PL · one of 3,433,373 GLEIF LEI records on the directory
259400RDL4HDQUMS0O69Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
RBHPRA0004851636Verbatim 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_CONSOLIDATING2594000FTEG0GNQL1X84 · ACTIVE · from 2019-04-042594007NR40EVNRTO503 · ACTIVE · from 2019-04-0425940085WOJG580XE547 · ACTIVE · from 2019-04-0425940087UC2SQIKEBI35 · ACTIVE · from 2021-01-05259400896YFTHXY0J095 · ACTIVE · from 2025-12-312594009GLNN8X9WD0U33 · ACTIVE · from 2019-04-042594009THCJUOWI1QK54 · ACTIVE · from 2019-04-04259400DR5E105EJ8A897 · ACTIVE · from 2019-04-04259400MOM0L0HHW3LC37 · ACTIVE · from 2019-04-04259400MZWPP0DEG34W73 · ACTIVE · from 2019-04-04259400Y6TTK8AIHONL08 · ACTIVE · from 2019-04-04Verbatim 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/259400RDL4HDQUMS0O69web+usd://org-gleif-259400rdl4hdqums0o69 — 1-of-1 edition · universal linkweb+usd://org-gleif-259400rdl4hdqums0o69 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/259400RDL4HDQUMS0O69 — 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.