LEI 2138008RH4TVDKIING31 · BIRMINGHAM, GB-BIR, GB · one of 3,428,529 GLEIF LEI records on the directory
2138008RH4TVDKIING31Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
VV0WRA000585IC205427Verbatim 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.
NO_KNOWN_PERSONNO_KNOWN_PERSON213800C8W49H2BS46702 · ACTIVE · from 2024-02-0621380079MCAHGT9VIL26 · ACTIVE · from 2024-02-062138007X6M3SQX1V1U26 · ACTIVE · from 2025-04-142138008NQENYWBH4ZJ27 · ACTIVE · from 2025-04-142138008TL3FBUWAMRK59 · ACTIVE · from 2024-08-15213800BAYMJMC6SGIN93 · ACTIVE · from 2025-04-28213800EZCWXTGSBM5R33 · ACTIVE · from 2025-04-14213800K4LJ41ZQH4Z575 · ACTIVE · from 2025-04-28213800KT6QCWKFYTJE35 · ACTIVE · from 2024-02-06213800M2LSSUEPH4EK87 · ACTIVE · from 2026-09-17213800UQ1P5YTQGGTZ02 · ACTIVE · from 2025-04-26Verbatim 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.
#://CNXTTHePeoPLe/ORG/GLEIF/2138008RH4TVDKIING31web+usd://org-gleif-2138008rh4tvdkiing31 — 1-of-1 edition · universal linkweb+usd://org-gleif-2138008rh4tvdkiing31 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/2138008RH4TVDKIING31 — 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.