LEI JBONEPAGQXF4QP29B387 · 東京都 千代田区, JP · one of 3,472,754 GLEIF LEI records on the directory
JBONEPAGQXF4QP29B387Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
T417RA0004120100-01-008770Verbatim from the GLEIF LEI Golden Copy record for this LEI (fetched 2026-10-25). 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.
353800V2V8PUY9TK3E06 · ACTIVE · from 2018-04-01353800V2V8PUY9TK3E06 · ACTIVE · from 2018-04-012138002PVBMEHILJ1340 · ACTIVE · from 2022-01-21353800DQZQCDGGA8Y993 · ACTIVE · from 2020-04-01353800FAPFF0X0CM0L48 · ACTIVE · from 2017-04-015493009GCYS5Q8HOI372 · ACTIVE · from 2025-04-01549300RNOMHTVUH4ZS51 · ACTIVE · from 2022-06-069845006E08B8E7099D42 · ACTIVE · from 1998-07-0321380055V4FDCASCZH62 · ACTIVE · from 2026-04-142138006II4EGYDBVEE63 · ACTIVE · from 2025-08-182138007ZYYXRQIPQOJ72 · ACTIVE · from 2025-12-17213800DG3LVOEXZJW413 · ACTIVE · from 2025-07-09213800XAQBEK9DXK2624 · ACTIVE · from 2023-07-05213800Z62TAUEH1U7N95 · ACTIVE · from 2025-12-09549300TEPTHBQZF0OO29 · ACTIVE · from 2017-08-093538002I13FXDIIGZY15 · ACTIVE · from 2023-10-103538006UDWAKYXLM2Q34 · ACTIVE · from 2024-03-0135380089UDJDNYSQYG31 · ACTIVE · from 2023-04-143538009HRWRX6FH4UY39 · ACTIVE · from 2024-01-22353800B3WKHMNOX9I656 · ACTIVE · from 2024-01-22353800BCEAYXLHIR4J91 · ACTIVE · from 2020-10-20353800EXPWVK5PGM1X14 · ACTIVE · from 2024-04-02353800HJXPEVTA9YOX10 · ACTIVE · from 2023-10-10353800IL95X7ITHCSJ19 · ACTIVE · from 2023-09-06353800J8630PJEEG7K66 · ACTIVE · from 2023-08-07Verbatim 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-25.
MTBCGB2LLEN · GBMTBCGB2LLER · GBMTBCGB2LXXX · GBMTBCHKHHXXX · HKMTBCJPJTXXX · JPMTBCSGSGXXX · SGMTBCUS33XXX · 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.
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/JBONEPAGQXF4QP29B387web+usd://org-gleif-jbonepagqxf4qp29b387 — 1-of-1 edition · universal linkweb+usd://org-gleif-jbonepagqxf4qp29b387 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/JBONEPAGQXF4QP29B387 — 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.