LEI 3CCUJEU88P85MIG5R153 · Montreal, CA-QC, CA · one of 3,400,368 GLEIF LEI records on the directory
3CCUJEU88P85MIG5R153Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
6TRARA999999Verbatim from the GLEIF LEI Golden Copy record for this LEI (fetched 2026-10-19). 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.
NON_CONSOLIDATINGNON_CONSOLIDATING254900AB4BJVMBBCNW42 · ACTIVE · from 2016-08-045493000N0UA5ARYE7012 · ACTIVE · from 2013-12-185493001JWDCM8LHPGT98 · ACTIVE · from 2015-08-175493004G2GG6J5219347 · ACTIVE · from 2015-08-27549300B456N0WEIC5249 · ACTIVE · from 2005-09-26549300G2BAP5Z1O6HF50 · ACTIVE · from 2017-09-07549300LEFZ55QPGQT147 · ACTIVE · from 2021-02-22Verbatim 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.
PSPBCAMMXXX · 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/3CCUJEU88P85MIG5R153web+usd://org-gleif-3ccujeu88p85mig5r153 — 1-of-1 edition · universal linkweb+usd://org-gleif-3ccujeu88p85mig5r153 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/3CCUJEU88P85MIG5R153 — 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.