LEI 549300GEP62IUCL05M64 · TORONTO, CA-ON, CA · one of 3,428,529 GLEIF LEI records on the directory
549300GEP62IUCL05M64Verbatim projection — every field above is exactly what the registry publishes. GLEIF LEI Golden Copy · CC0 · gleif.org
O90RRA000072855494-3Verbatim 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.
NON_CONSOLIDATINGNON_CONSOLIDATING5493006MLXETMOV59P26 · ACTIVE · from 2017-06-2854930075H34ALZ5KTY81 · ACTIVE · from 2017-06-28549300C976SLIZ44I578 · ACTIVE · from 2017-06-28549300DX42KXU7W2OP74 · ACTIVE · from 2017-07-21549300FLDQ1H1ACPZZ32 · ACTIVE · from 2018-04-09549300FNG3GXV0KCWO59 · ACTIVE · from 2018-04-09549300FQCDUOVPZSCZ15 · ACTIVE · from 2017-06-28549300HXJ5SCIP1KT508 · ACTIVE · from 2017-07-21549300I23D6OJU4GU489 · ACTIVE · from 2017-07-21549300ISGCIQFZT7BH79 · ACTIVE · from 2017-06-272138006OW6K94IBW4A67 · ACTIVE · from 2025-03-1954930001BZUFRBLXPW96 · ACTIVE · from 2000-06-055493000AYE65DOIWI658 · ACTIVE · from 2023-03-285493000AYFZKR6IREP05 · ACTIVE · from 2023-03-285493000AYGAG68K75870 · ACTIVE · from 2023-03-285493000AYGW1HB5OFG29 · ACTIVE · from 2023-03-285493000AYH8Z7Z9XQD32 · ACTIVE · from 2023-03-285493000AYJCEK1EN4D18 · ACTIVE · from 2023-03-285493000BGAIBP7C24I90 · ACTIVE · from 2015-05-295493000C5GB8N6H4TQ90 · ACTIVE · from 1990-07-05Verbatim 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.
RGAMCAT1XXX · 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/549300GEP62IUCL05M64web+usd://org-gleif-549300gep62iucl05m64 — 1-of-1 edition · universal linkweb+usd://org-gleif-549300gep62iucl05m64 reserved — activates when the edition is minted; no holder or balance until thenGET /api/orgs/gleif/549300GEP62IUCL05M64 — 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.