LEI 5493002BABWBYV2A7Q82 · Toronto, CA-ON, CA · one of 3,428,529 GLEIF LEI records on the directory
5493002BABWBYV2A7Q82Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
8888RA00007200010120Verbatim 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. The registration authority name is GLEIF's own list entry for the record's code.
NON_CONSOLIDATINGNON_CONSOLIDATING213800LBGGLJPIBQ4P08 · ACTIVE · from 2016-10-173358007NLRUNZXQ5XN06 · ACTIVE · from 2006-02-19549300087S13LU11Z373 · ACTIVE · from 2021-04-22549300Y1FXTO6EZYWR82 · ACTIVE · from 2017-10-13549300ZPZ17K5JZRSK73 · ACTIVE · from 2022-01-01894500R4SVUPV6XAIG26 · ACTIVE · from 2026-07-23549300MP5VAUMKUWMF31 · ACTIVE · from 2023-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-19.
SLOCCATTXXX · CACross-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.
#://CNXTTHePeoPLe/ORG/GLEIF/5493002BABWBYV2A7Q82web+usd://org-gleif-5493002babwbyv2a7q82 — 1-of-1 edition · universal linkweb+usd://org-gleif-5493002babwbyv2a7q82 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/5493002BABWBYV2A7Q82 — 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.