LEI 5493006GGLR4BTEL8O61 · 東京都 千代田区, JP · one of 3,397,343 GLEIF LEI records on the directory
5493006GGLR4BTEL8O61Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
T417RA0004120100-01-146005Verbatim 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.
353800P843RLCDBLNT17 · ACTIVE · from 2018-04-01353800P843RLCDBLNT17 · ACTIVE · from 2018-04-01353800IP0P0T93PR4658 · ACTIVE · from 2025-06-30549300QEXRT6QOS1RA18 · ACTIVE · from 1978-10-09YVE6V0WZG64JLXC7QM27 · ACTIVE · from 2018-02-13300300C1133931000043 · ACTIVE · from 2005-04-203538000WJLJL6IUWVH31 · ACTIVE · from 2025-03-2535380020YJWEFSYLDP91 · ACTIVE · from 2023-02-243538002L5X0E362KX163 · ACTIVE · from 2023-01-2435380033UJVD7XB0T341 · ACTIVE · from 2024-05-23353800390RPGH444RB74 · ACTIVE · from 2020-12-143538004BDSOHS4690789 · ACTIVE · from 2024-03-073538005285INFIXFOV49 · ACTIVE · from 2024-02-163538005MDN1C05MB3F89 · ACTIVE · from 2025-05-233538005U5HB349EXK511 · ACTIVE · from 2024-03-223538006LEYXSSG2KB186 · ACTIVE · from 2024-02-16Verbatim 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-19.
STBCGB2LXXX · GBSTBCHKHHXXX · HKSTBCJPJTXXX · JPSTBCSGSGXXX · SGSTBCUS33XXX · USCross-registry identity (LiNx) for this LEI and BIC
Verbatim rows from GLEIF's certified BIC-to-LEI mapping file (bic-registry dataset) — a certified correspondence between this LEI and SWIFT BIC codes, not an inference.
550 ISINs loaded for this LEI so far in GLEIF's ISIN-to-LEI file — showing the first 24.
US86563K5A72 · US · 1-of-1 editionUS86563K5D12 · US · 1-of-1 editionUS86563VAM19 · US · 1-of-1 editionUS86563VAN91 · US · 1-of-1 editionUS86563VBA61 · US · 1-of-1 editionUS86563VBE83 · US · 1-of-1 editionUS86563VBH15 · US · 1-of-1 editionUS86563VBM00 · US · 1-of-1 editionUS86563VBP31 · US · 1-of-1 editionUS86563VBQ14 · US · 1-of-1 editionUS86563VBR96 · US · 1-of-1 editionUS86563VBT52 · US · 1-of-1 editionUS86563VBU26 · US · 1-of-1 editionUS86563VBV09 · US · 1-of-1 editionUS86563VBW81 · US · 1-of-1 editionUS86563VBX64 · US · 1-of-1 editionUS86563VBZ13 · US · 1-of-1 editionUS86563VCA52 · US · 1-of-1 editionUS86563VCB36 · US · 1-of-1 editionUS86563VCC19 · US · 1-of-1 editionUS86563VCF40 · US · 1-of-1 editionUS86563VCG23 · US · 1-of-1 editionUS86563VCH06 · US · 1-of-1 editionUS86563VCJ61 · US · 1-of-1 editionAll 550 ISINs from this issuer
Waiting for the first complete refresh of GLEIF's ISIN-to-LEI file. Until one finishes, links for this LEI may not be loaded yet, so an empty list is not a negative. Each ISIN doubles as a CNXT 1-of-1 edition address on the network.
Indicative correspondences from the CNXT registry-linkage layer (SEC EDGAR / BIC / FedNow families) — asserted only where the registries' own published identifiers agree; certified BIC↔LEI rows appear in their own panel above.
#://CNXTTHePeoPLe/ORG/GLEIF/5493006GGLR4BTEL8O61web+usd://org-gleif-5493006gglr4btel8o61 — 1-of-1 edition · universal linkweb+usd://org-gleif-5493006gglr4btel8o61 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/5493006GGLR4BTEL8O61 — 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.