LEI 353800X7JTY3BHOXB714 · 東京都 千代田区, JP · one of 3,433,629 GLEIF LEI records on the directory
353800X7JTY3BHOXB714Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
T417RA0004120100-01-098893Verbatim 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.
549300O25PYTRUFEI882 · ACTIVE · from 2023-01-015PRBRS5FEH7NREC8OR45 · ACTIVE · from 2023-01-01213800YMYKE14VO44Q72 · ACTIVE · from 2025-02-12549300Z1OC8JF168JI28 · ACTIVE · from 2018-08-28Verbatim 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.
PIMJJPJ1XXX · JPCross-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.
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.
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.
No changes seen since tracking began on 2026-10-21. Each record keeps its newest 50 changes for 13 months.
#://CNXTTHePeoPLe/ORG/GLEIF/353800X7JTY3BHOXB714web+usd://org-gleif-353800x7jty3bhoxb714 — 1-of-1 edition · universal linkweb+usd://org-gleif-353800x7jty3bhoxb714 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/353800X7JTY3BHOXB714 — 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.